Re: SQL Technique Available?

"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