The basic functions (applications) of HSMS are described in the first part of this chapter:
Basic function | DMS files | Node files |
Backup | X | X |
Archival | X | X |
Migration | X | – |
Data transfer | X | – |
Version backup | X | – |
X | The basic function is supported. |
– | The basic function is not supported. |
The options for copying save files are also described here.
All basic functions (with the exception of migration) are described in full, i.e. both the application and management of these functions are described. Control and management of the migration function are described in chapter "Management of HSMS", since they are much more extensive for migration than for the other basic functions.
The second part of the chapter contains a description of the supporting functions relating to the basic functions. These include:
Action statements and their processing (section "Request handling")
Allocating volumes and controlling tape access (section "Volume processing")
Support of various disk formats and conversion during load operations (section "Handling BS2000 disks")
HSMS screen masks and reports (section "HSMS output")
Support of aliases (section "Aliases for BS2000 files and job variables")
In the following, UNIX files are referred to as “node files”.
The node files may be located either on the local BS2000-UFS or on a remote file system. A remote UNIX file system can be backed up directly with NFS. For the NFS backup a remote UNIX file system must be mounted on the special “HSMS” directory of the local BS2000-UFS. Wherever differences exist between the basic functions for BS2000 files/job variables on the one hand and UNIX files on the other, they are dealt with in separate sections.
HSMS also processes environments with SM pubsets. The backup, version backup and migration functions are specific to an environment, i.e. they only process objects located in that environment. By contrast, the archiving function is not restricted to a particular environment: it can process objects from different environments (SF and SM pubsets) in one run. However, if default system long-term archive is to be used for archival function, no default long-term archive must be defined in SM-environment for the SM pubsets concerned in order mixture of files from different environments can be possible.