To avoid overriding the COND='s in PROC2, specify the following:
//STEP1 EXEC PROC1
//*
//COND4A EXEC PGM=IEFBR14,COND=(4,LE)
//COND4B EXEC PGM=IEFBR14,COND=(0,EQ,COND4A)
//*
//STEP2 EXEC PROC2,COND=(0,EQ,COND4B)
Regards,
Chris Poncelet
Software Engineer
CA
Dean Montevago wrote:
Hi,
I'm looking at the JCL manual and I'm not clear as to what's written
on this topic. If I have the following:
//STEP1 EXEC PROC1
//*
//STEP2 EXEC PROC2
Proc 2 contains multiple steps with COND='s on the EXEC steps. If I
add a COND=(0,NE) to the statement that calls PROC2 will this override
the COND='s on the individual steps in PROC2 ? Basically what I want
to do is flush the job if the first proc doesn't complete with a
condition code of zero.
TIA
Dean
Dean Montevago
Sr. Systems Specialist
Visiting Nurse Service of New York
(212) 609 - 5596
[EMAIL PROTECTED]
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
