CC: Specifying concurrent copy for data set backup

Explanation: CC is an optional parameter specifying that you want to use concurrent copy during BACKDS processing to provide a point-in-time backup copy. The parameters of the CC parameter are explained:

STANDARD

specifies that you want to use standard backup methods without using concurrent copy.

PREFERRED

ANYPREFERRED

specifies the data is to be processed with concurrent copy if possible. Virtual concurrent copy is attempted first, if the storage subsystem on which the data resides is capable of virtual concurrent copy and working-space data sets have been defined. Otherwise, cache-based concurrent copy is attempted if the storage subsystem is capable of it. If both types of concurrent copy are not possible or fail, the data is processed using standard I/O as if CONCURRENT were not specified.

CACHEPREFERRED

CPREF

specifies that data is to be processed with cache-based concurrent copy. Otherwise, the data is processed using standard I/O as if CONCURRENT were not specified. Virtual concurrent copy is not attempted.

VIRTUALPREFERRED

VPREF

specifies that data is to be processed with virtual concurrent copy if possible. Otherwise, the data is processed using standard I/O as if CONCURRENT were not specified. Cache-based concurrent copy is not attempted.

REQUIRED

ANYREQUIRED

specifies the data is to be processed with concurrent copy if possible. Virtual concurrent copy is attempted first, if the storage subsystem on which the data resides is capable of it and working-space data sets have been defined. Otherwise, cache-based concurrent copy is attempted if the storage subsystem is capable of it. If both types of concurrent copy are not possible or fail, the data will not be processed.

CACHEREQUIRED

CREQ

specifies that data is to be processed with cache-based concurrent copy if possible. If a cache-based concurrent copy session cannot be established, the data set will not be backed up. Virtual concurrent copy and standard I/O are not attempted.

VIRTUALREQUIRED

VREQ

specifies that data is to be processed with virtual concurrent copy if possible. If a virtual concurrent copy session cannot be established, the data set will not be backed up. Cache-based concurrent copy and standard I/O are not attempted.

PHYSICALEND

PE

specifies that control returns to the application or user only after the backup physically completes.

LOGICALEND

LE

specifies that control returns to the application or user when concurrent copy initialization completes.

Defaults: If you do not specify any subparameters with the CC parameter, the defaults are STANDARD and PHYSICALEND.

If you do not specify CC, then DFSMShsm does not use concurrent copy for non-SMS data sets. However, for SMS data sets, DFSMShsm uses the values from the management class.