IBM Mainframe Forum

For us we have around 300 jobs are running using ca-jobtrac scheduler. Is there any option to write jcl or rexx code to trigger an email when job abend occurs.

Is there not a feature of the scheduler itself that does this?

from the sales brochure I found at http://www.ca.com/~/media/Files/ProductBriefs/jobtrac-job-mgmt-ps.pdf

email/wireless support: CA Jobtrac JM can now send emails to a specified list of addresses
based on the normal or abnormal completion of a job. This feature allows multiple
addresses to be specified. You can use template emails to provide additional text to include
in your email. Standard email text is also included to provide the job name, business group,
version, and other job-related information.

Now, I'd bet there is some layer between you and the folks authorized to add names to this list. I had the same problem. What I did was to set up a small job that sends the email, then had my scheduler force that job out if the target job abended.

Now, there might be a layer between you and the folks authorized to add jobs to the schedule. I had the same problem. What I did was create a test schedule that repetitively ran a job that watched for abends in the target schedule and then would force out the small email job.

Now, you may not be able to create a test schedule. I had the same problem. What i did was create a Rumba (terminal emulator) script to watch for abends, then send an email if needed.

I'm not trying to be a smarta$$ here, I really did go through all of these phases in the last 15 years. At one point I had the rumba script doing nothing but pressing the enter key until is saw a "job ended" message. Then it would play a wav file to wake me up. I slept on the floor of the computer room while the jobs ran and would have to check the status of each job when the system woke me up. That was a long couple of months.

Ed Goodman wrote:Now, I'd bet there is some layer between you and the folks authorized to add names to this list. [...] Now, there might be a layer between you and the folks authorized to add jobs to the schedule. [...] Now, you may not be able to create a test schedule.

Do not these things suggest that heesh wasn't intended to be a lone wolf developer, but function as part of a team?

Indeed they do suggest that. I'm trying to forestall the inevitable "that's great but I can't change that" reply that usually comes next. However, they may be motivated enough to try a bunch of different work-arounds instead of holding out for the "proper" way.