IBM Mainframe Forum

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.

Ya steve i got you, this is the thing which I won't be doing again and neither i'll promote this thing to any other user. Thanks for the advice

hi Billy,

I have made the JCL in such a way that the e-mail step is only run whenever a job abends. The rest of the time the job will complete normally. So the problem of e-mail flooding won't be there. I'll talk to our administrators regarding the scheduler thing, but that infinite thing is now a nightmare for me

Thanks

OK, glad it is over for you. Although you might want to be ready for some questions from puzzled people on Monday

Learn from it. Think things through better. Seek advice if trying something you've not tried before.

If anyone suggests this sort of solution to you, you've earned the right to tell them very directly how bad an idea it is. You kept your head and managed to stop it before Cold Start, so you've got something going for you

BillyBoyo wrote:... However, as schedulers cost money, and need to be supported, often there is not a scheduler available in testing environments.

There is a free one, Personal Job Scheduler

Hi,

You can try out with JES2 time processing command to schedule incase if you don't own any schedulers.

To report on abend then again you have to have some tool to monitor your spool area or you can write a rexx code to monitor and use SMTP to send email to the concerned developer or user or a group.