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?
> Date: Fri, 4 Jan 2008 07:55:12 +0100
> From: [EMAIL PROTECTED]
> Subject: Re: JCL parms
> To: [email protected]
>
> That is more or less the solution we are using now: to circumvent the
> limitations of PARM= we pipe the template through several steps of the
> utility. Every step replaces as much of the variables in the template as
> the PARM will allow. I consider this rather clumsy and was looking for a
> more elegant solution that could be implemented in a single step.
>
> What we really need of course is variabel substitution in inline data by
> the system:
>
> // EXEC PGM=XXX
> //SYSIN DD *
> PRINT &DATASET(&MEMBER)
> /*
> //
>
> 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....
>
> Fred!
_________________________________________________________________
Don't get caught with egg on your face. Play Chicktionary!
http://club.live.com/chicktionary.aspx?icid=chick_wlhmtextlink1_dec
----------------------------------------------------------------------
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
