USLCMAX parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
Line 11: Line 11:
<dd>All
<dd>All
<dt>Introduced
<dt>Introduced
<dd><var class="product">Model 204 V7.4</var>
<dd><var class="product">Model 204 V7.1</var>
</dl>
</dl>
==Description==
==Description==
This counter is decremented each time a user reaches the bottom of a FOR loop, REPEAT loop, performs a backward JUMP TO, and on a number of other occasions. When that number reaches zero, a call is made to the CLSICE (Check SLICE) routine to see if the user has exceeded any maximums-MCPU, MDKRD, MDKWR, MUDD, MCNCT, or MOUT-and should be given the LONG REQUEST message or put into a wait (USLCWAIT). Decreasing this number increases scheduler overhead since CSLICE will be called more often. Increasing the number reduces scheduler overhead, but allows users to run longer before being checked for exceeding maximums.
This counter is decremented each time a user reaches the bottom of a FOR loop, REPEAT loop, performs a backward JUMP TO, and on a number of other occasions. When that number reaches zero, a call is made to the CLSICE (Check SLICE) routine to see if the user has exceeded any maximums-MCPU, MDKRD, MDKWR, MUDD, MCNCT, or MOUT-and should be given the LONG REQUEST message or put into a wait (USLCWAIT). Decreasing this number increases scheduler overhead since CSLICE will be called more often. Increasing the number reduces scheduler overhead, but allows users to run longer before being checked for exceeding maximums.

Revision as of 16:29, 28 November 2017

User slice max to CSLICE

Summary

Default value
50
Parameter type
System
Where set
On user's parameter line by system manager
Related products
All
Introduced
Model 204 V7.1

Description

This counter is decremented each time a user reaches the bottom of a FOR loop, REPEAT loop, performs a backward JUMP TO, and on a number of other occasions. When that number reaches zero, a call is made to the CLSICE (Check SLICE) routine to see if the user has exceeded any maximums-MCPU, MDKRD, MDKWR, MUDD, MCNCT, or MOUT-and should be given the LONG REQUEST message or put into a wait (USLCWAIT). Decreasing this number increases scheduler overhead since CSLICE will be called more often. Increasing the number reduces scheduler overhead, but allows users to run longer before being checked for exceeding maximums.