ARC0771I
RECOVER WITH FROMDUMP SPECIFIED BUT {NO ELIGIBLE DUMP COPY EXISTS | THE SOURCE AND TARGET DEVICE TYPES ARE NOT SIMILAR}, {A BACKUP VERSION HAS BEEN RECOVERED}

Explanation

The RECOVER command was issued requesting that a dump copy be restored for a data set. However, an incremental backup version was recovered for the data set instead of a dump copy. The message indicates which of the following conditions was encountered:
  • No eligible dump copy was found for the restore to be done.
  • The volume that was dumped is not of a similar device type to the target volume.

A more recent backup version has been recataloged and recovered for a VSAM data set.

System action

The restore request is for a VSAM data set that did not exist when the process began, or for an existing non-SMS-managed VSAM data set that is on a different volume (with the TOVOLUME parameter) than the data set is currently on. DFSMShsm found a valid backup version and recovered it first to create the data set’s catalog records properly before the restore operation. This operation was successful, but a restore of a dump copy was not permitted for the reason indicated in the message. DFSMShsm processing continues.

Programmer response

Verify that an eligible dump copy exists for the data set in question. Reissue the RECOVER command specifying the dump copy with the FROMDUMP and DUMPVOLUME parameters. The LIST command can be used to determine what the dump copies are for a given source volume. It can also be used to determine the contents of the VTOC at the time of the dump, if the dump VTOC copy data set exists.

Source

DFSMShsm