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 IC91825 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 / A10 - 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:                                              * 
* Data Studio users.                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Please See Error Description.                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please See Error Description.                                * 
****************************************************************
Local Fix:
No local fix is available.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95330 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.04.2013
02.10.2013
02.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList