Forcing RESTORE to the same volumes as the source VSAM data set (OW07077)

If a user does not specify output volumes, you can force the RESTORE operation to attempt to return a VSAM data set assigned to an SMS storage class with guaranteed space to the same set of primary volumes that the source data set had occupied when dumped.

This function is affected by setting the flag at offset X'3F' in ADRPATCH. The settings are listed below:

X'00': Unless the user specifies output volumes, RESTORE processing does not pass the source volume list to SMS, and the restored data set probably does not occupy the same primary volumes that the source data set occupied when it was dumped. Because this allows the use of any volumes in the storage group, there is less chance of a failure due to lack of space on volumes.
Any setting other than X'00': Unless the user specifies output volumes, RESTORE processing passes the source volume list to SMS, forcing the restored data set to occupy the same primary volumes that the source data set had occupied when it was dumped, provided that it is assigned to an SMS storage class with guaranteed space. If it will not fit, RESTORE fails processing.

Note:

DFSMSdss cannot ensure that the order of volumes are maintained during a restore of a multivolume data set. SMS determines volume order.
This patch does not support data sets with candidate space volumes. The restore of such a data set will fail with an ADR709E message.

To set the flag to on dynamically, use the SET PATCH command. To set the flag to on permanently, modify the sample JCL (see Sample JCL) as follows:

//SYSIN DD *
   NAME ADRDSSU ADRPATCH
   VER   3F        00
   REP   3F        FF