Actually, any RC>=9 will skip the step. I always have to rethink the COND= to mean SKIP=. That is, if the condition holds true, then SKIP the step. My brain implicitly tries to think the opposite, that the step should execute only if the condition is true. It's really a conditional SKIP expression. Weird.
/J > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of J R > Sent: Tuesday, August 07, 2007 1:23 PM > To: [email protected] > Subject: Re: COND= running a step that it should not. WHY? BFOM! Options > > The step should be executed unless any prior step has RC>9. > > > Neal Eckhardt said: > >OK, I'm usually pretty good at spotting these things, but this one has me > >baffled. > > > >z/OS 1.4 system and here is the JCL setup > > > > > >Job card with COND=(9,LT). > > > > > >An IF/THEN/ELSE/ENDIF construct with another IF/THEN/ELSE/ENDIF imbeded > in > >the first one. > > > > > >A PROC that has an override COND.STEPX=(4,LT,SORT0035) for a step within > >the PROC, and the above mentioned IF/THEN/ELSE/ENDIF is also contained > >within the PROC. > > > > > >Following the outer IF/ENDIF construct, outside of the PROC is a step > with > >COND=(9,LT). This step is executing. Looking at all of the Return Codes > for > >this execution, all steps finished with a RC=0 except for one step that > >ended with a RC=4. Several steps were FLUSHED due to the IF/ENDIF > testing. > > > > > >For the life of me, I cannot see why this step is running. > > > > > >Can anybody throw ANY ideas my way to explain this? > > > > > >Thanks, Neal ---------------------------------------------------------------------- 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
