After the DASD backup volume to be cleaned up is allocated, the
following is performed:
- The VTOC is read.
- A check is performed to determine if the data set name corresponds
to a VTOC or VCAT copy data set.
- If the data set name corresponds to a VTOC or VCAT copy data set,
a check is performed to determine if the data set is a current version
on any volume. If the data set is a current version, the data set
is scratched.
- If the data set name does not correspond to a VTOC or VCAT copy
data set, a check is performed to determine if the data set name corresponds
to a DFSMShsm created backup version.
- If the data set name corresponds to a DFSMShsm created backup
version, the backup version record (MCC) from the BCDS is read. If
no backup version record exists, the backup version is scratched.
- If the data set name does not correspond to a DFSMShsm created
backup version, the data is not processed.
- After the VTOC is read and all unnecessary backup versions, VTOC
copy data sets and VCAT copy data sets are scratched, and the percentage
of allocated space on the DASD backup volume is determined.
- If a full DASD daily backup volume was cleaned up, and the allocated
space is less than or equal to the user-specified allocated space
threshold, the volume is no longer considered full and is used to
back up DFSMShsm-managed volumes.
- If a full DASD spill backup volume was cleaned up, and the allocated
space is less than or equal to the user-specified allocated space
threshold, the volume is no longer considered full and is used to
spill a full DASD daily backup volume.
Tip: The allocated space threshold
can be specified using the THRESHOLD parameter of the ADDVOL command.
Note: When cleanup is performed, the backup volume
record (BVR) for the volume is held with an exclusive enqueue while
the cleanup process is performed. This enqueue can cause message ARC0712I
to be issued during the cleanup process.