IBM Support

PH35266: RECOVER UTILITY FUTURE ENHANCEMENT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • Code to support future enhancement to the RECOVER utility
    Ref: E15907 E1554
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 for z/OS users of the RECOVER                     *
    * utility.                                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * This APAR enhances the RECOVER                               *
    * utility:                                                     *
    *    To support redirected recovery                            *
    *    of index spaces and indexes using                         *
    *    the recovery resources (image                             *
    *    copies and Db2 logs) of different                         *
    *    index spaces and indexes.                                 *
    *    This feature is available at                              *
    *    function level 500 or higher.                             *
    * Previously, this capability was only                         *
    * allowed on table spaces (see APAR                            *
    * PH27043).                                                    *
    * This APAR also contains fixes for                            *
    * several issues with redirected                               *
    * recovery on table spaces.                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Testing the recovery of production data without impacting
    the data and applications can be time consuming and complex. A
    safe, easier method is needed to run test recoveries - without
    affecting production index spaces or indexes, with no impact to
    production applications - to determine with accuracy how long
    the recoveries will take, to check for recovery issues, for
    review or forensic analysis of production data, and for
    generating data at different points in time with transactional
    consistency.  Redirected recovery is needed for index spaces
    and indexes.
    This APAR also addresses the following issues with redirected
    recovery on table spaces: (Items 1 through 4 are not
    supported.)
    1. Concurrent image copies were allowed to be used as a
       recovery base.
    2. If the source table space was not defined (DEFINE NO) and
       the target table space was defined, redirected recovery was
       allowed.
    3. Redirected recovery was allowed on XML table spaces whose
       base table was not in a universal table space (UTS).
    4. It was not detected if the target and source table columns
       have different NULL or DEFAULT attributes.
    5. The DSNU1569I - RECOVERY LOGPOINT - message was issued
       for recoveries with the TOCOPY, TOLASTCOPY, or
       TOLASTFULLCOPY option.  This message should not be issued
       when one of these options is specified because for fuzzy
       copies created with COPY SHRLEVEL CHANGE, the recovery log
       point is indeterminate.
    6. When the DSNU181I - RESTART NOT ALLOWED - message was issued
       for redirected recovery on a table space, it is followed by
       an ABEND04E RC00E40018.  The SVC dump for this abend should
       be suppressed but it was not.
    

Problem conclusion

Temporary fix

Comments

  • With this APAR:
       The FROM option of the RECOVER utility is enhanced to
       allow a target index space or index -and- a
       source index space or index to be specified at function
       level 500 or higher. Specification of this syntax
       indicates a redirected recovery.  Both the source and
       target index spaces or indexes must have the COPY YES
       attribute.
    The external changes described in APAR PH27043, the enabling
    APAR for redirected recovery on table spaces, also apply to
    redirected recovery on index spaces and indexes.
    This APAR has fixed the following issues with redirected
    recovery on table spaces.
    1. Concurrent image copies are not allowed to be used as a
       recovery base.  Message DSNU508I - IN FALLBACK PROCESSING
       TO PRIOR IMAGE COPY - is now issued when a concurrent
       copy is encountered by redirected recovery.( MSGDSNU508I )
    2. If the source table space is not defined (DEFINE NO),
       message DSNU185I - THE VSAM DATA SET DOES NOT EXIST - will
       now be issued.  ( MSGDSNU185I )
    3. Redirected recovery will not be allowed on XML table
       spaces whose base table is not in a UTS. Error message
       DSNU1564I - UTILITY NOT SUPPORTED - is now issued for this
       case.  ( MSGDSNU1564I )
    4. If target and source table columns have different NULL or
       DEFAULT attributes, error message DSNU1567I - DEFINITION
       OF TARGET DIFFERS FROM SOURCE - is issued.
       ( MSGDSNU1567I )
    5. For recoveries with the TOCOPY, TOLASTCOPY, or
       TOLASTFULLCOPY option specified, MSGDSNU1569I RECOVERY
       LOGPOINT, is no longer issued.
    6. The SVC dump for the ABEND04E RC00E40018 is now suppressed
       after MSGDSNU181I is issued for redirected recovery.
    Note: The text of error message DSNU1564I - utility-name
    UTILITY IS NOT SUPPORTED FOR type - has been revised
    by this APAR.  In addition, new error texts have been added
    to the DSNU1567I - DEFINITION OF TARGET DIFFERS FROM SOURCE:
    mismatch information - message to describe the differences in
    the definition for target and source indexes and index
    spaces.  (The revisions can be seen at the Db2 product
    documentation website.)
    
    The Db2 product documentation is updated for these changes.
    For more information about the new feature delivered in this
    APAR see:
    https://www.ibm.com/docs/en/
    db2-for-zos/12?topic=12-recent-enhancements-db2
    

APAR Information

  • APAR number

    PH35266

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-03-11

  • Closed date

    2021-06-23

  • Last modified date

    2021-08-02

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

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

    UI76045

Modules/Macros

  • DSNGDAIX DSNUCAIN DSNUGPPL DSNUGSRI DSNUCARS DSNUCASV DSNUCBVR
    DSNFUDIR DSNUGTER DSNUGTE0 DSNUCATM DSNUIEPL DSNUCALA DSN1SYSX
    DSNUCALC DSNFUDRE DSNUMSGE DSNUGUCA DSNUCASA DSNUCACR
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI76045

       UP21/07/02 P F107

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:
03 August 2021