IBM Support

PM76803: REORG TS - INCORRECT JOB BREAKDOWN FOR GROUP PARTITIONS BY STEP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When specifying "Group Partitions By Step" on TS REORG utility
    profile, the job breakdown is incorrect after building the job.
    Prior to this fix, specifying Group Partitions By "S" (Step)
    works as if Group Partitions By "J" (Job) were specified.
    A difference between Job and Step is described below:
    .
    Group Partitions By "J" specifies that all partitions of a
    partitioned object are to be grouped together in the same Job.
    The partitioned objects will be grouped into one step within
    that job.  Objects will not be split across multiple jobs even
    though this might exceed other job breakdown values.
    .
    Group Partitions By "S" specifies that all partitions of a
    partitioned object are to be grouped together in the same Step.
    Like the "J" option, this might override other job breakdown
    values.  Using this option, partitions of a partitioned object
    might be split across multiple jobs as required by job breakdown
    values.  However, all related partitioned objects will be
    grouped together in the same step within each job.  When
    REORGing partitioned objects with Non-Partitioning Indexes
    (NPIs) using DB2 V9+, specifying "J" prevents DB2 from shadowing
    the NPIs more than once.
    .
    Group Partitions By "N" specifies that grouping of partitioned
    objects is not required.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Automation Tool.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: When specifying "Group Partitions By    *
    *                      Step" on TS REORG utility profile, the  *
    *                      job breakdown is incorrect after        *
    *                      building the job. Prior to this fix,    *
    *                      specifying Group Partitions By "S"      *
    *                      (Step) works as if Group Partitions     *
    *                      By "J" (Job) were specified. A          *
    *                      difference between Job and Step is      *
    *                      described below:                        *
    *                      Group Partitions By "J" specifies that  *
    *                      all partitions of a partitioned object  *
    *                      are to be grouped together in the same  *
    *                      Job. The partitioned objects will be    *
    *                      grouped into one step within that job.  *
    *                      Objects will not be split across        *
    *                      multiple jobs even though this might    *
    *                      exceed other job breakdown values.      *
    *                      Group Partitions By "S" specifies that  *
    *                      all partitions of a partitioned object  *
    *                      are to be grouped together in the same  *
    *                      Step. Like the "J" option, this might   *
    *                      override other job breakdown values.    *
    *                      Using this option, partitions of a      *
    *                      partitioned object might be split       *
    *                      across multiple jobs as required by     *
    *                      job breakdown values.  However, all     *
    *                      related partitioned objects will be     *
    *                      grouped together in the same step       *
    *                      within each job.  When REORGing         *
    *                      partitioned objects with                *
    *                      Non-Partitioning Indexes (NPIs) using   *
    *                      DB2 V9+, specifying "J" prevents DB2    *
    *                      from shadowing the NPIs more than once. *
    *                      Group Partitions By "N" specifies that  *
    *                      grouping of partitioned objects is not  *
    *                      required.                               *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM76803

  • Reported component name

    DB2 AUTOMATION

  • Reported component ID

    5697G6300

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-11-08

  • Closed date

    2013-04-22

  • Last modified date

    2013-05-06

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

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

    PM76852 UK93686

Modules/Macros

  •    HAA$BMSG HAA$BULJ HAA$BUTR HAA$BUTT HAA$CALL
    HAA$CVT  HAA$DCVT HAA$EXPF HAA$IMPF HAA$JBRK HAA$UOPT HAA#BPRI
    HAA#UPRI HAA#UTED HAA#UTOP HAAHUREO HAAHVREO HAAREORC HAA586E
    

Fix information

  • Fixed component name

    DB2 AUTOMATION

  • Fixed component ID

    5697G6300

Applicable component levels

  • R310 PSY UK93686

       UP13/04/30 P F304

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310"}]

Document Information

Modified date:
30 March 2021