PTF RO26726 (for version 11.3) has introduced a new parm and OPER command - CCCHKSTP. It can be used to customize the inserted CCCHK step.
This command has the following format:
CCCHKSTP ('//ESPCCCHK EXEC procname,GROUP=') procname Specifies the name of a member containing a catalogued JCL procedure for the ESPCCCHK step. For example, CCCHKSTP ('//ESPCCCHK EXEC ESPCCCHK,GROUP=') A sample JCL procedure can be found in CYBESS40: //ESPCCCHK PROC GROUP= //*------------------------------------------------------------------ //* This is the ESPCCCHK step which is inserted into each job //* whose definition contains one or more CCCHK statement. //* The name of this step must be ESPCCCHK. //* Change the STEPLIB statement as required. //*------------------------------------------------------------------ //ESPCCCHK EXEC PGM=CYBES080,PARM='&GROUP' //STEPLIB DD DSN=<CAI>.SSCPLINK,DISP=SHR //SYSIN DD DDNAME=PARMS //SYSPRINT DD SYSOUT=(,)
Note: the &GROUP variable will be replaced with the value of ESPGROUP from the ESP that submits the job. This will require that the ESP master and proxies from both environments use same ESPGROUP value.
If this can't be done, then you can avoid use this &GROUP variable:
#1 Set up JCL Procedure on both environments with same proc name, but different contents. For example:
On environment #1, presume ESPGROUP is defined with value of 'prod':
//ESPCCCHK PROC
//ESPCCCHK EXEC PGM=CYBES080,PARM='prod'
//STEPLIB DD DSN=<ESP.LOADLIB.PROD,DISP=SHR
//SYSIN DD DDNAME=PARMS
//SYSPRINT DD SYSOUT=(,)
On environment #2, presume ESPGROUP is defined with value of 'nonprod':
//ESPCCCHK PROC
//ESPCCCHK EXEC PGM=CYBES080,PARM='nonprod'
//STEPLIB DD DSN=<ESP.LOADLIB.NONPROD,DISP=SHR
//SYSIN DD DDNAME=PARMS
//SYSPRINT DD SYSOUT=(,)
#2 In ESPPARM for ESP master and proxies of both non-prod and prod environments, add following:
CCCHKSTP ('//ESPCCCHK EXEC ESPCCCHK')
With above settings, when ESP master on non-prod environment submits the internodal job A, the step below is added before it's sent to JES:
//ESPCCCHK EXEC ESPCCCHK
But the JCL Proc ESPCCCHK won't be expanded until the job A is on the execution system on prod environment, so it will be expanded as below:
//ESPCCCHK PROC
//ESPCCCHK EXEC PGM=CYBES080,PARM='prod'
//STEPLIB DD DSN=<ESP.LOADLIB.PROD,DISP=SHR
//SYSIN DD DDNAME=PARMS
//SYSPRINT DD SYSOUT=(,)
And for normal jobs that run on non-prod systems, ESPCCCHK Proc will be expanded to following:
//ESPCCCHK PROC
//ESPCCCHK EXEC PGM=CYBES080,PARM='nonprod'
//STEPLIB DD DSN=<ESP.LOADLIB.NONPROD,DISP=SHR
//SYSIN DD DDNAME=PARMS
//SYSPRINT DD SYSOUT=(,)