VOLUMEDUMP: Specifying concurrent copy options for dump volumes
Explanation: VOLUMEDUMP is an optional parameter specifying whether DFSMShsm will request that DFSMSdss use a type of Concurrent Copy function for dump volumes or no Concurrent Copy function for dump volumes.
| Subparameter | Explanation |
|---|---|
| CC | DFSMShsm specifies Concurrent Copy when DFSMSdss dumps volumes. DFSMSdss determines if the device and microcode can support this operation. Customers can specify SETSYS DUMPVOLUME(CC). CC is an alias of PREFERRED and can be added next to the word PREFERRED like the other aliases. |
| STANDARD (NOCC) | STANDARD indicates Concurrent Copy will not be used when DFSMShsm dumps the volumes. Control returns to the requestor at the end of the physical copy. |
| REQUIRED (ANYREQUIRED) | DFSMShsm requests DFSMSdss to use concurrent copy to perform the dump. If virtual concurrent copy is unavailable DFSMSdss uses cache-based concurrent copy. If both types of concurrent copy are unavailable, the dump fails. |
| PREFERRED (ANYPREFERRED) | DFSMShsm requests DFSMSdss to use concurrent copy to perform the dump. If virtual concurrent copy is unavailable, DFSMSdss uses cache-based concurrent copy. If both types of concurrent copy are unavailable, the dump continues as if the CC keyword was not specified. |
| VIRTUALREQUIRED (VREQ) | DFSMShsm requests DFSMSdss to use virtual concurrent copy to dump volumes. If virtual concurrent copy is unavailable, the dump fails. |
| VIRTUALPREFERRED (VPREF) | DFSMShsm requests DFSMSdss to use virtual concurrent copy to dump volumes. If virtual concurrent copy is unavailable, the dump continues as if the CC keyword was not specified. |
| CACHEREQUIRED (CREQ) | DFSMShsm requests DFSMSdss to use cache-based concurrent copy to dump the data sets. If cache-based concurrent copy is unavailable, the dump fails. |
| CACHEPREFERRED (CPREF) | DFSMShsm requests DFSMSdss to use cache-based concurrent copy to dump the data sets. If cache-based concurrent copy is unavailable, the data set dump continues as if the CC keyword was not specified. |
Note:
- The correct level of hardware and microcode must be present in your system environment for the Concurrent Copy function to work.
- In a mixed hardware environment, where some volumes are capable of Concurrent Copy and others are not, specifying a type of Concurrent Copy will be accepted and only apply to those volumes capable of this process, and the noncapable volumes will be dumped using traditional methods.
SMS relationship: Parameter has the same meaning when applied to SMS-managed or non-SMS-managed DASD volumes or data sets.
SETSYS default: None.
DFSMShsm default: If you do not specify this parameter on any SETSYS command, the DFSMShsm default is NOCC.