Re: global MONMSG to catch everything

I think you are asking for trouble with that global monmsg.

Consider doing one of the following 

1) Use separate jobq's for batch jobs that are not sequence dependent

For example if Job C must follow jobs A & B then keep them in the same
jobq but if Jobs D,E & F can run whether or not A,B & C have run the
place them in a different jobq. If they are all seq dependent then you
could end up with a trashed database with the global monmsg.  A very
simple example is backup - our backup jobs run in their own jobq.  If
the operator loads the wrong tape or there is a an error on the tape
drive everything else can complete normally and we can take care of it
the next morning.  

2) Purchase some type of Monitoring/paging software.  This will set you
back about 2k (P10) but will give you much better results than just
doing a global monmsg.  You can set them up to page you if any jobs go
into a msgw status or if certain jobs do not complete by a specific
time.  I'm sure it would have e been easier for you to get a page in the
middle of the night and handle it at that time than to wait until
everyone was standing around waiting for you to fix the problem.

We use messenger plus from bytware.com  



> At 12:03 PM 10/1/99 -0700, you wrote:
> >I guess it had to happen. After 6 months, a nightly
> >batch job finally bombed, hanging because of a message
> >that wasn't monitored. As a result, the nightly batch
> >processing was delayed until 7 this morning and,
> >needless to say, there weren't too many happy people
> >when I walked in. TGIF!
> >
> >So... I need to absolutely, positively ensure that
> >this batch job will not hang due to a message not
> >being monitored. If I'm not monitoring for a specific
> >message that is sent to the program, this app should
> >be ended automatically & immediately.
> >
> >I seem to remember a global MONMSG to use for this.
> >Something like:
> > MONMSG MSG(CPF0000 MCH0000 ???0000)
> >(Can't remember the third one.)
> >
> >Is that foolproof? Or is there a better way?
> >__________________________________________________
+---
| 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
+---