PK76470: DISPLAY THREAD COMMAND SHOWS INCORRECT PLANNAME

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DDFL09 DB2DRDA DB2INACTIVE defect pk76470 dpk76470
  The "DIS THD(*)" command report will  show an incorrect plan
  name of DISTSERV. The problem occurs when a new request arrives
  on a (type2) inactive connection but there is no available
  pooled DBAT (DA/DISCONN thread) handy to service the request.
  ****************************************
  Additional symptoms and keywords:
    Planname plan name CCBRESNM DSNV404I MSGDSNV404I
    DSN6FAC CMTSTAT INACTIVE
    DSNTIPR DDF THREADS INACTIVE
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  *                 Specifically where DB2 is configured with    *
  *                 DDF THREADS = INACTIVE specified             *
  *                 (DSN6FAC CMTSTAT INACTIVE).                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Plan name value incorrectly changed     *
  *                      to "DISTSERV" even though the remote    *
  *                      requester system is DB2 for z/OS.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Non DB2 z/OS requester systems have no concept of DB2 z/OS
  plan names and hence any server thread (DBAT) or connection
  associated with a non DB2 z/OS requester system will utilize
  a generic plan name of DISTSERV.
  In this case the requester system was DB2 z/OS so the plan name
  was initially forwarded to the DB2 z/OS server system as
  expected. The connection with the remote DB2 z/OS requester
  system then became (type 2) inactive, and at this point the
  "DISPLAY THREAD(*) TYPE(INACTIVE)" command report will continue
  to show the appropriate plan name. However, once the connection
  is activated, as a result of a new SQL request being received
  from the DB2 z/OS requester, the plan name may be lost in favor
  of the more generic DISTSERV value. This problem will only
  occur if there were no pool DBATs (DA DISCONN) readily
  available to service the new work on the connection. In this
  case, a DBAT must be dynamically created with a DISTSERV
  association but then the original plan name associated with
  the connection is, incorrectly, not restored.
  The loss of the plan name value may impact performance since
  the plan name value is considered in subsequent Enclave
  classification.
  

Problem conclusion

• DB2 z/OS has been changed to restore the plan name value when a
  connection is activated to a dynamically created DBAT.
  

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:

  UK42169 UK42170

Modules/Macros

• DSNLQDIS DSNLTACX
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R810 PSY UK42169

     UP08/12/20 P F812

• R910 PSY UK42170

     UP08/12/20 P F812

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.