On Thu, 2 Dec 2021 21:16:30 -0600, Dale R. Smith wrote:
> ...
>To me. the biggest problem with not having a way to ignore a unused PROC
>parameter is what do you do when you have a PROC parameter that is obsolete?
>If you remove it from the PROC, then Jobs that specify that parameter will get
>the IEFC657I error message. Changing JCL to remove the PROC parameter is
>often difficult in a real Production environment. Depending on the parameter
>you might be able to add a dummy statement to the PROC like:
>//DUMMYDD DD DUMMY,DSN=SYS1.PROCLIB(&OBPARM.),DISP=SHR
>The parameter is now referenced in the PROC and hopefully the values specified
>in JCL will equate to a valid member name, (the member does not have to exist,
>it just needs to be valid). Obviously this option will not work for all
>parameters.
>
I suppose you can always tolerate ENQ SHR on SYS1.PROCLIB.
For values that might not be valid member names, I'd prefer:
//STEP99 EXEC PGM=IEFBR14,COND=(0,LE),PARM='&OBSPARM'
o Put this last so "COND=(0,LE)" has the desired effect.
o Still, the Devil can supply a value for OBSPARM that causes syntax errors,
such as an unbalanced apostrophe.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
