|
Follow-up on this thread: I am getting most of the desired results of my original post by using GET DIAGNOSTICS as outlined by Birgitta. The problem with using MESSAGE_TEXT is that you sacrifice the second-level text of the SQLnnnn message, which often gives important information, especially in the case of errors. Unless you pull another rabbit out of IBM's hat, Birgitta <g>, I'll probably use DB2_MESSAGE_ID* and whatever gives the message data; which I still haven't been able to determine. Maybe I'll have to QMHRCVPM (RCVMSG) API? (Ugghhh.) - Dan
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.