STOP command: Stopping an application subsystem: Difference between revisions
Jump to navigation
Jump to search
m (Automatically generated page update) |
No edit summary |
||
| (5 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
<dl> | <dl> | ||
<dt>Privileges | <dt>Privileges | ||
<dd>Defined in the | <dd>Defined in the subsystem definition | ||
<dt>Function | <dt>Function | ||
<dd>Stops an application subsystem | <dd>Stops an application subsystem | ||
</dl> | </dl> | ||
==Syntax== | ==Syntax== | ||
<p class="syntax">STOP <b>SUBSYS</b>TEM < | <p class="syntax">STOP <b>SUBSYS</b>TEM <span class="term">subsysname</span> [FROM <span class="term">location</span>] | ||
</p> | </p> | ||
Where: | |||
<table> | <table> | ||
<tr> | <tr> | ||
<th>subsysname</th> | <th>subsysname</th> | ||
<td> | <td>The name of the [[Application Subsystem development|application subsystem]], comprised of a maximum of ten characters.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<th>location</th> | <th>location</th> | ||
<td> | <td>Valid only for [[Application Subsystem development#Parallel Query Option.2F204 .28PQO.29_considerations|Parallel Query Option/204 service subsystems]], this is the CCAIN <code>LOCATION</code> parameter of the client node that activated the service subsystem. | ||
<p> | |||
<var class="term">location</var> is also the value of the <code>CLNT</code> field in the <var>LOGWHO</var> command output.</p></td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
==Usage notes== | ==Usage notes== | ||
<p>If the STOP command is issued when there are no active users in the application subsystem, the subsystem is completely stopped. The subsystem frees the core-resident control blocks and the CCATEMP pages associated with precompiled procedures. All enqueued procedures and file groups are released and all subsystem files and groups are closed.</p> | <p> | ||
<p>If the STOP command is issued with active users in the subsystem, the application subsystem facility sets the application subsystem to the drain state. Other users are barred from entering the subsystem. When the last user leaves, the subsystem is completely stopped. </p> | If the <var>STOP</var> command is issued when there are no active users in the application subsystem, the subsystem is completely stopped. The subsystem frees the core-resident control blocks and the CCATEMP pages associated with precompiled procedures. All enqueued procedures and file groups are released and all subsystem files and groups are closed.</p> | ||
<p>For more information about STOP SUBSYSTEM when it specifies a subsystem that uses remote files, see | <p> | ||
If the <var>STOP</var> command is issued with active users in the subsystem, the application subsystem facility sets the application subsystem to the drain state. Other users are barred from entering the subsystem. When the last user leaves, the subsystem is completely stopped. </p> | |||
<p> | |||
For more information about <var>STOP SUBSYSTEM</var> when it specifies a subsystem that uses remote files, see [[PQO: Scattered APSY subsystems#STOP SUBSYSTEM command processing|STOP SUBSYSTEM command processing]]. </p> | |||
[[Category:Commands]] | [[Category:Commands]] | ||
[[Category:Subsystem commands]] | |||
Latest revision as of 16:20, 23 March 2017
Summary
- Privileges
- Defined in the subsystem definition
- Function
- Stops an application subsystem
Syntax
STOP SUBSYSTEM subsysname [FROM location]
Where:
| subsysname | The name of the application subsystem, comprised of a maximum of ten characters. |
|---|---|
| location | Valid only for Parallel Query Option/204 service subsystems, this is the CCAIN LOCATION parameter of the client node that activated the service subsystem.
location is also the value of the |
Usage notes
If the STOP command is issued when there are no active users in the application subsystem, the subsystem is completely stopped. The subsystem frees the core-resident control blocks and the CCATEMP pages associated with precompiled procedures. All enqueued procedures and file groups are released and all subsystem files and groups are closed.
If the STOP command is issued with active users in the subsystem, the application subsystem facility sets the application subsystem to the drain state. Other users are barred from entering the subsystem. When the last user leaves, the subsystem is completely stopped.
For more information about STOP SUBSYSTEM when it specifies a subsystem that uses remote files, see STOP SUBSYSTEM command processing.