|
I guess it depends if you have the source for the job. I also have a program that monitors for jobs in msgw - it could be modified to get the job information & perhaps cancel the job. Let me know if you want me to mail it to you. -----Original Message----- From: James H H Lampert [mailto:jamesl@xxxxxxxxxxx] Sent: Thursday, April 22, 2004 11:29 AM To: midrange-l@xxxxxxxxxxxx Subject: Exceptions and *MSGW In one of our client-server products, we've had a chronic issue with server jobs going into a *MSGW state on exceptions that IN THEORY are being monitored for and handled. I just had a thought on the matter: is there a simple way to set a job to immediately terminate in such cases, instead of going into *MSGW? -- JHHL _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.
midrange.com
