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

WHEN TRYING TO RESOLVE INDOUBT TRANSACTIONS, ZOS CLIENT CONNECTED TO DB2
LUW SERVER GETS THE ERROR DSNL414E.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
If zOS client, when trying toresolve  indoubt transactions, 
sends a non-existent UOWID to DB2 LUW server, the server doesn't 
 
handle this situation correctly and causes error DSNL414E. 
This happens because the server is trying to match the UOWID 
with the XID (transaction ID) and using an old XID format.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users below V91FP10.                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* WHEN TRYING TO RESOLVE INDOUBT TRANSACTIONS, ZOS CLIENT      * 
* CONNECTED TO DB2 LUW SERVER GETS THE ERROR DSNL414E.         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 version V91FP10                               * 
****************************************************************
Local Fix:
NA
available fix packs:
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Move to V91FP10 or higher to resolve this problem.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67965 IC71525 IC71526 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.04.2010
16.06.2011
16.06.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.