Description status: Functional area: Domain: Privileges: | MSCF V 21.0A Pubset and MRSCAT management MULTI-CATALOG-AND-PUBSET-MGMT OPERATING |
Routing code: | R |
Function
Systems support can use the RELEASE-CLUSTER-RECOVERY-LOCK command to manually release the Cluster Recovery Lock (CRL).
Under certain special conditions of the operating system (e.g. during CPU reconfiguration) the operating system is halted for a certain time. To prevent the risk of incorrect failure detection by MSFC, the system component responsible for the special condition can reserve the Cluster Recovery Lock (CRL) during the critical period. While the CRL is reserved, a fail reconfiguration by MSCF is only started after confirmation by systems support.
Current users of the CRL are the VM2000 command MOVE-VM and, on the SX 150 model series, dynamic reconfiguration.
Reservation and release of the CRL by a system component is indicated by the messages MCS1048 and MCS1049.
Application for manual release of the CRL
Normally the CRL is reset after the special condition has terminated. If this is not done (e.g. because of an error), automatic failure handling is blocked. In this case the CRL can be released using a command.
Reservation of the CRL is indicated in the SHOW-MSCF-CONFIGURATION command with RECOVERY-START=LOCKED.
Format
RELEASE-CLUSTER-RECOVERY-LOCK |
| HOST-NAME = *OWN / <alphanum-name 1..8> |
Operands
HOST-NAME =
Specifies the BCAM name of the processor which keeps the CLUSTER-RECOVERY-LOCK to be released
HOST-NAME = *OWN
The CLUSTER-RECOVERY-LOCK kept by the own host is to be released. This corresponds to the functionality of the command in earlier versions.
HOST-NAME = <alphanum-name 1..8>
The CLUSTER-RECOVERY-LOCK kept by specified partner is to be released on the own host.
The fail recognition by MSCF is reactivated for the specified partner. This is done exclusively on the host on which the command has been issued. Thus, if necessary, a fail reconfiguration can be started by MSCF.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
| 0 | CMD0001 | Command executed without error | |
| 1 | 0 | CMD0001 | No action required |
| 1 | CMD2201 | Parameter error | |
| 2 | CMD2202 | MSCF subsystem not defined | |
| 3 | CMD2203 | Installation error | |
| 40 | MCS1054 | Specified host is not known | |
| 64 | CMD0216 | User is not privileged | |
| 65 | CMD2241 | MSCF subsystem is not loaded | |
| 65 | MCS0003 | MSCF subsystem currently being loaded | |
| 65 | MCS0004 | MSCF subsystem currently being unloaded | |
| 66 | CMD2242 | No connection to the MSCF subsystem | |
| 128 | CMD2280 | MSCF subsystem temporarily not available | |
| 129 | CMD2281 | MSCF subsystem unavailable for an extended period | |
| 130 | CMD2282 | MSCF subsystem unavailable for an undefined period |