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

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

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
>
> --- "Chevalier, Rick" <Rick.Chevalier@xxxxxxxxxxxxxxx> wrote:
> > Message CPF2102 is not monitorable from DSPPGMREF.  Prompt the command,
> > move the cursor to the heading and press F1.  Scroll down until you see
> > the monitorable error messages.
> >
> > The CPF3033 and CPF3034 messages are monitorable however.  That makes me
> > think what you are seeing is the expected behavior.  CPF2102 is caught
> > by the IBM program which then issues a message monitorable by your CL.
> >
> > HTH,
> >
> > Rick