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

TRANSACTION MANGER REMAINS WAITING FOR XA_ROLLBACK AFTER ABEND ON Z/OS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
This situation might happen when distributed transaction take 
place DB2 z/OS server(resource manager - RM) reports ABEND. 
DB2Connect server is configured in the connection path with 
connection concentrator enabled to handle TM using 
mufti-transport model like Tuxedo. 
DB2 z/OS ABEND causes connection reroute between DB2Connect 
Server and DB2 Z/OS. Transaction is marked for rollback only. TM 
sends xa_end and xa_rollback to rollback the transaction. XA_END 
receives XA_RBOTHER and XA_ROLLBACK request hang on DB2Connect 
Server. 
 
For example when Tuxedo Transaction Manager is configured on DB2 
Connect Server and application abnormal ends on z/OS. 
In the Tuxedo logs the information regarding ABEND, xa_end = 104 
and hang on xa_rollback can be found. 
 
Apply the APAR on client.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using DB2Connect server and distributed            * 
* transaction processing                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local Fix:
Solution
First fixed in Version 10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.05.2015
22.07.2015
22.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