PI24284: ALLOW DISTRIBUTED DATABASE ACCESS THREADS (DBATS) WHICH HAVE ACCESSED ACCELERATORS TO BE POOLED AT COMMIT/ROLLBACK

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• DB2DDF DB2INACTIVE defects pi24284 dpi24284
  DDF allowing clean DBATs to be pooled and connection being made
  inactive is being prevented when those DBATs accessed an IDAA
  accelerator.
  **************************************************************
  Additional Symptoms and Keywords:
   IDAA  IDAAV2R1/K IDAAV3R1/K IDAAV4R1/K
   DSNTIPR DDF THREADS INACTIVE
   DSN6FAC CMTSTAT INACTIVE
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 for z/OS users who use IBM DB2       *
  *                 Analytics Accelerator.                       *
  *                 Specifically where:                          *
  *                 - the (DSNTIPR) DDF THREADS (DSN6FAC         *
  *                   CMTSTAT) subsystem parameter is set to     *
  *                   INACTIVE, and                              *
  *                 - remote (distributed) client applications   *
  *                   execute SQL that gets offloaded to an      *
  *                   accelerator.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: More concurrent active DBATs are        *
  *                      required when distributed client        *
  *                      requests access an accelerator.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When DB2 is configured with the (DSNTIPR) DDF THREADS (DSN6FAC
  CMTSTAT) subsystems parameter set to INACTIVE, a distributed
  server thread (DBAT) is pooled at the end of a transaction so
  that the DBAT will be available to service requests from other
  remote client connections.
  However, when a distributed client's requests lead to an
  accelerator being accessed, the DBAT is prevented from being
  pooled even if an active offloaded query no longer exists.
  This leads to a higher number of concurrent active DBATS.
  

Problem conclusion

Temporary fix

Comments

• DB2 has been changed to allow the pooling of DBATs when an
  accelerator is no longer being utilized.
   Note: Standard pooling/inactivation rules still apply.
         For example, open WITH HOLD cursors, including
         offloaded queries, and KeepDynamic packages will still
         prevent pooling.
  

APAR Information

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

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

  UI26306 UI26307

Modules/Macros

•    DSNLCDG1 DSNLCDP1 DSNLCITR DSNLCMBE DSNLCSRR
  DSNLDALB DSNLIAAC DSNLIRCA DSNLISDA DSNLQINA DSNLTGBK DSNLTSET
  DSNLXCMT DSNLXCQH DSNLXMRF DSNLXPCA DSNLXRBF DSNLXRCN DSNLXREL
  DSNLXRFT DSNLXROP DSNLZMON DSNTABA  DSNTADL  DSNVDTA  DSNWVZSA
  DSNXONZA DSNXONZB DSNX8API DSNX8CDA DSNX8CLN DSNX8EPL DSNX8SMF
  DSNX8STA DSNX8STO DSNX8WAC HDBAA10J HDBBB10J
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI26306

     UP15/04/11 P F504

• RB10 PSY UI26307

     UP15/04/11 P F504

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.