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



Hi Reeve -

G, this code works fine for *EXCP messages when you use MSGQ(*PGMQ)
MSGTYPE(*EXCP) (and *COMP messages too).  But those pesky *DIAG's are just
out of my reach.

I suspect that the program is sending the diagnostic messages to itself, or to its caller but that caller is not your program but some intermediate program. As a result, the messages are not in the message queue of your program but of some lower program that has ended.

If you look at the program that the messages were sent to, is it your program or some other program?

If it's not your program, that's the problem. You'll have to process the joblog to get the messages.

If it is your program, then there is something else going on; you should be able to receive those messages. You might have loop through multiple diagnostic messages to get to the one you want, but you should be able to get it with RCVMSG *if* it is your program that the message was sent to.

Ken
http://www.kensims.net/
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.


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.