SLICEMAX parameter: Difference between revisions
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 | <dd><var class="product">Model 204 V2.1</var> or earlier | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>The maximum CPU time slice in milliseconds that immunity aging can produce</p> | <p>The maximum CPU time slice in milliseconds that immunity aging can produce</p> |
Revision as of 15:35, 5 July 2017
Max age slice
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- On User 0's parameter line or reset by system manager
- Related products
- All
- Introduced
- Model 204 V2.1 or earlier
Description
The maximum CPU time slice in milliseconds that immunity aging can produce
This parameter is used to control the time an aged user remains at the aging-produced priority. Increasing SLICEMAX allows an aged user to monopolize the CPU, possibly locking out high-priority users.
SLICEMAX has no effect unless aging is enabled (that is, unless the AGESCAN parameter value is greater than zero). If aging is enabled, SLICEMAX must not be set to less than either CPUSLICE or IOSLICE.
See the System management topics for more information about Model 204 queue aging and dynamic dispatching.