SPILL and NOSPILL: Specifying whether DFSMShsm does spill or cleanup processing on full DASD daily backup volumes

Explanation: SPILL | NOSPILL are mutually exclusive, optional parameters specifying whether DFSMShsm can do spill or cleanup processing on full-DASD daily backup volumes during backup volume selection and limiting the selection and allocation of an output volume during spill processing.

SPILL specifies that DFSMShsm spills full DASD daily backup volumes when a DASD daily backup volume is needed and none is available. Spill processing moves all but the latest backup version of each data set from the daily backup volumes to the spill backup volumes.

Subparameter	Explanation
ANY	Any type of spill backup volume can be used for output during spill processing.
DASD	Only DASD spill backup volumes are used for output during spill processing. TAPE specifies that only tape spill backup volumes be used for output during spill processing. In addition, when a tape spill backup volume is allocated during spill or recycle processing, the volume is allocated using the unit name specified on the ADDVOL command for the volume.
TAPE(unittype)	Only tape spill backup volumes that can be mounted and written on the specified unittype are used during spill processing. In addition, when the tape spill backup volume is allocated during spill processing, the volume is allocated using the unit name specified with the TAPE subparameter of the SPILL parameter, overriding the unit name specified on the ADDVOL command for the tape spill backup volume. For unittype, specify a generic or esoteric unit name. The following generic unit names are acceptable: 3480, 3480X, 3490, and 3590-1. If an esoteric unit name is specified, it must have been previously defined to DFSMShsm using the USERUNITTABLE parameter of the SETSYS command.

NOSPILL specifies that DFSMShsm never spills full DASD daily backup volumes. Instead, DFSMShsm cleans up full DASD daily backup volumes when one is needed and none is available. During cleanup processing, DFSMShsm scratches the following data sets from the full unallocated DASD daily backup volume that DFSMShsm has not cleaned up in the longest period of time:

Unneeded VTOC copy data sets
Unneeded VCAT copy data sets
Backup versions without backup-version (MCC) records.

SMS relationship: Parameter has the same meaning when applied to SMS-managed or non-SMS-managed DASD volumes or data sets.

SETSYS default: If you specify SPILL without any value, any previous spill output specification is retained.

DFSMShsm default: If you do not specify either parameter on any SETSYS command, the DFSMShsm default is SPILL(ANY).

Note: During spill, DFSMShsm does not keep the association of a primary volume and a particular backup device category. You specify this association with the PRIMARY(BACKUPDEVICECATEGORY) parameter of the ADDVOL command. For example, if you specify ADDVOL PRIMARY(BACKUPDEVICECATEGORY(DASD)), the backup version can be moved to a tape spill backup volume; however, the latest backup version of each data set on the primary volume remains on a DASD daily backup volume.