We did something similar for end-of-year processing. A few of the IT staff had e-mail capable Nextel phones. Instead of sending a message upon error, we chose to send a status message upon completion. Rather than key staff needing to be in attendance for end-of-year processing, the staff with phones kept his/her phone active until receiving the last completion message. Having a timeline of events, we would expect the page at certain intervals, and if we did not receive then we would dial-in to review any possible problems. We had several jobs that were submitted from within a single CL progam, so we add another Submit to send the completion message. Only thing to remember is that hopefully the job queues utilized are single thread and to submit to the same job queue. If this job is a single CL then in order to implement, you would need to add SNDDST TYPE(*MSG) at key points within the program. If this job runs multiple (call/submit) you could execute a SNDDST between each CL program. Good luck.

Reply With Quote