RESLTHR parameter - Revision history

JAL: misc formatting

2017-05-23T16:29:29Z

misc formatting

← Older revision		Revision as of 16:29, 23 May 2017
Line 15:		Line 15:

	==Description==		==Description==
	<p>The RESLTHR parameter specifies the minimum number of times an ~~<var>~~[[~~Application_Subsystem_development~~\|APSY]]~~</var>~~ precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's ~~<var>~~[[~~LNTBL_paramete\|~~NTBL]]~~</var>~~ and ~~<var>~~[[~~LQTBL_parameter\|~~QTBL]]~~</var>~~ resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>		<p>
	<p>RESLTHR=-1 ~~is the default and~~ indicates that the parameter has not been set and is not active.</p>		The <var>RESLTHR</var> parameter specifies the minimum number of times an [[Application Subsystem development\|APSY]] precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's [[NTBL]] and [[QTBL]] resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>
	<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce ~~<var>~~[[~~CCATEMP\|~~CCATEMP]]~~</var>~~ I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>		<p>
	<p>You can view APSY LOAD statistics by using the <var>[[~~MONITOR_command~~\|MONITOR]]</var> command with the STATISTICS parameter.</p>		The <var>RESLTHR</var> default is -1; it indicates that the parameter has not been set and is not active.</p>
			<p>
			The <var>RESLTHR</var> parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore <var>RESLTHR</var>) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce [[CCATEMP]] I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>
			<p>
			You can view APSY LOAD statistics by using the <var>[[MONITOR command\|MONITOR]]</var> command with the <var>STATISTICS</var> parameter.</p>

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

DCameron: /* Description */

2017-05-23T12:57:37Z

Description

← Older revision		Revision as of 12:57, 23 May 2017
Line 18:		Line 18:
	<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>		<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>
	<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce <var>[[CCATEMP\|CCATEMP]]</var> I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>		<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce <var>[[CCATEMP\|CCATEMP]]</var> I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>
	<p>You can view APSY LOAD statistics by using the MONITOR command with the STATISTICS parameter.</p>		<p>You can view APSY LOAD statistics by using the <var>[[MONITOR_command\|MONITOR]]</var> command with the STATISTICS parameter.</p>
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2017-05-23T12:50:30Z

Description

← Older revision		Revision as of 12:50, 23 May 2017
Line 17:		Line 17:
	<p>The RESLTHR parameter specifies the minimum number of times an <var>[[Application_Subsystem_development\|APSY]]</var> precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's <var>[[LNTBL_paramete\|NTBL]]</var> and <var>[[LQTBL_parameter\|QTBL]]</var> resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>		<p>The RESLTHR parameter specifies the minimum number of times an <var>[[Application_Subsystem_development\|APSY]]</var> precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's <var>[[LNTBL_paramete\|NTBL]]</var> and <var>[[LQTBL_parameter\|QTBL]]</var> resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>
	<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>		<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>
	<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>		<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce <var>[[CCATEMP\|CCATEMP]]</var> I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>
	<p>You can view APSY LOAD statistics by using the MONITOR command with the STATISTICS parameter.</p>		<p>You can view APSY LOAD statistics by using the MONITOR command with the STATISTICS parameter.</p>
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2017-05-22T14:49:02Z

Description

← Older revision		Revision as of 14:49, 22 May 2017
Line 15:		Line 15:

	==Description==		==Description==
	<p>The RESLTHR parameter specifies the minimum number of times an <var>[[Application_Subsystem_development\|APSY]]</var> precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's NTBL and QTBL resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>		<p>The RESLTHR parameter specifies the minimum number of times an <var>[[Application_Subsystem_development\|APSY]]</var> precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's <var>[[LNTBL_paramete\|NTBL]]</var> and <var>[[LQTBL_parameter\|QTBL]]</var> resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>
	<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>		<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>
	<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>		<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>

DCameron: /* Description */

2017-05-22T14:45:52Z

Description

← Older revision		Revision as of 14:45, 22 May 2017
Line 15:		Line 15:

	==Description==		==Description==
	<p>The RESLTHR parameter specifies the minimum number of times an APSY precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's NTBL and QTBL resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>		<p>The RESLTHR parameter specifies the minimum number of times an <var>[[Application_Subsystem_development\|APSY]]</var> precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's NTBL and QTBL resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>
	<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>		<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>
	<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>		<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>

DCameron: /* Summary */

2014-09-10T11:08:48Z

Summary

← Older revision		Revision as of 11:08, 10 September 2014
Line 11:		Line 11:
	<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 V5.1</var>
	</dl>		</dl>

	==Description==		==Description==
	<p>The RESLTHR parameter specifies the minimum number of times an APSY precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's NTBL and QTBL resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>		<p>The RESLTHR parameter specifies the minimum number of times an APSY precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's NTBL and QTBL resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>

Admin: /* Description */

2014-05-12T20:46:19Z

Description

← Older revision		Revision as of 20:46, 12 May 2014
Line 17:		Line 17:
	<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>		<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>
	<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>		<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>
	<p>You can view APSY LOAD statistics by using the ~~<var>[[~~MONITOR ~~command\|MONITOR]]</var>~~ command with the ~~<var>[[STATISTICS parameter\|~~STATISTICS~~]]</var>~~ parameter.</p>		<p>You can view APSY LOAD statistics by using the MONITOR command with the STATISTICS parameter.</p>
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Admin: /* Description */

2014-05-12T20:42:25Z

Description

← Older revision		Revision as of 20:42, 12 May 2014
Line 16:		Line 16:
	<p>The RESLTHR parameter specifies the minimum number of times an APSY precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's NTBL and QTBL resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>		<p>The RESLTHR parameter specifies the minimum number of times an APSY precompiled procedure must be loaded into a user's server before <var class="product">Model 204</var> attempts to make the procedure's NTBL and QTBL resident and shareable in virtual storage. Once a procedure's NTBL and QTBL have been made resident, subsequent evaluation of that procedure no longer requires loading those tables into the user's server. </p>
	<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>		<p>RESLTHR=-1 is the default and indicates that the parameter has not been set and is not active.</p>
	<p>The RESLTHR parameter is similar to the RESTHRSH parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>		<p>The RESLTHR parameter is similar to the <var>[[RESTHRSH parameter\|RESTHRSH]]</var> parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>
	<p>You can view APSY LOAD statistics by using the MONITOR command with the STATISTICS parameter.</p>		<p>You can view APSY LOAD statistics by using the <var>[[MONITOR command\|MONITOR]]</var> command with the <var>[[STATISTICS parameter\|STATISTICS]]</var> parameter.</p>
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: Automatically generated page update

2013-08-27T16:43:17Z

Automatically generated page update

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

DmeWiccan: Automatically generated page update

2013-04-23T01:51:19Z

Automatically generated page update

← Older revision		Revision as of 01:51, 23 April 2013
Line 17:		Line 17:
	<p>The RESLTHR parameter is similar to the RESTHRSH parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>		<p>The RESLTHR parameter is similar to the RESTHRSH parameter, which sets the minimum number of times a procedure must be swapped, along with the evaluating user, to CCASERVR before the procedure's NTBL and QTBL will be made resident. In a system with little or no server swapping, the number of APSY LOADs (and therefore RESLTHR) provides a better metric for determining whether to make a procedure's NTBL and QTBL resident. Resident requests may reduce CCATEMP I/O by as much as 20 percent and the number of bytes transferred per server I/O by as much as 30 percent.</p>
	<p>You can view APSY LOAD statistics by using the MONITOR command with the STATISTICS parameter.</p>		<p>You can view APSY LOAD statistics by using the MONITOR command with the STATISTICS parameter.</p>
	[[Category:System ~~Parameters~~]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]