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


  1.  Home
  2. MIDRANGE-L
  3. January 2004

Re: Cannot RCVMSG a SQL0204 *DIAG message

Hi David,

> A co-worker of mine is trying to receive a diagnostic message in a CL,
> but for some reason (that is totally escaping us) we cannot.
>
[SNIP]
> RCVMSG     MSGTYPE(*DIAG) RMV(*NO) MSGID(&MSGID)
[SNIP]
>   To module . . . . . . . . . :   QSQPROC
>   To procedure  . . . . . . . :   CLEANUP

Your RCVMSG statement is using the default value for the program queue
that you're receiving the message from.  The default value is *SAME.

The message, however, is being sent to procedure CLEANUP in module
QSQPROC, so unless that RCVMSG statement happens to be running in the
CLEANUP procedure of QSQPROC, it won't be able to find it.

You need to chnage the PGMQ parameter of RCVMSG to specify the message
queue for the particular callstack entry that the CLEANUP procedure runs
in.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.