IBM Support

PM66173: STORAGE LEAK IN THE BB1RMID POOL OF TRQ'S . THIS MIGHT SHOW UP AS LC23 AND LC32 CONTENTION OR PAGE LATCH CONTENTION.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Storage leak in the BB1RMID POOL of TRQ's . This might show up
    as LC23 and LC32 contention or page latch contention.
    Storage leak is for page P-LOCK exit acquiered TRQ's .
    The DUMP wil typically show lots of entries for x'50' long
    TRQ blocks that have a TRQNEXT pointing to itself and a
    TRQWAIT value of 5000. This could cause fragmentation of
    the POOL, which in turn might cause DSNSVBK to run down long
    chains in the POOL, trying to fit the next block in.
    .
    DB2STGLK/K
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 data sharing users.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Storage leak in a buffer manager pool,  *
    *                      where timer wait control blocks used    *
    *                      by the page P-lock exit are lost.       *
    *                      This can result in fragmentation of the *
    *                      pool, which can increase wait time for  *
    *                      page latches, latch class 23, or latch  *
    *                      class 32.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The page P-lock exit employs a two-phase page latch wait, where
    the timer wait control block (TRQ) may need to be reinserted in
    the queue after an initial timeout.  The reinsert logic fails to
    reset a link pointer, which may result in the TRQ being dropped
    off the queue entirely.
    

Problem conclusion

  • The TRQ reinsert logic has been modified to ensure that the
    residual link pointer is cleared.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM66173

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-05

  • Closed date

    2012-07-25

  • Last modified date

    2012-09-05

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

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

    UK80522

Modules/Macros

  • DSNB1TMR
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK80522

       UP12/08/09 P F208

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":"10.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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
05 September 2012