A connection setup to a partner or the import of a pubset shared by the partner will be rejected by MSCF configuration management if the integrity of the network would otherwise be endangered. The following points are checked:
Coordination of monitoring characteristics
FAIL-DETECTION-LIMIT must be the same on both processors.Uniqueness of partner
The host name of the partner must be unique. A partner can therefore only re-enter the MSCF network of the processor when the previous network session with this partner has ended in full.Uniqueness of XCS network
The XCS name must be unique. Two different XCS networks with the same name must not be interconnected directly by HIPLEX MSCF or indirectly via another processor.
If a connection to a partner is rejected, this is indicated by the message MCS1005 being issued.
The rejection of the partner by configuration management results in the termination of the connection setup or the forced export (see "Abnormal termination of an MSCF system task") of the shared pubsets by the watchdog. After a partner crashes, it should particularly be ensured that no unanswered failure inquiry (message MCS1100) is outstanding and that all reconfigurations are completed before HIPLEX MSCF is restarted on the crashed partner.