PM27064: (26460) MISSING THREAD LOCK WAIT DATA FROM PANEL ZLOCKW

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• (26460) Missing thread lock wait data from panel  ZLOCKW
  (26484) Lock number is different from V410 and V510
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   OMEGAMON collector                       *
  *                 -   Classic Interface                        *
  *                 -   CUA Interface                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. Missing thread lock wait data on     *
  *                      panel ZLOCKW                            *
  *                      2. Incorrect total locks owned on panel *
  *                      ZLOCKO.                                 *
  *                      3. D5API task ACON showed high CPU due  *
  *                      to abend in XTHS                        *
  *                      4. incorrect lock status in thread      *
  *                      display                                 *
  *                      5. incorrect # to repeat lock timeout   *
  *                      was displayed on panel ZLOCKW           *
  *                      6. LKUS exception triggered incorrectly *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  *                                                              *
  ****************************************************************
  PROBLEM SUMMARY:
  1. No lock wait data were collected
  2. Some of locks related to partition datasets were not
  collected.
  3. Repeating abends from XTHS caused high CPU in D5API
  ACON sub-task.
  4. Thread status for waiter threads were not set correctly.
  5. Incorrect lock timeout multiplier was collected
  6. Incorrect lock count field was used to trigger the LKUS
  exception
  
  PROBLEM CONCLUSION:
  1. Collected lock wait data when it is available.
  2. Collected locks owned data related to partitioned datasets.
  3. Corrected logical error to avoid abend in XTHS.
  4. Set thread lock status accordingly.
  5. Used the correct lock timeout multiplier in display.
  6. Used page/row locks owned to trigger thread LKUS exception
  

Problem conclusion

• 1. Collected lock wait data when it is available.
  2. Collected locks owned data related to partitioned datasets.
  3. Corrected logical error to avoid abend in XTHS.
  4. Set thread lock status accordingly.
  5. Used the correct lock timeout multiplier in display.
  6. Used page/row locks owned to trigger thread LKUS exception
  
  KEYWORDS : XTHS LKUS LOCK LOCKS
  

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:

  UK63274

Modules/Macros

• FPEVDB2F KO2APCBA KO2APCBK KO2APCB2 KO2APCNA
  KO2APCNK KO2APCN2 KO2APC9A KO2APC9K KO2APC92 KO2CIF3A KO2CIF3K
  KO2CIF32 KO2CLKDA KO2CLKDK KO2CLKD2 KO2CTHBA KO2CTHBK KO2CTHB2
  KO2CTHEA KO2CTHEK KO2CTHE2 KO2CTHOA KO2CTHOK KO2CTHO2 KO2CTHSA
  KO2CTHSK KO2CTHS2 KO2NCSTB KO2NDRVB KO2ODINB KO2OLOKB KO2OTHLB
  KO2OXSYB KO2OXTHB KO2XLKDA KO2XLKDK KO2XLKD2 KO2XTHSA KO2XTHSK
  KO2XTHS2 KO2ZLOCH
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R510 PSY UK63274

     UP10/12/21 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.