PM02383: IDLE THREAD TIME-OUT PROCESSING IS INCORRECT FOR JCC CONNECTIONS/THREADS THAT ARE COMMITTED WITH KEEPDYNAM 09/12/01 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DDFL09 DB2DRDA defect pm02383 dpm02383
  Threads are not being timed out when they should.
  The problem can only occur in V9 since PK69339 only applies to
  V9. Further, the problem will only come into play if the remote
  client is JCC 3.51.x or higher or JCC 4.01.x or higher, and only
  if the application packages are bound with KeepDynamic(Yes).
  **************************************************************
  ADDITIONAL KEYWORDS AND SYMPTOMS:
    KeepDynamic Refresh DBAT
    IDTHTOIN Idle Thread Timeout time-out
    CMTSTAT INACTIVE
    DDF THREADS ACTIVE
    MAXDBAT
    5740XYR00 DDF
    DPSB_ACEKPDYN
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  *                 Specifically where DB2 is being accessed     *
  *                 by distributed applications using the IBM    *
  *                 Data Server Driver or Client product family  *
  *                 and the packages utilized by the appli-      *
  *                 cation were bound with KEEPDYNAMIC(YES).     *
  ****************************************************************
  * PROBLEM DESCRIPTION: After applying PTF UK50565              *
  *                      (APAR PK69339), DBATs that were idle    *
  *                      for longer than the specified           *
  *                      IDTHTOIN time interval may not be       *
  *                      terminated.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  APAR PK69339 (PTF UK50565) provided new DB2 9 for z/OS server
  function to refresh DBATs that remained active if the packages
  used by the client application were bound with KEEPDYNAMIC(YES).
  The intent was to provide this function only to certain remote
  client environments (the IBM Data Server Driver for JDBC or
  SQLJ) and only if they qualified based on client
  configurational properties.  However, due to an oversight in
  APAR PK69339 logic, Idle Thread timeout processing was
  incorrectly disabled for these client environments even though
  they did not qualify for the new function.
  

Problem conclusion

• DB2 has been changed to now properly detect any active DBAT
  as exceeding the idle thread timeout (IDTHTOIN) subsystem
  parameter value if and only if the connection had not
  requested the KEEPDYNAMIC refresh support.
  

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:

  UK53313

Modules/Macros

• DSNLEDDA
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R910 PSY UK53313

     UP10/01/07 P F001

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.