PM27482: WITH UK61131, QDSTQDBT WAS USED FOR #'DP_SY_EXC.SYS_MDBW' while QDSTQDBT is cumulative counter resulting in incorrect data

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• QDSTQDBT was used for threads waiting on limit.  QDSTQDBT is a
  cumulative counter resulting in incorrect data.
  More checking is added to determine the number of threads
  waiting on limit.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   The component that transfers DB2         *
  *                     monitoring data collected by the         *
  *                     OMEGAMON collector to the TEMA           *
  *                 -   Tivoli Enterprise Monitoring Agent       *
  *                 -   Classic Interface                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: - Attribute 'Threads Waiting on Limit'  *
  *                      in workspace 'System Status' may be     *
  *                      incorrect in TEP                        *
  *                      - Situation on 'Threads Waiting on      *
  *                      Limit' may be incorrectly tripped in    *
  *                      TEP                                     *
  *                      - The system exception MDBW may be      *
  *                      incorrectly tripped in Classic          *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  *                                                              *
  ****************************************************************
  PROBLEM SUMMARY:
  - Incorrect field was used to collect the data for Threads
  Waiting on Limit and exception MDBW.
  - "Inactive connections waiting" due to MAXDBAT reached was
  incorrectly documented as "threads waiting" due to MAXDBAT
  reached.
  
  PROBLEM CONCLUSION:
  - Added more checking for the number of inactive connections
  waiting due to MAXDBAT reached.
  - Changed "threads waiting" due to MAXDBAT reached to "Inactive
  connections waiting" due to MAXDBAT reached.
  

Problem conclusion

• - Added more checking for the number of inactive connections
  waiting due to MAXDBAT reached.
  - Changed "threads waiting" due to MAXDBAT reached to "Inactive
  connections waiting" due to MAXDBAT reached.
  
  KEYWORDS : MAXDBAT MDBW THREADS WAITING ON LIMIT TEP
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  UK62964 PM30844

Modules/Macros

• KO2APCAA KO2APCAS KO2APCA2 KO2CDFSA KO2CDFSS
  KO2CDFS2 KO2OXMGB KO2SMDBW KO2SYSTM KO2ZMDBW
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R420 PSY UK62964

     UP10/12/11 P F012 ®

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.