What is description of OVERDUE fields in History Report

Products

• ESP Workload Automation

Issue/Introduction

What are the different OVERDUE description fields in the ESP History Report?

 

Resolution

ESP OVERDUE Description in History Report:

• OVERDUE START SINCE: OVDBEGAT (table field name is JHR_OVDSTRT). This is the Overdue Start Time and represents the time and date at which the job last became overdue for start (i.e., the DUEOUT INPUT time set in the job definition).
• OVERDUE END FOR: OVDEND (derived from field name JHRENDT (end time) and JHRLETIM (late end time). This field specifies the elapsed time that the job was overdue when it finished executing. In other words, it's the difference between the job's actual end time and the DUEOUT EXEC time set in the job definition.
• OVERDUE CMPL FOR: OVDCOMP (derived from field name JHRCOMPT (completion time) and JHRLCTIM (late completion time). This field specifies the elapsed time that a job was overdue when it was completed. In other words, it's the difference between the job's actual completion time and the DUEOUT OUTPUT time set in the job definition.
• OVERDUE END SINCE: OVDENDAT (table field name JHR_OVDEND_AT). This is the Overdue End time and represents the time and date that the job last became overdue to finish executing (i.e., the DUEOUT EXEC time set in the job definition).
• OVERDUE STRT FOR: OVDSTART (derived from field name JHREXECT (exec start time) and JHRLSTIM (late start time)). This field specifies the elapsed time that the job was overdue to start executing. In other words, it's the difference between the job's actual start time and the DUEOUT INPUT time set in the job definition.
• OVERDUE SUBMIT SINCE: OVDSUBAT (table field name JHR_OVDSUB_AT). This is the Overdue Submit time and represents the time and date at which the job last became overdue for submission (i.e., the LATESUB time set in the job definition).