STOP command: Stopping an application subsystem: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (add link)
m (add link)
Line 15: Line 15:
<tr>
<tr>
<th>subsysname</th>
<th>subsysname</th>
<td>The name of the application subsystem, comprised of a maximum of ten characters.</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>Valid only for Parallel Query Option/204 service subsystems, this is the CCAIN LOCATION parameter of the client node that activated the service subsystem. <var class="term">location</var> is also the value of the CLNT field in the <var>LOGWHO</var> command output.</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 LOCATION parameter of the client node that activated the service subsystem. <var class="term">location</var> is also the value of the CLNT field in the <var>LOGWHO</var> command output.</td>
</tr>
</tr>
</table>
</table>

Revision as of 19:43, 6 January 2016

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 CLNT field in the LOGWHO command output.

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 the Parallel Query Option/204 User's Guide.