× 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 Tuesday, January 6, 2004, at 05:30 AM, David Gibbs wrote:


 From module . . . . . . . . :   QSQPROC
 From procedure  . . . . . . :   CLEANUP
 Statement . . . . . . . . . :   12551
 To module . . . . . . . . . :   QSQPROC
 To procedure  . . . . . . . :   CLEANUP
 Statement . . . . . . . . . :   12551

Hello David,


The message has been sent from QSQPROC to itself. Since your program invokes QSQPROC to perform the DROP the message is on a call stack queue lower than your program. You can try to set the PGMQ values PGMQ(CLEANUP QSQPROC QSQPROC) but I've never been successful receiving messages from call stack queues lower in the stack unless I also knew the message key.

Why not have the RPG program return the SQLSTATE from which you can derive the message ID?

Failing that you could use the QMHLJOBL API to list the job log messages and scan for the one you want.

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

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             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.