START command: Starting an application subsystem - Revision history

ELowell: /* Usage notes */

2017-03-23T17:23:30Z

Usage notes

← Older revision		Revision as of 17:23, 23 March 2017
Line 33:		Line 33:
	If the application subsystem is draining when the command is issued, the Subsystem Management facility makes the subsystem available for use.</p>		If the application subsystem is draining when the command is issued, the Subsystem Management facility makes the subsystem available for use.</p>
	<p>		<p>
	If the subsystem is not autostart, then information passed via this parameter can be used only by the subsystem utilization procedure. Otherwise, the subsystem <var>LOGIN</var> procedure can make use of the information passed. </p>		If the subsystem is not autostart, then information passed via this parameter can be used only by the subsystem utilization procedure. Otherwise, the subsystem <var>LOGIN</var> procedure can make use of the information passed.</p>
	<p>
	For more information about <var>START SUBSYSTEM</var> when it specifies a subsystem that uses remote files, see [[PQO: Scattered APSY subsystems#Subsystem command processing\|PQO subsystem command processing]]. </p>		<p>For more information, see [[System requirements for Application Subsystems#Subsystem startup\|Subsystem startup]].</p>

			<p>For more information about <var>START SUBSYSTEM</var> when it specifies a subsystem that uses remote files, see [[PQO: Scattered APSY subsystems#Subsystem command processing\|PQO subsystem command processing]]. </p>

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

ELowell: /* Summary */

2017-03-23T17:09:43Z

Summary

← Older revision		Revision as of 17:09, 23 March 2017
Line 2:		Line 2:
	<dl>		<dl>
	<dt>Privileges		<dt>Privileges
	<dd>Defined in the subsystem definition		<dd>Defined in the [[System requirements for Application Subsystems#Overview of the Subsystem Management facility\|subsystem]] definition
	<dt>Function		<dt>Function
	<dd>Activates an application subsystem		<dd>Activates an application subsystem

ELowell at 16:20, 23 March 2017

2017-03-23T16:20:08Z

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

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

JAL: /* Syntax notes */ add link

2016-11-30T16:56:32Z

Syntax notes: add link

← Older revision		Revision as of 16:56, 30 November 2016
Line 25:		Line 25:

	===Syntax notes===		===Syntax notes===
	The user class determines whether this command can be issued.		The [[SCLASS\|user class]] determines whether this command can be issued.

	==Usage notes==		==Usage notes==

JAL: minor formatting

2016-01-28T22:11:42Z

minor formatting

← Older revision		Revision as of 22:11, 28 January 2016
Line 6:		Line 6:
	<dd>Activates an application subsystem		<dd>Activates an application subsystem
	</dl>		</dl>

	==Syntax==		==Syntax==
	<p class="syntax">START SUBSYSTEM <i>subsysname</i> [<i>parameters</i>]		<p class="syntax">START SUBSYSTEM <span class="term">subsysname</span> [<span class="term">parameters</span>]
	</p>		</p>

	~~<b>~~Where:~~</b>~~		Where:
	<table>		<table>
	<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 10 characters.</td>
	</tr>		</tr>

	<tr>		<tr>
	<th>parameters</th>		<th>parameters</th>
	<td> ~~specify subsystem~~-specific parameters. As many as 255 characters of information can be entered.</td>		<td>Subsystem-specific parameters. As many as 255 characters of information can be entered.</td>
	</tr>		</tr>

	</table>		</table>

	===Syntax notes===		===Syntax notes===
	The user class determines whether this command can be issued.		The user class determines whether this command can be issued.

	==Usage notes==		==Usage notes==
	<p>		<p>

JAL: /* Usage notes */ add link

2016-01-28T22:08:08Z

Usage notes: add link

← Older revision		Revision as of 22:08, 28 January 2016
Line 26:		Line 26:
	The user class determines whether this command can be issued.		The user class determines whether this command can be issued.
	==Usage notes==		==Usage notes==
	<p>If the application subsystem is inactive when the START command is issued, the Subsystem Management facility opens all the application subsystem files, builds core-resident control blocks, and includes the application subsystem initialization procedure. </p>		<p>
	<p>If the application subsystem is draining when the command is issued, the Subsystem Management facility makes the subsystem available for use.</p>		If the application subsystem is inactive when the <var>START</var> command is issued, the Subsystem Management facility opens all the application subsystem files, builds core-resident control blocks, and includes the application subsystem initialization procedure. </p>
	<p>If the subsystem is not autostart, then information passed via this parameter can be used only by the subsystem utilization procedure. Otherwise, the subsystem LOGIN procedure can make use of the information passed. </p>		<p>
	<p>For more information about START SUBSYSTEM when it specifies a subsystem that uses remote files, see ~~the <var>Parallel Query Option/204 User's Guide~~.~~</var>~~ </p>		If the application subsystem is draining when the command is issued, the Subsystem Management facility makes the subsystem available for use.</p>
			<p>
			If the subsystem is not autostart, then information passed via this parameter can be used only by the subsystem utilization procedure. Otherwise, the subsystem <var>LOGIN</var> procedure can make use of the information passed. </p>
			<p>
			For more information about <var>START SUBSYSTEM</var> when it specifies a subsystem that uses remote files, see [[PQO: Scattered APSY subsystems#Subsystem command processing\|PQO subsystem command processing]]. </p>

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

Alex: Automatically generated page update

2013-02-28T01:05:27Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>Defined in the subsystem definition
<dt>Function
<dd>Activates an application subsystem
</dl>
==Syntax==
START SUBSYSTEM subsysname [parameters]


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>parameters</th>
<td> specify subsystem-specific parameters. As many as 255 characters of information can be entered.</td>
</tr>

</table>
===Syntax notes===
The user class determines whether this command can be issued.
==Usage notes==
If the application subsystem is inactive when the START command is issued, the Subsystem Management facility opens all the application subsystem files, builds core-resident control blocks, and includes the application subsystem initialization procedure. 
If the application subsystem is draining when the command is issued, the Subsystem Management facility makes the subsystem available for use.
If the subsystem is not autostart, then information passed via this parameter can be used only by the subsystem utilization procedure. Otherwise, the subsystem LOGIN procedure can make use of the information passed. 
For more information about START SUBSYSTEM when it specifies a subsystem that uses remote files, see the <var>Parallel Query Option/204 User's Guide.</var> 
[[Category:Commands]]