Catalog Management hooks required after applying GDG PHASE II PTF RO69420

Products

• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• DISK BACKUP AND RESTORE

Issue/Introduction

While trying to run a restore you can get the following error messages: 

ADSDM903 2433 AN SVC 99 ERROR HAS OCCURRED IN -- DYNAMIC ALLOCATION
ADSDM903 2433 ---------------------------------------------------------
ADSDM903 2433 S99R15RC => 4
ADSDM903 2433 S99ERRCD => 0218
ADSDM903 2433 S99INFCD => 0000
ADSDM903 2433 ---------------------------------------------------------
ADSDM903 2433 DSNAME=S06.SXXXX
ADSDM903 2433 VOLUME=MIGRAT .
ADSDM903 2433 UNIT=3390
ADSDM903 2433 THE VOLUME IS NOT MOUNTED AND MOUNT WAS NOT REQUESTED/AUTHORIZED.

This issue occurs when PTF RO69420(GDG Phase II) and its associated corrective ptfs are installed.

Environment

Release: Disk™ Backup and Restore 12.5

Resolution

Data set catalog entries are now kept in catalog during the archive and restore process.  As a result, the Disk Catalog Management hooks are now required. Catalog volser problems can occur if the hooks are not installed. The Catalog Management hooks are installed by the command:  S DMSAR

Prior to IBM GDG Phase II, if the data sets were not recatalog for Auto-restore, nothing was catalogued to ARCIVE so the hooks were not absolutely required. With GDG Phase II, Disk is keeping the existing catalog entry even for a real data set, so it gets altered to MIGRAT and the physical data set deleted.  It then restores the data set and alters it back to the new volume(s).

Disk is using MIGRAT behind the scenes and needs the hooks being installed to make sure Disk code gets ARCIVE (RECATVOL sysparm) value back – not MIGRAT. The hooks are needed as gatekeeper so the system sees what it needs as Disk does. Recommend leaving RECATMIT at N, but Disk still needs the catalog hooks. 

Additional Information

Refer to the Disk tech docs for Sysparm RECATMIG and RECATVOL for more details.