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 IC95330 Status: Closed

"SQLCODE" VARIABLE MAY HAVE AN UNEXPECTED VALUE (0) WHEN A STORED
PROCEDURE IS BEING DEBUGGED IN IBM DATA STUDIO.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When a stored procedure is being debugged in IBM Data Studio 
then the value of "SQLCODE" variable under "Diagnostic 
Information" section of "Variables" view of "Debug" perspective 
is always rendered as 0 and does not reflect the actual SQLCODE 
provided by DB2 LUW server.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 Version 10.5.0.3.                              * 
****************************************************************
Local Fix:
No local fix is available.
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem fixed In DB2 Version 10.5.0.3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
25.03.2014
25.03.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList