A fix is available
APAR status
Closed as program error.
Error description
DB2DDF DB2XA DB2DSHR SQLCODE -913 and message DSNT376I for an XA transaction because work is not re-routed to the owning data sharing group member if DB2 is configured (DSNZPARM) with DSN6FAC TCPALVER=NO/SERVER. *************************************************************** Additional Symptoms and Keywords: DSNT376I MSGDSNT376I SQLCODE -913 SQLCODE913 SQL913n SQL00913N ABEND04E AB04E S004E 04E 04E-00D35011 00D35011 RC00D35011 DSNLZHC0 DSNLZHC0:0136 0136 VRADC0136 ABNDID0136
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All Distributed Data Facility (DDF) Users. * * DB2 12 for z/OS data sharing (After New Function Activated) * * users only. * **************************************************************** * PROBLEM DESCRIPTION: * * Two conditions are reported: * * 1. An XA related re-route connection to the data sharing * * group member that owns the Global Transaction XID is not * * established if the owning member is configured (DSNZPARM) * * with DSN6FAC TCPALVER=NO/SERVER. This may result in message * * DSNT376I and SQLCODE -913. * * 2. An invalid XA_End condition may not be detected. This may * * result in abend 04E-00D35011 DSNLZHC0:0136. * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote client XA (perhaps XA Transaction Manager) based application specifies a client (ClientApplCompat) property in order to utilize new XA Global Transaction features of DB2 12 for z/OS. Two conditions are reported: 1. If the SQL traffic must be re-routed to another data sharing group member that owns the Global Transaction XID, the re-route connection will not be established if the owning member is configured (DSNZPARM) to disallow Already Verified authentication (DSN6FAC TCPALVER=NO/SERVER). This causes the SQL work to remain local which may potentially lead to lock time-out conditions as described by message DSNT376I and SQLCODE -913. 2. If the remote client environment incorrectly drives XA_End processing without driving a prior XA_Start, the invalid XA_End condition may not be detected which may result in abend 04E-00D35011 DSNLZHC0:0136.
Problem conclusion
Two conditions are corrected: 1. DB2 XA related re-route processing has been changed to connect to the owning member with the same authentication credentials that was received from the remote client environment. 2. DB2 has been changed to detect the invalid XA_End with an XAER_NOTA condition.
Temporary fix
Comments
APAR Information
APAR number
PI73711
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-12-13
Closed date
2017-01-03
Last modified date
2017-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI43688
Modules/Macros
DSNLTDSR
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RC10 PSY UI43688
UP17/01/20 P F701
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 February 2017