PM41863: NEW EXCEPTION PROCESSING RUNSTATS OPTION PROCESS NPIS TO CONTROL COLLECTION OF NPI STATISTICS.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• A new "PROCESS NPIs" field is added to the HAA$ERST Runstats
  Options panel (Exception Condition Processing Runstats Options)
  that enables a user to fully control whether statistics are
  gathered for non-partitioning indexes (NPIs).  When Objects are
  at the PART level, Runstats parameters get created with the PART
  nnnnn keyword.  However, a bug in the current code does not
  generate the PART keyword for the first generated partitioned
  Index, thereby gathering Runstats statistics on ALL Index
  Partitions, and it also generates the NPIs as well. The PROCESS
  NPIs field controls the generation of the INDEX keyword Runstats
  parameters for NPIs.  Allowable values are:
  - A (Automatic) to indicate that you want Exception Processing
    to determine whether or not to collect statistics for
  determine whether or not to collect statistics for
  Non-Partitioning Indexes (NPIs) based on the following criteria:
  1) Statistics will be collected when ALL partitions for an
     Object are included in the Objects Profiles
  2) Statistics will not be collected when only SOME of the parts
     (a subset) are included in the Objects Profiles, i.e., when
  there are missing parts for an Object;  this can occur when:
  
  a) Objects are at the PART Level and only a subset of all the
     partitions are selected in the Objects Profiles; for example,
     only parts 2, 5, and 9 are included in the Objects Profiles;
  b) Individual partitions are specifically EXCluded by using the
     EXCluded indicator in the Objects Profiles.
  - Y (Yes) to always collect NPI statistics regardless of the
     above criteria.
  - N (No) to not collect NPI statistics.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Automation Tool.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: A new "PROCESS NPIs" field is added to  *
  *                      the HAA$ERST Runstats Options panel     *
  *                      (Exception Condition Processing         *
  *                      Runstats Options) that enables a user   *
  *                      to fully control whether statistics     *
  *                      are gathered for non-partitioning       *
  *                      indexes (NPIs).  When Objects are at    *
  *                      the PART level, Runstats parameters     *
  *                      get created with the PART nnnnn         *
  *                      keyword.  However, a bug in the current *
  *                      code does not generate the PART         *
  *                      keyword for the first generated         *
  *                      partitioned Index, thereby gathering    *
  *                      Runstats statistics on ALL Index        *
  *                      Partitions, and it also generates the   *
  *                      NPIs as well. The PROCESS NPIs field    *
  *                      controls the generation of the INDEX    *
  *                      keyword Runstats parameters for NPIs.   *
  *                      Allowable values are:                   *
  *                      - A (Automatic) to indicate that you    *
  *                       want Exception Processing to determine *
  *                       whether or not to collect statistics   *
  *                       for Non-Partitioning Indexes (NPIs)    *
  *                       based on the following criteria:       *
  *                      1. Statistics will be collected when    *
  *                         ALL partitions for an Object are     *
  *                         included in the Objects Profiles     *
  *                      2. Statistics will not be collected     *
  *                         when only SOME of the parts (a       *
  *                         subset) are included in the Objects  *
  *                         Profiles, i.e., when there are       *
  *                         missing parts for an Object;  this   *
  *                         can occur when:                      *
  *                      a. Objects are at the PART Level and    *
  *                         only a subset of all the partitions  *
  *                         are selected in the Objects          *
  *                         Profiles; for example,               *
  *                         only parts 2, 5, and 9 are included  *
  *                         in the Objects Profiles;             *
  *                      b. Individual partitions are            *
  *                         specifically EXCluded by using the   *
  *                         EXCluded indicator in the Objects    *
  *                         Profiles.                            *
  *                      - Y (Yes) to always collect NPI         *
  *                         statistics regardless of the         *
  *                         above criteria.                      *
  *                      - N (No) to not collect NPI statistics. *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

Temporary fix

Comments

• APPLY the PTF.
  

APAR Information

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

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

Modules/Macros

• HAA53
  

Fix information

• Fixed component name

  DB2 AUTOMATION

• Fixed component ID

  5697G6300

Applicable component levels

• R310 PSY UK73166

     UP11/10/29 P F110

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.