The basic requirements for a successful MSCF connection setup are described in section “BCAM dependencies”.
The connections to partner processors can be set up for all of the desired connections via the configuration file, or for each individual connection by entering a command (START-MSCF-CONNECTION , see "START-MSCF-CONNECTION (Dynamically establish MSCF connection to partner system)"). The type (LCS or CCS) of connection to the respective partner processor is also defined at this point.
If a connection is lost (indicated by message MCS0014), it can also be re-established with the START-MSCF-CONNECTION command.
The connection to a partner processor is only established if the corresponding command for the local processor has already been issued on the partner processor named in the command. If this is not the case (message MCS0009 is output), the local processor notes that a connection is to be established to the partner processor. The connection is set up as soon as the START-MSCF-CONNECTION command for the local processor is issued on the partner processor (message MCS0013 is output on the local processor, message MCS0010 is output on the partner processor).
With each connection setup, HIPLEX MSCF updates the availability of the of the home pubset in MRSCAT in both the requesting and the accepting processor ("Pubsets as file containers").
Notes
An MSCF connection cannot be established if the SYSID of a processor is the same as that of another processor in the same network. The MSCF connection setup is rejected with message MCS0009 (error code: 08).
A processor cannot be connected to more than 163 partners at the same time (restriction imposed by the SYSID).
If the BCAM-SOF file was not processed in full due to an error when loading BCAM, the Start Option File (SOF) must be explicitly executed again with CALL-BCAM-COMMANDS before MSCF connections are established (reason: incomplete network or BCMAP configuration).