Does using an OVERDUE statement and a NOTIFY statement on Job 3 provide what you need?
DUEOUT EXEC <TIME>
NOTIFY OVERDUE USER(<USER>)
NOTIFY OVERDUE ALERT(<ALERT>)
If you use the second NOTIFY statement you will also need to create the ALERT.
https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-workload-automation-esp-edition/12-0/reference/statements/notify-statement-notify-users-or-consoles.html
------------------------------
Senior Systems Analyst
UPS
United States
------------------------------
Original Message:
Sent: 05-04-2021 08:11 AM
From: Elliott Fitzgerald
Subject: Job running late or other notifications across lpars
Good morning all,
I currently have an application that consists of 3 jobs. The first is located on our production LPAR after that completes and using the external scheduler it releases job#2 on the Tech1 LPAR. After that job finishes it releases the 3rd and final job on the Production side.
What I am trying to find out is if there is a practical way that if the 2nd job was running late on the Tech1 side, or its overdue if there is a way to notify the NOC team who only monitors the Production side of things?