IBM Support

PK60863: EXCEPTION PROCESSING WITH RUNSTATS NOT TRIGGERING SOME IXS WHEN TS HAS MULTIPLE IXS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a TS has more than one IX, the 2nd through n IX, such as
    NPIs on a partitioned TS, may not be triggered even though they
    meet all the Exception Conditions. This happens only when
    Exception Processing executes Runstats to obtain current
    Runstats statistics. The Runstats statistics nodes for the
    subsequent IXs were created with the incorrect IXSPACE name
    those causingo be incorrectly deleted as duplicates.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Automation Tool.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a TS has more than one IX, the     *
    *                      2nd through n IX, such as NPIs on a     *
    *                      partitioned TS, may not be triggered    *
    *                      even though they meet all the Exception *
    *                      Conditions. This happens only when      *
    *                      Exception Processing executes Runstats  *
    *                      to obtain current Runstats statistics.  *
    *                      The Runstats statistics nodes for the   *
    *                      subsequent IXs were created with the    *
    *                      incorrect IXSPACE name those causing    *
    *                      to be incorrectly deleted as            *
    *                      duplicates.                             *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK60863

  • Reported component name

    DB2 AUTOMATION

  • Reported component ID

    5697G6300

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-02-11

  • Closed date

    2008-07-17

  • Last modified date

    2008-08-02

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

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

    UK38232

Modules/Macros

  • HAA$ERRS
    

Fix information

  • Fixed component name

    DB2 AUTOMATION

  • Fixed component ID

    5697G6300

Applicable component levels

  • R220 PSY UK38232

       UP08/07/23 P F807

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