PI34903: NEW RELEASE OF THE IBM DB2 DRIVER FOR JDBC AND SQLJ (RELEASE 4.17) PROVIDING VARIOUS ENHANCEHMENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• NEW RELEASE OF THE IBM DB2 DRIVER FOR JDBC AND SQLJ (RELEASE
  4.17) PROVIDING VARIOUS ENHANCEHMENT
  

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 4.17.55 is provided by     *
  *                      this APAR ( JCCV41755 )                 *
  *                                                              *
  *                      This APAR is applicable to IBM Data     *
  *                      Sever Driver for JDBC and SQLJ          *
  *                      for DB2 z/OS V11, DB2 z/OS V10 and      *
  *                      DB2 z/OS V9( JCCZOSDB2V11,              *
  *                      JCCZOSDB2V10, JCCZOSDB2V9 )             *
  *                                                              *
  *                      This APAR delivers a new release (4.17) *
  *                      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:
  _______________________________________________________________
  Type-4 Connectivity: SQLJ customization on a
  3-tier connection fails with ERRORCODE4499(-4499),
  after rollback is sent on the connection.
  "Execution failed due to a distribution protocol error that
  caused deallocation of the conversation A DRDA Data Stream
  Syntax Error was detected. Reason: 0x1900. ERRORCODE=-4499,
  SQLSTATE=58009".
  This problem has been fixed. (RTC 33509)
  _______________________________________________________________
  Type-4 Connectivity: When JCC driver hits the limit for
  seamless retries, SQL20542N will now be thrown instead of
  ERRORCODE4228(-4228) .
  This problem has been fixed. (RTC 32315)
  _______________________________________________________________
  Type-4 Connectivity: Due to best member calculation prior
  to flowing any query, a member that initially failed for a
  query may get picked again during seamless failover, which
  is incorrect. This can causes sub-optimal reroute behavior
  or seamless failover failures such as SQLCODE20542N in high
  frequency.
  Note: There are cases where SQLCODE20542N is issued correctly.
  This problem has been fixed. (RTC 41553)
  _______________________________________________________________
  Type-4 Connectivity: In case of reuse JCC closes all the open
  statements, which can cause start of a new transaction on the
  server. This results in the connection unfit to be reused and
  possible occurrence of Conversational Protocol Error
  exception: "Execution failed due to a distribution protocol
  error that caused deallocation of the conversation. A DRDA
  Conversational Protocol Error was detected.
  Reason: 0x1245. ERRORCODE=-4499, SQLSTATE=58009"
  This problem has been fixed. (RTC 25374)
  _______________________________________________________________
  Type-4 Connectivity: A batch update may fail with
  SQLCODE302 (-302) and SqlState=22001 if it's using
  setDBStringAsByte to set Unicode text and the first row of the
  same batch had null for the same column.
  This problem has been fixed. (RTC 31674)
  ______________________________________________________________
  Type-4 XA Connectivity: Driver does not close a non-XA
  transaction (with autocommit on) in case of an exception in
  execution. After the exception, the transaction remains open
  causing the next XA start to fail. A symptom of this issue is a
  global transaction failing to start with XA Exception
  "XAER_OUTSIDE ERRORCODE=-4228", ERRORCODE4228(-4228)
  immediately after a local transaction has completed on the XA
  connection with autocommit on.
  This problem has been fixed. (RTC 28121)
  _______________________________________________________________
  Type-4 Connectivity: The driver frees a transport on
  receiving a RLSCONV REUSE reply for a COMMIT request even
  when there is a new UOW chained to the COMMIT. The
  symptoms in an application would indicate loss of session
  data or other failures that can be associated with the
  transport having been switched in the middle of a UOW.
  This problem has been fixed. (RTC 45936)
  _______________________________________________________________
  Type-4 Connectivity: During XA transaction,
  connection processing may hang due to a server outage
  preventing failover to an available alternate DB2 members to
  succeed. In a WebSphere environment, the condition is
  marked by WebSphere warning messages, that indicate threads
  have been hung for a long time. The thread stack
  traces show the thread is waiting in a socket read call.
  Socket read is a common driver activity so an
  XA Connection and a coinciding server failure are
  necessary to be present simultaneously to indicate this
  error condition.
  This problem has been fixed. (RTC 39487)
  _______________________________________________________________
  Type-4 Connectivity: Subsequent to a failover, in a client
  reroute environment, the client info special registers
  sometimes do not get replayed on the rerouted connection.
  This problem has been fixed. (RTC 33125)
  _______________________________________________________________
  Type-4 Connectivity: JCC driver throws a SQLCODE799(+799)
  warning when client info values set using the generic
  special register. Example as below:
  prop.put ("specialRegisters","CURRENT CLIENT_APPLNAME=testApp")
  DriverManager.getConnection(url,prop)
  This problem has been fixed. (RTC 35263)
  _______________________________________________________________
  Type-4 Connectivity: When the JCC driver is connected to a data
  sharing group and carrying out an
  automatic client reroute, there are situations when the
  creation of a TCP/IP socket to a member of the data
  sharing group succeeds, but subsequent flows fail. The
  driver may not handle such errors correctly and cause
  reroute not to succeed or incorrectly throws a SQLCODE30108N
  when a reroute may not actually have succeeded.
  This problem has been fixed. (RTC 31222)
  _______________________________________________________________
  Type-4 Connectivity:
  getJccSpecialRegisterProperties method call
  from JCC fails with SQLCODE4700(-4700) error.
  This is due to JCC trying to get the value of
  CLIENT_CORR_TOKEN special register which is
  absent in DB2 V11 CM or lower. JCC should avoid sending
  request to get the value of CLIENT_CORR_TOKEN in these cases.
  This problem has been fixed.(RTC 47261)
  _______________________________________________________________
  Type-4 Connectivity:
  During a XA transaction if the first SQL fails with
  SQLCODE204(-204) or SQLCODE727(-727) then the subsequent
  attempt to prepare a select query on a second
  table will fail with following exception.
  "Error executing XAResource.start().  Server returned
  XAER_PROTO. ERRORCODE=-4203, SQLSTATE=null"
  SQLCODE204(-204) or SQLCODE727(-727) errors will not prevent
  transaction from starting.
  This problem has been fixed. (RTC 39374)
  _______________________________________________________________
  All Connectivities: Support a new value
  DB2BaseDataSource.CONNECTION_CLOSE_WITH_COMMIT (3) for
  "connectionCloseWithInFlightTransaction" driver property.
  This value allows an application to indicate that if a
  connection is closed in the middle of a transaction and
  autoCommit disabled, then any uncommitted operations should
  be implicitly committed before closing the connection. No
  exception is raised to the application.
  (RTC 47251)
  _______________________________________________________________
  Type 4 Connectivity: Enhancement to support commandTimeout
  on ResultSet and DatabaseMetaData operations. With this
  enhancement, any configured commandTimeout value should apply
  to ResultSet and DatabaseMetaData operations such as
  ResultSet.next() and DataBaseMetadata.getCatalogs().
  (RTC 31075)
  _______________________________________________________________
  All Connectivities: The driver throws SQLException with
  ERRORCODE4463(-4463), SQLSTATE=4261,
  "Error parsing <Data Type> literal value starting at index
  <index>.  Error Detail: Invalid character ' M' found in
  <Data Type> literal. Full SQL statement
  text=<statement text> ERRORCODE=-4463, SQLSTATE=42601",
  when a CALL statement is constructed with embedded CR-LF
  between parameters as below:
  CALL CALL_FUNCTION_NAME(PARAM1,PARAM2,<CR-LF>
  PARAM3,PARAM4)
  This defect has been fixed.
  (RTC 37914)
  

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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI26208 UI26209 UI26210

Modules/Macros

•    DSNAJJC1 DSNAJJC2 DSNAJ3CC DSNAJ3CE DSNAJ3CF
  DSNAJ3CM DSNAJ3C0 DSNAJ3C1 DSNAJ3C2 DSNAJ3C3 DSNAJ3C4 DSNAJ3C5
  DSNAJ3C6 DSNAJ3C7 DSNAJ3C9 DSNAJ6CC DSNAJ6CE DSNAJ6CF DSNAJ6CM
  DSNAJ6C0 DSNAJ6C1 DSNAJ6C2 DSNAJ6C3 DSNAJ6C4 DSNAJ6C5 DSNAJ6C6
  DSNAJ6C7 DSNAJ6C9
  

Fix information

• Fixed component name

  DB2 ODBC/JDBC/S

• Fixed component ID

  5740XYR02

Applicable component levels

• RA12 PSY UI26208

     UP15/03/25 P F503

• RB12 PSY UI26209

     UP15/03/25 P F503

• R912 PSY UI26210

     UP15/03/25 P F503

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.