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

WITH CONNECTION CONCENTRATOR ENABLED WE INTERMITTENTLY SENDING RDBNAM IN
UNICODE INSTEAD OF EBCDIC

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
With Connection Concentrator enabled, DB2 intermittently sends 
RDBNAM in UNICODE instead of EBCDIC even if Unicode is disabled 
in 
 
EXCSAT:  the codepoint 1C08  has value 0000. 
 
Because we send RDBNAME in wrong encoding the following error is 
getting reported on zOS server: 
 
REASON=00D35E0B 
ERROR ID=DSNLZSAS0122
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the recommended level                             * 
****************************************************************
Local Fix:
Disable Connection Concentrator
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
First fixed in v10.1fp2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2012
24.09.2013
24.09.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList