START command: Starting an application subsystem: Difference between revisions
Jump to navigation
Jump to search
m (Automatically generated page update) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| 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 | ||
</dl> | </dl> | ||
==Syntax== | ==Syntax== | ||
<p class="syntax">START SUBSYSTEM < | <p class="syntax">START SUBSYSTEM <span class="term">subsysname</span> [<span class="term">parameters</span>] | ||
</p> | </p> | ||
Where: | |||
<table> | <table> | ||
<tr> | <tr> | ||
<th>subsysname</th> | <th>subsysname</th> | ||
<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> | <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 [[SCLASS|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>For more information about START SUBSYSTEM when it specifies a subsystem that uses remote files, see | 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, 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]] | |||
Latest revision as of 17:23, 23 March 2017
Summary
- Privileges
- Defined in the subsystem definition
- Function
- Activates an application subsystem
Syntax
START SUBSYSTEM subsysname [parameters]
Where:
| subsysname | The name of the application subsystem, comprised of a maximum of 10 characters. |
|---|---|
| parameters | Subsystem-specific parameters. As many as 255 characters of information can be entered. |
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, see Subsystem startup.
For more information about START SUBSYSTEM when it specifies a subsystem that uses remote files, see PQO subsystem command processing.