Occasionally, it may become necessary for you to manually back
up the control data sets. This manual backup could be needed if CDS
version backup fails to get a good copy of the control data sets,
or if you receive a message that the journal is full. DFSMShsm provides
parameters for the BACKVOL command that allow you to back up all the
control data sets manually:
BACKVOL CDS(DATAMOVER(HSM | DSS)
BACKUPDEVICECATEGORY(DASD | TAPE(NOPARALLEL | PARALLEL)))
where:
- DATAMOVER(HSM | DSS)
- specifies which CDS backup data mover should be used when backing
up the control data sets.
- BACKUPDEVICECATEGORY(TAPE | DASD)
- specifies the device on which the backup copies are recorded.
- TAPE(NOPARALLEL | PARALLEL)
- specifies whether one or more tape devices are allocated. If
DATAMOVER(DSS) is specified, TAPE(NOPARALLEL) cannot be specified.
Note: - If you do not specify DATAMOVER with the BACKVOL CDS command,
the last DATAMOVER specified by SETSYS CDSVERSIONBACKUP is the default.
- If you do not specify BACKUPDEVICECATEGORY with the BACKVOL CDS
command, the last BACKUPDEVICECATEGORY specified by SETSYS CDSVERSIONBACKUP
is the default.
- If you specify BACKVOL CDS DATAMOVER(DSS) without BACKUPDEVICECATEGORY,
and the DFSMShsm CDS version backup environment indicates TAPE(NOPARALLEL),
the BACKVOL command terminates with an error message indicating that
the CDSVERSIONBACKUP options of DATAMOVER(DSS) and TAPE(NOPARALLEL)
are in conflict.
- Use caution if you change device types with the BACKUPDEVICECATEGORY
parameter. See the topics on Changing backup device from tape to DASD and Changing backup device from DASD to tape.
- Using DATAMOVER(DSS) provides advantages of validation during
backup as well as (with the concurrent copy function) reduced serialization
of the control data sets. DATAMOVER(HSM) is retained as an option
for purposes of coexistence with previous releases.
- In a single DFSMShsm host environment, DFSMShsm obtains an exclusive
enqueue on the control data sets. In a multiple DFSMShsm host environment,
DFSMShsm reserves the volumes, or if using RLS, does an exclusive
enqueue on a SYSTEMS wide global resource which will prevent other
HSMs in an HSMplex from accessing the control data sets.