For it to be possible to use HIPLEX MSCF, a network managed by BCAM must already exist.
The transport system BCAM is used by HIPLEX MSCF as the basis for the processing of elementary functions of the message transmission (see the "BCAM" manual [13 (Related publications)]).
Protocols
HIPLEX MSCF supports all transport protocols known to BS2000 OS DX or BCAM from (ISO class 4 and NEA protocols and TCP/IP).
To avoid network problems, all BCAM control files (e.g. APPLICATION-TABLE, SOCKETHOST-TABLE and PROCESSOR-TABLE, see the "openNet Server - BCAM" manual [13]) must be cataloged in the home pubset.
Independent monitoring connections
If a partner is being monitored through two independent monitoring connections, a partner failure can be recognized automatically, even without a shared pubset. In that case a partner-specific setting of RECOVERY-START=*AUTOMATIC is additionally required.
The monitoring connections have to be configured as physically independent communication paths (redundant network topology) between the MSCF applications $MRSAPP4 and $MRSAPP5 on the local processor and on the partner using BCMAP commands. The communication path should preferably follow geographically different routes so that it is unlikely that they could both be destroyed through the same external event (e.g. construction work).
The specification of NUMBER-OF-CTRL-CONN=2 in the START-MSCF-CONNECTION or MODIFY-MSCF-CONNECTION command acknowledges that two physically independent monitoring connections were generated between the partners. However, MSCF cannot verify the specification, so making the wrong specification could lead to erroneous failure recognition and loss of data integrity.
Adjusted network generation
From the point of view of HIPLEX MSCF, the network generation is regarded as adjusted when the processor and host name of each processor in the network agree and the corresponding name is also used on the partner processor. If there are several routes between two processors, we recommend working with alternative routers (see the "openNet Server - BCAM" manual [13 (Related publications)]) but not with different processor names (see also “Processor identification”).
For security reasons, MSCF connections should be established over a network that the system administration classifies as secure. The configuration of the MSCF connection via a specific connection takes place via the definition of the line connection, the processor name and the corresponding route name to the partners. For details on the configuration, please also refer to the "openNet Server - BCAM" manual [13].
Start time
If HIPLEX MSCF is started within the BS2000 startup procedure (CREATION-TIME=*BEFORE-SYSTEM-READY), BCAM must also be started within the BS2000 startup procedure. The latter can be initiated by the startup parameter service, e.g.
/BS2000 PARAMS /BEGIN BCAM DCSTART <dcstart parameter>, LWRESD=NO /EOF /END PARAMS
Wait time for MSCF with the BCEND command
The BCAM command BCTIMES, MAX-MSCF-DELAY operand, enables you to set a delay time for terminating MSCF when the BCAM command BCEND is entered, see the “openNet Server - BCAM” manual [13 (Related publications)]. The default value is 60 seconds.
You obtain information on the current value using the BCAM command SHOW-BCAM-ATTRIBUTES SELECT=*TIMER(*ALL / MAX-MSCF-DELAY)
The effects of BCEND on MSCF are described on "Terminating HIPLEX MSCF".