HIGHPRIORITY (JANUS DEFINE parameter): Difference between revisions
m (moved HIGHPRIORITY to HIGHPRIORITY (JANUS DEFINE parameter)) |
mNo edit summary |
||
| Line 2: | Line 2: | ||
<span class="pageSubtitle"><section begin="desc" />Start session at upper end of priority range.<section end="desc" /></span> | <span class="pageSubtitle"><section begin="desc" />Start session at upper end of priority range.<section end="desc" /></span> | ||
HIGHPRIORITY is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]]. | <var>HIGHPRIORITY</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]]. | ||
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. | 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. | ||
| Line 19: | Line 19: | ||
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 <var>HIGHPRIORITY</var> parameter is valid only for ''Janus Web Server'' ports. | |||
The HIGHPRIORITY parameter is valid only '' | |||
==References== | ==References== | ||
Revision as of 21:56, 24 February 2012
<section begin="desc" />Start session at upper end of priority range.<section end="desc" />
HIGHPRIORITY is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port. See the List of JANUS DEFINE parameters.
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.
References
See: List of Janus commands | List of JANUS DEFINE parameters.