A fix is available
APAR status
Closed as program error.
Error description
DB2DDF DB2ABTERM DB2TERM RC00E20027 at DSNLXREL.DSNSVBK +0A3E or SQLCODE330 at DSNXEDC3 on remote query to OS/400 table. DB2/400 can have max 60-byte column labels while that of DB2/zOS is 30-bytes. This lets AR's DESCRIBE BOTH to be responded with unexpectedly-long SQLVARs, causing an overlay into SQLDA storage. DB2 may be eventually terminated. SMCOVERLAY ******************************************** Additional symptoms and keywords: ABND04E AB004E S004E 04E 00E20027 SQLDARD long SQLNAME -330
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those using DB2 for z/OS to * * access data at a DB2 for i server system. * **************************************************************** * PROBLEM DESCRIPTION: The DB2 for z/OS system terminates * * after the following abend occurs: * * .ABND=04E-00E20027 * * LOC=DSNLXREL.DSNSVBK +0A3E * **************************************************************** * RECOMMENDATION: * **************************************************************** An application on a DB2 for z/OS requester system connects to a DB2 for i server to prepare a cursor against a table on which LABELs are defined, where one or more label names are greater than 30 bytes long. When parsing the DESCRIBE information received from the server (in a DRDA SQLDARD object), the DB2 requester incorrectly handles the label names that are greater than 30 bytes long, resulting in a storage overlay. At COMMIT or ROLLBACK time, DB2 detects the storage overlay and abends as reported. Since this occurs during must-complete processing, DB2 terminates.
Problem conclusion
DB2 has been changed to handle label names that are greater than 30 bytes long.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM32398
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2011-02-10
Closed date
2011-04-27
Last modified date
2011-06-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK67393 UK67394 UK67395
Modules/Macros
DSNLZRDA
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK67393
UP11/05/18 P F105
R810 PSY UK67394
UP11/05/18 P F105
R910 PSY UK67395
UP11/05/18 P F105
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":"8.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":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 June 2011