ESP Workload Automation

I have an appl that has several jobs in it.  The first job has a Delaysub and a Latesub.  This works fine.  However, I'm having a difficult time trying to code something to indicate when the next jobs are late to send a notification.  Can anyone help me?  Thanks in advance for your help - it is  appreciated!

JOB JOB1                          
   DELAYSUB 19:00                            
   LATESUB 19:01 

   RELEASE ADD(JOB2)AD                                
   RUN DAILY                                 
   NOTIFY OVERDUE MAILBOX(ECM)               
ENDJOB       

JOB JOB2

   LATESUB --- need something to indicate if JOB2 has not started within 1 minute of the completion  of JOB1

   RELEASE ADD(JOB3) 

   RUN DAILY                                 
   NOTIFY OVERDUE MAILBOX(ECM)               
ENDJOB       

JOB JOB3

   LATESUB --- need something to indicate if JOB3 has not started within 1 minute of the completion  of JOB2

   RUN DAILY                                 
   NOTIFY OVERDUE MAILBOX(ECM)               
ENDJOB                 

Critical Path?

Hi, 

I think I am missing something.  From the statement. 

 "need something to indicate if JOB2 has not started within 1 minute of the completion  of JOB1" 

When would this case ever come up? I don't see RESOURCEs in here. The only case where I can see this happening is if ESP is not working correctly. Why would job 2 take more than 1 minute to be submitted after job1 ends? 

Like I say I am sure I am missing something. 

We do not use Critical Path.

While I agree this should not be something that happens, the system is a critical one and they are asking for notifications on all of the jobs they have - just like this. 

Just as an opinion, might I be better off trying to convince the Users that this is not really something to be concerned about, especially if the first job ran without issue?  I also have a failure notification on the jobs so if they fail, an email will be sent to the Users.

Thanks for your responses - they are helpful.

Does the DUEOUT provide what you need?

JOB JOB2

   DUEOUT EXEC NOW PLUS 1 MINUTE  

   RELEASE ADD(JOB3) 

   RUN DAILY                                 
   NOTIFY OVERDUE MAILBOX(ECM)               
ENDJOB      

Hi, 

Let's take this scenario that they want to monitor for. 

The jobA ends and ESP is not working correctly for some reason and jobB does not get submitted. 

Is ESP (that is not working correctly) going to be able to catch the condition notify someone? Unknown..... Any monitoring for this condition would need to be done by an outside source.  

For me. I used this strategy.
Every last job of a stream (and standalone jobs) get a DUEOUT EXEC
Every critical job in the path gets a DUEOUT EXEC.
In this case you could code DUEOUT INPUT in jobs as well.

But I did use hard coded times like 09.01

Just a note:

The NOW / REALNOW times are set when the event scheduled / builds. They will not work in the scenario here. 

2¢

The DUEOUT may work.  I tested it by putting JOB2 on hold and it came up as overdue.  I originally thought that the DUEOUT would not work because I thought it wouldn't recognize the job as being late until it completed.

Again, thanks for your help!

I just spoke with the User and as of right now, they are agreeable to just let a failure notify them that they job did not complete (except for JOB1 which has a DELAYSUB and a LATESUB).  That being said, I tried the DUEOUT and it looks like it will work - so if the User comes back and decides they still want the late notification on the other jobs, I'm ready to go with it.

Again, thanks so much for your help and input!