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




On 22/12/2009, at 2:29 AM, rob@xxxxxxxxx wrote:

I do not like to see unnecessary escape messages in my joblog. If I
monitor for them then I like to remove them. This way, when I scan the
joblog for Escape, I only see the ones of import.

Excellent! So my continued bitching on this topic is paying off ...


So, instead of
ADDLIBLE ...
MONMSG CPF0000

I will do something like the following instead:
START: PGM
DCL &DATA *CHAR 30 /* Message data from RCVMSG */
DCL &KEYVAR *CHAR 4 /* Message key from RCVMSG */
DCL &MSGID *CHAR 7 /* Message id from RCVMSG */

ADDLIBLE TLACS
MONMSG CPF2103 EXEC(DO) /* Library is already in library list */
/* Remove message from cluttering joblog */
RCVMSG MSGTYPE(*NEXT) MSGKEY(*TOP) RMV(*YES) KEYVAR(&KEYVAR) +
MSGDTA(&DATA) MSGID(&MSGID)
EndDo

ENDPGM

This sort of RCVMSG has to be in a loop else you'll only get the first message of any type removed.

To remove escape messages I normally use RCVMSG MSGTYPE(*EXCP) because *EXCP receives the LAST exception message (i.e., the one that just occurred). All the other values for MSGTYPE receive the FIRST message of the specified type.



This little test program works fine. If I run it repeatedly I will see:
call a01
116 - ADDLIBLE LIB(TLACS)
135 - RCVMSG MSGTYPE(*NEXT) MSGKEY(*TOP) RMV(*YES) KEYVAR(&KEYVAR)
MSGDTA(&DATA) MSGID(&MSGID)
- RETURN /* RETURN due to end of CL program */

and no escape message.

However, I have this logic buried in another program and I am still seeing
the escape message.

Message . . . . : 3100 - ADDLIBLE LIB(TLACS)
CPF2103-Library TLACS already exists in library list.
Message . . . . : 3400 - RCVMSG MSGTYPE(*NEXT) MSGKEY(*TOP) RMV(*YES)
KEYVAR(&KEYVAR) MSGDTA(&DATA) MSGID(&MSGID)

I expect there is another message being sent prior to this that is not being removed (*COMP, *INFO, *DIAG, etc.) and that message is removed by this RCVMSG therefore leaving the one you want to remove in the job log.

Comment out all RCVMSG commands in this program and run it again to see what's really in the job log (or run it in debug and look at the job log before the RCVMSG command runs).

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.