USLCMAX parameter: Difference between revisions
Jump to navigation
Jump to search
m (misc formatting) |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| 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 | ||
| Line 15: | Line 15: | ||
==Description== | ==Description== | ||
This counter is decremented each time a user reaches the bottom of a FOR | This counter is decremented each time a user reaches the bottom of a <var>[[Record loops#FOR EACH RECORD statement|For]]</var> or <var>[[Flow of control in User Language#Repeat loops|Repeat]]</var> loop, performs a backward <var>[[Flow of control in User Language#JUMP TO statement|Jump To]]</var>, and on a number of other occasions. | ||
When the counter reaches zero, a call is made to the CLSICE (Check SLICE) routine to see if the user has exceeded any maximums — <var>[[MCPU parameter|MCPU]]</var>, <var>[[MDKRD parameter|MDKRD]]</var>, <var>[[MDKWR parameter|MDKWR]]</var>, <var>[[MUDD parameter|MUDD]]</var>, <var>[[MCNCT parameter|MCNCT]]</var>, or <var>[[MOUT parameter|MOUT]]</var> — and should be given the LONG REQUEST message or put into a wait (<var>USLCWAIT</var>). | |||
Decreasing the counter 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. | |||
[[Category:Scheduler parameters]] | [[Category:Scheduler parameters]] | ||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Latest revision as of 22:39, 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 or Repeat loop, performs a backward Jump To, and on a number of other occasions.
When the counter 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 the counter 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.