A fix is available
APAR status
Closed as program error.
Error description
IBM DB2 DRIVER FOR JDBC AND SQLJ RELEASE 3.62 GENERAL SERVICE Additional Symptom(s) SEARCH KEYWORD: ZOS113T/K DFHSJ1004 OSGi
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Users of the IBM Data * * Server Driver for JDBC and SQLJ * **************************************************************** * PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and * * SQLJ version 3.62.73 is provided by * * this APAR ( JCCV36273 ) * * * * This APAR is applicable to IBM Data * * Sever Driver for JDBC and SQLJ * * for DB2 z/OS V10, DB2 z/OS V9 and * * the alternate supplemental driver * * for DB2 z/OS V8. ( JCCZOSDB2V10, * * JCCZOSDB2V9, JCCZOSDB2V8 ) * * * * This APAR delivers a service bundling * * to release 3.62 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. * **************************************************************** * RECOMMENDATION: * **************************************************************** JCC sub-category keywords: JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ The following changes are delivered in this APAR: ____________________________________________________________ All connectivity types: A NullPointerException may thrown when the driver prints out the "Out Of Package" diagnostics information for SQL code -805. This problem has been fixed. (wsdbu00720606) ____________________________________________________________ All connectivity types: When data type Cursor is used as stored procedure parameters and there are multiple resultsets returned from the stored procedure, an ArrayIndexOutOfBoundException may be thrown. This problem has been fixed. (wsdbu00728452) ____________________________________________________________ All connectivity types: When CCSID 16684 is used, SQLException with message "unsupported ccsid, encoding, or locale: Cp16684" may occur. This problem has been fixed. (wsdbu00740081) ____________________________________________________________ All connectivity types: When one of the encryption security mechanisms is used, Client userid special register is not set correctly. This problem has been fixed. (wsdbu00840342) ____________________________________________________________ Type-4 Connectivity: When driver is waiting for the reply from the DB2 server and the value set by blockingReadConnectionTimeOut property is expired, driver will try auto client reroute to a new connection without cleaning up the old connection to DB2 server. This can result in a lockwait if there was a transaction held by this old connection before blockingReadConnectionTimeOut occurred. The problem has been fixed. (wsdbu00716902) ____________________________________________________________ Type-4 Connectivity: Under sysplexWLB environment, driver might create more transport objects than the value set by db2.jcc.maxTranportObjects global property while doing auto fail-over. The problem has been fixed. (wsdbu00836844) ____________________________________________________________ Type-4 Connectivity: Under sysplexWLB environment, driver does not properly balance workload if DB2 server returns a server list with zero weight for one or more members. The problem has been fixed. (wsdbu00740129) ____________________________________________________________ Type-4 Connectivity: Driver throws a NullPointerException during the failover processing for application connecting to a data sharing or a HADR system. This problem has been fixed. (wsdbu00738031) ____________________________________________________________ Type-2 z/OS Connectivity: A NullPointerException might be thrown when running a Batch Container application with only one connection or running in a Java Stored Procedure using DB2SimpleDataSource. This has been fixed. (wsdbu00734274) ____________________________________________________________ Type-2 z/OS Connectivity: When ProgressiveStreaming is turned off and FullyMaterializeLobData is turned on, the lob data from a Resultset returned from a call statement may be processed incorrectly and cause an ArrayIndexOutOfBoundsException. This problem has been fixed. (wsdbu00719228) ____________________________________________________________ Type-2 z/OS Connectivity: ArrayIndexOutOfBoundsException may thrown when processing resultset metadata returned from a call statement. This has been fixed. (wsdbu00732160) ____________________________________________________________ Type-2 z/OS Connectivity: Possible LE HEAP latch contention in multi-threaded environments due to LE condition handler registration/deregistration calls made by the Type-2 z/OS driver code. In order to avoid the LE HEAP latch contention, the Type-2 z/OS driver code was changed to only use LE condition handling in the specific environment that requires it to be used. (wsdbu00729344) ____________________________________________________________ SQLJ ALL Connectivities: In a Websphere environment, an SQLJ application may hit an ArrayIndexOutOfBoundsException thrown from the Websphere runtime. This occurs when application issues a SELECT statement, closes the SQLJ iterator, and the Java Finalizer thread drives a close on the underlying statement concurrently. If the SQLJ ConnectionContext is closed after the iterator close in the application, the chances of hitting this timing window is eliminated. The fix ensures the PreparedStatement close is not driven twice. (wsdbu00718833) ____________________________________________________________ SQLJ ALL Connectivities: In a Websphere environment, an SQLJ application may hit a 'Statement is closed' error. This is more likely to occur when Connection Sharing is enabled for the Websphere application. The error occurs when SQLJ Runtime reuses a Statement which was closed by Websphere at the transaction boundary. The fix ensures the statement is re-prepared if it was closed by Websphere. (wsdbu00734485)
Problem conclusion
The items described in the APAR Problem Summary have been resolved as noted in the summary and included in this APAR. KEYWORDS: ZOS0201T/K ZOS0202T/K
Temporary fix
Comments
APAR Information
APAR number
PM36832
Reported component name
DB2 ODBC/JDBC/S
Reported component ID
5740XYR02
Reported release
912
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2011-04-12
Closed date
2011-07-13
Last modified date
2015-01-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK69732 UK69733 UK69734
Modules/Macros
DSNAQJBA DSNAQJBB DSNAQJB1 DSNAQJB2 DSNAQJB3 DSNAQJB4 DSNAQJB5 DSNAQJB6 DSNAQJB7 DSNAQJB8 DSNAQJC1 DSNAQJC2 DSNAQJC3 DSNAQJC4 DSNAQJRM DSNAQJS1 DSNAQJS2 DSNAQ3BA DSNAQ3BB DSNAQ3B1 DSNAQ3B2 DSNAQ3B3 DSNAQ3B4 DSNAQ3B5 DSNAQ3B6 DSNAQ3B7 DSNAQ3B8 DSNAQ3B9 DSNAQ3CA DSNAQ3CC DSNAQ3CE DSNAQ3CF DSNAQ3CM DSNAQ3C0 DSNAQ3C1 DSNAQ3C2 DSNAQ3C3 DSNAQ3C4 DSNAQ3C5 DSNAQ3C6 DSNAQ3C7 DSNAQ3C8 DSNAQ3C9 DSNAQ3E1 DSNAQ3F1 DSNAQ3F2 DSNAQ3F3 DSNAQ3F4 DSNAQ3L2 DSNAQ3L9 DSNAQ3RM DSNAQ3S1 DSNAQ3S2 DSNAQ6CC DSNAQ6CE DSNAQ6CF DSNAQ6CM DSNAQ6C0 DSNAQ6C1 DSNAQ6C2 DSNAQ6C3 DSNAQ6C4 DSNAQ6C5 DSNAQ6C6 DSNAQ6C7 DSNAQ6C9
Fix information
Fixed component name
DB2 ODBC/JDBC/S
Fixed component ID
5740XYR02
Applicable component levels
RA12 PSY UK69732
UP11/07/26 P F107
R812 PSY UK69733
UP11/07/26 P F107
R912 PSY UK69734
UP11/07/26 P F107
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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":"912"}]
Document Information
Modified date:
04 March 2021