Using concurrent copy for data set backup

The BACKDS command has the optional CC keyword, which allows you to specify concurrent copy for both SMS and non-SMS data sets.

   BACKDS dsname CC(PREFERRED)

   BACKDS dsname CC(REQUIRED)
   BACKDS dsname CC(VIRTUALPREFERRED)
   BACKDS dsname CC(VIRTUALREQUIRED)
   BACKDS dsname CC(CACHEREQUIRED)
   BACKDS dsname CC(CACHEPREFERRED)

REQUIRED indicates that concurrent copy must be used as the backup method. If virtual concurrent copy is unavailable cache-based concurrent copy is used. The data set backup should fail if both types of concurrent copy are not available.

PREFERRED indicates that you want to use concurrent copy as the backup method, if it is available. If virtual concurrent copy is not available, cache-based concurrent copy is used. If both types of concurrent copy are not available, the data set will be backed up as if this keyword were not specified.

VIRTUALREQUIRED indicates that virtual concurrent copy must be used as the backup method. The data set backup should fail if virtual concurrent copy is not available.

VIRTUALPREFERRED indicates that you want to use virtual concurrent copy as the backup method, if it is available. If virtual concurrent copy is not available, the data set will be backed up as if this keyword were not specified.

CACHEREQUIRED indicates that cache-based concurrent copy must be used as the backup method. The data set backup should fail if cache-based concurrent copy is not available.

CACHEPREFERRED indicates that you want to use cache-based concurrent copy as the backup method, if it is available. If cache-based concurrent copy is not available, the data set will be backed up as if this keyword were not specified.

You can also specify the STANDARD keyword, which indicates that you want to use a standard backup method (without using concurrent copy). The standard backup method may possibly override a management class option to use concurrent copy.

Note: For SMS data sets, DFSMShsm uses the management class values if you do not specify the CC parameter. For non-SMS data sets, DFSMShsm does not use concurrent copy if you do not specify the CC parameter.

There are two additional options: PHYSICALEND (PE) and LOGICALEND (LE).

PHYSICALEND (the default) indicates that control returns to the application only after the backup has physically completed.
LOGICALEND indicates that control returns to the application when the concurrent copy initialization completes. If PREFERRED was specified and concurrent copy is unavailable for the data set, the backup continues as if this keyword had not been specified. The BACKDS command fails if you specify both STANDARD and LOGICALEND keywords.

DFSMShsm uses the STGADMIN.ADR.DUMP.CNCURRNT facility class resource to limit concurrent copy use to those users who are authorized to use the CC option.