SLICEMAX parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
Line 17: Line 17:
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>For more information about <var class="product">Model&nbsp;204</var> queue aging and dynamic dispatching, see the <var>Model&nbsp;204 System Manager's Guide</var>. </p>
<p>See the System management topics for more information about <var class="product">Model&nbsp;204</var> [[Controlling system operations (CCAIN)#Queue aging|queue aging]] and [[Controlling system operations (CCAIN)#Dynamic dispatching|Dynamic dispatching]].</p>
[[Category:Scheduler parameters]]
[[Category:Scheduler parameters]]
[[Category:System parameters]]
[[Category:System parameters]]
[[Category:Parameters]]
[[Category:Parameters]]

Revision as of 22:54, 6 August 2015

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