Take suspended subsystem off hold
Component: | DSSM |
Functional area: | Subsystem management |
Domain: | SYSTEM-MANAGEMENT |
Privileges: | OPERATING |
Routing code: | R |
Function
The RESUME-SUBSYSTEM command enables systems support staff to take a suspended subsystem off hold.
Once this command has been executed successfully, connections can be set up once again to the specified subsystem, provided that the subsystem was previously placed in a defined hold state by means of a HOLD-SUBSYSTEM command. This ensures that all the necessary resources (holder task, address space) are still available and the initialization routine can be executed.
Format
RESUME-SUBSYSTEM |
SUBSYSTEM-NAME = <structured-name 1..8> ,VERSION = *STD / <product-version mandatory-man-corr> / <product-version without-man-corr> / *HIGHEST ,SUBSYSTEM-PARAMETER = *NONE / <c-string 1..254> ,RESET = *NO / *YES ,SYNCHRONOUS = *NO / *YES |
Operands
SUBSYSTEM-NAME = <structured-name 1..8>
Name of the subsystem which is to be taken off hold.
VERSION = *STD / <product-version mandatory-man-corr> / <product-version without-man-corr> / *HIGHEST
Identifies 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; see description of the data type "product-version" (SDF syntax representation)).
VERSION = *STD
If there is only one version of the subsystem that is on hold, the default value applies for this version.
If there are several suitable versions, the version must be specified.
VERSION = *HIGHEST
The highest version of the subsystem entered in the static subsystem catalog is selected.
SUBSYSTEM-PARAMETER = *NONE / <c-string 1..254>
Specifies whether special parameters that can only be evaluated by the specified subsystem are to be processed.
RESET =
Determines the mode and urgency of command processing.
RESET = *NO
If the relevant system is not yet in a defined hold state, the command is rejected until this is achieved.
RESET = *YES
The command is accepted irrespective of any cleardown process still outstanding and the subsystem or some components are immediately initialized (see notes).
SYNCHRONOUS =
Enables synchronous or asynchronous processing to be selected.
SYNCHRONOUS = *NO
The command is to be processed asynchronously, i.e. there is no need to wait for it to execute before making another input. No error messages relating to the execution of the command will be output.
SYNCHRONOUS = *YES
The command must be executed before another entry can be made. Any messages relevant to its execution are output.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | No error | |
1 | 0 | CMD0001 | No action necessary; subsystem already on hold |
1 | ESM0414 | Syntax error: an invalid version was specified | |
32 | ESM0224 | Command not processed | |
32 | ESM0228 | Command terminated abnormally |
Notes
To ensure a high degree of parallelism and data integrity, time-consuming management functions are not performed under the control of the calling task; instead they 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.
After the HOLD-SUBSYSTEM command, RESUME-SUBSYSTEM is rejected if DSSM has not yet fully suspended the subsystem. The RESET=*YES operand, however, enables systems support to cancel the hold state for the subsystem unconditionally, without waiting for completion of a HOLD-SUBSYSTEM command. In this case, the initialization routine is initiated. The subsystem involved, which is informed of the RESET, can determine the scope of the initialization routine itself (full initialization, partial initialization, no initialization).