HIPLEX MSCF is started separately on each processor, either automatically when BS2000 starts up or manually via the START-SUBSYSTEM MSCF command. Starting HIPLEX MSCF establishes the respective processor as a sharer in the HIPLEX MSCF communication network and a sharer in the MSCF network.
The communication system initializes the BCAM applications, creates the server tasks, and initializes configuration management. The registered functions required for entering the network, which create their network entities on the processor, are in turn initialized by configuration management. This concludes the "local initialization", and message
MCS0011 is output.
Network entry occurs as soon as the local initialization process is completed successfully. Of the total of four possible network types, LCS and particularly CCS form the basis for communication between the processors connected in the MSCF network. The shared pubset and XCS network types depend on the existence of the CCS network type.
If HIPLEX MSCF is started with the delivered configuration file or without a configuration file, the local processor remains isolated and does not join any network. But if the configuration file contains START-MSCF-CONNECTION commands, the local processor enters into the relevant networks if the partners have already expressed similar connection requests to the local processor. Once a CCS connection exists a shared pubset can be imported in order to establish a shared pubset network with the relevant partner.
If the configuration file permits the processor to participate in an XCS network, the processor joins the network by establishing the CCS connection to an already active partner of the same XCS network. At the same time a shared pubset network is established or extended with the XCS partner processor because of the mandatory XCS pubset. If no active XCS partner processor is available as yet, the local processor starts the XCS network (in which case it is the sole member of the XCS network). An MSCF connection to partner processors that have not yet expressed a connection request to the local processor is postponed until the partner processors actually request a connection.
So, depending on the contents of the configuration file, the processor can join either one, several, all or none of the networks of the available network types when the START-SUBSYSTEM MSCF command is executed. The command itself is always the same.Independent of the contents of the configuration file, the local processor can join further LCS, CCS, or shared pubset (SPVS) networks by entering the relevant START-MSCF-CONNECTION or IMPORT-PUBSET command during operation. Joining an existing XCS network, however, is only possible by including the XCS name and the relevant START-MSCF-CONNECTION command in the MSCF configuration file.
At startup HIPLEX attempts to establish MSCF connections to the processors named in the configuration file (see section “Establishing connections” and section “MSCF configuration file”). If the processor is to join an XCS network, the registered XCS and CCS functions are initialized and after the connection establishment attempts have been concluded, entry of the processor into the XCS network is initiated. If participation in an XCS network is not provided for, only CCS functions are started. From this point on the registered CPM function allows shared pubsets to be imported. A successful network entry concludes the start of HIPLEX MSCF on the processor.
Coordinating the start of BCAM and MSCF
When MSCF is started, MSCF connections can only be established (initiated by the relevant commands in the parameter file) once BCAM startup is successfully completed and the routes required for the MSCF connections are activated.
As well as BCAM commands you can also enter BS2000 commands in the SOF file. To make sure that the routes required by MSCF are available, we recommend setting up the SOF file as follows:
Activate the routes required by MSCF
Start the MSCF subsystem
Other BCAM and/or BS2000 commands.
To start MSCF from the BCAM-SOF file, SET-CODE CODE=R,CONSOLE=BCAM must be specified in the OPR parameter service.
Example
|  | Activate the routes required by MSCF |
| Start MSCF | |
|
| Other BCAM or BS2000 commands |
Notes
The start of HIPLEX MSCF on a processor with SYSID 250 is rejected with message MCS0007 (error code: 01).
Message MCS0029 indicates which configuration file was used when starting HIPLEX MSCF.
Message MCS0030 indicates which MSCF trace file was opened.
When message MCS0011 is output, a connection setup to partner processors is initiated but not yet concluded.
It is not possible to import shared pubsets before the start of HIPLEX MSCF. The import job is either delayed (slave import) or rejected (master import).
If MSCF is to be started within the BS2000 startup procedure (see "BCAM dependencies"), BCAM and MSCF cannot be coordinated from the SOF file with the START-SUBSYSTEM MSCF command (in this system state only DSSM can start a subsystem). However, if the BCAM routes needed by MSCF are activated at the beginning of the SOF file, once MSCF is loaded the MSCF connections specified in the configuration file are established in the BS2000 startup.