IBM Support

PM41874: ADD OPTION TO CREATE INDEX RUNSTATS AT THE PARTITION LEVEL AS PART OF TABLESPACE RUNSTATS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Add on option on the Runstats Utility Panel to indicate that
    Runstats are to be generated at the partition level for indexes.
    Currently, the only option for generating Runstats for indexes
    while generating Runstats for tablespaces is to use INDEX(ALL).
    This new option will allow partition level index Runstats as
    part of the Tablespace Runstats.  For example:
    RUNSTATS TABLESPACE DBNAME.TSNAME
    PART 3
    INDEX(DBNAME.IDXNAME PART 3)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Automation Tool                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Add on option on the Runstats Utility   *
    *                      Panel to indicate that Runstats are to  *
    *                      be generated at the partition level     *
    *                      for indexes. Currently, the only        *
    *                      option for generating Runstats for      *
    *                      indexes while generating Runstats for   *
    *                      tablespaces is to use INDEX(ALL).       *
    *                      This new option will allow partition    *
    *                      level index Runstats as part of the     *
    *                      Tablespace Runstats.  For example:      *
    *                      RUNSTATS TABLESPACE DBNAME.TSNAME       *
    *                      PART 3                                  *
    *                      INDEX(DBNAME.IDXNAME PART 3)            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

  • Apply the PTF.
    

APAR Information

  • APAR number

    PM41874

  • Reported component name

    DB2 AUTOMATION

  • Reported component ID

    5697G6300

  • Reported release

    310

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-16

  • Closed date

    2011-12-06

  • Last modified date

    2012-01-01

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

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

    UK74526

Modules/Macros

  • HAA$BMSG HAA$BUTT HAA$URST HAA$VRST HAA#OBEX
    HAA#UPRI HAA#UTED HAA#UTOB HAABTMP  HAAHURST HAAHVRST HAARUNSC
    HAA37    HAA375E  HAA56    HAA569E  HAA58    HAA585E
    

Fix information

  • Fixed component name

    DB2 AUTOMATION

  • Fixed component ID

    5697G6300

Applicable component levels

  • R310 PSY UK74526

       UP11/12/17 P F112

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":"SSAUWB","label":"IBM Db2 Automation Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","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":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
12 February 2021