A job that was triggered by its triggering job entered the queue but started at step 080 when it was supposed to start at step 005. The previous executions were fine. The SYSOUT shows like CA-11 understood the job was suppose to start at step 080, as it was a restart. But the job didn’t abend since its last run.
Here goes some information I gathered:
U11-001 CA-11 - PARM RECEIVED FOR JOB K86NPAL1 - PARM='P'
U11-055 RESTART REQUESTED - START PROC/STEP= /JS080 END PROC/STEP=
U11-109 * PROC-STEP= STEP=JS005 POSTED WITH CC=0000
U11-109 * PROC-STEP= STEP=JS010 POSTED WITH CC=0000
U11-109 * PROC-STEP= STEP=JS020 POSTED WITH CC=0000
U11-109 * PROC-STEP= STEP=JS030 POSTED WITH CC=0000
U11-109 * PROC-STEP= STEP=JS040 POSTED WITH CC=0000
U11-109 * PROC-STEP= STEP=JS050 POSTED WITH CC=0000
U11-109 * PROC-STEP= STEP=JS060 POSTED WITH CC=0000
U11-109 * PROC-STEP= STEP=JS070 POSTED WITH CC=0000
LRLOG,JOB=K86NPAL1,DATE=*
DATE=* DATE=15.092 PAGE 0001
EVENT OBJECT ENTRY TRGR LATE
TYPE TIME TYPE NAME CA7# SCH SYSTEM STATUS MODE CA7# START END
C 15088/2001 J K86NPAL1 8252 030 SMOLOL1 COMP AUTO 8244 15088/2001 15088/2001
C 15089/2002 J K86NPAL1 9791 030 SMOLOL1 COMP AUTO 9787 15089/2001 15089/2002
C 15090/2002 J K86NPAL1 4594 030 SMOLOL1 COMP AUTO 4587 15090/2001 15090/2002
R 15091/2058 J K86NPAL1 9596 030 SMOLOL1 JCLER AUTO 9593 15091/2001 15091/2001
REASON=IM102636386
C 15091/2059 J K86NPAL1 9596 030 SMOLOL1 COMP AUTO 9593 15091/2058 15091/2059
SLIF-00 REQUEST COMPLETED AT 13:51:02 ON 15.092
I wonder how the job could be triggered and start from step 080 if it didn't abend at the previous execution.
Thanks,
MM