SCRNSTBL parameter - Revision history

Alan at 19:43, 25 May 2017

2017-05-25T19:43:48Z

← Older revision		Revision as of 19:43, 25 May 2017
Line 20:		Line 20:
	SCRNSTBL can be set higher than LSTBL. However, at the time a procedure containing a screen object is compiled, LSTBL must be set to a value that accommodates both the largest screen object in the procedure and the other STBL-resident strings in the procedure.		SCRNSTBL can be set higher than LSTBL. However, at the time a procedure containing a screen object is compiled, LSTBL must be set to a value that accommodates both the largest screen object in the procedure and the other STBL-resident strings in the procedure.

	~~An application~~ that exceeds its ~~screen STBL~~ allocation is cancelled, usually with a message like:		A procedure using a screen object that exceeds its SCRNSTBL allocation is cancelled, usually with a message like:
	<p class="code">MSIR.0750: Class Screen, function AddField: no more space for screen field data ...		<p class="code">MSIR.0750: Class Screen, function AddField: no more space for screen field data ...
	</p>		</p>

ELowell: /* Description */

2017-05-25T17:29:40Z

Description

← Older revision		Revision as of 17:29, 25 May 2017
Line 18:		Line 18:
	<var>Screen</var> object must allocate the maximum allowable STBL space, even if some of this space may not be used by a particular application.		<var>Screen</var> object must allocate the maximum allowable STBL space, even if some of this space may not be used by a particular application.

	~~While~~ SCRNSTBL can be set higher than LSTBL, at the time a procedure containing a screen object is compiled LSTBL must be set to a value that accommodates both the largest screen object in the procedure ~~as well as~~ the other STBL-resident strings in the procedure.		SCRNSTBL can be set higher than LSTBL. However, at the time a procedure containing a screen object is compiled, LSTBL must be set to a value that accommodates both the largest screen object in the procedure and the other STBL-resident strings in the procedure.

	An application that exceeds its screen STBL allocation is cancelled, usually with a message like:		An application that exceeds its screen STBL allocation is cancelled, usually with a message like:
Line 25:		Line 25:
	Some Sirius RKTools products, like [[SirScan]] and [[SirPro]], also make use of <var>Screen</var> objects. The <var>SCRNSTBL</var> default value is sufficient for those products for Model 2 terminals. However, the default <var>SCRNSTBL</var> might not be sufficient for other terminal models, especially Model 4 or [[SIRTERM_parameter\|Model 6]] terminals.		Some Sirius RKTools products, like [[SirScan]] and [[SirPro]], also make use of <var>Screen</var> objects. The <var>SCRNSTBL</var> default value is sufficient for those products for Model 2 terminals. However, the default <var>SCRNSTBL</var> might not be sufficient for other terminal models, especially Model 4 or [[SIRTERM_parameter\|Model 6]] terminals.

	If no [[Screen class\|Screen objects]] are used in the Model 204 region, SCRNSTBL can be set to zero. If [[Screen class\|Screen objects]] are used, calculating the correct value is complicated by performance issues related to object swapping. See the discussion at [[Managing server space for objects]], especially the discussion of the ~~SIRIUS MINOBJECTS~~ compiler directive.		If no [[Screen class\|Screen objects]] are used in the Model 204 region, SCRNSTBL can be set to zero. If [[Screen class\|Screen objects]] are used, calculating the correct value is complicated by performance issues related to object swapping. See the discussion at [[Managing server space for objects]], especially the discussion of the <var>[[Managing server space for objects#Using compiler directives to modify object allocation\|Sirius MinObjects]]</var> compiler directive.

	<p class="note"><b>Note:</b> The <var>SCRNSTBL</var> parameter affects the space allocated for <var>Screen</var> objects at compilation time. As such, increasing <var>SCRNSTBL</var> does not increase the amount of space available to pre-compiled requests unless those requests are re-compiled after resetting <var>SCRNSTBL</var>. </p>		<p class="note"><b>Note:</b> The <var>SCRNSTBL</var> parameter affects the space allocated for <var>Screen</var> objects at compilation time. As such, increasing <var>SCRNSTBL</var> does not increase the amount of space available to pre-compiled requests unless those requests are re-compiled after resetting <var>SCRNSTBL</var>. </p>

Alan at 16:03, 25 May 2017

2017-05-25T16:03:43Z

← Older revision		Revision as of 16:03, 25 May 2017
Line 17:		Line 17:
	This is a numeric parameter (with valid values 0 or greater) that indicates the maximum amount of <var>[[LSTBL_parameter\|STBL]]</var> space available to <var class="product">Janus SOAP</var> [[Screen class\|Screen objects]]. <var>Screen</var> objects use STBL space and not <var>[[LFSCB_parameter\|FSCB]]</var> space, and any instance of a		This is a numeric parameter (with valid values 0 or greater) that indicates the maximum amount of <var>[[LSTBL_parameter\|STBL]]</var> space available to <var class="product">Janus SOAP</var> [[Screen class\|Screen objects]]. <var>Screen</var> objects use STBL space and not <var>[[LFSCB_parameter\|FSCB]]</var> space, and any instance of a
	<var>Screen</var> object must allocate the maximum allowable STBL space, even if some of this space may not be used by a particular application.		<var>Screen</var> object must allocate the maximum allowable STBL space, even if some of this space may not be used by a particular application.

			While SCRNSTBL can be set higher than LSTBL, at the time a procedure containing a screen object is compiled LSTBL must be set to a value that accommodates both the largest screen object in the procedure as well as the other STBL-resident strings in the procedure.

	An application that exceeds its screen STBL allocation is cancelled, usually with a message like:		An application that exceeds its screen STBL allocation is cancelled, usually with a message like:
Line 22:		Line 24:
	</p>		</p>
	Some Sirius RKTools products, like [[SirScan]] and [[SirPro]], also make use of <var>Screen</var> objects. The <var>SCRNSTBL</var> default value is sufficient for those products for Model 2 terminals. However, the default <var>SCRNSTBL</var> might not be sufficient for other terminal models, especially Model 4 or [[SIRTERM_parameter\|Model 6]] terminals.		Some Sirius RKTools products, like [[SirScan]] and [[SirPro]], also make use of <var>Screen</var> objects. The <var>SCRNSTBL</var> default value is sufficient for those products for Model 2 terminals. However, the default <var>SCRNSTBL</var> might not be sufficient for other terminal models, especially Model 4 or [[SIRTERM_parameter\|Model 6]] terminals.

			If no [[Screen class\|Screen objects]] are used in the Model 204 region, SCRNSTBL can be set to zero. If [[Screen class\|Screen objects]] are used, calculating the correct value is complicated by performance issues related to object swapping. See the discussion at [[Managing server space for objects]], especially the discussion of the SIRIUS MINOBJECTS compiler directive.

	<p class="note"><b>Note:</b> The <var>SCRNSTBL</var> parameter affects the space allocated for <var>Screen</var> objects at compilation time. As such, increasing <var>SCRNSTBL</var> does not increase the amount of space available to pre-compiled requests unless those requests are re-compiled after resetting <var>SCRNSTBL</var>. </p>		<p class="note"><b>Note:</b> The <var>SCRNSTBL</var> parameter affects the space allocated for <var>Screen</var> objects at compilation time. As such, increasing <var>SCRNSTBL</var> does not increase the amount of space available to pre-compiled requests unless those requests are re-compiled after resetting <var>SCRNSTBL</var>. </p>

DCameron: /* Summary */

2017-05-25T09:15:33Z

Summary

← Older revision		Revision as of 09:15, 25 May 2017
Line 5:		Line 5:
	<dd>6144		<dd>6144
	<dt>Parameter type		<dt>Parameter type
	<dd>~~User~~		<dd>System
	<dt>Where set		<dt>Where set
	<dd>System manager resettable		<dd>System manager resettable

DCameron: /* Description */

2017-05-24T14:44:13Z

Description

← Older revision		Revision as of 14:44, 24 May 2017
Line 15:		Line 15:

	==Description==		==Description==
	This is a numeric parameter (with valid values 0 or greater) that indicates the maximum amount of STBL space available to <var class="product">Janus SOAP</var> [[Screen class\|Screen objects]]. <var>Screen</var> objects use STBL space and not FSCB space, and any instance of a		This is a numeric parameter (with valid values 0 or greater) that indicates the maximum amount of <var>[[LSTBL_parameter\|STBL]]</var> space available to <var class="product">Janus SOAP</var> [[Screen class\|Screen objects]]. <var>Screen</var> objects use STBL space and not <var>[[LFSCB_parameter\|FSCB]]</var> space, and any instance of a
	<var>Screen</var> object must allocate the maximum allowable STBL space, even if some of this space may not be used by a particular application.		<var>Screen</var> object must allocate the maximum allowable STBL space, even if some of this space may not be used by a particular application.

JAL: misc cleanup

2016-02-25T20:55:14Z

misc cleanup

← Older revision		Revision as of 20:55, 25 February 2016
Line 13:		Line 13:
	<dd><var class="product">[[Sirius Mods]]</var> 7.1		<dd><var class="product">[[Sirius Mods]]</var> 7.1
	</dl>		</dl>

	==Description==		==Description==
	This is a numeric parameter (with valid values 0 or greater) that indicates the maximum amount of STBL space available to ''Janus SOAP'' [[Screen class\|Screen objects]]. Screen objects use STBL space and not FSCB space, and any instance of a		This is a numeric parameter (with valid values 0 or greater) that indicates the maximum amount of STBL space available to <var class="product">Janus SOAP</var> [[Screen class\|Screen objects]]. <var>Screen</var> objects use STBL space and not FSCB space, and any instance of a
	Screen object must allocate the maximum allowable STBL space, even if some of this space may not be used by a particular application.		<var>Screen</var> object must allocate the maximum allowable STBL space, even if some of this space may not be used by a particular application.

	An application that exceeds its screen STBL allocation is cancelled, usually with a message like:		An application that exceeds its screen STBL allocation is cancelled, usually with a message like:
	<p class="code">MSIR.0750: Class Screen, function AddField: no more space for screen field data ...		<p class="code">MSIR.0750: Class Screen, function AddField: no more space for screen field data ...
	</p>		</p>
	Some Sirius ~~ULSPF~~ products, like [[SirScan]] and [[SirPro]], also make use of ~~screen~~ objects. The SCRNSTBL default value is sufficient for those products for Model 2 terminals. However, the default SCRNSTBL might not be sufficient for other terminal models, especially Model 4 or [[SIRTERM_parameter\|Model 6]] terminals.		Some Sirius RKTools products, like [[SirScan]] and [[SirPro]], also make use of <var>Screen</var> objects. The <var>SCRNSTBL</var> default value is sufficient for those products for Model 2 terminals. However, the default <var>SCRNSTBL</var> might not be sufficient for other terminal models, especially Model 4 or [[SIRTERM_parameter\|Model 6]] terminals.

			<p class="note"><b>Note:</b> The <var>SCRNSTBL</var> parameter affects the space allocated for <var>Screen</var> objects at compilation time. As such, increasing <var>SCRNSTBL</var> does not increase the amount of space available to pre-compiled requests unless those requests are re-compiled after resetting <var>SCRNSTBL</var>. </p>

	Note that the SCRNSTBL parameter affects the space allocated for Screen objects at compilation time. As such, increasing SCRNSTBL will not increase the amount of space available to pre-compiled requests unless those requests are re-compiled after resetting SCRNSTBL.
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: Automatically generated page update

2013-08-27T16:43:44Z

Automatically generated page update

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

JALWiccan: Automatically generated page update

2013-04-19T20:07:03Z

Automatically generated page update

← Older revision		Revision as of 20:07, 19 April 2013
Line 10:		Line 10:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Sirius Mods</var> 7.1		<dd><var class="product">[[Sirius Mods]]</var> 7.1
	</dl>		</dl>
	==Description==		==Description==

Alex: /* Description */

2012-09-12T23:41:55Z

Description

← Older revision		Revision as of 23:41, 12 September 2012
Line 13:		Line 13:
	</dl>		</dl>
	==Description==		==Description==
	This is a numeric parameter (with valid values 0 or greater) that indicates the		This is a numeric parameter (with valid values 0 or greater) that indicates the maximum amount of STBL space available to ''Janus SOAP'' [[Screen class\|Screen objects]]. Screen objects use STBL space and not FSCB space, and any instance of a
	maximum amount of STBL space available to ''Janus SOAP'' [[Screen class\|Screen objects]].		Screen object must allocate the maximum allowable STBL space, even if some of this space may not be used by a particular application.
	Screen objects use STBL space and not FSCB space, and
	any instance of a
	Screen object must allocate the maximum allowable STBL space, even if some of this
	space may not be used by a particular application.
	~~An application that exceeds its screen STBL allocation is cancelled~~.

	Some Sirius ~~User Language SPF~~ products, like [[SirScan]], also make use of screen objects.		An application that exceeds its screen STBL allocation is cancelled, usually with a message like:
	The SCRNSTBL default value is sufficient for those products.		<p class="code">MSIR.0750: Class Screen, function AddField: no more space for screen field data ...
			</p>
			Some Sirius ULSPF products, like [[SirScan]] and [[SirPro]], also make use of screen objects. The SCRNSTBL default value is sufficient for those products for Model 2 terminals. However, the default SCRNSTBL might not be sufficient for other terminal models, especially Model 4 or [[SIRTERM_parameter\|Model 6]] terminals.

			Note that the SCRNSTBL parameter affects the space allocated for Screen objects at compilation time. As such, increasing SCRNSTBL will not increase the amount of space available to pre-compiled requests unless those requests are re-compiled after resetting SCRNSTBL.
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: 1 revision

2012-06-22T19:25:03Z

1 revision

New page

==Summary==
<dl>
<dt>Default value
<dd>6144
<dt>Parameter type
<dd>User
<dt>Where set
<dd>System manager resettable
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Sirius Mods</var> 7.1
</dl>
==Description==
This is a numeric parameter (with valid values 0 or greater) that indicates the
maximum amount of STBL space available to ''Janus SOAP'' [[Screen class|Screen objects]].
Screen objects use STBL space and not FSCB space, and
any instance of a
Screen object must allocate the maximum allowable STBL space, even if some of this
space may not be used by a particular application.
An application that exceeds its screen STBL allocation is cancelled.

Some Sirius User Language SPF products, like [[SirScan]], also make use of screen objects.
The SCRNSTBL default value is sufficient for those products.
[[Category:System parameters]]
[[Category:Parameters]]