SUSPEND SUBSYSTEM command: Difference between revisions
m (Automatically generated page update) |
No edit summary |
||
| Line 20: | Line 20: | ||
</p> | </p> | ||
[[Category:Commands]] | [[Category:Commands]] | ||
[[Category:Subsystem commands]] | |||
Latest revision as of 16:18, 23 March 2017
Summary
- Privileges
- Defined in the subsystem definition
- Function
- To quiesce a subsystem so that no users are running while you change and refresh a series of procedures that may be related to each other.
Syntax
SUSPEND SUBSYSTEM subsys-name
Usage
A subsystem is not suspended until all active users have left it.
Unlike the STOP SUBSYSTEM command, the SUSPEND SUBSYSTEM command preserves all procedures which have been precompiled up to this point. They will not have to be recompiled following a RESUME SUBSYSTEM command.
The APSY initialization routine is not rerun.
Overriding the SUSPEND SUBSYSTEM command
The STOP SUBSYSTEM command may override the SUSPEND command. If the subsystem is suspended and you issue the STOP SUBSYSTEM command, then the subsystem will be stopped.
The START command cannot override the SUSPEND SUBSYSTEM command. If a subsystem is suspended and you issue the START command, the following messages are produced:
M204.2661: SUBSYSTEM subsys-name SUSPENDED M204.0473: UNABLE TO INITIALIZE subsys-name