AnsweredAssumed Answered

Cyclic ESP job has the last started time

Question asked by gunasekaran.loganathan on May 12, 2017
Latest reply on May 15, 2017 by powdo03

When a cyclic job is resubmitted it has the last submitted time as the start time of the job, addition to this when an MAXRUNTIME is added to the job definition(In our case 15 min). The job turns out to an overdue status even before it starts executing. 

 

Just curious why the last started time is always tagged to a resub job and how to set up a process to accurately identify if the cyclic job is actually running long.  

 

Job=JOBNAME1(12648454), Wob=AX, Wait
Rerun of: J9502848 CC 0, 12713986 CC 0, 11731086 CC 0, 12386492 CC 0,
11862118 CC 0, J8781824 CC 0, J9961492 CC 0, J7930000 CC 0,
15204400 CC 0, J7012432 CC 0, 11862212 CC 0, 15466498 CC 0,
13041822 CC 0, J6881352 CC 0, 14155956 CC 0, 14024938 CC 0,
13041766 CC 0, 11206880 CC 0, 11206674 CC 0, J9961500 CC 0,
11993242 CC 0, J8716288 CC 0, 12058744 CC 0, 13828248 CC 0,
J9764908 CC 0, 11272248 CC 0, 15204454 CC 0, 14155862 CC 0,
15794410 CC 0, 11206864 CC 0, 12845160 CC 0, J7274516 CC 0,
J8519924 CC 0, 15532090 CC 0, J7405796 CC 0, 11993194 CC 0,
J7209156 CC 0, 13041882 CC 0
Resub parms: RESUB_USER(UNIX)
Delay submit ............. 2017/05/12 15:36
Started .................. 2017/05/12 15:18
Due out .................. 2017/05/12 15:33
End Overdue .............. 2017/05/12 15:33
Expected completion ...... 2017/05/12 15:36
.... this job is predicted to be late .....
MaximumRunTime=15, AverageRunTime=1

 

CSF:

JOBNAME1      SPECIAL 4126 WAITING UNTIL 15.36 12 MAY OVERDUE SERVER1 

 

LTJ:

JOB JOBNAME1, MODEL MODEL1, OWNER OBRICUS, 30 JOBS INDEXED, 30 MAX
12648454 ON RDR AT 15.18.23 FRI 12MAY2017, COMPLETED, CC 0, 2.8 MINS_EXEC, 0:0
J9502848 ON RDR AT 15.00.30 FRI 12MAY2017, COMPLETED, CC 0, 2.8 MINS_EXEC, 0:0
12713986 ON RDR AT 14.42.15 FRI 12MAY2017, COMPLETED, CC 0, 3.0 MINS_EXEC, 0:0

 

Please let me know your thoughts. 

Outcomes