If the configuration file SYSPAR.MSCF.<ver> is used as delivered, only the MSCF subsystem is activated on the local processor. Connections to partner processors will not be set up automatically. They must be established explicitly for each of those processors with the START-MSCF-CONNECTION command.
By including the commands in the delivered configuration file or in another configuration file, these processes can be rendered automatic. The other configuration parameters can also be defined there. The configuration file is automatically processed when the MSCF subsystem is started.
Specification
The name of the configuration file can be specified in the DSSM subsystem catalog entry by MSCF as SUBSYSTEM-INFO-FILE (MODIFY-SUBSYSTEM-PARAMETERS command for the dynamic catalog or MODIFY-SUBSYSTEM-ATTRIBUTES statement for the static catalog) or as a subsystem parameter when HIPLEX MSCF is started (START-SUBSYSTEM command). On delivery SYSPAR.MSCF.<ver> is specified in the static DSSM subsystem catalog.
The specification as a subsystem parameter has priority over the entry in the DSSM subsystem catalog.File name
The configuration file can be stored under any name on any user ID but always on the processor’s home pubset. The file name must, however, be specified in full in the commands listed above.
If no user ID is specified, the specified file is searched for under the $TSOS ID and the $defluid ID (secondary read). If the configuration file is to be called with SUBSYSTEM-PARAMETER=’FILE-NAME=*SYSTEM when the START-SUBSYSTEM command is initiated, it must be stored under the file name SYS.MSCF-CONFIGURATION.File attributes
The configuration file must be a SAM file with variable-length records
(FILE-STRUCT=SAM, REC-FORM=V). It should have the attributes
USER-ACCESS=*OWNER-ONLY and ACCESS=*READ and may be protected by a write password.
Configuration file format
The configuration file contains entries in command format.:
The SET-MSCF-ENVIRONMENT command must be the first command in the configuration file (excepting remark lines). The following MSCF configuration parameters can be set with the command:
ABORT-LIMIT, HOST-PRIORITY, LEAVE-LIMIT,
LOCAL-PASSWORD, NOTIFY-BY-MAIL, XCS-NAME, TRACE-FILE,
FAIL-DETECTION-LIMIT, RECOVERY-START (general value), USER-TERM-LIMIT, NUMBER-OF-SERVERS and SERVER-TASK-LIMIT.
The configuration parameters presented in italics can be modified using the command MODIFY-MSCF-ENVIRONMENT.The START-MSCF-CONNECTION command is used to define the required MSCF connections. The partner-specific configuration parameters NUMBER-OF-CTRL-CONN and RECOVERY-START are also set with this command. They can be modified with the MODIFY-MSCF-CONNECTION command.
Up to 164 of these commands are permissible. A command may exist for the local processor but is, however, ignored. More than one entry for the same processor is not allowed.
Unambiguous abbreviations are permissible for the commands.
The commands are largely subject to the SDF rules with just the following exceptions:
Command lines can only be continued after a comma. The continuation character(" - ") can be located in any position.
Continuation lines must begin with "/".
The continuation of comment lines is not permitted.
The maximum permissible record length is 256 bytes (including record length field).
Configuration file in an XCS network
For participation in an XCS network, a configuration file must be set up. It must contain at least the SET-MSCF-ENVIRONMENT command with the name of the XCS network in which the processor is to participate.
The configuration files of all processors participating in the same XCS network must agree in terms of the following entries:
In the SET-MSCF-ENVIRONMENT command, the values of XCS-NAME and FAIL-DETECTION-LIMIT must agree.
The configuration files of all the processors which are to participate in the same XCS network must contain the START-MSCF-CONNECTION command for a CCS connection (not necessarily with the same RECOVERY-START operands).
In addition we also recommend keeping the values of RECOVERY-START and USER-TERM-LIMIT the same in the SET-MSCF-ENVIRONMENT command.
If no XCS name was specified when HIPLEX MSCF is started because:
the operand was not specified in the SET-MSCF-ENVIRONMENT command,
there is no configuration file,
The processor is started in CCS mode. It is only possible to restart MSCF in XCS mode during the current BS2000 session if system parameter MCXSPXCS=V is set (see "Global control parameters ").
Example of a configuration file
/REMARK "This is a configuration file for PROCNAM1." /REMARK "Processors PROCNAM1, PROCNAM2 and PROCNAM3 are to" /REMARK "form an XCS network with the name HUGO." /REMARK "In addition, the development system PROCNAM4 is" /REMARK "also to have access to the production processors." /REMARK /SET-MSCF-ENVIRONMENT XCS-NAME=HUGO, - / LOCAL-PASSWORD=C'OWN-PASS',- / FAIL-DETECTION-LIMIT=308, - / USER-TERM-LIMIT=240, - / LEAVE-LIMIT=600, - / HOST-PRIORITY=8, - / RECOVERY-START=*AUTOMATIC, - / TRACE-FILE=*STD /REMARK /REMARK "Production mode" /REMARK /REMARK "Participant in XCS network HUGO" /START-MSCF-CONNECTION PROCESSOR-NAME=PROCNAM1,- /CONNECTION-TYPE=*CLOSELY-COUPLED(REMOTE-PASSWORD=C'CCS-PSW1',- / RECOVERY-START=*AUTOMATIC) /REMARK /START-MSCF-CONNECTION PROCESSOR-NAME=PROCNAM2,- /CONNECTION-TYPE=*CLOSELY-COUPLED(REMOTE-PASSWORD=C'CCS-PSW2'),- / RECOVERY-START=*AUTOMATIC) /REMARK /START-MSCF-CONNECTION PROCESSOR-NAME=PROCNAM3,- /CONNECTION-TYPE=*CLOSELY-COUPLED(REMOTE-PASSWORD=C'CCS-PSW3'),- / RECOVERY-START=*AUTOMATIC) /REMARK /REMARK "Test and development processor" /REMARK /START-MSCF-CONNECTION PROCESSOR-NAME=PROCNAM4,- / RECOVERY-START=*CONSISTENT-BY-OPERATOR
The configuration file can be copied to processors PROCNAM1, PROCNAM2, PROCNAM3 and PROCNAM4. If the processor passwords (OWN-PASS, CCS-PSW1, CCS-PSW2, CCS-PSW3) are not identical, the LOCAL-PASSWORD operand in the SET-MSCF-ENVIRONMENT command must be supplied correctly on each processor before it is used.