For requests which refer to storage level S2 and concern SEVERAL-SVID archives, HSMS offers the option of updating save files that already exist. In this case the current save version is written to cartridge behind the save versions already contained there. The new data is written to the volume behind the existing blocks. The save versions already contained in the save file are not changed in the process. The new data is written to the volume behind the existing blocks.
Whether and to what extent a standard save file is continued depends on the intervals at which a new standard save file is started for the archive. These are controlled by the archive definition (operand NEW-STD-SAVE-FILE):
If *AT-EACH-REQUEST is specified for NEW-STD-SAVE-FILE, i.e. a new standard save file is started with each save request, the save file is not continued at all. Each save version is written to a separate save file.
If *EACH-TAPE-SESSION is specified for NEW-STD-SAVE-FILE, i.e. a new standard save file is started at the beginning of each tape session, the save file is continued until the end of the tape session. This means that, during a tape session, all save versions are normally written to the same save file.
A continuation period in days can be defined by using *IN-PERIODS and the operand CONTINUATION-PERIOD. The standard save file is always switched at the beginning of each continuation period. It is continued until the end of the continuation period. All save versions are written to this save file during this period unless otherwise specified.
The expiration date of a save file is calculated as follows if a continuation period is defined:
Expiration date = creation date + retention period + continuation period
(Expiration date = Creation date + Retention period + Continuation period)HSMS creates all save files with SEVERAL-SVID structure as continuable files, irrespective of the specification in the archive definition. This enables save files to be continued explicitly by the HSMS administrator using an HSMS statement. This can be done with various HSMS statements by specifying SAVE-FILE=*CONTINUE.
*PUBLIC-DISK(...) enables the catalog ID of a pubset to be agreed on for a backup node archive. Because of this entry the BACKUP-NODE-FILES statement and the reference to the standard save file (specification SAVE-FILE=*STD) cause backup jobs to be executed for node as a backup on the defined pubset.
Save files which were created on storage level S1, on shared disk, or on Net-Storage in HSMS version V9.0B and earlier can only be continued in HSMS V10.0A and higher if SAVE-FILE-PROCESSING=*HSMS-V9-COMPATIBLE (default) is set.
Save files on storage level S1, on shared disk, or on Net-Storage which were created with *HSMS-V10-COMPATIBLE mode cannot be read or continued in HSMS V9.0B or earlier.
Save files which were created on the extended storage level S1 (formed from all volume sets of the SM pubset under HSMS management) can only be continued with SAVE-FILE-PROCESSING=*HSMS-V10-COMPATIBLE. This also applies when the S1 level has been reduced to a specific volume set again. In this case the volume set last used is continued.
Save files can only be continued if the same value has been specified for the SAVE-SAM-STRUCTURE operand as for the save file that is to be continued.
In case the last SFID/SVID is inconsistent due to a DMS error, the current save file cannot be continued. A new save file has to be created.