RESLTHR parameter: Difference between revisions
m (misc formatting) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 15: | Line 15: | ||
==Description== | ==Description== | ||
<p>The RESLTHR parameter specifies the minimum number of times an | <p> | ||
<p>RESLTHR | 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 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> | ||
<p>You can view APSY LOAD statistics by using the MONITOR 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]] | ||
Latest revision as of 16:29, 23 May 2017
APSY load threshold for making request resident
Summary
- Default value
- -1
- Parameter type
- System
- Where set
- On User 0's parameter line or reset by system manager
- Related products
- All
- Introduced
- Model 204 V5.1
Description
The RESLTHR parameter specifies the minimum number of times an APSY precompiled procedure must be loaded into a user's server before Model 204 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.
The RESLTHR default is -1; it indicates that the parameter has not been set and is not active.
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.
You can view APSY LOAD statistics by using the MONITOR command with the STATISTICS parameter.