Moving data sets with SnapShot copy

DFSMSdss prefers to use SnapShot copy to quickly move the data from the source device to the target device. DFSMSdss can do this when the source and target devices are both in the RVA, and DFSMSdss does not need to manipulate data. This process, called regular SnapShot support, is much faster than traditional methods, especially when moving large amounts of data.

To use regular SnapShot, the following requirements must be met:

Source and target device types (3390 or 3380, for example) must be the same.
Source and target devices must be in the same RVA.
Data must not require manipulation, such as reblocking.
The data movement must not require utilities.

If the source data is in an RVA, DFSMSdss attempts to allocate the target data set on the same device type in the same RVA. This increases the probability that SnapShot can copy the data. DFSMSdss cannot allocate the target to use SnapShot if the source data set is multivolume, but is not entirely within one partition of an RVA subsystem. DFSMSdss allocates these data sets to whatever volumes are available, irrespective of their SnapShot capability.

DFSMSdss automatically performs SnapShot processing if possible, even when you specify the CONCURRENT keyword.