PI18798: JCC 4.15: IBM DATA SERVER DRIVER FOR JDBC AND SQLJ NEW RELEASE 4.15 GENERAL SERVICE CONT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• JCC 4.15: IBM DATA SERVER DRIVER FOR JDBC AND SQLJ NEW RELEASE
  4.15 GENERAL SERVICE CONT
  

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.15.132 is provided by    *
  *                      this APAR ( JCCV415132 )                *
  *                                                              *
  *                      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.15) *
  *                      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 zos Connectivity: When a client info field has a single
  quote at its truncation limit, JCC driver issues
  SQLCODE10 (-10). Below is an example:
  db2con.setDB2ClientApplicationInformation("'12345678901234567'")
  db2con.setDB2ClientAccountingInformation("'SAP_J2E'")
  The total length of string is 19 ('12345678901234567').
  During parsing each single quote is converted to two single
  quotes, making the total length = 21.
  The truncation limit is = 18, making the
  string after truncation = ''12345678901234567'. The string
  does not have a closing single quote leading to SQLCODE10 (-10).
  This issue has been fixed.(RTC 42568)
  _______________________________________________________________
  All zos Connectivity: JCC driver throws NullPointerException
  when executing a batch containing an SQL with a
  'INSERT FROM SELECT' clause
  This issue has been fixed.(RTC 31622)
  _______________________________________________________________
  Type-2 zos Connectivity: JCC driver does not set the client
  info special registers in the IMS JBP region.
  If the client info is set in the global property file as such
  db2.jcc.clientAccountingInformation=TKCLIENTACC
  db2.jcc.clientWorkstation=TKCLIENTWS
  db2.jcc.clientApplicationInformation=TKCLIENTINFOS
  There is no error reported, neither will JCC driver able to
  set these special registers.
  This issue has been fixed. (RTC 59014).
  _______________________________________________________________
  Type-2 zos Connectivity: JCC driver unable to send the special
  registers coming through a Properties object embedded inside
  another Properties object. Below is an example:
  Properties dbProp = new Properties();
  dbProp.put("currentSQLID", "SYSIBM");
  dbProp.put("CURRENT SCHEMA", "SYSIBM1");
  Properties newdbProp = new Properties(dbProp);
  DriverManager.getConnection("jdbc:db2:STLEC1",newdbProp);
  This issue has been fixed.(RTC 52718)
  _______________________________________________________________
  Type-2 zos Connectivity: JCC driver disables all the V10 and
  older server features while working in CICS environment.
  For an example,
  the LBF (LIMITEDBLOCKFETCH)feature
  does not work as expected and there is NO error reported
  when the JCC driver connects to a DB2 V10 server.
  This issue has been fixed. (RTC 57966).
  _______________________________________________________________
  Type-4 Connectivity: JCC driver attempts to load the native
  library even for a T4 connection in CICS environment.
  This results in the below exception.
  "com.ibm.db2.jcc.am.SqlException:  jcc  10389  12245  4.15.99
  Failure in loading native library db2jcct2zos4_64, java.lang.
  UnsatisfiedLinkError: db2jcct2zos4_64 (Not found in
  java.library.path): ERRORCODE=-4472, SQLSTATE=null "
  and JCC driver not allows to establish a T4 connection through
  Datasource or DriverManager in CICS environment.
  The exception reported is as below.
  "com.ibm.db2.jcc.am.SqlFeatureNotSupportedException:  jcc
   10247  10035  4.15.120  Type-4 connectivity not supported
  under CICS, IMS, or Java SP environments. Use Type-2
  connectivity only. ERRORCODE=-4450, SQLSTATE=0A504 "
  This issue has been fixed.(RTC 62607).
  _______________________________________________________________
  Type-4 Connectivity: A java.lang.NullPointerException is
  observed in com.ibm.db2.jcc.am.Connection.writeEntryInJccLog()
  when attempting to acquire a XA connection using
  The exception reported is as below.
  "com.ibm.db2.jcc.am.SqlFeatureNotSupportedException:  jcc
   10247  10035  4.15.120  Type-4 connectivity not supported
  under CICS, IMS, or Java SP environments. Use Type-2
  connectivity only. ERRORCODE=-4450, SQLSTATE=0A504 "
  This issue has been fixed.(RTC 62607).
  _______________________________________________________________
  Type-4 Connectivity: A java.lang.NullPointerException is
  observed in com.ibm.db2.jcc.am.Connection.writeEntryInJccLog()
  when attempting to acquire a XA connection using
  com.ibm.db2.jcc.DB2XADataSource.getXAConnection()
  This occurs due to a failure in writing to the JCCDIAG.LOG file.
  This issue has been fixed.(RTC 47917)
  _______________________________________________________________
  Type-4 connectivity: Currently committed semantics are not
  applied if a SELECT subquery is embedded in an UPDATE/INSERT
  query. The driver requests concurrent access resolution of
  USE CURRENTLY COMMITTED only for purely SELECT queries.
  However, when SELECT queries are embedded within INSERT or
  UPDATE queries, the driver does not request USE CURRENTLY
  COMMITTED concurrent access resolution even though the
  driver property concurrentAccessResolution is configured as
  DB2BaseDataSource.CONCURRENTACCESS_USE_CURRENTLY_COMMITTED (1).
  This issue has been fixed.
  (RTC 43913)
  _______________________________________________________________
  Type-4 connectivity: On a 3-tier connection to DB2 Linux, Unix,
  and Windows version 10.1 or above via DB2 Connect version 9.7
  or lower gateway, connection fails with the following exception:
  " jcc  t4  2034  11148  3.64.106  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 occurs due to the driver sending MONITOR element in the
  COMMIT and ROLLBACK DRDA commands which the downlevel DB2
  Connect gateway does not understand and results in a DRDA
  error. This issue has been fixed. (RTC 33509)
  _______________________________________________________________
  Type-4 Connectivity: A
  java.nio.channels.OverlappingFileLockException occurs when
  acquiring a connection. This may typically be seen with
  connection pooling; for example, a connection pool of an
  application server attempts to create multiple connections
  simultaneously. Some of the connection attempts may fail
  with OverlappingFileLockException.
  This issue has been fixed. (RTC 59561)
  

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:

  UI25316 UI25317 UI25318

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 UI25316

     UP15/02/24 P F502

• RB12 PSY UI25317

     UP15/02/24 P F502

• R912 PSY UI25318

     UP15/02/24 P F502

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.