Since MSCF is managed as a subsystem of DSSM and controlled by the DSSM commands START-SUBSYSTEM and STOP-SUBSYSTEM, the subsystem declaration of MSCF (file SYSSSC.MSCF.<ver>) must be entered in the subsystem catalog of DSSM; it is imported implicitly during installation. This entry can be modified with the MODIFY-SUBSYSTEM-PARAMETER command in the dynamic subsystem catalog or with the MODIFY-SUBSYSTEM-ATTRIBUTES in the static subsystem catalog.
The two operands listed below permit modifications:
An MSCF configuration file (see "MSCF configuration file") can be specified with SUBSYSTEM-INFO-FILE which is processed when HIPLEX MSCF is started. The default setting is file SYSPAR.MSCF.<ver>.
The use of a configuration file is mandatory for the XCS network.The start time of HIPLEX MSCF can be defined with CREATION-TIME. The available choices are as follows:
CREATION-TIME = *AT-CREATION-REQUEST (default)
HIPLEX MSCF is started via the START-SUBSYSTEM MSCF command by starting the MSCF subsystem.CREATION-TIME = *BEFORE-SYSTEM-READY
HIPLEX MSCF is started implicitly during the BS2000 system start. This presupposes that BCAM is also started during the BS2000 system start.
This setting is recommended where a processor is to participate in an XCS network because global lock requests are rejected until the processor is integrated in an XCS network.