usage of JOBRC parameter

JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc...

Re: usage of JOBRC parameter

Postby 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

for it to stand any chance of working.
"You have sat too long for any good you have been doing lately ... Depart, I say; and let us have done with you. In the name of God, go!" -- what I say to a junior programmer at least once a day
User avatar
Global moderator
Posts: 1058
Joined: Sat Oct 16, 2010 2:31 am
Location: Bloomington, IL
Has thanked: 6 times
Been thanked: 51 times

Re: usage of JOBRC parameter

Postby MrSpock » Thu May 24, 2012 4:37 am

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

//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.
User avatar
Global moderator
Posts: 809
Joined: Wed Jun 06, 2007 9:37 pm
Location: Raleigh NC USA
Has thanked: 0 time
Been thanked: 4 times

Re: usage of JOBRC parameter

Postby ibmmf4u » Thu May 24, 2012 6:50 am

Thanks Spock and Akatsukami.It helps a lot.
Posts: 65
Joined: Wed Dec 14, 2011 10:26 pm
Has thanked: 0 time
Been thanked: 1 time


Return to JCL


  • Related topics
    Last post