STOP command: Stopping an application subsystem - Revision history

ELowell at 16:20, 23 March 2017

2017-03-23T16:20:39Z

← Older revision		Revision as of 16:20, 23 March 2017
Line 35:		Line 35:

	[[Category:Commands]]		[[Category:Commands]]
			[[Category:Subsystem commands]]

JAL: link repair

2016-11-30T17:02:59Z

link repair

← Older revision		Revision as of 17:02, 30 November 2016
Line 11:		Line 11:
	</p>		</p>

	~~<b>~~Where:~~</b>~~		Where:
	<table>		<table>
	<tr>		<tr>
Line 20:		Line 20:
	<tr>		<tr>
	<th>location</th>		<th>location</th>
	<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>		<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>
Line 30:		Line 32:
	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>		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>		<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>		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]]

JAL: link repair

2016-05-04T16:59:24Z

link repair

← Older revision		Revision as of 16:59, 4 May 2016
Line 30:		Line 30:
	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>		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>		<p>
	For more information about <var>STOP SUBSYSTEM</var> when it specifies a subsystem that uses remote files, see ~~the <var class="book">~~[[~~Media~~:~~M204_PQO204UserGuide_V75.pdf~~\|~~Parallel Query Option/204 User's Guide~~]]~~</var>~~. </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]]

JAL: add link

2016-01-06T19:43:33Z

add link

← Older revision		Revision as of 19:43, 6 January 2016
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>

JAL: add link

2015-07-22T19:16:43Z

add link

← Older revision		Revision as of 19:16, 22 July 2015
Line 30:		Line 30:
	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>		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>		<p>
	For more information about <var>STOP SUBSYSTEM</var> when it specifies a subsystem that uses remote files, see the <var class="book">Parallel Query Option/204 User's Guide</var>. </p>		For more information about <var>STOP SUBSYSTEM</var> when it specifies a subsystem that uses remote files, see the <var class="book">[[Media:M204_PQO204UserGuide_V75.pdf\|Parallel Query Option/204 User's Guide]]</var>. </p>

	[[Category:Commands]]		[[Category:Commands]]

JAL at 00:54, 7 November 2014

2014-11-07T00:54:54Z

← Older revision		Revision as of 00:54, 7 November 2014
Line 2:		Line 2:
	<dl>		<dl>
	<dt>Privileges		<dt>Privileges
	<dd>Defined in the ~~subsytem~~ definition		<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 <i>subsysname</i> [FROM <i>location</i>]		<p class="syntax">STOP <b>SUBSYS</b>TEM <span class="term">subsysname</span> [FROM <span class="term">location</span>]
	</p>		</p>

Line 14:		Line 15:
	<tr>		<tr>
	<th>subsysname</th>		<th>subsysname</th>
	<td> ~~is the~~ name of the application subsystem, comprised of a maximum of 10 characters.</td>		<td>The name of the 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, 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</td>		<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>
	</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 the <var>Parallel Query Option/204 User's Guide</var>. </p>		<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 the <var class="book">Parallel Query Option/204 User's Guide</var>. </p>

	[[Category:Commands]]		[[Category:Commands]]

Alex: Automatically generated page update

2013-02-28T01:05:28Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>Defined in the subsytem definition
<dt>Function
<dd>Stops an application subsystem
</dl>
==Syntax==
STOP SUBSYSTEM subsysname [FROM location]


Where:
<table>
<tr>
<th>subsysname</th>
<td> is the name of the application subsystem, comprised of a maximum of 10 characters.</td>
</tr>

<tr>
<th>location</th>
<td>, valid only for Parallel Query Option/204 service subsystems, 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</td>
</tr>

</table>
==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 <var>Parallel Query Option/204 User's Guide</var>. 
[[Category:Commands]]