HIGHPRIORITY (JANUS DEFINE parameter): Difference between revisions
m (1 revision) |
(Automatically generated page update) |
||
| (11 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
<span class="pageSubtitle">Start session at upper end of priority range</span> | |||
<span class="pageSubtitle"> | |||
HIGHPRIORITY is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port | <var>HIGHPRIORITY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
This parameter adjusts the <var class="product">Model 204</var>-scheduling priority of <var class="product">[[Janus Web Server]]</var> threads by starting them at the upper end of their priority range rather than at their default priority. | |||
<var class="product">Model 204</var> has three basic priority classes: | |||
<table class="syntaxTable"> | <table class="syntaxTable"> | ||
<tr><th>HIGH</th> | <tr><th><var>HIGH</var></th> | ||
<td>Ranges from 80 to 127</td></tr> | <td>Ranges from 80 to 127</td></tr> | ||
<tr><th>STANDARD</th> | <tr><th><var>STANDARD</var></th> | ||
<td>Ranges from 32 to 79</td></tr> | <td>Ranges from 32 to 79</td></tr> | ||
<tr><th>LOW</th> | <tr><th><var>LOW</var></th> | ||
<td>Ranges from 0 to 47 | <td>Ranges from 0 to 47 | ||
</td></tr></table> | </td></tr></table> | ||
By default, when a user logs in, they get a privilege 16 greater than the bottom of its class. This can be a problem for web threads, because the priorities of 3270 threads often "drift" to the top of their range. As a result, the web threads ultimately have lower priorities than 3270 threads. | By default, when a user logs in, they get a privilege 16 greater than the bottom of its class. This can be a problem for web threads, because the priorities of 3270 threads often "drift" to the top of their range. As a result, the web threads ultimately have lower priorities than 3270 threads. | ||
If you set HIGHPRIORITY, web threads start out at the top of their range, so they will tend to get as good or better service than 3270 threads | If you set <var>HIGHPRIORITY</var>, web threads start out at the top of their range, so they will tend to get as good or better service than 3270 threads. | ||
The HIGHPRIORITY parameter is valid only for | The <var>HIGHPRIORITY</var> parameter is valid only for <var class="product">Janus Web Server</var> ports. | ||
== | ==See also== | ||
<ul> | |||
<li>[[List of Janus commands]] | |||
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] | |||
</ul> | |||
[[Category:JANUS DEFINE parameters|HIGHPRIORITY]] | [[Category:JANUS DEFINE parameters|HIGHPRIORITY]] | ||
Latest revision as of 22:15, 16 April 2013
Start session at upper end of priority range
HIGHPRIORITY is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
This parameter adjusts the Model 204-scheduling priority of Janus Web Server threads by starting them at the upper end of their priority range rather than at their default priority.
Model 204 has three basic priority classes:
| HIGH | Ranges from 80 to 127 |
|---|---|
| STANDARD | Ranges from 32 to 79 |
| LOW | Ranges from 0 to 47 |
By default, when a user logs in, they get a privilege 16 greater than the bottom of its class. This can be a problem for web threads, because the priorities of 3270 threads often "drift" to the top of their range. As a result, the web threads ultimately have lower priorities than 3270 threads.
If you set HIGHPRIORITY, web threads start out at the top of their range, so they will tend to get as good or better service than 3270 threads.
The HIGHPRIORITY parameter is valid only for Janus Web Server ports.