RESLTHR parameter: Difference between revisions
| 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> | ||
Revision as of 14:45, 22 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.
RESLTHR=-1 is the default and 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.