RE: MONMSG CPF2103 but still "unmonitored", causing halt -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

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

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.