The functional enhancements are included in both manuals “HSMS Volumes 1 and 2”.
HSMS V12.0C
New version backup features
In HSMS V12.0C more features for version backup are introduced:
- During reorganization of version backup archive, it is possible to save the archive directory (new SAVE-DIRECTORY operand was added). Due to this process the archive directory, which is updated during the reorganization process, can also be written to the save file.
- The new values of DIRECTORY-LOCK parameter of //MDA command is implemented. UNLOCK-VERSION-DIR value have been added in order the directory can be usable again in case it was previously locked as a result of abnormal shutdown of the //BACKUP-FILE-VERSIONS or //REORGANIZE-VERSION-BACKUP commands or after importing it from the save file created via REORGANIZE-VERSION-BACKUP with SAVE-DIRECTORY=*YES.
Migration features improvements
- In HSMS V12.0C, migration from S2 to S2 level removes duplicates of valid files, leaving only one unique valid file version in the reorganized save file.
- From HSMS V12.0C REPAIR-CATALOG-BY-RESTORE issues messages into report when no suitable version of the file of FULL save type in the specified (version) backup archive. Output of these messages is provided when among the list of files that are contained in the (version) backup archive and can be restored there are no files with the PARTIAL save type.
Support of the new Net-Storage volume type - NETVOL
The new Net-Storage volume type NETVOL is introduced with BS2000 V21.0A, HSMS V12.0C provides support of Net-Storage files residing on NETVOL volumes. The Net-Storage volumes of NETVOL volume type can be used as a storage media.
Handling of obsolete device types
Since BS2000 V21.0A some of device types have become old and are not supported in the new environment. For such purpose displaying of such devices was changed, now ?XX? is displayed for unknown devices (XX = the hex code of the volume type).
HSMS V12.0D
Automatic reorganization of HSMS directories
In HSMS V12.0D it is possible to activate automatic reorganization of a directory during HSMS save runs. Thus it is no longer necessary to use DIRCONV for reorganizing directories. For details see section "Archive directory".
Reorganization of save file of long term archives
From HSMS V12.0D it is possible to delete automatically the save file in a long term archive after copying only the save versions which file expiration date has not yet been reached or had been reached after the specified date in the past. This is done with the new operand EXPIRATION-AFTER=<date>(INPUT-SAVE-FILE=*DELETE) in the save version selection of COPY-SAVE-FILE statement.
Forced move of save files within version backup archives
From HSMS V12.0D it is possible to use REORGANIZE-VERSION-BACKUP statement for moving save files within a version backup archive irrespective of existence of obsolete files versions. For details see section "REORGANIZE-VERSION-BACKUP".
Removing of duplicates of valid files during migration from S1 to S1
From HSMS V12.0D migration from S1 to S1 storage transfers only one valid version of a valid file and removes all its existing copies within the selected save files.
Restoring files with dialog file select via range of original save versions
From HSMS V12.0D it is possible to select files/job variables versions via DIALOG-FILE-SELECT/DIALOG-JV-SELECT based on their original save version dates from the range of dates specified by the CREATED-BEFORE and CREATED-AFTER operands. It is possible to see the original date and time on which the file/job variable version was saved in long-term or migration archive on the selection mask.
HSMS V12.0E
LIST-SAVE-FILE
From HSMS V12.0E it is possible to list disk save files. For details see section "LIST-SAVE-FILE".
DIALOG-FILE-SELECT with RESTORE-NODE-FILES
The option to select restoring of node files via dialog select is available from HSMS V12.0E. For details see section "RESTORE-NODE-FILES".
Improvement of the mask header of DIALOG-FILE-SELECT for RESTORE-FILES
In HSMS V12.0E, all the types of the mask headers for restore process are changed to a single format. For details see section "RESTORE-FILES".
Forced deletion of save files is logged at the console
From HSMS V12.0E if a user deletes save files with FORCE=*YES option via //MODIFY-ARCHIVE, the message ARC0824 is issued at the console. Also see section "MODIFY-ARCHIVE".
HSMS V12.0F
Support for WORM Volumes
WORM (Write Once, Read Many) refers to a storage concept in which data on a WORM volume can be written only once and, after that, cannot be modified or deleted, but can be read any number of times. 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.
Notes:
- 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 these archive types.
- Save files on a WORM volume cannot be continued (SAVE-FILE=*CONTINUE(..) is rejected).
Restrictions for pilot usage:
New media must be initialized before first use. During initialization, the protection period preconfigured for WORM volumes of a volume group in the ETERNUS CS is activated. Until the protection period has expired or the protection expiration date has been reached, it is not possible to delete the tape in the ETERNUS CS.
In MAREN, the protection period or the protection expiration date is only calculated when the tape is opened for writing and data is written, for example as part of a save. It is therefore recommended to initialize volumes only shortly before their use, so that the protection expiration date displayed in MAREN matches the protection period in the ETERNUS CS.
This restriction will be removed with the general customer release as part of SP 26.1. From then on, MAREN will be able to calculate the protection expiration date during tape initialization and thus determine it automatically and correctly.
In general, it is recommended to write to the WORM volume promptly after initialization so that the protection period covers the user’s planned usage timeframe. As usual, the user controls data retention via the expiration date or the retention period. The user has no influence on the protection period in the ETERNUS CS.