home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC99978 Status: Closed

CLI-BASED APPLICATIONS RECEIVE SQL0501N AGAINST DB2 Z/OS WHEN STORED
PROCEDURE CALL HAS MULTIPLE CURSORS

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
A CLI-based application might receive an SQL0501N error against 
DB2 z/OS when a stored procedure call has multiple cursors. 
 
SQL0501N  The cursor specified in a FETCH statement or CLOSE 
statement is not open or a cursor variable in a cursor scalar 
function reference is not open. 
 
When a stored procedure with multiple cursors opened is executed 
and when the server has closed only few of the cursors, the CLI 
driver wrongly assumes that server has closed on all the cursors 
for the stored procedure.  The CLI driver then returns the error 
-501 to the application when the fetch statement is driven to 
the server after a partial bindout.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI based application users connecting to  DB2 z/OS          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.5.                             * 
****************************************************************
Local Fix:
Solution
The problem is first fixed in DB2 version 10.1.0.5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.03.2014
10.07.2015
10.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList