AGESCAN parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
(Undo revision 56797 by DmeWiccan (talk))
Line 19: Line 19:
<p class="note"><b>Note:</b> The <var class="product">Model&nbsp;204</var> aging facility increases scheduler overhead and is of limited use in XA environments with many servers and more than four megabytes of virtual storage for <var class="product">Model&nbsp;204</var>.</p>
<p class="note"><b>Note:</b> The <var class="product">Model&nbsp;204</var> aging facility increases scheduler overhead and is of limited use in XA environments with many servers and more than four megabytes of virtual storage for <var class="product">Model&nbsp;204</var>.</p>
[[Category:Scheduler parameters]]
[[Category:Scheduler parameters]]
[[Category:System parameters]]
[[Category: System Parameters]]
[[Category:Parameters]]
[[Category:Parameters]]

Revision as of 15:47, 19 April 2013

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 allowable real-time interval in milliseconds between scans of wait queues performed by the aging logic

AGESCAN controls how fast the scheduler notices that a particular user should be aged. Setting this parameter to 0 deactivates queue aging, in which case AGEINCR, AGEINTVL, AGESLICE, PRIOMAX, and SLICEMAX are ignored.

Increasing AGESCAN increases the time it takes the scheduler to notice that a user has waited long enough to be aged. However, it also reduces scheduler overhead.

Avoid small nonzero values, because the smaller values require more frequent checking, causing an increase in scheduler overhead. Do not set AGESCAN to a nonzero value less than AGEINTVL.

Note: The Model 204 aging facility increases scheduler overhead and is of limited use in XA environments with many servers and more than four megabytes of virtual storage for Model 204.