MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2014

Re: capture the table name on SQL error



fixed

If it is included in the associated error message then you should be able to retrieve it via GET DIAGNOSTICS. See http://www.ibmsystemsmag.com/ibmi/developer/rpg/unexpected_errors/ if you are unfamiliar with that technique.


On 2014-06-17, at 3:00 PM, "Needles,Stephen J" <SNEEDLES@xxxxxxxxxxxxxxxx> wrote:

In a generic error capture routine, I have a need to retrieve the table name for SQL events. I can't find in the SQL CA where the table name(s) is(are) listed, so I'm hoping one of you knows where I can capture the name of the Table(s) involved in a SQLCod <> 0 and SQLCod <> 100 situation.

My requirement is to format the captured name into a CPF9898 message so that a standardized Condition Handler be invoked to report on the event.


Steve Needles

________________________________
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.

TRVDiscDefault::1201
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact