BS2000 files are files which are managed and edited in BS2000. Unless an explicit distinction is made, in the case of files on Net-Storage the term "BS2000 file" refers to both the file type BS2000 and the file type node file which is also supported in BS2000 OSD/BC V10.0 and higher.
Within the context of this section, the term “files” always refers to BS2000 files.
HSMS saves data logically.
Large files (files > 32 GB) can also be saved. No particular provisions are required to do this. However, when restoring large files, bear in mind their special characteristics (see section "Restoring large files (> 32 GB)").
Encrypted files are saved in encrypted format and restored again in the original encrypted format. The associated crypto password need not be specified for saving or restoring. Other accesses to the restored file require the crypto password to be specified again, and the technical prerequisites for file encryption must be provided in the system.
When the HSMS statements BACKUP-FILES or BACKUP-FILE-VERSIONS are used in an environment with SF pubsets, they can only process SF pubsets; SM pubsets cannot be processed.
When the HSMS statements BACKUP-FILES or BACKUP-FILE-VERSIONS are used in an environment with SM pubsets, they are restricted to the environment in which they are called, i.e. they relate to precisely one SM pubset.
By default it is defined (see //SHOW-HSMS-PARAMETERS, MIGRATION-CONTROL, BACKUP-MANDATORY=YES) that, for security reasons, a file cannot be migrated until the current version of the file has been written to a save file at least once.
In the event of backup, it is possible to save either just the catalog entries of migrated files (save type MIGF) or both the catalog entries and the data contained in the files. With version backup, both the catalog entries and the data are saved. For further details, see section "Data backup and migrated files".
How a save file can be extended depends on its structure and its storage location:
In the case of backup archives with single SVID structure or save files on disk, specifying the operand SAVE-FILE=*CONTINUE permits a disjunct set of files to be added to a save file written to an archive.
In the case of archives with several SVID structure, the save file can be updated with a new save version (irrespective of whether the same files are saved). The file must be distinguished by their save version.