A save version is created each time a write request is issued for an archive. A save version contains all files and job variables saved by the request plus – in the event of incremental backup of files – references to those registered as “cataloged-not-saved” (CNS).
A save version is always part of a save file.
A save version is identified internally by its save version ID (SVID), which is formed by the date and time of its creation. HSMS statements can subsequently refer to a save version either via its creation date or via the name assigned to it in the action statement that resulted in the creation of the save version. The relevant operand in this case is SAVE-VERSION-NAME. Except for save versions created by means of version backups which can be referred only via their creation date. It is not possible to assign names to save versions of version backup archives; the specification of a value for the operand SAVE-VERSION-NAME in the MODIFY- ARCHIVE statement is rejected.
Note for ARCHIVE users
The distinction between save file and save version has been introduced in HSMS because in contrast to ARCHIVE, several backup versions can be contained in a single save file for backup, archival and migration.
When processing magnetic tape cartridges of this type using ARCHIVE, the save file ID (SFID) in the report is output as a save version ID (SVID). If the user wishes to import individual files, then they will need to specify the output SVID as the SFID when carrying out an IMPORT run.
The SVID can be located using the HSMS statements LIST-VOLUMES. If the SVIDs are listed in an ordered sequence on the magnetic tape cartridge, then the user can use the LIST statement of ARCHIVE to obtain the SVIDs of the various files by specifying the SFID.