USLCMAX parameter: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
<dl> | <dl> | ||
<dt>Default value | <dt>Default value | ||
<dd> | <dd>0 | ||
<dt>Parameter type | <dt>Parameter type | ||
<dd>System | <dd>System | ||
<dt>Where set | <dt>Where set | ||
<dd>On user's parameter line | <dd>On user's parameter line | ||
<dt>Related products | <dt>Related products | ||
<dd>All | <dd>All | ||
Revision as of 11:43, 29 November 2017
User slice max to CSLICE
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- On user's parameter line
- 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.