IBM Support

PM82111: RECOVER FAILS TO RECOGNIZE HSM ERROR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Recover of an object using a system level back up failed with
    ABEND04E RC00D10307 and RC00E40106. There was a problem with the
    HSM restore of the data set:
    
    ARC1860I THE FOLLOWING 0001 DATA SET(S) FAILED DURING 951
    
    ARC1860I (CONT.) FAST REPLICATION DATA SET RECOVERY:
    ARC1860I (CONT.) hlq.DSNDBC.dbname.tsname.I0001.A001,
    COPYPOOL=cpname, DEVTYPE=TAPE, VOLUME=095030, ARC1866,
    RC=32
    ARC1802I FAST REPLICATION DATA SET RECOVERY HAS 953
    ARC1802I (CONT.) COMPLETED FOR DATA SET
    ARC1802I (CONT.) hlq.DSNDBC.dbname.tsname.I0001.A001,
    AT 22:08:37
    ARC1802I (CONT.) ON 2013/01/17, FUNCTION RC=0008, MAXIMUM DATA
    SET
    ARC1802I (CONT.) RC=0066
    
    DB2 ignored the MSGARC1860I and the RC0066 and attempted to
    continue the recovery.
    
    Additional symptoms:
    ABEND0C4 RC00000010 DSNB1GET OFFSET09C4
    
    Additional keywords:
    DB2OVRLAY/K
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
    *                 users of RECOVER utility on objects being    *
    *                 restored from a system level backup          *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND04E RC00D10307 RC00C90070          *
    *                      MSGARC1801I MSGARC1860I MSGARC1802I     *
    *                      ARC1866 RC=32 on RECOVER utility        *
    *                      on an object which is restored          *
    *                      from a system level backup              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
      User ran RECOVER utility on a non-partitioned object whose
    recovery base was a system level backup (SLB).  During HSM
    processing of the data set the following messages were issued:
    ARC1801I FAST REPLICATION DATA SET RECOVERY IS
    ARC1801I (CONT.) STARTING FOR DATA SET
    ARC1801I (CONT.) aaaa.DSNDBC.bbbbbbb.cccccccc.I0001.A001,
    ARC1801I (CONT.) AT hh:mm:ss ON yyyy/mm/dd
    ARC1860I THE FOLLOWING 0001 DATA SET(S) FAILED DURING
    ARC1860I (CONT.) FAST REPLICATION DATA SET RECOVERY:
    ARC1860I (CONT.) aaaa.DSNDBC.bbbbbbb.cccccccc.I0001.A001,
    COPYPOOL=DSN$PZ$DB, DEVTYPE=TAPE, VOLUME=nnnnnn, ARC1866, RC=32
    ARC1802I FAST REPLICATION DATA SET RECOVERY HAS
    ARC1802I (CONT.) COMPLETED FOR DATA SET
    ARC1802I (CONT.) aaaa.DSNDBC.bbbbbbb.cccccccc.I0001.A001,
    ARC1802I (CONT.) AT hh:mm:ss ON yyyy/mm/dd, FUNCTION RC=0008,
    ARC1802I (CONT.) MAXIMUM DATA SET RC=0066
      This happened because the user specified that only SLBs on
    tape should be used for recovery (zparm
    RESTORE_RECOVER_FROMDUMP = Yes) but had made their SLB only
    on DASD.  This was unintentional but DB2 failed to detect it
    and the RECOVER job ultimately abended with
    ABEND04E RC00D10307 (log read failure due to invalid RBA values)
    and RC00C90070 (fast log apply failure due to internal error).
    These reason codes were not meaningful and in fact different
    and unpredictable errors could have been seen.
    

Problem conclusion

  • Code was changed in RECOVER utility to properly handle an
    error which is caused by the absence of an SLB on tape when
    the user specified zparm RESTORE_RECOVER_FROMDUMP = YES and
    the recovery is of an entire non-partitioned object.
      In this case
    msgDSNU1522I THE DFSMSHSM CALL TO RESTORE...FAILED WITH
                 RC = X'hsm-rc' AND REASON CODE X'hsm-rsc'...
    will now be issued and RC8 set for the object.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM82111

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-05

  • Closed date

    2013-04-22

  • Last modified date

    2014-10-30

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

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

    UK93662 UK93663

Modules/Macros

  • DSNUCBMT DSNUCBRT
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK93662

       UP13/05/07 P F305

  • R910 PSY UK93663

       UP13/05/07 P F305

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 October 2014