A fix is available
APAR status
Closed as program error.
Error description
DB2DDF DDFL09 defect pk89820 dpk89820 x'F3' for RLSCONV is not supported by all DB2 on LUW version or JCC driver. DB2 on Z/OS returns x'F3' for RLSCONV to some client and results in -30020 due to not supporting. ************************************** Additional keywords and symptoms: SQL30020N SQLCODE-30020 SQLC30020N -30020 RC124C 124C DRDA RLSCONV Release Conversation NO_KDO F3
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those that have remote client * * systems which uses a DB2/LUW gateway server * * to access data at a DB2 for z/OS system. * **************************************************************** * PROBLEM DESCRIPTION: After applying PK41236, a remote * * client application using IBM Data * * Server driver for JDBC and SQLJ * * (version V9.1 FP3 or better) receives * * SQL30020N reason code 0x124C when * * attempting to access data at a * * DB2 for z/OS server via a downlevel * * DB2/LUW (version V9.5 FP2 or lower) * * gateway server. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PK41236 introduced companion support for remote client systems which uses the IBM Data Server Driver for JDBC and SQLJ (version 3.51.x/4.1.x or better) with the "keepDynamic" and "enableSysplexWLB" datasource connection properties enabled. As a result, DB2 z/OS (with APAR PK41236 installed) will honor this client feature enhancement support only to those remote client systems using this level (or better) of this driver. However, in this case, the remote client system connects to the DB2 z/OS server via a downlevel DB2/LUW gateway (version V9.5 FP2 or lower) but DB2 z/OS failed to recognize that it cannot honor the same JDBC client support enhancement to the DB2/LUW gateway. NOTE: DB2/LUW V9.5 FP3 or better can support the new enhancements that PK41236 provides. But any versions of DB2/LUW below V9.5 FP3 will not. Because DB2 z/OS failed to recognize the DB2/LUW gateway lack of tolerance for the new function, DB2 incorrectly returned the new function indication to the DB2/LUW gateway. Hence, this causes the DB2/LUW gateway server to detect a DRDA error (invalid values parsed) and the remote end client system receives SQL30030N reason code 0x124C from the DB2/LUW gateway.
Problem conclusion
DB2 has been changed to correctly identify the remote partner's product level with respect to processing the new client feature support introduced with APAR PK41236.
Temporary fix
Comments
APAR Information
APAR number
PK89820
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
2009-06-25
Closed date
2009-07-20
Last modified date
2009-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK48537 UK48538
Modules/Macros
DSNDDPSB DSNLTCM1 DSNLTEXC DSNLTRB1
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:
02 September 2009