IBM Support

PI75518: NEW FUNCTION FOR REORG TABLESPACE TO PROVIDE USER CONTROL ON THENUMBER OF IMAGE COPY DATA SETS ALLOCATION 21/07/05 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • REORG was executed to convert a partitioned table space to
    Relative Page Numbers. Relative page numbers requires a
    template that allocates a separate data set for each partition.
    If the image copies are allocated to tape, then a tape drive is
    allocated for each partition. This could result in more
    allocation requests that tape drives available. If STACK YES is
    specified, then the partlevel specification is ignored and a
    single image copy is created for the full table space,
    resulting in MSGDSNU2922I PARTITION LEVEL INLINE DATASETS ARE
    NOT SPECIFIED
    
    This APAR also fixes a problem where REORG REBALANCE places rows
    into the wrong partition when PH14235 is applied. As a result of
    that, incorrect output (INCORROUT) symptoms can occur, where too
    few rows are returned with index access. In some instances, it
    can also result in rebalance failure with RC8 returned.
    To circumvent the INCORROUT and RC8 issues, either avoid running
    reorg rebalance or apply this fix (PTF UI75979).
    
    Dublicate limitkeys may be seen in the LIMITKEY column in table
    SYSIBM.SYSTABLEPART.
    
    ====================
    INCORROUT
    

Local fix

  • Allocate image copies on DASD or use dataset level FlashCopy
    images.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 for z/OS users of REORG                           *
    * TABLESPACE utility                                           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * New function for REORG TABLESPACE to                         *
    * provide user control on the number of                        *
    * image copy data sets allocation                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR introduces two new keyword options to the REORG
    TABLESPACE utility, ICLIMIT_DASD and ICLIMIT_TAPE, for user
    control on how many partition level image copy data sets REORG
    can or should allocate based on the table space being
    reorganized and the restrictions in the user environment.
    The details on the related keyword options and equivalent
    subsystem parameter changes are detailed further below.
    In addition, this APAR removes the previous restriction where
    a REORG TABLESPACE targeting a partition-by-range (PBR) table
    space with relative page numbering (RPN) must be run with
    partition level inline image copies.  Prior to this APAR,
    performing a multi-part REORG TABLESPACE against a PBR RPN
    without a valid TEMPLATE (i.e. with &PART. or &PA. specified)
    in the COPYDDN/RECOVERYDDN keyword would cause REORG to fail
    with RC8 and message DSNU2922I - PARTITION LEVEL INLINE
    DATASETS ARE NOT SPECIFIED.  This APAR removes this requirement
    and user can choose to run the REORG with one or more image
    copy datasets.
    Due to hardware restrictions (e.g. number of available tape
    drives) or virtual memory requirements on a large partitioned
    table space with many partitions, it might not always be
    feasible for REORG to allocate a separate image copy data set
    for each data partition being reorganized.  At the same time,
    reducing to a single image copy data set for all target
    partitions can result in management and recovery performance
    afterward.  As a result, two new keyword options, ICLIMIT_DASD
    and ICLIMIT_TAPE, are added to the REORG TABLESPACE utility for
    user to dictate the upper bound of the number of image copy
    data sets REORG can allocate, and REORG would use this factor
    to decide on how many partition level image copies it can
    allocate, where each image copy data set can have the data for
    one or more partitions assigned to it.
    The Utility Guide and Reference will be updated with the
    following information:
    https://www.ibm.com/docs/en/db2-for-zos/12?topic=tablespace-
    syntax-options-reorg-control-statement
    >--REORG TABLESPACE--...
       |--ICLIMIT_DASD 0---------|   |--ICLIMIT_TAPE 0---------|
    >--|-------------------------|---|-------------------------|
       |--ICLIMIT_DASD num-dasd--|   |--ICLIMIT_TAPE num-tape--|
    ICLIMIT_DASD num-dasd
    Specifies the maximum number of sequential image copies to DASD
    that REORG TABLESPACE utility can allocate. This keyword value
    takes precedence over the value specified by the
    REORG_IC_LIMIT_DASD subsystem parameter.
    num-dasd - specifies number of DASD image copies to be
               allocated. Valid value is from range of 0 to 32767.
               A value of 0 indicates that no limit is given for
               the number of DASD image copies REORG can allocate
               during its processing.
    ICLIMIT_TAPE num-tape
    Specifies the maximum number of sequential image copies to TAPE
    that REORG TABLESPACE utility can allocate. This keyword value
    takes precedence over the value specified by the
    REORG_IC_LIMIT_TAPE subsystem parameter.
    num-tape - specifies number of TAPE image copies to be
               allocated. Valid value is from range of 0 to 32767.
               A value of 0 indicates that no limit is given for
               the number of TAPE image copies REORG can allocate
               during its processing.
    _______________________________________________________________
    The following new messages added to support this REORG new
    function.  The Message Guide will be updated as follows:
    https://www.ibm.com/docs/en/db2-for-zos/12?topic=
    messages-dsnu2937i
    https://www.ibm.com/docs/en/db2-for-zos/12?topic=
    messages-dsnu2938i
    DSNU2937I csect-name - SEQUENTIAL INLINE IMAGE COPY PROCESSING
                           SUMMARY
          MAXIMUM NUMBER OF DASD IMAGE COPIES REQUIRED IS a
          MINIMUM NUMBER OF DASD IMAGE COPIES REQUIRED IS b
          ACTUAL NUMBER OF DASD IMAGE COPIES ALLOCATED IS c
          MAXIMUM NUMBER OF TAPE IMAGE COPIES REQUIRED IS d
          MINIMUM NUMBER OF TAPE IMAGE COPIES REQUIRED IS e
          ACTUAL NUMBER OF TAPE IMAGE COPIES ALLOCATED IS f
    Explanation
    This message provides a summary on the number of image copies
    being processed by the utility. For REORG TABLESPACE, refer to
    the keywords ICLIMIT_TAPE, ICLIMIT_DASD and subsystem
    parameters REORG_IC_LIMIT_TAPE and REORG_IC_LIMIT_DASD for
    additional information. The value of a and d represents the
    maximum number of image copies required by the utility during
    runtime execution, while b and e represents the minimum number
    of required image copies. The value of c and f are the actual
    number of image copies allocated.
    System action
    Utility processing continues.
    Severity
    0 (informational)
    DSNU2938I csect-name - UTILITY CANNOT ALLOCATE THE MINIMUM
    NUMBER OF REQUIRED IMAGE COPY DATA SETS DUE TO KEYWORD OR
    SUBSYSTEM PARAMETER specification
    Explanation
    The utility cannot allocate the minimum number of sequential
    inline image copy data sets required to continue execution due
    to user provided keyword or subsystem parameter values.
    For the REORG TABLESPACE utility, refer to the image copy
    summary report in message DSNU2937I for more details, and also
    the documentation for keywords ICLIMIT_TAPE, ICLIMIT_DASD and
    subsystem parameters REORG_IC_LIMIT_TAPE and
    REORG_IC_LIMIT_DASD for additional information.
    User action
    Re-run the utility by either specifying a higher limit on the
    maximum number of image copy data sets allowed, or reduce the
    number of objects or partitions to be processed by the utility.
    System action
    Utility processing terminates.
    Severity
    8 (error)
    _______________________________________________________________
    For ease of enablement, two new online changeable subsystem
    parameters are also introduced to enable this image copy limit
    without specifying the new ICLIMIT_DASD and ICLIMIT_TYPE
    keywords in the utility statement:
    REORG IC LIMIT DASD ( REORG_IC_LIMIT_DASD subsystem parameter)
    The REORG_IC_LIMIT_DASD subsystem parameter specifies the
    maximum number of sequential image copies allocated to DASD
    that the REORG TABLESPACE utility can allocate during its
    execution.
    - Value range is from 0 to 32767.
    - Default value: 0 - specifies that REORG TABLESPACE utility
      will allocate the number of DASD image copies based on the
      number of objects being reorganized without a user-imposed
      limit.
    REORG IC LIMIT TAPE ( REORG_IC_LIMIT_TAPE subsystem parameter)
    The REORG_IC_LIMIT_TAPE subsystem parameter specifies the
    maximum number of sequential image copies allocated to TAPE
    that the REORG TABLESPACE utility can allocate during its
    execution.
    - Value range is from 0 to 32767.
    - Default value: 0 - specifies that REORG TABLESPACE utility
      will allocate the number of TAPE image copies based on the
      number of objects being reorganized without a user-imposed
      limit.
    

Problem conclusion

Temporary fix

Comments

  • Code has been modified to introduce the aforementioned
    new function to the REORG TABLESPACE utility.
    

APAR Information

  • APAR number

    PI75518

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED UR1

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-26

  • Closed date

    2021-06-18

  • Last modified date

    2022-02-11

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

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

    UI75979

Modules/Macros

  • DSNTINMF DSNURBID DSNDQWPZ DSNURSWD DSNWZIFC DSNTIDXA DSNTIVMD
    DSNURWBR DSNTIJUZ DSNTINST DSNTIDXC DSNTIWIA DSNTIDXB DSNTIVIA
    DSNTIWMD DSNUGBAC DSNTIWIE DSNTIVIE DSNURCCP DSNFUDRE DSNURECS
    DSNUGPRV DSN@XAZP DSNUGPRS DSNUGPRT DSN6SPRM DSNUGDDM DSNTXAZP
    DSNURPCT DSNTIWPC DSNTIP63 DSNDSPRM DSNURORG DSNURSLD DSNUGUTC
    DSNFUDIR DSNURPDC DSNTIVMN DSNTIWMN DSNTIVAF DSNTIVIN DSNTIWMS
    DSNTIVMS DSNTIWAF DSNTIWIN DSNUMSGE DSNUGUCA
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI75979

       UP21/06/26 P F106

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0"}]

Document Information

Modified date:
12 February 2022