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.
If job 2 is the only dependency for Job three and this application runs pretty routinely, then you could use a latesub statement on job three.
One condition that needs to be steady state is that job three needs to have a pretty steady execution time meaning it kicks off say at 2 pm routinely. If this is the case and job 2 is the only dependency then the latesub statement would be simple to implement indicating that if job three is late then there is an issue with job 2.
I am making a few assumptions here, but this seems to be the simplest way to me.
Dustin Neely DevOps Analyst/Certified Automation button pusher
W 423.535.5784 M 423.208.6255 E Dustin_Neely@bcbst.com www.bcbst.com
Batch Scheduling Wiki
Thank you for the help and feedback, I will try both methods. Job 2 does run at 6am everyday, and only runs for on average less than 1 minute so the latesub is a good solution as well.
Last question (at least for now), say I have a job on the Tech1 LPAR that is not a predecessor to any jobs on the Production LPAR. What method could I use to notify the NOC if the job runs into an issue on Tech1?
Not sure what notification systems are available to your NOC but assuming they have a Distribution list email you could setup and alert for the non monitored LPAR and have that alert send an email to that DL for the issues you define!