× 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.


  • Subject: Re: monmsg in clp pgm questions
  • From: "David Morris" <dmorris@xxxxxxxxxxxxx>
  • Date: Wed, 29 Dec 1999 16:00:13 -0700

Kerwin,

I don't believe that you can monitor for those messages because 
they are sent as diagnostics.  You should be able to do something 
like:

RCVMSG MSGTYPE(*LAST/*DIAG) RMV(*NO) MSGID(&MSGID)
IF    (&MSGID *EQ 'CPF2869') THEN(GOTO TAG1)...

David Morris


>>> crawfork@toastmaster.com 12/29/99 03:21PM >>>
I have a clp program that has a command in it that I am doing a monmsg.  I want 
to do different things for each message.  I am having problems with it.  This 
is the code that I am using.  Am I doing this correctly?  It appears to only be 
looking at the cpf0000 part.
 
CPYF       FROMFILE(FROMLIB/FROMFILE) +                  
             TOFILE(TOLIB/TOFILE) FROMMBR(*FIRST) +    
             TOMBR(*FIRST) MBROPT(*REPLACE) CRTFILE(*NO) 
MONMSG     MSGID(CPF2869) EXEC(GOTO CMDLBL(TAG1))  
MONMSG     MSGID(CPF2861) EXEC(GOTO CMDLBL(TAG2)) 
MONMSG     MSGID(CPF0000) EXEC(GOTO CMDLBL(TAG3))

TIA

Kerwin S. Crawford
Toastmaster Inc.
System Analyst


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.