ESP JCL "IF" and "COND" STATEMENTS

Products

• ESP Workload Automation

Issue/Introduction

We hit a JCL flush on our IF and COND JCL statements.

Tested the following.

JOB1

//ESPCCCHK EXEC PGM=CYBES080,PARM=ESPGRPI             ====     RC=0
//STEPLIB  DD   DISP=SHR,DSN=your.ESP.loadlib.CD7YLOAD
//                 DD   DISP=SHR,DSN=your.loadlib
//SYSPRINT DD   SYSOUT=(,)
//SYSIN     DD   *
//STEP10   EXEC PGM=IDCAMS                                                   ====     RC=12                               
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
// IF STEP10.RC EQ 12 THEN                                                        ====     FLUSH
//STEP20   EXEC PGM=IDCAMS,COND=(0000,EQ)
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
// ENDIF

JOB2
 
//ESPCCCHK EXEC PGM=CYBES080,PARM=ESPGRPI            ==== RC=0
//STEPLIB  DD   DISP=SHR,DSN=your.ESP.loadlib.CD7YLOAD
//                 DD   DISP=SHR,DSN=your.loadlib
//SYSPRINT DD   SYSOUT=(,)
//SYSIN     DD   *
//STEP10   EXEC PGM=IDCAMS                                                 ==== RC=12
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
// IF STEP10.RC EQ 12 THEN
//STEP20   EXEC PGM=IDCAMS                                                 ==== RC=12  (COND=) statement removed
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
// ENDIF

Environment

This is standard MVS JCL but impacted a job where ESP places a CCCHK step into STEP1 which always give RC=0.

Cause

Using JCL COND statements and IF statements together is RISKY at best.

Resolution

JCL IF and COND statement conflict.
ESP not involved.  JCL is working as designed. 

Additional Information

For samples and details please refer attached document Condition Code Tests.