Folks: I have done support for automated JCL management tools for the past 30+ years and it is amazing the number of "features" in JCL that are not documented in the IBM JCL reference manual. It was difficult dealing with clients who would tell us they had coded something in their JCL, yet there was no mention of it being a capability. .....made it difficult sometimes to keep up!
Mitch McCluhan, Legacy Modernization Consultant -----Original Message----- From: Paul Gilmartin <[email protected]> To: IBM-MAIN <[email protected]> Sent: Fri, Nov 8, 2013 9:29 am Subject: Re: JCL On 2013-11-08, at 09:54, Frank Swarbrick wrote: > Hmmm! You're right. It's not the symbolic that is not allowed. It's the omparison to non-numeric values that is not allowed. Interesting! ... s this documented as supported, or is one comparand required o be a return code? Is it documented that comparing return odes of two previous steps is supported? > Wish I would have realized this a few years ago! nd the only use of the boolean primaries, TRUE and FALSE ocumented as supported is as operands of relational operators. o, my predecessor settled on: //STEP0 EXEC PGM=IEFBR14 ... /IF ( STEP0.RUN EQ FALSE ) THEN ... o unconditionally bypass a job step. I followed his lead. his appears to employ only documented supported constructs. ut who can tell? The JCL Ref states that transgressions may ot be reported. (And STEP0 circumvents the misbehavior of IF before the irst job step.) -- gil ---------------------------------------------------------------------- or IBM-MAIN subscribe / signoff / archive access instructions, end email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
