pushkal2gud wrote:Hi Billy, I am automating batch monitoring for my project. For this the job has to run in background all the time so that whenever a job is abended, it'll mail the concerned people. That is why I need to run it in infinite loop all the time. I hope this explains.
Hi NicC, everytime I am getting a different error message. I'll update the forum once I am done with my troubleshooting part. Thank
Missed this one. If you submit through the scheduler, you may be able to deal with it that way. However, as schedulers cost money, and need to be supported, often there is not a scheduler available in testing environments.
If you need to do this, I think a step at the end of each job which is only run when the job abends is going to be a better way to do it. You still might get floods of e-mails, I'm not sure what your "all the time" job would have done if it was already e-mailing.
This is a complex task to do in a fully-automatic way. So, do it an easy way, with the JCL.
I didn't even think that your job might only be running for a short time. Then you get the problem of the relative speed of "breakdown" to "initiation". Plus scrillions of jobs on the output queue.
Plus, it would be a huge waste to have something running all the time just to send some e-mails.
Glad you're out of it.
Let us know if you need more ideas, and if you can be specific about what you are trying to do.