Hi Sharon,
I am hoping others weigh in on this..... This solution is not ideal.
The basics:
Every job at the end of every stream and critical jobs in the stream need to have a late time. This includes standalone jobs.
When the job goes late it triggers the NOTIFY OVERDUE ( LATE ) at the top of the appl and notifies the responsible application team. Depending on the LATECRIT for the job it creates a ticket, pages out, or just sends an E-Mail. CRIT and LATECRIT were something I set up for each job and part of the doc for the job.
Tracking what went late::
The LATE application contains a IEBGENER job that appends the information about the late job (JOB QUAL APPL GEN current time......) to a GDG. This creates a basic list of what went late and when. This can be sent to the application teams to see if the late time needs to be moved or whether they need to address the issue. Monthly a new +1 of the GDG is created. This process is fairly easy to add.
Addionally
It is is possible to run a ESP report job for the jobs in the late list to see when they actually completed.
The two outputs can be combined using REXX. This is more involved.
.
Don
2¢