Re: SQL exception diagnostics -- MIDRANGE-L

Subject: Re: SQL exception diagnostics
From: Luis Rodriguez <luisro58@xxxxxxxxx>
Date: Thu, 9 Jan 2020 14:38:28 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Justin,

Have you checked all the GET DIAGNOSTICS options? IIRC, there is one that
returns the message text. Another returns you the CPD text. Again, IIRC, is
something like DB2_MESSAGE_ID2.

Regards,

Luis Rodriguez

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: SQL exception diagnostics , Justin Taylor

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.