|
I did this a few year back so I don't have the API name handy. You build a list of all jobs active on the system into a user space then compare it to a file you put the job names to watch for. Be sure to include the subsystem name in your file. You might also need to have some date and time values to test on as well. When we shut down some of our applications for nightly backups we didn't want to be bugged by messages that a watched job was inactive. Special consideration are also needed if your watching multiple jobs with the same name in the same subsystem. Then launch this watcher job to stay active in batch somewhere (I suggest you use JOBQ QSYSNOMAX) and have it wait on a dataQ on 15 minute cycles. Now when a exception is found send a message. If sent to QSYSOPR be sure it stands out or it will get lost with all the standard non important ones. As you can see it is not as simple as it first looks. Good luck. --- Douglas Hart Sr. Consulting Technical Analyst mailto:dah6696@goulds1.com From: John Cirocco [mailto:JCirocco@gw.ctg.com] >>>We are trying to write a CL that would monitor a set of jobs running in a subsystem to see if they >>>are all up, and if not to submit the appropriate missing job(s). >>> >>>I'm sure there must be an API or something that we could use to test if a job of a given name is >>>active - can someone give us some guidance? If you already have HelpSystems Robot Scheduler, you can have it launch all the jobs and notify you of abnormal (or normal) job completions. Just a thought, John +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.