Description status: Functional area: Domain: Privileges: | MSCF V21.0A Pubset and MRSCAT management MULTI-CATALOG-AND-PUBSET-MGMT TSOS |
Routing code: | R |
Function
The START-MSCF-CONNECTION command is used to set up the connection to a partner system. This can either be an LCS or CCS connection. CCS connections are required for shared pubset or XCS networks. If passwords have been specified for local systems and/or partner systems, they have to be entered when a connection of the CCS type is established.
When MSCF is started, the connection is set up via entries in a configuration file (entered in the subsystem catalog or specified with SUBSYSTEM-PARAMETER='FILE-NAME=...' in the START-SUBSYSTEM command). The START-MSCF-CONNECTION and STOP-MSCF-CONNECTION commands allow MSCF connections to be set up or closed down. This does not modify the configuration file.
The connection to a partner system will only be established if the relevant command has already been executed on the partner system named in the command. Otherwise the connection request is only provisionally recorded, i.e. the local system will accept future connection requests from the partner system.
Format
START-MSCF-CONNECTION | ||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||
Operands
PROCESSOR-NAME = <alphanum-name 1..8>
Name of the system to which a connection is to be set up.
CONNECTION-TYPE =
Specifies the type of connection.
CONNECTION-TYPE = *CLOSELY-COUPLED(...)
Default. Selects CCS (closely-coupled system). CCS is a prerequisite for shared pubset and XCS network operation.
REMOTE-PASSWORD = *NONE / *SECRET / <c-string 1..8> / <x-string 1..16>
Here you have to give the password that the partner system defined with its LOCAL-PASSWORD operand. Otherwise the partner system will reject the connection.The REMOTE-PASSWORD operand has the following special characteristics:
The password entered is not logged.
The input field is automatically blanked out in the guided dialog.
In unguided dialog and foreground procedures, the entry *SECRET or ^, SDF provides a blanked out input field for inputting the password .
LOCAL-PASSWORD = *NONE / *SECRET / <c-string 1..8> / <x-string 1..16>
A password can be defined for an MSCF session on a system through an MSCF configuration file (see command SET-MSCF-ENVIRONMENT). If this has been done for the local system, then the password has to be entered here. Otherwise the command will be rejected.
On the partner system, the password must be specified for the local system in the REMOTE-PASSWORD operand of the START-MSCF-CONNECTION command.
The LOCAL-PASSWORD operand has the following special characteristics:
The password entered is not logged.
The input field is automatically blanked out in the guided dialog.
In unguided dialog and foreground procedures, the entry *SECRET or ^, SDF provides a blanked out input field for inputting the password .
NUMBER-OF-CTRL-CONN = *NOT-SPECIFIED / 1 / 2
Defines the number of independent monitoring connections through which the partner is monitored.
NUMBER-OF-CTRL-CONN = *NOT-SPECIFIED
When the connection is established for the first time, the partner is monitored via a monitoring connection. Otherwise the value set with the last START-MSCF-CONNECTION or MODIFY-MSCF-CONNECTION command remains invalid.
NUMBER-OF-CTRL-CONN = 1
The partner is monitored via a monitoring connection.
NUMBER-OF-CTRL-CONN = 2
The partner is monitored via two independent monitoring connections. If they both fail simultaneously a partner failure can be detected automatically, even without using a shared pubset if RECOVERY-START= *AUTOMATIC is set partner-specifically.
Note
Independent monitoring connections only exist 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 the BCMAP command. MSCF cannot check whether this is actually the case. This means that NUMBER-OF-CTRL-CONN=2 confirms that the communication paths specified are physically independent. An incorrect specification may lead to erroneous failure detection and the loss of data integrity.
RECOVERY-START = *NOT-SPECIFIED / *STD / *AUTOMATIC / *BY-OPERATOR / *CONSISTENT-BY-OPERATOR / *SECURE
Defines partner-specifically when the partner is monitored or not (see “Activating and deactivating MSCF partner monitoring” (Global control parameters)) and how recovery measures are to be initiated in the case of an error (e.g. failure of a system or a connection).
Note
The setting for RECOVERY-START cannot be changed while a system component holds the Cluster Recovery Lock (CRL) (see also the RELEASE-CLUSTER-RECOVERY-LOCK command).
A fail reconfiguration can only be started automatically if partner monitoring is certain that the partner has failed and if this is allowed both by the general and the partner-specific RECOVERY-START settings on the local system and on the partner system (see “Inhibiting the automatic start of fail reconfiguration” (Global control parameters)).
RECOVERY-START = *NOT-SPECIFIED
When the connection is established for the first time, system behavior is the same as for RECOVERY-START=*STD (see below). Otherwise the value set when the START-MSCF-CONNECTION or MODIFY-MSCF-CONNECTION command last executed in the current MSCF session applies.
RECOVERY-START = *STD
Partner monitoring 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 start fail reconfiguration for the partner automatically even if the partner is only being 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 start fail reconfiguration for this partner until the action is confirmed by systems support.
RECOVERY-START = *CONSISTENT-BY-OPERATOR
Same behavior as with RECOVERY-START=*BY-OPERATOR. Additionally, the partner system does not start fail reconfiguration for the local system until the action is confirmed by systems support.
RECOVERY-START = *SECURE
The value *SECURE is still accepted for reasons of compatibility. The behavior is the same as with RECOVERY-START = *CONSISTENT-BY-OPERATOR.
CONNECTION-TYPE = *LOOSELY-COUPLED
LCS (loosely-coupled system) does not support shared pubset or XCS network operation.
Return codes
| (SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
| 0 | CMD0001 | Command executed without errors | |
| 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 |
Notes
The commands START- and STOP-MSCF-CONNECTION do not modify entries in the (static) MSCF configuration file.
If an MSCF connection is lost due to an error, MSCF automatically starts a connection recovery. If this is successful the message MCS0018 is issued on the console and data communication continues. Remote tasks may be lost during connection recovery and may cause an error on the caller.
The system automatically and if necessary repeatedly tries to establish a new connection, if connection recovery was not successful. The attempts are stopped when there is no hope of reestablishing a connection (e.g. the partner has failed or is unknown to BCAM). During the connection recovery attempts there is no connection to the partner, so remote tasks are rejected.
If the MSCF connection fails due to BCAM, a new MSCF connection is not automatically established if the BCAM network is re-established through external influences (e.g. BCIN-/BCACT command). The START-MSCF-CONNECTION command has to be entered again. If the START-MSCF-CONNECTION command is entered anew values other than the standard value *NONE for the REMOTE-PASSWORD and LOCAL-PASSWORD operands have to be re-specified. However, the current value of the NUMBER-OF-CTRL-CONN and RECOVERY-START monitoring parameters remains in place. This is also the case following an explicit connection establishment.