Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Generation of the CCS network

&pagelevel(3)&pagelevel

As regards BCAM, the dependencies described in section “BCAM dependencies”, (MAXTSDU, protocols) must be taken into account. BCMAP commands for $MRSAPP and $MRSAPPS are recommended. The host names assigned on different processors by the DCOPT or DCSTART commands must be unique and should be the processor names.

We recommend generating an MSCF configuration file for the CCS network (see "MSCF configuration file"). The configuration file can be entered in the DSSM subsystem catalog as SUBSYSTEM-INFO-FILE.
If HIPLEX MSCF is to be started during the BS2000 startup process, the start time must be set to BEFORE-SYSTEM-READY and BCAM must also be started during the BS2000 startup.
If CCS connections are to be established automatically when HIPLEX MSCF is started (see "MSCF configuration file") or if the processor is to be protected in the network by a password, an MSCF configuration file is mandatory (see "Global control parameters").

A decentralized administration function must ensure that the processors in a CCS network have the following attributes:

  • unique SYSIDs

  • unique catalog IDs of the home pubsets

  • same value for the system parameter ENCRYPT
    If password coding is required, all the processors in the network must work with it.

  • mutually adjusted SRPM databases
    User jobs are processed on the remote side by MSCF server tasks. The server tasks "mask" themselves for this purpose with the ID and privileges of the local job submitter.

  • same values for FAIL-DETECTION-LIMIT.