The system-wide RACF® tape volume protection option is in effect. The tape security option RACF or RACFINCLUDE is specified with the TAPESECURITY parameter of the SETSYS command.
DFSMShsm has selected tape volume volser for use during backup or migration processing.
The records in DFSMShsm control data sets indicate that the tape volume is not full and is not RACF-protected by DFSMShsm. Because the RACF or RACFINCLUDE tape security option is in effect, DFSMShsm is going to RACF-protect this tape volume in one of DFSMShsm’s RACF tape volume sets of HSMHSM or DFHSMx (where x is the last nonblank character of the tape volume’s volume serial number). See z/OS DFSMShsm Implementation and Customization Guide, under "Authorizing and Protecting DFSMShsm Resources" for a description of how to add tape volumes to DFSMShsm’s RACF tape volume sets. Before RACF-protecting the tape volume, DFSMShsm issues two RACHECK macros to determine the current protection status of the tape volume.
The first RACHECK macros issued by DFSMShsm indicates that the tape volume is RACF-protected. The second RACHECK macro issued by DFSMShsm indicates that the tape volume does not appear in a DFSMShsm RACF tape volume set of either HSMHSM or DFHSMx.
Because the tape volume is RACF-protected but does not appear in a DFSMShsm RACF tape volume set, DFSMShsm will not use it. The tape volume is indicated as full in all necessary records in the DFSMShsm control data sets to prevent DFSMShsm from using it again. DFSMShsm control data set records indicate that the tape volume already contains valid DFSMShsm data.
RLIST TAPEVOL volser ALLThe sender of the command must have a certain level of access authority to the resource depending on the information being requested.
For additional information, see z/OS Security Server RACF Command Language Reference.
If the volume is defined to DFSMShsm as a backup volume or a tape migration volume, the system programmer or storage administrator responsible for DFSMShsm operations can determine which valid data is on the tape volume by entering the following DFSMShsm space manager command: LIST TTOC(volser) TERMINAL
If the volume is defined to DFSMShsm as a dump volume, the following command will appear if the volume contains a valid dump copy: LIST DUMPVOLUME (volser)
If a DUMP VTOC data set is associated with the dump copy of the tape volume, the following command will display the contents of the tape volume at the time of the dump: LIST DUMPVOLUME (volser) BACKUPCONTENTS
The system programmer should print the data on the tape volume to determine what data actually exists on the volume. The data printed should be visually inspected to determine if the volume contains DFSMShsm backup versions or migration copies. DFSMShsm backup versions or migration copies are written in 16K records. The beginning of the first 16K record of a backup version or migration copy contains a control black known as the common data set descriptor record (CDD). For additional information, see z/OS DFSMShsm Diagnosis.
The header labels (HDR1 and HDR2) and trailer labels (EOF1 and EOF2) of the data sets on the tape volume can also be useful in determining if data sets are DFSMShsm backup version or migration copies.
If the tape volume physically contains DFSMShsm backup versions or migration copies, the RACF security administrator should inform the owner of the tape volume that the tape volume contains DFSMShsm backup versions or migration copies. If the volume does not contain necessary data and can be used by DFSMShsm, the owner should remove the RACF protection.
To delete the profile from the RACF data set or delete the volume from a tape volume set, the user entering the RDELETE or RALTER command must have a certain attribute or certain level of access authority to the resource being deleted. For additional information, see z/OS Security Server RACF Command Language Reference.
If the owner suggests the tape volume contains the data and is needed, the system programmer should help in retrieving, recovering, and re-creating the user’s data.
If the tape volume is defined to DFSMShsm as a backup volume and the volume does not physically contain any DFSMShsm backup versions but DFSMShsm thinks that valid backup versions exist on the tape volume, the system programmer should delete each backup version that DFSMShsm thinks is on the tape volume. To logically delete each backup version that resides on the tape backup volume, the system programmer should remove the volume from DFSMShsm’s control by entering the following DFSMShsm space manager command: DELVOL (volser) BACKUP(PURGE)
The DELVOL command causes each valid backup version that DFSMShsm thinks is on the tape volume to be marked invalid in the tape table of contents record TTOC) in the offline control data set (OCDS). Also, all records about this volume are deleted from the DFSMShsm control data sets. The system programmer should consider creating a new backup version for each data set that has a backup version deleted.
If the tape volume is defined to DFSMShsm as a migration volume and the volume does not physically contain any DFSMShsm migration copies but DFSMShsm thinks that valid migration copies exist on the tape volume, the system programmer should delete each migrated data set that DFSMShsm thinks is on the tape volume. To logically delete each migrated data set that resides on the tape migration, the system program should enter the following DFSMShsm space manager command: MIGRATE VOLUME(volser DBA (0))
The MIGRATE command with the DBA parameter causes data set deletion to be performed on the tape migration level 2 volume. Any migrated data sets residing on the tape level 2 migration volume that are not referred to in the specified number of days (zero) will be logically deleted. Because the number of days specified is zero, DFSMShsm logically deletes all valid migrated data sets that reside on the volume. After data set deletion is completed on the tape migration volume, the system programmer can remove the volume from DFSMShsm’s control by entering the following DFSMShsm space manager command: DELVOL volser MIGRATION(PURGE)
The DELVOL command causes all records associated with the tape volume to be deleted from the DFSMShsm control data sets. The system programmer should consider how her or she is going to recover a copy of each of the migrated data sets that has been logically deleted during data set deletion.
If the tape volume is defined to DFSMShsm as a dump volume, the volume can be removed from the control of DFSMShsm with the following command: DELVOL volser DUMP(PURGE)
The entire dump copy that the volume belongs to will be invalidated.
DFSMShsm