A fix is available
APAR status
Closed as program error.
Error description
NEW RELEASE OF THE IBM DATA SERVER DRIVER FOR JDBC AND SQLJ 4.33 PROVIDING VARIOUS ENHANCEMENTS.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Users of the IBM Data * * Server Driver for JDBC and SQLJ * **************************************************************** * PROBLEM DESCRIPTION: SQLJ version 4.33.39 is provided by * * this APAR ( JCCV43339 ) * * * * This APAR is applicable to IBM Data * * Sever Driver for JDBC and SQLJ * * for DB2 z/OS V13, DB2 z/OS V12 * * (JCCZOSDB2V13, JCCZOSDB2V12) * * * * This APAR delivers a new release (4.33) * * of the IBM Data Server Driver for JDBC * * and SQLJ providing an accumulation of * * defect fixes and enhancements. * * * * Individual items are documented in the * * APAR summary section that follows. * **************************************************************** JCC sub-category keywords: JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ The following changes are delivered in this APAR: _______________________________________________________________ All Connectivities: During connection establishment, if a password present in property object and in URL, JCC throws exception with the password name in the message. This issue has been fixed.(DT256996, DBC-14992) _______________________________________________________________ Type4 Connectivity: When smart card Login security enabled with IBM Semeru JDK, connection fails with NoSuchProviderException : IBMCAC This issue has been fixed. (DT245697, DBC-14646 bug ,DBC-14613 CRM) _______________________________________________________________ Type4 Connectivity:Using securityMechanism 9 during trusted context scenario, Switch user fails with Exception Unsupported DDM object code point: 0x1219. This issue has been fixed. (DT269687, DBC-15299, DBC-15240, DBC-15257) _______________________________________________________________ Type4 Connectivity: When driver receiving ENDUOWRM in response to EXCSAT/ACCSEC buffer during connection establishment, it is observed that the driver is retrying for the connection. This issue has been fixed.(DT261720, DBC-15084) _______________________________________________________________ Type4 Connectivity: When sysplex pool dump is enabled to log the details in JCC trace, we could see NPE due to missing check of an object for null. This issue has been fixed.(DT246671,DBC-14852) _______________________________________________________________
Problem conclusion
The items described in the APAR Problem Summary have been resolved as noted in the summary and included in this APAR.
Temporary fix
Comments
APAR Information
APAR number
PH60240
Reported component name
DB2 ODBC/JDBC/S
Reported component ID
5740XYR02
Reported release
B12
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-03-08
Closed date
2024-04-22
Last modified date
2024-05-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI96603 UI96604
Modules/Macros
DSNAJ3C0 DSNAJ3C1 DSNAJ3C2 DSNAJ3C3 DSNAJ3C4 DSNAJ3C5 DSNAJ3C6 DSNAJ3C7 DSNAJ3C9 DSNAJ3CC DSNAJ3CE DSNAJ3CF DSNAJ3CM DSNAJ3CN DSNAJ6C0 DSNAJ6C1 DSNAJ6C2 DSNAJ6C3 DSNAJ6C4 DSNAJ6C5 DSNAJ6C6 DSNAJ6C7 DSNAJ6C9 DSNAJ6CC DSNAJ6CE DSNAJ6CF DSNAJ6CM DSNAJ6CN DSNAJJC1 DSNAJJC2
Fix information
Fixed component name
DB2 ODBC/JDBC/S
Fixed component ID
5740XYR02
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":"BU048","label":"IBM Software"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B12","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 May 2024