HIGHPRIORITY (JANUS DEFINE parameter): Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 8: Line 8:
''Model 204'' has three basic priority classes:
''Model 204'' has three basic priority classes:


<table class="list">
<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>

Revision as of 18:25, 1 November 2011

<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.

HIGHPRIORITY is available as of Sirius Mods Version 6.5 (originally in a 6.4 ZAP).

The HIGHPRIORITY parameter is valid only Janus Web Server ports.

References

See: List of Janus commands | List of JANUS DEFINE parameters.