|
jamesl=81cl4rDYvJpBDgjK7y7TUQ@xxxxxxxxxxxxxxxx wrote: > As to why, well, I'm working on a program that scans through all > active jobs with a particular jobname, and needs to be able to > recognize which ones are in *MSGW state (which would indicate that > they're stuck in an error condition). *MsgW is not necessarily indicative of an error condition! An example is a job that processes Inactive Job messages, this job waits for a message to appear on the queue. While it's waiting, it is status *MSGW. Bill
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
