Restarting jobs

shubh · New User Joined: 01 Oct 2007 Posts: 16 Location: USA

Hi,

what does COND=(0,LT) means?
In every job i can see, it is used in every step.

//STEP0010 EXEC PGM=BTQMAIN,COND=(0,LT)
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSIN DD DSN=FDCK.PROD.TERADATA.APP.PARMLIB(FDCKBTHB),
// DISP=SHR
// DD DSN=FDCK.PROD.TERADATA.APP.PARMLIB(CKSDBASE),
// DISP=SHR
// DD DSN=FDCK.PROD.TERADATA.APP.PARMLIB(CKSV14WK),
// DISP=SHR
// DD DSN=FDCK.PROD.TERADATA.APP.PARMLIB(QUIT),
// DISP=SHR
//*

Also starting of every job #SCC,COND=(0,NE,*) is written.

If a job fails at any step can i just restart it from abended step or i have to restart it form one step before(because of the condition quotes.)?

Also if i restart it from abended step will the triggers work correctly?

Douglas Wilder · Posted: Wed Jan 09, 2008 3:01 am

A COND on the job card will over-ride all of the CONDs on the steps.
I prefer to use the IF ELSE END-IF structure to check COND because it is easier to read and understand. We are not allowed to put COND on the steps in this shop because they are hard to understand.

If the COND does not specifically use a step name you are restarting after, the COND will not affect where to restart the job.

There many other things to look at to determine what step to restart in such as dataset disp, GDGs, etc.

COND=(0,LT) on a step would mean that if zero is less than the condition code of any prior step than this step will not run. (If it is true you are through) In other words if any prior step ends with a condition code greater than zero you will not execute the step.

I hope this helps.

expat · Posted: Wed Jan 09, 2008 11:33 am