HSMS statements can be used to process files and job variables residing on a shared pubset.
If no backup server is specified and the shared pubset is imported on the slave host, it is necessary to differentiate between the following two modes:
“Master mode”
The HSMS statements are processed on the master sharer. This is the normal mode.“Local mode”
The HSMS statements are processed on the sharer where they were entered.
If a backup server is specified, the HSMS statements are processed on this server. In this case the backup server can be either the master or slave host of the shared pubset (see section "Backup server").
Backup requests created using the “Concurrent Copy” function form an exception. Such requests are handled in the usual slave/master environment. Any backup server settings are ignored. For details, see section "Backup using the function "Concurrent Copy".
If in your computer center several processors on which various HSMS versions are used share pubsets, you should also read section "Compatibility of HSMS definitions in different HSMS environments".
In the SF environments, HSMS save parallel runs on different systems creating save files on shared S1 levels or shared SF pubsets are serialized using the ARCHIVE.ASN, see section "Work files". In the SM-environment, the serialization is guaranteed by the local request file of the SM pubset and the ARCHIVE checkpoint file.