LENQTBL and (deprecated) LRESTBL parameters - Revision history

ELowell: adding Usage section and text that seems to have been missed during wiki conversion

2017-03-29T23:19:24Z

adding Usage section and text that seems to have been missed during wiki conversion

← Older revision		Revision as of 23:19, 29 March 2017
Line 54:		Line 54:
	<p class="code">(100 * 12 * 32) + 64 + (200 * 124) = 63,264 bytes		<p class="code">(100 * 12 * 32) + 64 + (200 * 124) = 63,264 bytes
	</p>		</p>

			==Usage notes==
			If SYSOPT = 1 or 2 (indicating CCASYS/APSY or CCAGRP), add 1 to the value of NFILES used in the formula. If SYSOPT = 3 (indicating both CCASYS/APSY and CCAGRP), add 2.

			<p>Use the value of NFILES you set in CCAIN. If you view NFILES after the run initializes, 1 or 2 has already been added, if needed, to reflect the SYSOPT value.</p>

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

JAL: add link

2015-04-06T15:11:17Z

add link

← Older revision		Revision as of 15:11, 6 April 2015
Line 1:		Line 1:
	The <var>LRESTBL</var> parameter is an alias for <var>LENQTBL</var>.		The <var>LRESTBL</var> parameter is an alias for <var>LENQTBL</var>.
	<var>LRESTBL</var> is deprecated — use <var>LENQTBL</var> instead.		<var>LRESTBL</var> is deprecated — use <var>LENQTBL</var> instead.

	==Summary==		==Summary==
	<dl>		<dl>
Line 17:		Line 18:
	==Description==		==Description==
	<p>		<p>
	The number of entries in the resource enqueuing table to be allocated for each user</p>		The number of entries in the [[Defining the runtime environment (CCAIN)#Resource locking\|resource enqueuing table]] to be allocated for each user</p>
	<p>		<p>
	The resource enqueuing table is used for many purposes. Opening many files concurrently and using nested <var>INCLUDE</var> commands contribute to filling up this table. </p>		The resource enqueuing table is used for many purposes. Opening many files concurrently and using nested <var>INCLUDE</var> commands contribute to filling up this table. </p>

JAL: misc formatting

2015-04-06T14:13:15Z

misc formatting

← Older revision		Revision as of 14:13, 6 April 2015
Line 36:		Line 36:
	<p>		<p>
	The total amount of storage required for the resource enqueuing table is:</p>		The total amount of storage required for the resource enqueuing table is:</p>
	<p>		<p class="code"><i>length of user entries</i> + <i>length of system header</i> + <i>length of file headers</i></p>
	length of user entries + length of system header + length of file headers,</p>
	<p>		<p>
	That is:</p>		That is:</p>

JAL: misc cleanup

2015-04-06T14:02:52Z

misc cleanup

← Older revision		Revision as of 14:02, 6 April 2015
Line 16:		Line 16:

	==Description==		==Description==
	<p>The number of entries in the resource enqueuing table to be allocated for each user</p>		<p>
	<p>The resource enqueuing table is used for many purposes. Opening many files concurrently and using nested ~~INCLUDEs~~ contribute to filling up this table. </p>		The number of entries in the resource enqueuing table to be allocated for each user</p>
	<p>The value of LENQTBL defaults to 6. However, if the product of <~~var~~>[[~~NUSERS_parameter~~\|NUSERS]]</~~var~~>*LENQTBL is less than 12, that product is forced to 12 so that the table will be allocated with a minimum of 12 user entries.</p>		<p>
	<p>The resource enqueuing table is a volatile structure: its entries can be allocated and deallocated very quickly. As a result, any prediction of its optimum size can only be roughly approximate. Typically, the following formula for sizing LENQTBL suffices, although there might be cases where you need a larger or a smaller LENQTBL value. </p>		The resource enqueuing table is used for many purposes. Opening many files concurrently and using nested <var>INCLUDE</var> commands contribute to filling up this table. </p>
	<p>Set LENQTBL to the sum of the following items.~~</p>~~		<p>
	~~<p>Algorithm for estimating the value of LENQTBL:~~</p>		The value of <var>LENQTBL</var> defaults to 6. However, if the product of <code>[[NUSERS parameter\|NUSERS]]*LENQTBL</code> is less than 12, that product is forced to 12 so that the table will be allocated with a minimum of 12 user entries.</p>
	<p class="code">LENQTBL = (<i>avg. no. of open permanent groups (~~<var>~~[[~~Application_Subsystem_development~~\|APSY]]~~</var>~~ or non-APSY)</i> + <i>avg. no. of open files per user (including files in groups)</i> + 1)		<p>
	</p><p> The ~~one~~ added at the end accounts for the maximum number of permanent ~~procs~~ (APSY or non-APSY) that can be in EVAL per user.</p>		The resource enqueuing table is a volatile structure: its entries can be allocated and deallocated very quickly. As a result, any prediction of its optimum size can only be roughly approximate. Typically, the following formula for sizing <var>LENQTBL</var> suffices, although there might be cases where you need a larger or a smaller <var>LENQTBL</var> value. </p>
	~~<p>~~Algorithm for corresponding storage requirements:</p>
	~~<p>~~The total amount of storage required for the resource enqueuing table is:</p>		===Algorithm for estimating the value of LENQTBL===
	<p>length of user entries + length of system header + length of file headers,</p>		<p>
	<p>~~that~~ is:</p>		Set <var>LENQTBL</var> to the sum of the following items.</p>
	<p class="code">(NUSERS * LENQTBL * 32) + 64 + (~~<var>~~[[NFILES_parameter\|NFILES]]~~</var>~~ * 124)		<p class="code">LENQTBL = (<i>avg. no. of open permanent groups ([[Application Subsystem development\|APSY]] or non-APSY)</i>
			+ <i>avg. no. of open files per user (including files in groups)</i> + 1) </p>
			<p>
			The 1 added at the end accounts for the maximum number of permanent procedures (APSY or non-APSY) that can be in EVAL per user.</p>

			===Algorithm for corresponding storage requirements===
			<p>
			The total amount of storage required for the resource enqueuing table is:</p>
			<p>
			length of user entries + length of system header + length of file headers,</p>
			<p>
			That is:</p>
			<p class="code">(NUSERS * LENQTBL * 32) + 64 + ([[NFILES_parameter\|NFILES]] * 124)
	</p>		</p>
	<p>For example, ~~when~~:</p>		<p>
	<p>NUSERS = 100</p>		For example, if:</p>
	<p>LENQTBL = 12, which is always the minimum allocation</p>		<p>
	<p>NFILES = 200</p>		NUSERS = 100</p>
	<p>~~then~~ the calculation is as follows:</p>		<p>
			LENQTBL = 12, which is always the minimum allocation</p>
			<p>
			NFILES = 200</p>
			<p>
			Then the calculation is as follows:</p>
	<p class="code">(100 * 12 * 32) + 64 + (200 * 124) = 63,264 bytes		<p class="code">(100 * 12 * 32) + 64 + (200 * 124) = 63,264 bytes
	</p>		</p>

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

DCameron: /* Description */

2014-11-27T12:44:37Z

Description

← Older revision		Revision as of 12:44, 27 November 2014
Line 28:		Line 28:
	<p>length of user entries + length of system header + length of file headers,</p>		<p>length of user entries + length of system header + length of file headers,</p>
	<p>that is:</p>		<p>that is:</p>
	<p class="code">(NUSERS * LENQTBL * 32) + 64 + (NFILES * 124)		<p class="code">(NUSERS * LENQTBL * 32) + 64 + (<var>[[NFILES_parameter\|NFILES]]</var> * 124)
	</p>		</p>
	<p>For example, when:</p>		<p>For example, when:</p>

DCameron: /* Description */

2014-11-27T12:43:39Z

Description

← Older revision		Revision as of 12:43, 27 November 2014
Line 22:		Line 22:
	<p>Set LENQTBL to the sum of the following items.</p>		<p>Set LENQTBL to the sum of the following items.</p>
	<p>Algorithm for estimating the value of LENQTBL:</p>		<p>Algorithm for estimating the value of LENQTBL:</p>
	<p class="code">LENQTBL = (<i>avg. no. of open permanent groups (APSY or non-APSY)</i> + <i>avg. no. of open files per user (including files in groups)</i> + 1)		<p class="code">LENQTBL = (<i>avg. no. of open permanent groups (<var>[[Application_Subsystem_development\|APSY]]</var> or non-APSY)</i> + <i>avg. no. of open files per user (including files in groups)</i> + 1)
	</p><p> The one added at the end accounts for the maximum number of permanent procs (APSY or non-APSY) that can be in EVAL per user.</p>		</p><p> The one added at the end accounts for the maximum number of permanent procs (APSY or non-APSY) that can be in EVAL per user.</p>
	<p>Algorithm for corresponding storage requirements:</p>		<p>Algorithm for corresponding storage requirements:</p>

DCameron: /* Description */

2014-11-27T12:40:46Z

Description

← Older revision		Revision as of 12:40, 27 November 2014
Line 18:		Line 18:
	<p>The number of entries in the resource enqueuing table to be allocated for each user</p>		<p>The number of entries in the resource enqueuing table to be allocated for each user</p>
	<p>The resource enqueuing table is used for many purposes. Opening many files concurrently and using nested INCLUDEs contribute to filling up this table. </p>		<p>The resource enqueuing table is used for many purposes. Opening many files concurrently and using nested INCLUDEs contribute to filling up this table. </p>
	<p>The value of LENQTBL defaults to 6. However, if the product of NUSERS*LENQTBL is less than 12, that product is forced to 12 so that the table will be allocated with a minimum of 12 user entries.</p>		<p>The value of LENQTBL defaults to 6. However, if the product of <var>[[NUSERS_parameter\|NUSERS]]</var>*LENQTBL is less than 12, that product is forced to 12 so that the table will be allocated with a minimum of 12 user entries.</p>
	<p>The resource enqueuing table is a volatile structure: its entries can be allocated and deallocated very quickly. As a result, any prediction of its optimum size can only be roughly approximate. Typically, the following formula for sizing LENQTBL suffices, although there might be cases where you need a larger or a smaller LENQTBL value. </p>		<p>The resource enqueuing table is a volatile structure: its entries can be allocated and deallocated very quickly. As a result, any prediction of its optimum size can only be roughly approximate. Typically, the following formula for sizing LENQTBL suffices, although there might be cases where you need a larger or a smaller LENQTBL value. </p>
	<p>Set LENQTBL to the sum of the following items.</p>		<p>Set LENQTBL to the sum of the following items.</p>

DCameron: /* Summary */

2014-11-27T12:39:14Z

Summary

← Older revision		Revision as of 12:39, 27 November 2014
Line 12:		Line 12:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Model 204 V6.1</var> or earlier		<dd><var class="product">Model 204 V2.2</var> or earlier
	</dl>		</dl>

	==Description==		==Description==
	<p>The number of entries in the resource enqueuing table to be allocated for each user</p>		<p>The number of entries in the resource enqueuing table to be allocated for each user</p>

DmeWiccan: Automatically generated page update

2013-04-23T01:51:02Z

Automatically generated page update

← Older revision		Revision as of 01:51, 23 April 2013
Line 36:		Line 36:
	<p class="code">(100 * 12 * 32) + 64 + (200 * 124) = 63,264 bytes		<p class="code">(100 * 12 * 32) + 64 + (200 * 124) = 63,264 bytes
	</p>		</p>
	[[Category:System ~~Parameters~~]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Dme: Undo revision 56871 by DmeWiccan (talk)

2013-04-19T15:23:11Z

Undo revision 56871 by DmeWiccan (talk)

← Older revision		Revision as of 15:23, 19 April 2013
Line 36:		Line 36:
	<p class="code">(100 * 12 * 32) + 64 + (200 * 124) = 63,264 bytes		<p class="code">(100 * 12 * 32) + 64 + (200 * 124) = 63,264 bytes
	</p>		</p>
	[[Category:System ~~parameters~~]]		[[Category:System Parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]