global MONMSG to catch everything

[Dan <dantanabanana@xxxxxxxxx>]

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?
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
+---
| 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
+---