IBM Support

PK13831: ALLOW EXCEPTION PROFILES TO COMBINE INDEX AND TABLESPACE CRITERIA

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Currently all INDEX exception criteria is applied to INDEXES and
    TABLESPACE criteria is applied to TABLESPACES.  This enhancement
    will
    allow some exceptions for INDEXES and some exceptions for
    TABLESPACES
    to be considered together.
    A new field has been added to panel HAA$EPRU:
    "Combine IX/TS Exceptions when evaluating IX triggering a TS"
    This field will have a default value of "N", allowing exceptions
    to be
    processed as before this enhancement.  Setting the flag to "Y"
    will
    allow Index and Tablespace criteria to be applied together.
    For example, the CLUSTERRATIO for the clustering INDEX and the
    allocated TRACKS of the corresponding TABLESPACE could be
    considered
    together when determining when to trigger a TABLESPACE REORG.
    NOTE:
    This feature is active ONLY when evaluating INDEX conditions
    that
    trigger the associated TABLESPACE (CLUSTERRATIO, CLUSTERRATIOF,
    xxxxOFFPOS/F). If a TABLESPACE meets its exception criteria, the
    TABLESPACE will be triggered regardless of the associated INDEX
    criteria. In other words, only when evaluating INDEX criteria do
    both
    the INDEX and associated TABLESPACE criteria have to be met.
    This
    prevents ONLY the INDEX criteria from triggering a TABLESPACE.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Automation Tool.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Currently all INDEX exception criteria  *
    *                      is applied to INDEXES and TABLESPACE    *
    *                      criteria is applied to TABLESPACES.     *
    *                      This enhancement will allow some        *
    *                      exceptions for INDEXES and some         *
    *                      exceptions for TABLESPACES  to be       *
    *                      considered together. A new field has    *
    *                      been added to panel HAA$EPRU:           *
    *                      "Combine IX/TS Exceptions when          *
    *                      evaluating IX triggering a TS"          *
    *                      This field will have a default value    *
    *                      of "N", allowing exceptions to be       *
    *                      processed as before this enhancement.   *
    *                      Setting the flag to "Y" will allow      *
    *                      Index and Tablespace criteria to be     *
    *                      applied together. For example, the      *
    *                      CLUSTERRATIO for the clustering INDEX   *
    *                      and the allocated TRACKS of the         *
    *                      corresponding TABLESPACE could be       *
    *                      considered together when determining    *
    *                      when to trigger a TABLESPACE REORG.     *
    *                      NOTE: This feature is active ONLY when  *
    *                      evaluating INDEX conditions that        *
    *                      trigger the associated TABLESPACE       *
    *                      (CLUSTERRATIO, CLUSTERRATIOF,           *
    *                      xxxxOFFPOS/F). If a TABLESPACE meets    *
    *                      its exception criteria, the TABLESPACE  *
    *                      will be triggered regardless of the     *
    *                      associated INDEX criteria. In other     *
    *                      words, only when evaluating INDEX       *
    *                      criteria do both  the INDEX and         *
    *                      associated TABLESPACE criteria have to  *
    *                      be met. This prevents ONLY the INDEX    *
    *                      criteria from triggering a TABLESPACE.  *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

Temporary fix

Comments

  • APPLY the PTF.
    

APAR Information

  • APAR number

    PK13831

  • Reported component name

    DB2 AUTOMATION

  • Reported component ID

    5697G6300

  • Reported release

    220

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2005-10-20

  • Closed date

    2006-03-15

  • Last modified date

    2006-04-05

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

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

Modules/Macros

  • HAATEMPC
    

Fix information

  • Fixed component name

    DB2 AUTOMATION

  • Fixed component ID

    5697G6300

Applicable component levels

  • R220 PSY UK12647

       UP06/03/18 P F603

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

Document Information

Modified date:
12 February 2021