On Fri, 4 Jan 2008 02:17:36 -0500, J R wrote:
>You appear to be using a setup step(s) prior to invoking an application
>in a subsequent JCL step. Why not have the setup step invoke the
>application directly, thus avoiding the 100-character PARM limit of JCL?
>
Likely because the PARM to that setup step itself would exceed the
100-character limit.
>> Date: Fri, 4 Jan 2008 07:55:12 +0100
>> From: Fred
>>
>> What we really need of course is variabel substitution in inline data by
>> the system:
>>
>> // EXEC PGM=XXX
>> //SYSIN DD *
>> PRINT &DATASET(&MEMBER)
>> /*
>> //
>>
Indeed. But for compatibility, it needs to be made optional:
//SYSIN DD *,SYMBOLS={NO|YES}
... defaulting to the current behavior.
>> where JES2, JES3, MVS or whatever treats those &VARs just like JCL
>> parameters and substitutes the current values. Then I wouldn't have to
>> figure out how I can retrieve JCL procedure paramater values. I'm sure
>> every shop would highly appreciate such a feature. This is probably not
>> the right place to lobby for this feature....
>>
That hasn't stopped many people. Nor will it stop the experts from
rebutting with a familiarity with internals that they will claim
makes such a feature impossible. SMOP, and worth the price.
BTW, there would be additional value to permitting instream data sets
in library procedures, often providing an alternative to large libraries
of parameter files.
-- 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
