A fix is available
APAR status
Closed as new function.
Error description
NEW RELEASE OF THE IBM DATA SERVER DRIVER FOR JDBC AND SQLJ 4.31 PROVIDING VARIOUS ENHANCEMENTS.
Local fix
PTF Required
Problem summary
**************************************************************** * USERS AFFECTED: All Users of the IBM Data * * Server Driver for JDBC and SQLJ * **************************************************************** * PROBLEM DESCRIPTION: SQLJ version 4.31.25 is provided by * * this APAR ( JCCV43125 ) * * * * This APAR is applicable to IBM Data * * Sever Driver for JDBC and SQLJ * * for DB2 z/OS V13, DB2 z/OS V12, * * DB2 and z/OS V11 ( JCCZOSDB2V13, * * JCCZOSDB2V12, JCCZOSDB2V11 ) * * * * This APAR delivers a new release (4.31) * * 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: _______________________________________________________________ Type2 Connectivity: Java Inter language Batch support in JCC driver. JIB designed to enable COBOL, PL/I and Java programs to interoperate with DB2 while maintaining transactional integrity. This enabled mixed language programs to process DB2 for z/OS requests in the same unit of work. This feature has been fixed.(DBC-11532) _______________________________________________________________ Type4 Connectivity: JCC throws ArrayIndexOutOfBoundsException When an SQLJ application runs a heterogeneous batch having statements with different number of host variables. This issue has been fixed.(DBC-12536) _______________________________________________________________ Type4 Connectivity: With queryTimeout setting in JCC driver at default level for timerLevelForQueryTimeOut i.e QUERYTIMEOUT_CONNECTION_LEVEL , JCC creates TimerTask objects for each transaction in the connection to monitor the query execution time. When the workload involves millions of transactions, with a large queryTimeOut value there is a possibility of out of memory due to the large TimerTask object in timer object queue. This issue has been fixed.(DBC-12311, DT172386)
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
PH48861
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
2022-08-23
Closed date
2022-11-14
Last modified date
2022-12-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI83242 UI83243 UI83244
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
RB12 PSY UI83242
UP22/11/15 P F211
RC12 PSY UI83243
UP22/11/15 P F211
RD12 PSY UI83244
UP22/11/15 P F211
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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B12","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
01 December 2022