Using SMS backups and IDCAMS REPRO copies

RUV supports the use of SMS backups and IDCAMS REPRO copies as described in this topic.

Automatically using SMS backups

RUV does not invoke SMS to perform backups. If you are already creating SMS backups, you do not need to change your backup jobs to implement RUV. RUV recognizes SMS backups automatically during restore and recovery processing. For automatic handling of SMS backups, the only action that you might need to take is to code the SMS value of the BACKUP_METHOD keyword on the SET or SET DEFAULT command. The SMS value is one of the default values of the BACKUP_METHOD keyword; therefore, you do not need to code it explicitly unless this default value has been changed in your environment.

If you do not want RUV to select SMS backups, you must code BACKUP_METHOD(NO_SMS) on the SET or SET DEFAULT command.

For information about how RUV handles SMS backups during restore processing, see Restoring-VSAM-data-sets.

Automatically using IDCAMS REPRO copies

RUV can recognize and automatically restore copies that were created by using the REPRO command of the IDCAMS utility. For automated handling of a REPRO copy, you must register the copy as a backup file in the RUV repository. Use the REGISTER BACKUP_FILE command of the RUVZSM0 utility, as described in Explicitly-registering-backups.

RUV can restore the IDCAMS copy under the following conditions:

• If the VSAM file is not registered, you must name the BACKUP_IN input file as you do when the REPRO file is not registered to RUV and the VSAM file to be restored is registered to RUV.
• If the REPRO file is registered to RUV, RUV will automatically consider the REPRO file to restore your VSAM file without your specifying the file with the BACKUP_IN keyword. RUV dynamically defines the VSAM file and uses the REPRO backup for the restore operation.