Type-4 connectivity: A special register configured on a
connection URL or a datasource may fail to take effect when
1) JCC triggers a license check immediately after acquiring a
connection and 2) application invokes a commit() or rollback()
as the first thing on the connection before any other SQL
operations. Incorrect special register values can cause
applications to receive SQL errors such as
SQLCODE204(-204) in this scenario. This issue is fixed.
(RTC 41202) APAR Number (IC99026)
---------------------------------------------------------------
Type-4 connectivity: The isValid(int timeout) API may throw
NullPointerException when client reroute is enabled. Also, the
isValid (int timeout) API may not honor the specified timeout
in certain scenarios. This issue is fixed.(RTC 35828).
APAR Number (IT02676)
---------------------------------------------------------------
Type-4 Connectivity: When using XADatasource with
enableSysplexWLB=true, a gradual and permanent growth in
transport objects occur which results SQLCODE4210(-4210).
This issue is fixed.(RTC 35561)
APAR Number (IC97033)
---------------------------------------------------------------
Type-4 connectivity: On an XA connection, if the first SQL
submitted suffers an SQLException, the subsequent SQL may
receive an XAER_PROTO along with the message "Error executing
XAResource.start(). This issue is fixed.(RTC 39374).
APAR Number (IC98295)
----------------------------------------------------------------
Type-4 Connectivity: A batch update may fail if its using
setDBStringAsByte to set Unicode text and the first
row of the same batch had null for the same column.(RTC 31674)
APAR Number (IC94489)
----------------------------------------------------------------
-
Type-4 Connectivity: NIST Compliance recommends to add the
support for TLS1.2 protocol to JCC driver. The defect adds the
support of TLS1.2 protocol to JCC Driver.(37443)
----------------------------------------------------------------
-
All zos Connectivity: When application calls setBytes() method,
this may fail with SQLCODE4474(-4474) if the target column type
is VARCHAR on ZOS Databases. This issue is fixed.(RTC 36106)
APAR Number (IC98220)
----------------------------------------------------------------
-
Type-2 zos Connectivity: When the streamChunkSize property is
not correctly sent by the JCC driver, this can result in a
application hang when reading blob data from the DB2 z/OS
server. This issue is fixed.(RTC 40269)
----------------------------------------------------------------
--
All zos Connectivity: DB2 V10 NFM or higher server supports
TIMESTAMP with TIME ZONE type. When application sends data like
9999-12-31 23:59:59.0 to a timestamp column into these DB2
servers results SQLCODE181(-181). This is because by default
the driver was sending TIME ZONE information to the server.
In the boundary values case, the server is not able to process
it. With the current fix, the driver is NOT sending TIME ZONE
information to theserver if the date part is 9999-12-31 or
0001-01-01.(RTC 37158)
APAR Number (IC96609)
----------------------------------------------------------------
---
Type-2 zos Connectivity: JCC driver not able to send the jcc
property currentSchema to the DB2 server. This results
SQLCODE204(-204) while executing statements. This issue is
fixed.(RTC 36321)
----------------------------------------------------------------
-- |
