USLCMAX parameter - Revision history

JAL: misc formatting

2017-11-29T22:39:36Z

misc formatting

← Older revision		Revision as of 22:39, 29 November 2017
Line 15:		Line 15:

	==Description==		==Description==
	This counter is decremented each time a user reaches the bottom of a [[Record loops#FOR EACH RECORD statement\|~~FOR loop~~]], [[Flow of control ~~in_~~ User Language#Repeat loops\|~~REPEAT loop~~]], performs a backward [[Flow of control in User Language#JUMP TO statement\|~~JUMP TO~~]], and on a number of other occasions.		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 (USLCWAIT).		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.		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.

JAL: misc formatting

2017-11-29T22:28:10Z

misc formatting

← Older revision		Revision as of 22:28, 29 November 2017
Line 15:		Line 15:

	==Description==		==Description==
	This counter is decremented each time a user reaches the bottom of a [[~~Record_loops~~#~~FOR_EACH_RECORD_statement~~\|FOR loop]], [[~~Flow_of_control_in_User_Language~~#~~Repeat_loops~~\|REPEAT loop]], performs a backward [[~~Flow_of_control_in_User_Language~~#~~JUMP_TO_statement~~\|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-<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 (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 [[Record loops#FOR EACH RECORD statement\|FOR loop]], [[Flow of control in_ User Language#Repeat loops\|REPEAT loop]], performs a backward [[Flow of control in User Language#JUMP TO statement\|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 — <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 (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.

	[[Category:Scheduler parameters]]		[[Category:Scheduler parameters]]
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2017-11-29T11:53:51Z

Description

← Older revision		Revision as of 11:53, 29 November 2017
Line 15:		Line 15:

	==Description==		==Description==
	This counter is decremented each time a user reaches the bottom of a [[Record_loops#FOR_EACH_RECORD_statement\|FOR loop]], [[Flow_of_control_in_User_Language#Repeat_loops\|REPEAT loop]], performs a backward [[Flow_of_control_in_User_Language#JUMP_TO_statement\|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-<var>[[MCPU_parameter\|MCPU]]</var>, 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 [[Record_loops#FOR_EACH_RECORD_statement\|FOR loop]], [[Flow_of_control_in_User_Language#Repeat_loops\|REPEAT loop]], performs a backward [[Flow_of_control_in_User_Language#JUMP_TO_statement\|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-<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 (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.
	[[Category:Scheduler parameters]]		[[Category:Scheduler parameters]]
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2017-11-29T11:51:11Z

Description

← Older revision		Revision as of 11:51, 29 November 2017
Line 15:		Line 15:

	==Description==		==Description==
	This counter is decremented each time a user reaches the bottom of a [[Record_loops#FOR_EACH_RECORD_statement\|FOR loop]], [[Flow_of_control_in_User_Language#Repeat_loops\|REPEAT loop]], performs a backward [[Flow_of_control_in_User_Language#JUMP_TO_statement\|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 [[Record_loops#FOR_EACH_RECORD_statement\|FOR loop]], [[Flow_of_control_in_User_Language#Repeat_loops\|REPEAT loop]], performs a backward [[Flow_of_control_in_User_Language#JUMP_TO_statement\|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-<var>[[MCPU_parameter\|MCPU]]</var>, 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.
	[[Category:Scheduler parameters]]		[[Category:Scheduler parameters]]
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2017-11-29T11:50:12Z

Description

← Older revision		Revision as of 11:50, 29 November 2017
Line 15:		Line 15:

	==Description==		==Description==
	This counter is decremented each time a user reaches the bottom of a [[Record_loops#FOR_EACH_RECORD_statement\|FOR loop]], [[Flow_of_control_in_User_Language#Repeat_loops\|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 [[Record_loops#FOR_EACH_RECORD_statement\|FOR loop]], [[Flow_of_control_in_User_Language#Repeat_loops\|REPEAT loop]], performs a backward [[Flow_of_control_in_User_Language#JUMP_TO_statement\|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.
	[[Category:Scheduler parameters]]		[[Category:Scheduler parameters]]
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2017-11-29T11:48:54Z

Description

← Older revision		Revision as of 11:48, 29 November 2017
Line 15:		Line 15:

	==Description==		==Description==
	This counter is decremented each time a user reaches the bottom of a [[Record_loops#FOR_EACH_RECORD_statement\|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 [[Record_loops#FOR_EACH_RECORD_statement\|FOR loop]], [[Flow_of_control_in_User_Language#Repeat_loops\|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.
	[[Category:Scheduler parameters]]		[[Category:Scheduler parameters]]
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2017-11-29T11:47:37Z

Description

← Older revision		Revision as of 11:47, 29 November 2017
Line 15:		Line 15:

	==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 [[Record_loops#FOR_EACH_RECORD_statement\|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.
	[[Category:Scheduler parameters]]		[[Category:Scheduler parameters]]
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Summary */

2017-11-29T11:43:45Z

Summary

← Older revision		Revision as of 11:43, 29 November 2017
Line 3:		Line 3:
	<dl>		<dl>
	<dt>Default value		<dt>Default value
	<dd>50		<dd>0
	<dt>Parameter type		<dt>Parameter type
	<dd>System		<dd>System
	<dt>Where set		<dt>Where set
	<dd>On user's parameter line ~~by system manager~~		<dd>On user's parameter line
	<dt>Related products		<dt>Related products
	<dd>All		<dd>All

DCameron: /* Summary */

2017-11-28T16:29:29Z

Summary

← Older revision		Revision as of 16:29, 28 November 2017
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.

DmeWiccan: Automatically generated page update

2013-08-27T16:49:16Z

Automatically generated page update

← Older revision		Revision as of 16:49, 27 August 2013
Line 1:		Line 1:
			{{Template:USLCMAX parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>