JAL: remove Sys Man guide

2014-11-17T19:50:33Z

remove Sys Man guide

JAL: /* Syntax */

2014-11-17T19:26:55Z

Syntax

← Older revision		Revision as of 19:26, 17 November 2014
Line 7:		Line 7:
	</dl>		</dl>
	==Syntax==		==Syntax==
	<p class="syntax">PRIORITY [<span class="term">usernumber</span> [,LOW \| ,STANDARD \| , HIGH]]		<p class="syntax">PRIORITY [<span class="term">usernumber</span> [,LOW \| ,STANDARD \| ,HIGH]]
	</p>		</p>
	<p>		<p>

JAL: /* Syntax */

2014-11-17T19:26:14Z

Syntax

← Older revision		Revision as of 19:26, 17 November 2014
Line 68:		Line 68:
	<p class="code">PRIORITY 8,,IOSLICE=,		<p class="code">PRIORITY 8,,IOSLICE=,
	</p>		</p>
	<p> Note ~~that~~ keyword=value must be preceded by ~~either~~ the value of <var class="term">cur, min, max</var> or by double commas (<tt>,,</tt>) to indicate that the values do not change. The comma following the equal sign is used to represent a null value.</p>		<p class="note">
			<b>Note:</b> <var class="term">keyword</var>=<var class="term">value</var> must be preceded by the value of <var class="term">cur, min, max</var> or by double commas (<tt>,,</tt>) to indicate that the values do not change. The comma following the equal sign is used to represent a null value.</p>
	<p>		<p>
	<table>		<table>

JAL: more conversion cleanup

2014-11-17T19:18:38Z

more conversion cleanup

Show changes

JAL at 02:04, 8 March 2013

2013-03-08T02:04:31Z

← Older revision		Revision as of 02:04, 8 March 2013
Line 233:		Line 233:
	[[Category: System administrator commands]]		[[Category: System administrator commands]]
	[[Category: System manager commands]]		[[Category: System manager commands]]
			[[Category: Operator commands]]
	[[Category:Commands]]		[[Category:Commands]]

Alex: Automatically generated page update

2013-02-28T01:05:19Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>System manager, system administrator, or operator
<dt>Function
<dd>Assigns a user to a priority class or displays information about priority assignments
</dl>
==Syntax==
PRIORITY [usernumber [,LOW | ,STANDARD | , HIGH]]

or
PRIORITY usernumber [,cur | (cur,min,max)] [,keyword=value]

or
PRIORITY usernumber, CANCEL


Where:
usernumber is the number of the user whose priority is being assigned or displayed.
<table>

<tr> <th>
If specifying... 
</th> <th>
Then <var class="product">Model 204</var> lists priority information...
</th> </tr>

<tr> <th><var>
Neither usernumber nor the priority 
</var></th> <td>
For all active users (see the format below).
</td> </tr>

<tr> <th><var>
Only usernumber 
</var></th> <td>
For only that user.
</td> </tr>

<tr> <th><var>
Both usernumber and the priority 
</var></th> <td>
Specified to that user.
</td> </tr>

</table>
<ul>
<li>
If no further parameters are specified, only usernumber is displayed.
</li>

<li>
If further parameters are specified, a comma must separate usernumber as well as the subsequent parameter values. 
</li>

<li>
cur specifies new current priority for specified user (0-253)
</li>

<li>
min specifies the new minimum priority for specified user (1-253)
</li>

<li>
max specifies the new maximum priority for specified user (1-253)
</li>

<li>
keyword=value is used to change the value of one of the parameters in the table below.
To change user 8's IOSLICE to 66 and their cur,min,max to 104,80,127, use the following: 
PRIORITY 8,(104,80,127),IOSLICE=66

To reset user 8's IOSLICE value back to the system default, specify a null value as follows: 
PRIORITY 8,,IOSLICE=,
 Note that keyword=value must be preceded by either the value of cur, min, max or by double commas (,,) to indicate that the values do not change. The comma following the equal sign is used to represent a null value.

<table>
<caption>PRIORITY command keywords </caption>

<tr> <th><var>
Keyword 
</var></th> <td>
Meaning
</td> </tr>

<tr> <th><var>
IOSLICE 
</var></th> <td>
CPU milliseconds allowed while user is I/O bound
</td> </tr>

<tr> <th><var>
CPUSLICE 
</var></th> <td>
CPU milliseconds allowed while user is CPU bound
</td> </tr>

<tr> <th><var>
SLCWAIT
</var></th> <td>
Sleep time in milliseconds when a user reaches minimum priority level.
</td> </tr>

<tr> <th><var>
SLCMAX 
</var></th> <td>
Number of SLCs before CSLICE invoked (max=65545). Declines in this number increase the accuracy of the slice interval. However, CPU overhead increases.
</td> </tr>

</table>

</li>

<li>
CANCEL will end the user's current request. The error procedure will be invoked if the user is in a subsystem.
</li>
</ul>
==Example==
The following example requests priority information about all active users. The SERV column is either a server number OUT for swapped out. Note that the column labeled MAX below is SLCMAX.
PRIORITY 
USER USERID P CUR,MIN-MAX SLICE IOSLICE CPUSLIC MAX SLCWAIT SERV CPU
0 NO USERI S 053,032-079 0.000I 0.070 0.100 50 0.00 OUT 0.001
1 BECKETT S 061,032-079 0.000I 0.070 0.100 50 0.00 OUT 0.013
2 LESTER H 127,080-127 0.000I 0.070 0.100 50 0.00 5 0.170
3 MATSUZAK S 061,032-079 0.000I 0.070 0.100 50 0.00 OUT 0.012
4 PENNY H 104,080-127 0.000I 0.070 0.100 50 0.00 1 0.422
5 WAKEFIEL H 114,080-127 0.000I 0.070 0.100 50 0.00 3 0.105
6 VARITEK S 079,032-079 0.000I 0.070 0.100 50 0.00 OUT 0.063
7 YOUKILIS S 079,032-079 0.000I 0.070 0.100 50 0.00 OUT 0.069
8 PEDROIA S 079,032-079 0.000I 0.070 0.100 50 0.00 6 0.133
9 LOWELL S 072,032-079 0.000I 0.070 0.100 50 0.00 OUT 0.032
11 LUGO S 079,032-079 0.000I 0.070 0.100 50 0.00 2 0.112

The following example requests priority information about user number 112:
PRIORITY 112

The following example assigns a HIGH priority to user number 2: 
PRIORITY 2, HIGH

==Usage notes==
The PRIORITY command allows <var class="product">Model 204</var> resources to be allocated to individual users or applications based upon their relative service requirements. This is done by placing users in one of three priority classes (LOW, STANDARD, or HIGH) or by assigning a number to indicate the user's priority. 
In general, HIGH priority users receive prompter service than STANDARD priority users, and STANDARD priority users receive prompter service than LOW priority users. A detailed presentation of priority scheduling is included in the <var>Model 204 System Manager's Guide.</var>
Once a priority has been assigned, that priority remains in effect until it is changed by another PRIORITY command or until you log out of <var class="product">Model 204</var>.
The output of the PRIORITY command displays the information listed in the following table.
<table>
<caption> PRIORITY command output formats</caption>

<tr> <th>
Header
</th> <th>
Description
</th> </tr>

<tr> <th><var>
USER 
</var></th> <td>
User number
</td> </tr>

<tr> <th><var>
USERID
</var></th> <td>
User ID as supplied at login
</td> </tr>

<tr> <th><var>
P
</var></th> <td>
Current priority class. L-Low, S-Standard, H-High, *-Set by PRIORITY Command, Z-Sleeping (priority 0), ? - Priority change in progress
</td> </tr>

<tr> <th><var>
CUR 
</var></th> <td>
Current priority
</td> </tr>

<tr> <th><var>
MIN
</var></th> <td>
Minimum priority
</td> </tr>

<tr> <th><var>
MAX
</var></th> <td>
Maximum priority
</td> </tr>

<tr> <th><var>
SLICE
</var></th> <td>
I for I/O bound or C for CPU bound.
</td> </tr>

<tr> <th><var>
IOSLICE
</var></th> <td>
CPU milliseconds allowed while user is I/O bound.
</td> </tr>

<tr> <th><var>
CPUSLIC
</var></th> <td>
CPU milliseconds allowed while user is CPU bound.
</td> </tr>

<tr> <th><var>
MAX
</var></th> <td>
SLCMAX. Number of Stop-Loop-Checks (SLCs) before CSLICE invoked (max=65535).
</td> </tr>

<tr> <th><var>
SLCWAIT
</var></th> <td>
Sleep time in milliseconds, invoked each time a user reaches minimum priority level.
</td> </tr>

<tr> <th><var>
SERV
</var></th> <td>
Server number the user currently occupies. OUT if not in-server.
</td> </tr>

<tr> <th><var>
CPU
</var></th> <td>
Amount of CPU time consumed by this user.
</td> </tr>

</table>
[[Category: System administrator commands]]
[[Category: System manager commands]]
[[Category:Commands]]

PRIORITY command - Revision history

JAL: remove Sys Man guide

JAL: /* Syntax */

JAL: /* Syntax */

JAL: more conversion cleanup

JAL at 02:04, 8 March 2013

Alex: Automatically generated page update