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



Dave,

I would like the ability to turn the message suppression on and off. The messages can be useful for debugging.

-mark

On 2/28/2018 10:52 AM, dlclark@xxxxxxxxxxxxxxxx wrote:
"MIDRANGE-L"<midrange-l-bounces@xxxxxxxxxxxx> wrote on 02/28/2018
10:14:07 AM:
"MIDRANGE-L"<midrange-l-bounces@xxxxxxxxxxxx> wrote on 02/28/2018
01:05:59 AM:
I always close the cursor before I open it. In an embedded SQL I just
ignore
the negative SQL code or State '24501'.
In an SQL routine I use a continue handler to handle the SQLSTATE
24501
as
you did.

For any (unexpected) error in an SQL routine, that is not handled
before, I
add a EXIT Handler which can close the SQL Cursor(s).
You may also add an global variable that is set in your routine to
indicate
whether the cursor is opened or not.
Something like this:
Declare Exit Handler for SQLEXCEPTION
Begin Close Your_Curor;
-- do whatelse you want to do if an error occurs
End;

Thanks. I wish that when an SQL error is being handled by a
continue handler that SQL would not put messages in the joblog --
similar to how the IBM API's don't put messages in the joblog when
the Error Code structure is supplied in the parameter list.

Anyone care to vote for this?

Suppress Handled SQL Messages from Joblog
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=116988


Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.