SIRAPSY command: Difference between revisions
No edit summary |
m (minor cleanup) |
||
| Line 1: | Line 1: | ||
<p class="note"><b>Note:</b> This is a <var class="product">[[Sirius Mods]]</var>-only command prior to Version 7.5 of <var class="product">[[Model 204]]</var>.</p> | <p class="note"><b>Note:</b> This is a <var class="product">[[Sirius Mods]]</var>-only command prior to Version 7.5 of <var class="product">[[Model 204]]</var>.</p> | ||
The <var>SIRAPSY</var> command allows the manual setting of the resident/non-resident | |||
attribute of a pre-compiled subsystem procedure. | attribute of a pre-compiled subsystem procedure. | ||
This is useful in overriding | This is useful in overriding | ||
<var class="product">Model 204</var>'s default behavior if the decisions it makes based on RESTHRSH and | <var class="product">Model 204</var>'s default behavior if the decisions it makes based on <var>[[RESTHRSH parameter|RESTHRSH]]</var> and <var>[[RESLTHR parameter|RESLTHR]]</var> are not appropriate. | ||
RESLTHR are not appropriate. | The <var>SIRAPSY</var> command can only be run | ||
The SIRAPSY command can only be run | against an active subsystem so a logical place for <var>SIRAPSY</var> commands might be | ||
against an active subsystem so a logical place for SIRAPSY commands might be | in a subsystem start/init procedure. | ||
in a subsystem start/init | |||
==Syntax== | |||
<p class="syntax">SIRAPSY DIS | DISPLAY | RES | NORES <span class="term">subsystem proc</span> </p> | |||
Where: | |||
<ul> | |||
<li><var class="term">subsystem</var> is the name of the subsystem to which the command applies.</li> | |||
<li><var class="term">proc</var> is the name of the procedure to which the command applies. </li> | |||
</ul> | |||
==Usage== | |||
The <var>SIRAPSY </var> command is only available with the <var class="product">Sirius Performance Enhancements V2</var>, and it can only be issued by a system manager or system administrator. | |||
==Example== | |||
The following command sets SIRMON procedure <code>MOPR-MENU</code> to become resident next time it is loaded: | |||
<p class="code">SIRAPSY RES SIRMON MOPR-MENU | <p class="code">SIRAPSY RES SIRMON MOPR-MENU | ||
</p> | </p> | ||
sets SIRMON procedure MOPR- | |||
This command sets SIRMON procedure <code>MOPR-SYSOVR</code> so that it will never be set to | |||
resident: | |||
<p class="code">SIRAPSY NORES SIRMON MOPR-SYSOVR | <p class="code">SIRAPSY NORES SIRMON MOPR-SYSOVR | ||
</p> | </p> | ||
<code>SIRAPSY NORES</code> will not drop the residency attribute of a | |||
SIRAPSY NORES will not drop the residency attribute of a | |||
procedure once it is made resident. | procedure once it is made resident. | ||
[[Category:System administrator commands]] | [[Category:System administrator commands]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
Latest revision as of 20:52, 11 November 2014
Note: This is a Sirius Mods-only command prior to Version 7.5 of Model 204.
The SIRAPSY command allows the manual setting of the resident/non-resident attribute of a pre-compiled subsystem procedure. This is useful in overriding Model 204's default behavior if the decisions it makes based on RESTHRSH and RESLTHR are not appropriate. The SIRAPSY command can only be run against an active subsystem so a logical place for SIRAPSY commands might be in a subsystem start/init procedure.
Syntax
SIRAPSY DIS | DISPLAY | RES | NORES subsystem proc
Where:
- subsystem is the name of the subsystem to which the command applies.
- proc is the name of the procedure to which the command applies.
Usage
The SIRAPSY command is only available with the Sirius Performance Enhancements V2, and it can only be issued by a system manager or system administrator.
Example
The following command sets SIRMON procedure MOPR-MENU to become resident next time it is loaded:
SIRAPSY RES SIRMON MOPR-MENU
This command sets SIRMON procedure MOPR-SYSOVR so that it will never be set to
resident:
SIRAPSY NORES SIRMON MOPR-SYSOVR
SIRAPSY NORES will not drop the residency attribute of a
procedure once it is made resident.