Re: Quick-and-dirty *MSGW?

["Ted Barry" <tbarry@xxxxxxxxxxxxxxxxxxxx>]

I'm out of the office today and will return on Monday 11/03.  If this is an 
emergency, please contact Mark Greenawalt at x311, John Censoplano at x353, 
Spencer Chun at x354 or John Phillips at x330. 

Thanks,
  Ted

>>> "midrange-l@xxxxxxxxxxxx" 11/01/03 12:23 >>>


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


_______________________________________________
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.