IBM Support

PH31775: A LINEAR INDEX WITH > 255 PIECES IS NOT RECOVERED BY RESTORE SYSTEM UTILITY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A linear index with more than 255 pieces is not recovered by
    the RESTORE SYSTEM utility and during RESTORE SYSTEM to open
    object MSGDSNP012I message shows bad VSAM catalog name:
    
    DSNI040I -CEB2 DSNIRSTR RESTORE SYSTEM UTILITY
              PROCESSING LOG RANGE FROM LRSN 00D7BB8123AE17613A00 TO
              00D830232D71A5523800
     DSNP012I -CEB2 DSNPCNP0 - ERROR IN ICF CATALOG
              LOCATE FUNCTION FOR DSNDBC.TPCEB100.TEHHIX2.I0001.A001
              CTLGRC=AAAAAA08
              CTLGRSN=AAAAAA08
              CONNECTION-ID=UTILITY, CORRELATION-ID=RESTORC,
              LUW-ID=DSNCEB0.DSNCEB2.D830232D5D25=4
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 for z/OS users.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * DSNP012I DSNPCNP0 - ERROR IN ICF                             *
    * CATALOG for non-partitioned index                            *
    * with more than 255 pieces opened                             *
    * during RESTORE SYSTEM.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    During the Restore System log apply phase, incorrect VCAT name
    was specified when opening non-partitioned index with more
    than 255 pieces. This results in Data Space Manager unable to
    find the data set in ICF catalog, and the non-partitioned
    index was not recovered by RESTORE SYSTEM utility.
    The VCAT value came from the PAGE SET OPEN log records. The
    problem for the PAGE SET OPEN log record is that for the
    non-partitioned index overflow will happen when the number of
    pieces opened is greater than 255. The PAGE SET OPEN log
    record will be truncated so the VCAT name information isn't in
    the log record.
    

Problem conclusion

  • Db2 code has been modified to write multiple PAGE SET OPEN log
    records when the pageset has more than 255 pieces so as to
    avoid the issue mentioned above.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PH31775

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-11-17

  • Closed date

    2022-01-05

  • Last modified date

    2022-02-01

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

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

    UI78823

Modules/Macros

  • DSNB1SSR
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI78823

       UP22/01/13 P F201 ¢

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:
02 February 2022