RE: MONMSG CPF2103 but still "unmonitored", causing halt

[G Armour <garmour400m@xxxxxxxxx>]

Vern and Rick,

Thanks for the reminder on RCVMSG!

How does one "walk backwards" through messages?  Do you have to have a
point of reference via MSGKEY to do it?  Does the fact that CPF2102 is
issued from another program going to affect how to get at it?

TIA, GA

--- Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> You can RCVMSG and get the MSGDTA, which will contain that MSGID
> somewhere. 
> You might need to go through a few messages to get one that has that 
> information. DSPMSGD to see the layout of substitution data. It may be
> that 
> the CPF2102 is in the message "stack".
> 
> Vern
> 
> At 11:38 AM 10/21/2003 -0700, you wrote:
> >Well, *how* would I detect this particular problem?  I have since
> replaced
> >the CPF2102 with a MONMSG CPF9999 after the others.  It appears that
> the
> >CPF9999 message tattles on the CPF2102.  Can I interrogate the CPF9999
> >message to make sure that it was caused by CPF2102?
> >
> >TIA, GA


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com