MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2014

RE: capture the table name on SQL error



fixed

Vern,

That's true, but then I'd have to capture the complete error message's text and parse out the file name...not sure how to pull that off and besides that...it sounds like a fair amount of work that I cannot spare.

Steve Needles


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Tuesday, June 17, 2014 2:29 PM
To: Midrange Systems Technical Discussion
Subject: Re: capture the table name on SQL error

Steve

There's almost always an SQLnnnn message included with an error - maybe that's usable for this.

HTH
Vern

On 6/17/2014 2:13 PM, Needles,Stephen J wrote:
Thanks Gary...I'll what I can find on Michael Sansoterra.

Steve Needles

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Gary Thompson
Sent: Tuesday, June 17, 2014 2:10 PM
To: Midrange Systems Technical Discussion
Subject: RE: capture the table name on SQL error

Steve,
Not the answer you are asking for but I have seen a >column< name in
SQLERM and SQLERRMC (SQLCODE -122 for example) Don't find any notes in
my SQLCA involving table name Sounds like something Michael Sansoterra
may have written about

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Needles,Stephen J
Sent: Tuesday, June 17, 2014 1:01 PM
To: midrange-l@xxxxxxxxxxxx
Subject: capture the table name on SQL error

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.

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


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






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