IBM Support

PM56725: DB2 V10 INCREASE IN DBM1 TCB TIME AND OPEN/CLOSE ACTIVITY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Increase in DBM1 TCB times and dataset open / close activity
    after migrating to DB2 v10 CM9.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 users.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Excessive dataset open/close activity,  *
    *                      resulting in increased CPU time for the *
    *                      DBM1 address space.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The deferred close process (responsible for closing excess data
    sets when DSMAX has been exceeded) builds a large candidate list
    which it may continue using for a long period of time (several
    hours).  Since this list is ordered by last-referenced time at
    the time the list was built, and the closing of candidates does
    not check to see if the reference time has changed, the order
    of closing datasets becomes less and less an LRU process the
    longer the list remains active.  This may result in incorrectly
    closing datasets which are currently being frequently accessed,
    rather than others which are not currently being used.  This
    may be particularly noticable if the list is built while one
    type of workload is being run (e.g. overnight batch jobs) but
    is still being used while another type of workload is being
    run (e.g. daytime online transactions).
    

Problem conclusion

  • The deferred close process has been modified to skip datasets
    on its candidate list which have been referenced since the time
    the list was built.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM56725

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-01-25

  • Closed date

    2012-03-27

  • Last modified date

    2012-05-02

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

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

    UK77298 UK77309

Modules/Macros

  • DSNB1DRN
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK77298

       UP12/04/12 P F204

  • R910 PSY UK77309

       UP12/04/12 P F204

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:
02 May 2012