>
> I agree that SET variables are very useful. But I think that
> they could
> be more useful if they were more like UNIX environment variables -
> accessible to running programs. Perhaps via the ASASYMBM
> interface. The
> 100 char limit on PARM, limits how much data you can pass to a program
As this problem drove me crazy today, I decided to developed some code. I
wrote a rexx exec that is an ISPF macro that replaces the buildin send
command, It does the following:
* save changes done until macro starts.
* Force undo on and nosave in the member's profile to keep the
var
--
A JCL SET statement value can also be passed and resolved as a PARM=
string, so it is possible to write a program in your favorite language
that takes the PARM= value and writes the data to a DD allocation in a
job-step. And if you must hav
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Barkow, Eileen
> Sent: Monday, June 30, 2008 9:22 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: JCL SET command and instream SYSIn
>
> I have a program that
>
very useful.
Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of McKown, John
Sent: Monday, June 30, 2008 9:56 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: JCL SET command and instream SYSIn
> -Original Message-
> From: IBM Mainframe Discussio
Jol allows this. You can set up a symbolic variable, or use one of the
pre-defined variables, and have it replaced on your card file.
For example, %DAY is set up by Jol
Then...
DCL X * REPLACE;
Today is %DAY
Month %MONTH
EOF;
Print x; /* Print the card file */
See www.ozemail.com.au/~osca
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin
> Sent: Monday, June 30, 2008 8:37 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: JCL SET command and instream SYSIn
[snip]
> Gee, that's ugly. And n
On Mon, 30 Jun 2008 07:53:35 -0500, Scott Barry wrote:
>A JCL SET statement value can also be passed and resolved as a PARM=
>string, so it is possible to write a program in your favorite language that
>takes
>the PARM= value and writes the data to a DD allocation in a job-step. And if
>you must
A JCL SET statement value can also be passed and resolved as a PARM=
string, so it is possible to write a program in your favorite language that
takes
the PARM= value and writes the data to a DD allocation in a job-step. And if
you must have multiple data lines substituted, for example as SYSI
On Mon, 30 Jun 2008 03:28:19 -0600, [EMAIL PROTECTED] wrote:
>I already tried that and it doesn't work: A jcl set variable orks only on real
>JCL not on instream SYSIN (DD *). Any workaround? Any alternative to modify
>JCL and SYSIN (for example, deleting/definning datasets with IDCAMS) at one
>I already tried that and it doesn't work: A jcl set variable orks only on real
>JCL not on instream SYSIN (DD *). Any workaround?
This has been discussed many times (see the archives).
The answer is NO.
And, this is documented in the JCL manual(s).
-
Too busy driving to stop for gas!
-
I already tried that and it doesn't work: A jcl set variable orks only on real
JCL not on instream SYSIN (DD *). Any workaround? Any alternative to modify JCL
and SYSIN (for example, deleting/definning datasets with IDCAMS) at one
parameter without having to use ISPF CHANGE ALL?
Thanks for your
12 matches
Mail list logo