IBM Mainframe Forum

by **Akatsukami** » Thu May 24, 2012 12:20 am

Well, that definitely won't work. It is entirely possible, as Mr. Spock suggests, that the sysprogs at your site have disabled the use of JOBRC to prevent it from leaking into the production environment. However, the JOBRC parameter shoiuld be coded as

Select all

JOBRC=(STEP,STEP60.STEP30)

for it to stand any chance of working.

by **MrSpock** » Thu May 24, 2012 4:37 am

JCL:

Select all

// JOBRC=(STEP,STEP060.STEP030)
//*
// JCLLIB ORDER=...
//*
//STEP060 EXEC PROCTST
//*

PROC:

Select all

//PROCTST PROC
//*
//STEP010 EXEC PGM=IEFBR14
//STEP020 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
// IF (STEP010.RC = 0 | STEP020.RC = 0) THEN
//STEP030 EXEC PGM=IEFBR14
// ENDIF
//*

worked, even though STEP020 had a return-code of 12, the job ended with MAXCC=0000.

by **ibmmf4u** » Thu May 24, 2012 6:50 am

Thanks Spock and Akatsukami.It helps a lot.

IBM Mainframe Forum

usage of JOBRC parameter

Re: usage of JOBRC parameter

Re: usage of JOBRC parameter

Re: usage of JOBRC parameter