A fix is available
APAR status
Closed as program error.
Error description
DB2DDF DB2DRDA DB2HOP DB2LOB DB2XML defect pm42060 dpm42060 DDF thread abend 04E-00D35011 from LOC=DSNLZGLM.DSNLZTRC:000A *********************************************************** Additional symptoms and keywords: ABEND04E AB04E S004E 04E 04E-00D35011 00D35011 RC00D35011 DSNLZGLM DSNLZTRC DSNLZTRC:000A 000A ABNDID000A ABID000A VRADC000A ABEND0C4 AB0C4 S00C4 0C4 0C4-00000011 00000011 RC00000011 DSNLZLLM DSNLZHP0 DSNLZHP0+03C6 03C6 OFFSET03C6
Local fix
no local workaround/fix
Problem summary
**************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users * * where a remote application on Site 1 * * connects to a DB2 for z/OS server at Site 2 * * and fetches LOB or XML query data located * * at another server at Site 3. * **************************************************************** * PROBLEM DESCRIPTION: The following abends can occur at the * * DB2 for z/OS server at Site 2: * * . 04E-00D35011 DSNLZGLM.DSNLZTRC:000A * * . 0C4-00000011 DSNLZLLM.DSNLZHP0+03C6 * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote application on Site 1 connects to a DB2 for z/OS server at Site 2 and opens a cursor that fetches data, including LOB or XML data, located at another server at Site 3. The server at Site 3 returns query data according to the DRDA query blocking protocol. When the application fetches data from the cursor, DB2 at Site 2 does not correctly handle the LOB or XML only data received from Site 3 which leads to the reported abends.
Problem conclusion
DB2 for z/OS server processing at Site 2 has been changed to correctly handle the LOB or XML only data received from Site 3.
Temporary fix
Comments
APAR Information
APAR number
PM42060
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-20
Closed date
2011-11-29
Last modified date
2012-01-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK74308 UK74309
Modules/Macros
DSNLCRTD DSNLCSRR DSNLIRTR DSNLXCQH
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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:
01 January 2012