A fix is available
APAR status
Closed as program error.
Error description
DB2DDF DB2DRDA DB2INACTIVE Application error: SQL Error: SQLCODE=-204, SQLSTATE=42704, due to lost of schema special register value after DB2 z/OS processes an "XA_RECOVER" or "DRDA Ping" with CMTSTAT=INACTIVE, and only if UK78128 (V9 PM61082) is applied. *************************************************************** Additional Symptoms and Keywords: SQLCODE -204 SQLCODE204 SQL204N SQL0204N SQL00204N ABEND04E AB04E S004E 04E 04E-00E70005 00E70005 RC00E70005 DSNXOOP DSNXOOP:M200 M200 because Application Encoding Scheme special register value is lost.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * DB2 9 for z/OS users only. * **************************************************************** * PROBLEM DESCRIPTION: Unpredictable output, including * * SQLCODE -204, because (Set) special * * register values, such as Schema, are * * lost. * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote application accesses a DB2 9 for z/OS system and establishes special register values, such as Schema. The DB2 9 for z/OS server may incorrectly purge the special register values after receiving an xa_recover or DRDA Ping sequence if DB2 also determines that the connection can be subsequently inactivated. The missing special register values may lead to unpredictable results including SQLCODE -204. The problem only occurs if DB2 9 for z/OS is configured with DDF Inactive Thread support (DSN6FAC CMTSTAT=INACTIVE) and only after applying PTF UK78128 (V9 APAR PM61082). The DB2 9 for z/OS PM61082 change (PTF UK78128) is in error because it did not consider that an xa_recover or DRDA Ping sequence may actually be related to an application that has established special register values which must be processed by the DB2 engine in order to allow the values to persist across connection inactivation and activation events. Note: The condition does not occur in DB2 10 for z/OS due to a redesign in how special register values are managed.
Problem conclusion
After processing an xa_recover or DRDA Ping request from a remote client system, DB2 9 for z/OS is changed to ensure that special register values are processed by the DB2 engine when the connection will be inactivated.
Temporary fix
Comments
APAR Information
APAR number
PM72269
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-09-05
Closed date
2012-10-05
Last modified date
2013-01-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK82380
Modules/Macros
DSNLQDIS DSNLTDSR DSNLTEXC
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
R910 PSY UK82380
UP12/10/23 P F210
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":"9.1","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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
17 January 2013