On Thu, 17 Sep 2009 15:43:04 -0600, Frank Swarbrick wrote:
>My god yes. VSE does this (allows symbolic JCL parms to be interrogated
>programatically).
>I was hesitant to bring it up, as people seem to think I just like to stir up
>trouble, but...
>:-)
>
>
>On 9/17/2009 at 2:13 PM, in message
><[email protected]>, Kirk Wolf wrote:
>> Not to drudge up old threads, but wouldn't it be nice if JCL PROC and SET
>> variables were not thrown away by the converter/interpreter and instead
>> placed in an ASASYMB-style symbol table by the initiator? This would be
>> useful in so many ways....
>>
Oh, drudge away! (Or, even "dredge" if you prefer.)
I wouldn't mind changing my JCL to enable this. A couple
possibilities:
o Support for symbol substitution in SYSIN data sets, so
one might code:
//STDPARM DD *,SYMBOLS=YES
FOO=&FOO
BAR=&BAR
...
(wouldn't you like to be able to substitute JCL symbols
in STDIN for COZBATCH?)
o Or support in JCL to pass these in the second, third, ...
arguments as in CALL (and without the 100-character limit):
//STEP EXEC PGM=MYPROG,PARM=(LIST,XREF),
// ALTPARM=('alternate DDNAME list','FOO=&FOO','BAR=&BAR',...)
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
