The table below shows where statements are processed when shared pubsets are concerned depending on whether or not a backup server is specified.
Statement | Processing | |
No backup server specified | Backup server specified | |
ARCHIVE-FILES | (1) | (2) |
ARCHIVE-NODE-FILES | local (node) | local (node) |
BACKUP-FILES | (1) | (2) |
| BACKUP-FILE-VERSIONS | (1) | (2) |
BACKUP-NODE-FILES | local (node) | local (node) |
| CHECK-CATALOGED-FILES | local + SM-dynamic | local + SM-dynamic |
COPY-EXPORT-SAVE-FILE | local (data transfer) | local (data transfer) |
COPY-NODE-SAVE-FILE | local (node) | local (node) |
COPY-SAVE-FILE | local (how many masters?) | local |
CREATE-ARCHIVE | local + SM-dynamic | local |
CREATE-MANAGEMENT-CLASS | local + SM-dynamic | local + SM-dynamic |
CREATE-SM-PUBSET-PARAMETERS | local + SM-dynamic | local + SM-dynamic |
DELETE-ARCHIVE | local + SM-dynamic | local + SM-dynamic |
DELETE-MANAGEMENT-CLASS | local + SM-dynamic | local + SM-dynamic |
DELETE-REQUESTS | (3) | (3) |
EXPORT-FILES | local (data transfer) | local (data transfer) |
IMPORT-FILES | local (data transfer) | local (data transfer) |
LIST-VOLUMES | local | local |
MIGRATE-FILES | (1) | (2) |
MODIFY-ARCHIVE | local + SM-dynamic | local + SM-dynamic |
MODIFY-ARCHIVE-ATTRIBUTES | local + SM-dynamic | local + SM-dynamic |
MODIFY-HSMS-PARAMETERS | local | local |
MODIFY-PUBSET-PARAMETERS | local | local |
MODIFY-SM-PUBSET-PARAMETERS | local + SM-dynamic | local + SM-dynamic |
MODIFY-TAPE-CONTROL | local + SM-dynamic | local + SM-dynamic |
MOVE-SAVE-FILES | local | local |
RECALL-MIGRATED-FILES | (1) | (2) |
RECALL implicit (by /SECURE-RESOURCE-ALLOCATION or OPEN) | (1) | (2) |
RECOVER-REQUESTS | local | local |
REORGANIZE-VERSION-BACKUP | local (how many masters?) | (2) |
REPAIR-CATALOG-BY-EXCHANGE | local | local |
REPAIR-CATALOG-BY-RESTORE | (1) | (2)* |
REPLACE-SAVE-FILE-BY-EXCHANGE | local | local |
REPLACE-SAVE-FILE-BY-RESTORE | local (how many masters?) | local |
RESTART-REQUESTS | (3) | (3) |
RESTORE-FILES | (1) and (4) | (2) and (4) |
RESTORE-LIBRARY-ELEMENTS | (1) and (4) | (2) and (4) |
RESTORE-NODE-FILES | local (node) | local (node) |
SELECT-FILE-NAMES | local | local |
SELECT-JV-NAMES | local | local |
SELECT-NODE-FILES | local (node) | local (node) |
SHOW-ARCHIVE | local | local |
SHOW-ARCHIVE-ATTRIBUTES | local | local |
SHOW-HSMS-PARAMETERS | local | local |
SHOW-MANAGEMENT-CLASS | local | local |
SHOW-NODE-PARAMETERS | local (node) | local (node) |
SHOW-PUBSET-PARAMETERS | local | local |
SHOW-PUBSET-USAGE | local | local |
SHOW-REQUESTS | local | local |
SHOW-SM-PUBSET-PARAMETERS | local | local |
SHOW-TAPE-CONTROL | local | local |
UPDATE-EXPORT-SAVE-FILE | local (data transfer) | local (data transfer) |
Key
(1)
The rules listed below are observed:
Shared pubsets imported in master mode are treated just like local pubsets.
If local pubsets are specified together with shared pubsets, the local pubsets are processed locally and the shared pubsets that were imported in slave mode are rejected with a warning.
Statements that deal with shared pubsets imported in slave mode are processed on the master, if the master is unequivocal; otherwise the statement is rejected.
(2)
The rules listed below are observed:
Requests are processed on the backup server when the archive definition BACKUP-SERVER-USAGE has the value *STD and at the same time the global HSMS parameter BACKUP-SERVER has a value other than *NONE.
If a host name is specified for BACKUP-SERVER, a check is made on the backup server to see whether the *LOCALHOST value or the name of the local system is set for BACKUP-SERVER. If this is not the case, the request is rejected and message HSM0329 is output to the log file.
If BACKUP-SERVER has the value *LOCALHOST, the request is executed locally as the local system is the backup server.
If the host name of the local system is specified for BACKUP-SERVER, the requests are handled as if *LOCALHOST had been specified.
If local pubsets are specified together with shared pubsets, the local pubsets are ignored as the backup server functionality is only supported for shared pubsets.
(2)*
Requests for REPAIR-CATALOG-BY-RESTORE are processed on the backup server depending on the archive attribute BACKUP-SERVER-USAGE of the SYSMIGRATE assigned to the pubset which is specified in the S0-PUBSET-ID operand.
(3)
Request management
See "Request management" for information on deleting/restarting requests.
(4)
Restore requests are processed locally when the catalog ID is renamed.
local (how many masters?)
Requests that very probably have more than one master are always processed locally. This applies in particular when a statement processes the entire save file.
local (data transfer)
Statements for data transfer are always processed locally.
local (node)
Statements for nodes are always processed locally.
local + SM-dynamic
Statements are processed locally. However, in an SM environment, the results of the statement processing can be viewed on other sharers of the SM pubset concerned.