The BCAM network must be generated (see the “openNet Server - BCAM” manual [13 (Related publications)]).BCAM and MSCF are loaded on each processor in the network independently of each other. BCAM must be loaded before MSCF.
The message length (MAXTSDU) in the BCAM definition must be at least 8 Kbytes.
BCMAP commands for the applications $MRSAPP and $MRSAPPS must be started (where necessary).
A DSSM subsystem catalog entry must be created with the MSCF declarations (start time for MSCF, where applicable the name of the configuration file).
Starting the MSCF network or entering an existing network and manually setting up connections to partner processors (without configuration file)
Start HIPLEX MSCF with the START-SUBSYSTEM MSCF command
The START-MSCF-CONNECTION command must be started for each processor to which a connection is to be set up.
Starting the MSCF network or entering an existing network and setting up connections to partner processors (where configuration file exists)
The following two options are possible:
Start HIPLEX MSCF with the START-SUBSYSTEM MSCF command. When the subsystem is started, the connections to the processors for which the configuration file contains the START-MSCF-CONNECTION command are automatically set up.
Start HIPLEX MSCF implicitly with the BS2000 startup
Start BCAM in the BS2000 startup
Enter "BEFORE-SYSTEM-READY" as the MSCF start time in the DSSM subsystem catalog
Enter the configuration file in the DSSM subsystem catalog as the subsystem information file
The RDF should be set up in such a way that the necessary things are executed for the home processor before the BCAM network is fully activated. If the BCAM-SOF file is used, the commands for the BCAM connections used by HIPLEX MSCF and the corresponding BCMAP commands (if needed) should therefore be placed as near to the beginning as possible.
Manually clearing down connections to partner processors and terminating the MSCF network
The STOP-MSCF-CONNECTION command can be issued for each partner processor to which a connection is set up.
If HIPLEX MSCF is terminated with the STOP-SUBSYSTEM MSCF command, the STOP-MSCF-CONNECTION command is implicitly executed with the command for all the partner processors to which a connection is set up.