IBM Support

PH22838: GETPAGES COLUMN OF SYSINDEXSPACESTATS AND SYSTABLESPACESTATS CANMAX OUT AND NOT GET INCREMENTED WITH SUBSEQUENT GETPAGE REQUESTS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The GETPAGES column of SYSINDEXSPACESTATS and SYSTABLESPACESTATS
    can be incremented up to the maximum positive integer for BIGINT
    and will remain at that value even if future getpage requests
    continue to occur for that object.  Programs relying on the
    GETPAGES column value to monitor getpage activity can
    encounter a problem once the maximum positive integer value
    for BIGINT is reached, before the next REORG utility job is
    run on the object.
    

Local fix

  • One possible bypass is to run the REORG utility on the object
    before the GETPAGE value hits the maximum positive BIGINT
    value.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Db2 for z/OS V12 users of Real Time                          *
    * Statistics who monitor GETPAGES activity.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * GETPAGES in SYSTABLESPACESTATS and                           *
    * SYSINDEXSPACESTATS remain at the                             *
    * maximum positive value of                                    *
    * +9,223,372,036,854,775,807.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    Internal counters for GETPAGE activity are aggregated for the
    corresponding object in SYSTABLESPACESTATS and
    SYSINDEXSPACESTATS. If the maximum positive value of
    +9,223,372,036,854,775,807 has been reached then it will remain
    at that value until the next REORG on the corresponding object.
    This prevents users from being able to monitor any ongoing
    GETPAGE activity because the value is now static at the
    maximum value.
    

Problem conclusion

  • Db2 code is changed to allow the GETPAGES column value to
    wraparound from the maximum positive value of
    +9,223,372,036,854,775,807 to +1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH22838

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-03-02

  • Closed date

    2020-06-17

  • Last modified date

    2020-07-06

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

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

    UI70107

Modules/Macros

  • DSNIRTSX
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI70107

       UP20/06/25 P F006

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
07 July 2020