At level S2, HSMS and ARCHIVE support all volumes of the TAPE class that are also supported by BS2000 versions on which the current HSMS version can run.
From HSMS V12.0F and BS2000 V21.0C WORM (Write Once, Read Many) volumes are supported. HSMS/ARCHIVE supports backup/export to and restore/import from WORM volumes (volumes of device type TAPE-U4W). HSMS considers that volumes which have already been written cannot be overwritten or appended to (continued). Note that:
- WORM volumes cannot be used for migration or version backup.
- The TAPE-U4W device type cannot be used as the default S2-DEVICE-TYPE for *MIGRATION or *VERSIONBACKUP archives.
- TAPE-U4W volumes cannot be added to the volume pools of migration and version backup archives.
- Save files on a WORM volume cannot be continued (SAVE-FILE=*CONTINUE(..) is rejected).
Action statements resulting in write requests to S2 need not specify the type of volume desired. The exception being volumes that do not belong to the archive (see section "Allocating volumes").
The type of volume requested is determined by global control parameters or by the definition of the archive which is to be written to.
It is the HSMS administrator’s task to define the default volume type which is to be supplied globally for all write requests to S2 unless the archive owner has explicitly defined a different device type:
//MODIFY-HSMS-PARAMETERS - // DEFAULT-HSMS-STORAGE=*PARAMETERS(S2-DEVICE-TYPE=<c-string>)
A different default volume type for saving data to a specific archive at storage level S2 can be defined by
//CREATE-ARCHIVE S2-DEVICE-TYPE=<c-string>
or
//MODIFY-ARCHIVE-ATTRIBUTES S2-DEVICE-TYPE=<c-string>
The definition of a default volume type can be used to introduce a new volume type for the entire system or for a specific archive without necessitating modifications to existing procedures.