IBM Support

PH27043: RECOVER UTILITY ENHANCEMENT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

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:                                                     *
    * 1. To support redirected recovery                            *
    *    of table spaces using the recovery                        *
    *    resources (image copies and Db2                           *
    *    logs) of different table spaces.                          *
    *    This feature is available at                              *
    *    function level 500 or higher.                             *
    * 2. To issue two new informational                            *
    *    messages.                                                 *
    * 3. To write the IFCID 24 trace record                        *
    *    once per object at the end of                             *
    *    certain log processing phases with                        *
    *    the number of log records applied                         *
    *    for each object.                                          *
    ****************************************************************
    * 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 table spaces and 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.
      The RECOVER utility does not give an indication of the
    recovery point (log point) -or- the number of log records read
    and applied.   Two new messages and a change to the IFCID 24
    trace record will now provide useful information for customers,
    ISV tools and serviceability.
    

Problem conclusion

Temporary fix

Comments

  • With this APAR:
    1. The syntax of the RECOVER utility is enhanced with the
       new FROM option which allows a target table space and a
       source table space to be specified at function level 500
       or higher. Specification of this new syntax indicates a
       redirected recovery.
    2. This change applies to both recovery and redirected
       recovery:  The RECOVER utility can issue these two new
       informational messages to the job output -
       - DSNU1568I csect-name - phase-name PHASE: n LOG RECORDS
           READ, m LOG RECORDS APPLIED
         Explanation:
           During the indicated log processing phase, the RECOVER
         utility read and might have applied the number of log
         records listed.
           For a data sharing group, this message is issued once
         for each member with logs to process in the PRELOGC,
         LOGCSR, or LOGUNDO phases. This message is issued only
         once in the PRELOGA and LOGAPPLY phases.
           For RESTART(CURRENT) in the LOGAPPLY phase, the number
         of log records read and applied will be larger than for
         non-restart processing, because some of the log records
         are read and processed again.
         csect-name:
           The name of the control section that issued the
         message.
         phase-name:
           The name of the RECOVER log phase. Possible values are
         PRELOGC, PRELOGA, LOGAPPLY, LOGCSR or LOGUNDO.
         n:
           The number of log records read. For recovery to the
         current state, this number includes only REDO type data
         manipulation log records. For recovery to a point in
         time, this number includes all log records.
         m:
           The number of log records applied.
         System action:
           Processing continues.
         User response:
           No action is required.
         Severity:
           0 (informational)
       - DSNU1569I csect-name - RECOVERY LOGPOINT IS
           X'recovery-point'
         Explanation:
           Objects will be recovered to the reported log point.
         For recovery to a point in time or for redirected
         recovery (to a point in time or to the current state),
         uncommitted work by units of recovery that are active
         at the LRSN or RBA on the source objects will be backed
         out on the target objects by RECOVER. This action
         ensures that each target object is left in a consistent
         state.
         csect-name:
           The name of the control section that issued the
         message.
         X'recovery-point':
           The recovery point in the log. This hexadecimal value
         is an RBA for standalone Db2 subsystems or an LRSN for
         members of a Db2 data sharing group.
           For recovery to the current state, this value is the
         current RBA or LRSN during RECOVER utility
         initialization.
         System action:
           Processing continues.
         User response:
           No action is required.
         Severity:
           0 (informational)
    3. This change applies to both recovery and redirected
       recovery: The IFCID 24 trace record written for the phase
       change after the PRELOGA, LOGAPPLY, or LOGUNDO phases will
       now be written once per object being recovered instead of
       just once for the phase change.  Field QW0024DN will
       contain the number of log records applied for the object.
    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/support/knowledgecenter/SSEPEK_12.0.0/
    wnew/src/tpc/db2z_12_enhancements.html
    

APAR Information

  • APAR number

    PH27043

  • 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

    2020-07-01

  • Closed date

    2020-10-13

  • Last modified date

    2020-11-02

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

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

    UI72057

Modules/Macros

  • DSNUCBMT DSNUCACL DSNUCALU DSNUCAIN DSNUGDDL DSNINTRA DSNUCARS
    DSNUGIFC DSNUGRAR DSNUCATM DSNISCHV DSNUCATO DSNUCALA DSNUCALC
    DSNUCADP DSNUCBAL DSNUGUCA DSNUCALZ DSNUCASA DSNUCACR DSNUCBDR
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI72057

       UP20/10/22 P F010

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0"}]

Document Information

Modified date:
31 March 2021