Description status: Functional area: Domain: Privileges: | MSCF V21.0A Pubset and MRSCAT management MULTI-CATALOG-AND-PUBSET-MGMT TSOS |
Routing code: | R |
Function
The MODIFY-MSCF-CONNECTION command is used to modify partner-specific monitoring parameters:
Number of monitoring connections
Defines how recovery measures are to be initiated
This command is evaluated only if a CCS connection to the partner exists. Use the START-MSCF-CONNECTION command to modify the monitoring parameters of an existing connection request or of an interrupted connection.
Format
MODIFY-MSCF-CONNECTION |
PROCESSOR-NAME = <alphanum-name 1..8> ,NUMBER-OF-CTRL-CONN = *UNCHANGED / 1 / 2 ,RECOVERY-START = *UNCHANGED / *STD / *AUTOMATIC / *BY-OPERATOR / *CONSISTENT-BY-OPERATOR / *SECURE |
Operands
PROCESSOR-NAME = <alphanum-name 1..8>
Name of the partner whose monitoring parameters are to be modified.
NUMBER-OF-CTRL-CONN = *UNCHANGED / 1 / 2
Number of independent monitoring connections through which the partner is to be monitored.
NUMBER-OF-CTRL-CONN = *UNCHANGED
The number of monitoring connections is not changed.
NUMBER-OF-CTRL-CONN = 1
The partner is to be monitored using one monitoring connection.
NUMBER-OF-CTRL-CONN = 2
The partner is to be monitored using two monitoring connection. If they fail concurrently, a partner failure can be detected automatically even without a shared pubset.
Note
Independent monitoring connections are only available if physically independent communication paths were configured between the same-name MSCF applications $MRSAPP4 and $MRSAPP5 on the local system and on the partner system using BCMAP commands. MSCF cannot verify this prerequisite, i.e. NUMBER-OF-CTRL-CONN=2 confirms that the specified communication paths are independent. An incorrect entry can lead to erroneous failure detection and a loss of data integrity.
RECOVERY-START = *UNCHANGED / *STD / *AUTOMATIC / *BY-OPERATOR / *CONSISTENT-BY-OPERATOR / *SECURE
Defines partner-specifically when the partner is monitored (see the section “Activating and deactivating MSCF partner monitoring” (Global control parameters)) and how the system is to respond in the event of the failure of the partner system (= partner-specific RECOVERY-START setting).
Note
The fail reconfiguration can only be started automatically if partner monitoring is certain that the partner has failed and this is permitted by both the general and the partner-specific RECOVERY-START settings on the local system and on the partner system (see the section “Inhibiting the automatic start of fail reconfiguration” (Global control parameters )).
RECOVERY-START = *UNCHANGED
The RECOVERY-START setting in not changed.
RECOVERY-START = *STD
Monitoring of the partner begins only when both the MSCF connection has been established and at least one joint shared pubset has been imported.
The general setting for the RECOVERY-START parameter determines the start time of fail reconfiguration.
Irrespective of this, fail configuration can never be initiated automatically if the partner is monitored only via two independent monitoring connections.
RECOVERY-START = *AUTOMATIC
Partner monitoring begins with the establishment of the MSCF connection.
The local system can automatically initiate fail reconfiguration for the partner even if it is only monitored via two independent monitoring connections (see NUMBER-OF-CTRL-CONN operand).
RECOVERY-START = *BY-OPERATOR
Partner monitoring begins with the establishment of the MSCF connection.
The local system does not initiate fail reconfiguration for the partner unless confirmed by systems support.
RECOVERY-START = *CONSISTENT-BY-OPERATOR
Same behavior as on RECOVERY-START=*BY-OPERATOR. In addition, the partner system does not initiate fail reconfiguration for the local system unless confirmed by systems support.
RECOVERY-START = *SECURE
The value *SECURE is only offered for reasons of compatibility and has the same behavior as RECOVERY-START = *CONSISTENT-BY-OPERATOR.
Return codes
| (SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
| 0 | CMD0001 | Command executed without error | |
| 1 | CMD2201 | Parameter error | |
| 2 | CMD2202 | MSCF subsystem not defined | |
| 3 | CMD2203 | Installation error | |
| 32 | MCS0025 | Internal error (bourse call, request memory) | |
| 64 | CMD0216 | User is not privileged | |
| 64 | MCS0009 | Local password invalid or local system specified as partner | |
| 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 |