coria
New User
Joined: 09 Oct 2006 Posts: 36
|
|
|
|
thanks, dick.
As of now, we are scheduling 3 jobs, JOBA, JOBB and JOBC, we want to make JOBA & JOBB as the predecessor to JOBC. the schedule is done in CA-JOBTRAC 3.5.
below are the details of the schedule:
********************************************************************
JOBA ASAPS* Q JOBC WORKDAYS
JOBAA0950S*+1 ? WORKDAYS
********************************************************************
JOBB ASAPS* Q JOBC WORKDAYS
********************************************************************
this schedule is done through Q dependency, when JOBA completed, it will triger another job JOBAG which will remove the Q dependency of JOBA, then JOBC will be triggered by JOBA. (also i am not very clear about why this kind of approach is preferred, actually JOBA is to be triggered by a dataset which transferred(NDM) from another system) . the same as JOBB.
below is JOBAG job for your reference:
---------------------------------------------------------------------------
//JOBAG JOB (57-57),'JOBTRAC EOJ EQ',CLASS=Y,
// REGION=0M,MSGCLASS=P
//*
//* THIS WILL REMOVE THE Q DEPENDENCY FROM JOB JOBA TO TRIGGER JOBC AFTER AMR
//*
//JS001 EXEC PGM=GJTRABTR,REGION=3072K,
// PARM='STACK()'
//JOBTRACX DD DSN=SYSS.JOBTRAC.CHKPT,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
MOD(JOB(JOBA) L(081) DEP (-Q))
/*
------------------------------------------------------
that is the case now, logically the 3 jobs would be running fine, but actually no, some times JOBC can be triggerred successfullly, sometimes not. we are obsessed by it now....
more information if you guys need pls let me know. |
|