Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

START-SUBSYSTEM Activate subsystem

&pagelevel(3)&pagelevel

Description status:

Functional area:

Domain:

Privileges:

DSSM V21.0A

Subsystem management

SYSTEM-MANAGEMENT

OPERATING
SUBSYSTEM-MANAGEMENT

Routing code:

R

Function

The following command description only applies to the MSCF subsystem. A full description of the command can be found in the “Commands” manual [10 (Related publications)].

The following information from the dynamic subsystem catalog is used for activating the MSCF subsystem:

  • data concerning the loading and linking of the subsystem

  • data concerning initialization/deinitialization and termination of job relations

  • data concerning entry points, secondary components, and operational dependencies (see the relevant SSCM statements in the "DSSM/SSCM Subsystem Management in BS2000" manual [ 6 (Related publications)])

The command is rejected if:

  • the subsystem could not be found in the dynamic subsystem catalog

  • the subsystem is already active

  • subsystems on which the subsystem to be activated depends are not loaded

  • a necessary file (e.g. message file, library) is missing

An appropriate message informs systems support staff whether the command has been accepted or rejected.

Format (excerpt)

START-SUBSYSTEM

SUBSYSTEM-NAME = MSCF

,VERSION = *STD / <product-version mandatory-man-corr> / 



<product-version without-man-corr> /*HIGHEST

,SUBSYSTEM-PARAMETER = *NONE / <c-string 1..254>


<c-string 1..254>



|

FILE-NAME = *NONE / *SYSTEM / <filename 1..54>



|

,NUMBER-OF-SERVERS = *STD / <integer 2..10>

,RESET = *NO / *YES

,SYNCHRONOUS = *NO / *YES

Operands

SUBSYSTEM-NAME = MSCF
Name of the subsystem to be activated.

VERSION = *STD / <product-version mandatory-man-corr> / <product-version without-man-corr> / *HIGHEST
Specifies the version number.
If a version number is specified, the format specified here must be identical to the format used when the subsystem was defined (release and correction status mandatory or not allowed).

VERSION = *STD

If several versions exist for the specified subsystem, and neither a version nor *STD is explicitly specified,  the lowest version number for this subsystem that is stored in the static subsystem catalog is selected.

VERSION = *HIGHEST
Selects the highest version of the subsystem entered in the static subsystem catalog.

SUBSYSTEM-PARAMETER = *NONE / C' ... '
Specifies whether special parameters which can only be evaluated by the specified subsystem (MSCF) are to be processed.

SUBSYSTEM-PARAMETER = *NONE
Default value. The file specified in the DSSM catalog as the subsystem file is interpreted as the MSCF configuration file. If no file is specified in the DSSM catalog, only the MSCF subsystem is loaded. No connections are established.
Any connections required must be established explicitly via the START-MSCF-CONNECTION command.

SUBSYSTEM-PARAMETER = <c-string 1..254>
Special parameters that can only be evaluated by the MSCF subsystem are to be processed. The following must be specified as C strings (C'...').

FILE-NAME = *NONE / *SYSTEM / <filename 1...54>
Name of the MSCF configuration file to be evaluated and processed when the subsystem is loaded. The MSCF configuration file contains the MSCF configuration parameters and a description of the MSCF connections to be established automatically (see "MSCF configuration file").
If the FILE-NAME parameter is not specified explicitly, the file specified in the DSSM catalog as the subsystem file is used as the configuration file.

FILE-NAME = *NONE
No MSCF configuration file is to be used. Any configuration file specified as the subsystem file in the DSSM catalog is also ignored.
The MSCF subsystem is loaded. No connections are established; they must be set up explicitly via the START-MSCF-CONNECTION command.

FILE-NAME = *SYSTEM
The MSCF configuration file with the name SYS.MSCF-CONFIGURATION is to be used. The file is sought under the user ID TSOS and, if not found, under the system default ID (secondary read). Any configuration file specified as the subsystem file in the DSSM catalog is ignored.

FILE-NAME = <filename 1..54>
The specified file is to be used as the MSCF configuration file. If no user ID is specified in the file name, the user ID $TSOS and, if not found, the system default ID (secondary read) are used.
Any configuration file specified as the subsystem file in the DSSM catalog is ignored.

NUMBER-OF-SERVERS = *STD / <integer 2..10>
Number of MSCF server tasks to be made available on this processor (at start time). This number can be between 2 and 10, depending on the operand value. If this operand is not specified, the value set in the configuration file applies (see SET-MSCF-ENVIRONMENT command). A value defined via this operand has priority over any specification in the configuration file. The number may increase in the course of an MSCF session.

NUMBER-OF-SERVERS = *STD
Four server tasks are made available.

NUMBER-OF-SERVERS = <integer 2..10>
The specified number of server tasks is made available.

RESET = *NO / *YES
Determines the mode and urgency of command processing.

RESET = *NO
If the respective subsystem is being deactivated, the command is rejected until this blocking process has been completed.

RESET = *YES
The command is accepted irrespective of any outstanding deactivation process, and the subsystem or some of its components are initialized.
The version parameter is mandatory for this operand.

SYNCHRONOUS = *NO / *YES
Enables synchronous or asynchronous processing to be selected.

SYNCHRONOUS = *NO
The command is to be processed asynchronously. As soon as the command is entered, it is possible to enter further commands. Error messages relating to the execution of the command are output on the console.

SYNCHRONOUS = *YES
Further commands cannot be entered until the command is executed. Any error messages regarding the execution of the command are output.

Return codes

(SC2)SC1MaincodeMeaning

0CMD0001Command executed without errors
10CMD0001No action required

32ESM0224Command not processed

32ESM0228Command terminated abnormally


Note

To ensure a high degree of parallelism and data integrity, time-consuming management functions are not performed under the control of the calling task, rather are transferred to a DSSM task.
As a rule, the requested function is checked synchronously (i.e. involving a wait state for the calling task). The actual processing, however, is performed by DSSM asynchronously and independently of the calling task.