SMS-managed Data Set Restore Examples

All examples in this section are found in the JCL library installed with FDR. The member names are EX5022x.

There are no special considerations when SMS-managed data sets are restored in place, on top of their existing allocations; ABR just replaces their contents. When any data set being restored by ABR must be allocated on a system with SMS active, the SMS ACS routines are invoked to decide if it is to be SMS-managed, to assign SMS classes, and to decide which volume it is to be placed on.

Any of the data sets in the examples in Data-Set-Restore-Examples could have been SMS-managed. If they needed to be allocated, ABR would have passed their previous SMS classes (if any) to your ACS routines, which could accept, reject, or override them. If an SMS storage class is assigned to a data set, SMS selects a storage group and a volume for the allocation. The following examples show how to influence or override the SMS allocation.

Override SMS classes example

Restore a data set from Volume Backups and request that the data set be SMS-managed; the original data set might be SMS-managed or not, but it is not currently cataloged; VOL= specifies the volume it was originally dumped from. The values specified for STORCLAS= and MGMTCLAS= are passed to the SMS ACS storage and management class routines, which may override them. If your ACS routines accept your storage class or assign a new storage class, SMS then selects a storage group and a volume. If your ACS routines assign a null storage class (non SMS-managed) to the data set, it is restored to the volume from which it was dumped (unless that volume was SMS-managed, since a non SMS-managed data set cannot be restored to an SMS-managed volume).

//RESTSMS EXEC PGM=FDRABR,REGION=0M //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSIN DD * RESTORE TYPE=ABR,DYNTAPE SELECT DSN=PROD.MASTER.FILE,DATACLAS=MASTER, MGMTCLAS=PERM,STORCLAS=PROD2,VOL=PROD01 /*

Restore to Non SMS-managed volume example

Restore a data set from Volume Backups and request that the data set be non-SMS; the original data set might be SMS-managed or not. It does not exist on DASD but is recorded in the ABR scratch catalog. NULLSTORCLAS specifies that a null value is passed to the SMS ACS storage class routine, which may override it. If your ACS routines honor the null storage class, it is restored as non-SMS on the volume TSO123; no SMS classes are associated with it. If your ACS routines assign a storage class, SMS then selects a storage group and a volume.

//RESTSMS EXEC PGM=FDRABR,REGION=0M //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSIN DD * RESTORE TYPE=ABR,RECAT,DYNTAPE SELECT DSN=USER01.ISPF.ISPPROF,NULLSTORCLAS,NVOL=TSO123 /*


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*