I understand why it would be necessary to have an effective COND=EVEN on each step in an IF ABEND controlled sequence, but why on IF NOT ABEND? In your IF ABEND...ELSE...ENDIF construct, the ELSE if treated as IF NOT ABEND, forcing the COND=EVEN behaviour.
Just for fun (and contrary to a previously posted doc excerpt), note that the following 'works' under z/OS 1.10 (I don't have 1.11 installed, yet). //TESTJOB JOB (0200),'BSquare',CLASS=X,MSGCLASS=X,NOTIFY=&SYSUID //* // IF FALSE THEN // EXEC PGM=KLUGE,COND=ONLY // ENDIF //* // IF (U0100 = U0140) THEN //YES1 EXEC PGM=IEFBR14 //NO1 EXEC PGM=IEFBR14 // ELSE //YES2 EXEC PGM=IEFBR14 // ENDIF By works, I mean: The unnamed step is _not_ executed (COND=ONLY on 1st step, no ABEND) YES1 and NO1 are _not_ executed (U0100 <> U0140) YES2 _is_ executed (U0100 <> U0140) If you comment out the IF FALSE...ENDIF lines: YES1 _is_ executed (1st step, 'IF (U0100 = U0140)' not evaluated yet) NO1 is _not_ executed (_now_ 'IF (U0100 = U0140)' has been evaluated) YES2 _is_ executed (U0100 <> U0140) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
