HSMS provides default system archives for each of the basic functions. Default system archives are created as public archives by the HSMS administrator and earmarked for use by the basic functions backup, archival and migration. Default system archives can be used for these functions even if their names are unknown, since they can be addressed by the following symbolic names:
SYSBACKUP for the system backup archive
SYSVERSION for the system version backup archive
SYSARCHIVE for the long-term system archive
SYSMIGRATE for the system migration archive
SYSNODEBACKUP for the system backup archive for node files of the POSIX file system or remote nodes S0
SYSNODEARCHIVE for the system long-term archive for node files of the POSIX file system or remote nodes S0
In an SF pubset environment, default system archives are created as shareable archives and assigned to the entire system as follows:
//MODIFY-HSMS-PARAMETERS DEFAULT-HSMS-STORAGE=*PAR( - // SYSBACKUP=<archive name>, - // SYSARCHIVE=<archive name>, - // SYSMIGRATE=<archive name>, - // SYSNODEBACKUP=<archive name>, - // SYSNODEARCHIVE=<archive name>)
The assignment of the system backup archive is only valid in this case for all imported SF pubsets and node S0s.
System archives for archival are also valid for all imported SF pubsets and node S0s but are not restricted to them (see relationship with SM pubsets).
The assignment of the system migration archive is valid only for those BS2000 S0 pubsets for which migration is permitted.
These system-wide assignments can be modified for specific pubsets/node S0s:
Individual pubsets can be assigned different SYSBACKUP, SYSARCHIVE, SYSMIGRATE and SYSVERSION default system archives by means of the HSMS statement MODIFY-PUBSET-PARAMETERS.
Individual node S0s can be assigned different SYSNODEBACKUP and SYSNODEARCHIVE default system archives by means of the HSMS statement MODIFY-NODE-PARAMETERS.
System version backup archives can only be assigned to individual pubsets by means of the HSMS statement MODIFY-PUBSET-PARAMETERS. Moreover, the same version backup archive can be assigned only to one pubset at the same time.
In an SM pubset environment, the default system archives are set up as shareable and assigned to the SM pubset with:
//MODIFY-SM-PUBSET-PARAMETERS - // SM-PUBSET-ID=<cat-id>, - // SYSBACKUP=<archive name>, - // SYSARCHIVE=<archive name>, - // SYSMIGRATE=<archive name>,- // SYSVERSION=<archive name>
The assignment of the system archives for backup, version backup, archival and migration is only valid within this SM pubset.
The archiving activity is not restricted to the SM pubset environment in which it is issued. The environment to which the archiving function relates can be the host environment. In this case the archive definition is stored in the central HSMS control file.
When a user addresses a default system archive by means of its symbolic name, this name is resolved. The name can thus be mapped onto the archive that the HSMS administrator has assigned to a predefined environment.
The environment from which the symbolic archive names are resolved is generally the catalog ID or node ID specified in the HSMS statement. All affected catalog or node IDs are searched for their assigned symbolic archive:
With HSMS statements that work in an SF environment, these are catalog IDs which are specified in the S0-PUBSET-ID operand (with the HSMS statements REPAIR-CATALOG-BY-EXCHANGE and REPAIR-CATALOG-BY-RESTORE) or which are used in the FILE-NAMES operand of an HSMS statement.
With HSMS statements that work in an SM environment, this is the catalog ID specified in the ENVIRONMENT operand.
With HSMS statements that work on workstations, the node IDs are taken from the NODE-ID operand.
An exception is the HSMS statement SHOW-ARCHIVE in an SF environment if the value *SAVE-VERSIONS, *SAVE-FILES or *VOLUMES is used with the SELECT operand. With these operand values no file list, catalog ID or node ID can be specified:
For a nonprivileged user, either the default catalog ID of the user (the default catalog ID is defined in the user catalog) or the BS2000-UFS is used in order to resolve the symbolic archive name.
For a privileged user, HSMS searches all catalog and node IDs defined in HSMS (with the HSMS statements MODIFY-PUBSET-PARAMETERS or MODIFY-NODE-PARAMETERS) in order to resolve the symbolic archive name.
The mapping of the symbolic names must be unequivocal. Since it is based on specific pubsets/node S0s, the following restriction applies:
If the operand FILE-NAMES or JV-NAMES is to refer to files or job variables of more than one pubset/node S0, the same default system archive must have been assigned to all of the pubsets/node S0s involved so that the corresponding symbolic archive name, when specified, always refers to the same archive. If this is not the case, each save request should refer to the files of one single pubset/node S0 only.
Regarding system version backup archives, it is not allowed to assign one and the same archive to several pubsets. Therefore, operand FILE-NAMES must refer to files from one pubset only when dealing with system version backup archives.
Nevertheless, it is useful to create various archives for the pubsets/node S0s for performance reasons, as some archiving activities can only be performed serially. Creating several system archives for each basic function reduces the probability of bottlenecks occurring when archives are accessed.