A fix is available
APAR status
Closed as program error.
Error description
DB2DDF DDFL09 DB2INACTIVE defect pm08659 dpm08659 QDSTPOOL appears to be doubled the amount it should be. When checking statistic output: GLOBAL DDF ACTIVITY QUANTITY --------------------------- -------- TYPE 2 INACTIVE DBATS HWM 1.00 ACC QUEUED TYPE 2 INACT THR 19.00 CUR QUEUED TYPE 2 INACT THR 0.00 QUEUED TYPE 2 INACT THR HWM 1.00 CURRENT ACTIVE DBATS 0.86 ACTIVE DBATS HWM 1.00 TOTAL DBATS HWM 1.00 CURRENT DBATS NOT IN USE 0.86 DBATS NOT IN USE HWM 1.00 DBATS CREATED 1.00 POOL DBATS REUSED 38.00 <== doubled ******************************************************** Additional symptoms and keywords: QDSTPOOL LCOMPOOL too high 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: The QDSTPOOL statistical value * * is incorrect and reflects a * * value that is too high. * **************************************************************** * RECOMMENDATION: * **************************************************************** The QDSTPOOL statistical value is intended to reflect the number of times that a disconnected (pooled) DBAT was readily available to service work on a connection from a remote system. There are two problems associated with the management of the QDSTPOOL value: 1. In the case where a disconnected DBAT *IS* readily available, the QDSTPOOL value is correctly incremented when the pooled DBAT is found and scheduled (resumed) to service the work. However, the value is then incorrectly incremented again once the pooled DBAT itself is dispatched and begins to process the connection work. The affect here is that QDSTPOOL will reflect a value that is twice as high as it should be. 2. In the case where a disconnected DBAT *IS NOT* readily available, the QDSTPOOL value will be incorrectly incremented once a DBAT has been created and dispatched to service the connection. The affect here is that QDSTPOOL will reflect an occurrence where a pooled DBAT was not available and had to be created, which is contrary to the definition of QDSTPOOL. Note: The QDSTNDBA statistical value is designed to reflect the case when a DBAT had to be created to service a connection.
Problem conclusion
DB2 has been changed to increment the QDSTPOOL value only when a pooled DBAT has been found (readily available) and scheduled to service the connection.
Temporary fix
Comments
APAR Information
APAR number
PM08659
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-01
Closed date
2010-04-08
Last modified date
2010-05-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK55927 UK55928
Modules/Macros
DSNLQDIS
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 May 2010