Explanation: TAPEDELETION is an optional
parameter specifying whether recycled tape volumes be deleted from
DFSMShsm control and become scratch tapes, or are to remain under
DFSMShsm control as unassigned, available tape backup volumes, migration
level 2 volumes, or dump volumes.
| Subparameter |
Explanation |
|---|
| HSMTAPE |
The recycled volumes remain under
DFSMShsm control and become either unassigned backup volumes or available
migration level 2 volumes, based on the previous definition of the
volume. The tape volume is now available to be selected as a daily
or spill backup volume, or as a target volume for data set migration,
volume migration, or recycling of tape migration level 2 or dump volumes. |
| SCRATCHTAPE |
Recycled tape volumes are deleted
from DFSMShsm control and become scratch tapes after DFSMShsm recycles
them. The tape volumes are not selected as tape backup or migration
level 2 volumes, but an operator can mount them in response to a mount
PRIVAT request for a tape backup or migration level 2 volume. |
If you specify the global TAPEDELETION(SCRATCHTAPE | HSMTAPE) parameter,
the parameter applies to all functions (migration, backup, and dump).
If you specify a specific volume type, the parameter applies only
to that type of function. If you specify a global value and a specific
volume type in a single command, the command fails.
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 SCRATCHTAPE.
Note: - Although the HSMBACKUPTAPE parameter has been changed to HSMTAPE,
if you specify HSMBACKUPTAPE, it has the same meaning as HSMTAPE.
The command will not fail.
- If you choose SCRATCHTAPE and the tape security method that DFSMShsm
used is an expiration date, the DFSMSrmm VLPOOL EXPDTCHECK(N) option
should be enough for DFSMSrmm to allow reuse with operator intervention
and to allow relabelling to reinitialize the tape before DFSMShsm
or any other user tries to reuse the tape volume.
- If you choose SCRATCHTAPE and the tape security method that DFSMShsm
used is a password, DFSMSrmm does not support password protection,
so you would need to initialize the tapes to avoid problems. You can
use the SECCLS parmlib options to specify the requirements to ERASE
volumes DFSMShsm uses before they return to scratch. You can automate
this, see Chapter 16, “Initializing and Erasing Volumes” in z/OS DFSMSrmm Implementation and Customization Guide.
- If you do not use a tape management system, you choose SCRATCHTAPE,
and the tape security method that DFSMShsm used is password or expiration
date, you must use the IEHINITT utility to reinitialize the tape before
DFSMShsm or any other user tries to reuse the tape volume.
- If you choose HSMTAPE, you do not need to reinitialize the tapes
that remain under DFSMShsm control before you reuse them as tape backup
or migration level 2 volumes.
- The disposition of tapes automatically made available for reuse
depends on the TAPEDELETION parameter of the SETSYS command. TAPEDELETION(HSMTAPE)
is equivalent to issuing a DELVOL UNASSIGN for the tapes. TAPEDELETION(SCRATCHTAPE)
is equivalent to issuing a DELVOL PURGE.