Description status: Functional area: Domain: Privileges: | DSSM V21.0A Subsystem management SYSTEM-MANAGEMENT OPERATING |
Routing code: | R |
Function
The following command description only applies to the MSCF subsystem. A complete description of the command can be found in the “Commands” manual [10 (Related publications)].
Systems support can use this command to deactivate the MSCF subsystem. The command has the following results:
MSCF is locked for all new callers
MSCF is unloaded
All resources allocated are released
The STOP-SUBSYSTEM command is rejected if:
The MSCF subsystem is not found in the dynamic subsystem catalog
Subsystems that are already active or are in the process of activation are dependent on the MSCF subsystem to be deactivated
Subsystems that are already active or are in the process of activation have linkage relations with the MSCF subsystem to be deactivated
Format (extract)
STOP-SUBSYSTEM |
SUBSYSTEM-NAME = MSCF ,VERSION = *STD / <c-string 4..4> / <c-string 7..7> ,SUBSYSTEM-PARAMETER = *NONE / 'FORCED = NO' / 'FORCED = YES' ,FORCED = *NO / *YES ,SYNCHRONOUS = *NO / *YES |
Operands
SUBSYSTEM-NAME = MSCF
The MSCF subsystem is to be deactivated.
VERSION = *STD / <c-string 4..4> / <c-string 7..7>
Version of the MSCF subsystem. The format specified here must be identical to the format used in the subsystem definition (release and correction level are either mandatory or must not be specified, see SDF notational conventions in the “Commands” manual [10 (Related publications)]).
VERSION = *STD
The currently loaded version of the MSCF subsystem is selected.
SUBSYSTEM-PARAMETER = *NONE / 'FORCED = NO / YES'
Specifies whether special parameters are to be evaluated by MSCF.
'FORCED = NO'
MSCF can reject execution of the STOP-SUBSYSTEM MSCF command if one or more shared pubsets are imported on the local processor.
'FORCED = YES'
Forces execution of the STOP-SUBSYSTEM MSCF command, even if MSCF has already rejected execution of the command. If 'FORCED=YES' is specified, the local processor is disconnected from an XCS or shared pubset network and all shared pubsets are exported.
FORCED = *NO / *YES
Determines the mode and urgency of command processing.
FORCED = *NO
MSCF is not terminated until the tasks linked to the MSCF subsystem (MSCF holder task, XCM and watchdog task TSN: MXCM, WDGS, MSCF server tasks) are processed and terminated normally.
FORCED = *YES
Not permitted for MSCF.
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. No error messages relating to the execution of the command are output.
SYNCHRONOUS = *YES
The command must first be executed before any other commands can be entered.Any error messages relevant to command execution are output.
Return codes
| (SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
| 0 | CMD0001 | Command executed without errors | |
| 1 | 0 | CMD0001 | No action required |
| 32 | ESM0224 | Command not processed | |
| 32 | ESM0228 | Command terminated abnormally |
Notes
There are usually a variety of relationships between subsystems (dependencies, load relations).
In order to guarantee the performance of individual subsystems, these relationships must be taken into account. DSSM attempts to avoid potential conflicts that may arise from the user’s requirements and therefore rejects certain commands. Illegal actions, such as the unloading of subsystems on which active subsystems depend, are not executed.
However, if the user also generates complex subsystems using the operand CHECK-REFERENCE=*NO (see the SSCM statement SET-SUBSYSTEM-ATTRIBUTES), DSSM executes the requested functions despite possible conflicts.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, only the checking of the requested function is carried out synchronously (i.e. involving a wait state for the calling task). The actual processing is carried out by DSSM asynchronously and independently of the calling task.