A save file is the “container” where data managed by the archive is stored. When HSMS saves data to cartridge, disk, or Net-Storage (regardless of the basic function for which it is intended), this data is entered in a save file. This means that HSMS does not create separate cataloged copies of the saved files.
In an HSMS save run, data is only ever written to a single save file, even if the save run involves a large number of files.
The save file itself consists of one or more catalogued BS2000 files on disk on one or more Net-Storage volumes or on cartridges. A save file on magnetic tape cartridges consists of a number of volumes having the same owner (i.e the same user ID is entered in the header of the magnetic tape cartridges) and the same retention period.
For the names of the save files created for HSMS by ARCHIVE, see the section "Save file names".
A save file on disk (storage level S1) is located under the user ID that contains the archive directory, connected with the archive where the save file is stored. To enhance portability, save files are created in the neutral NK4 format. This is done regardless of the format of the pubset (K/NK) or the setting of the BLKCTRL system parameter.
Each save file is uniquely identified by its save file ID (SFID). The save file ID is formed by the date and time of file creation as follows:
sfid = S.yymmdd.hhmmss
COPY-SAVE-FILE is a function which HSMS provides to copy save files (including excerpts of files) within the archive. This makes it possible, for example, to effectively reorganize older long-term archives. In BS2000/OSD-BC V9.0 and higher, the save file can also optionally be copied to an available Net-Storage. In HSMS V10.0 and higher, it can also be copied to shared disk.
To copy node save files of the POSIX file system or of remote nodes S0 within an archive, use the HSMS statement COPY-NODE-SAVE-FILE.
To copy save files created with the HSMS statement EXPORT-FILES or with the ARCHIVE statement EXPORT, use the HSMS statement COPY-EXPORT-SAVE-FILE.
A save file can contain either one or more save versions. This depends on the storage level of the save file and on the structure of the associated archive (SINGLE-SVID or SEVERAL-SVID).
Migration archives, long-term archives, version backup archives and archives for node files of the POSIX file system or of remote nodes S0 always have a SEVERAL-SVID structure. Backup archives can have either a SINGLE-SVID structure or a SEVERAL-SVID structure, depending on what is specified for the SAVE-FILE-STRUCTURE operand in the CREATE-ARCHIVE statement.
Save files for archives with a SINGLE-SVID structure and save files on storage level S1, on private disk, on pubset disk and on Net-Storage contain only a single save version.
Save files on storage level S2 for archives with a SEVERAL-SVID structure can contain more than one save version. When a save file containing multiple save versions is copied to storage level S1, private disk, shared disk, or Net-Storage, a separate save file is created for each save version of the original save file on the target medium.