This statement is for the HSMS administrator only. It is used to recover requests in an SM pubset after a host has crashed.
In the case of shared SM pubsets, this statement may only be issued on the master sharer.
DMS requests can be recovered independently of the node requests. This option is offered because, unlike node requests, DMS requests can be recovered very quickly after a crash. It takes longer to recover node requests because this is a more complex procedure.
The RECOVER-REQUESTS statement normalizes the status of all the requests of an SM pubset which is inhibited by the specified host. The result depends on the following factors:
type of request level (primary copy or master copy)
is this a Concurrent Copy session (CCOPY) or not?
status of the request
Inhibited requests | Recovery activities | ||
Request level | CCOPY | Status | |
Primary copy | no | ACCEPTED | Rename inhibit and local reactivation |
Primary copy | no | STARTED | Undo inhibit and new status INTERRUPTED |
Primary copy | no | STARTED SENT | Undo inhibit and new status INTERRUPTED |
Primary copy | yes | ACCEPTED | Undo inhibit and new status CANCELLED |
Primary copy | yes | STARTED | Undo inhibit and new status COMPLETED WITH ERRORS |
Primary copy | yes | STARTED SENT | Undo inhibit and new status COMPLETED WITH ERRORS |
Master copy | no | ACCEPTED | Undo inhibit and new status INTERRUPTED |
Master copy | no | STARTED | Undo inhibit and new status INTERRUPTED |
Master copy | yes | ACCEPTED | Undo inhibit and new status CANCELLED |
Master copy | yes | STARTED | Undo inhibit and new status COMPLETED WITH ERRORS |
Format (only for HSMS administrators)
RECOVER-REQUESTS | Alias: RER | ||||||||||||||||||||||||
| |||||||||||||||||||||||||
ENVIRONMENT =
Defines the HSMS environment where the request file to be processed is located.
ENVIRONMENT = *SYSTEM-MANAGED(...)
The HSMS statement relates only to the request file of the specified SM pubset environment.
CATALOG-ID = <cat-id>
Catalog ID of the SM pubset to which the HSMS statement applies.
HOST-NAME = <alphanum-name 1..8>
BCAM name of the host that is to be recovered.
FORCE =
Prior to the recovery, a number of checks can be made to establish the status of the host to be recovered.
FORCE = *NO
No checks are made.
In the case of an exclusively imported SM pubset, the current host is not included in the recovery.
For a shared SM pubset, the host to be recovered must not be an active sharer of the SM pubset.
FORCE = *YES
The status of the host to be recovered is not checked.
This option is not recommended.
REQUEST-DATA-ORIGIN =
You can specify the origin of the data which is to be processed by those requests for which the statement is valid.
This operand is used to quickly recover DMS requests after importing an SM pubset. You can also delay recovering node requests until all the corresponding POSIX/HSMS actions have been carried out successfully (see the “HSMS Vol. 1” manual [1], section “HIPLEX support for node files”).
REQUEST-DATA-ORIGIN = *PUBSET
Data to be processed by the affected requests originates from a pubset. The data therefore consists of DMS files.
REQUEST-DATA-ORIGIN = *NODE
Data to be processed by the affected requests originates from HSMS managed nodes. The data therefore consists of node files.