RESPAGE parameter: Difference between revisions
No edit summary |
(Elaborated on the meaning of RESPAGE) |
||
| Line 14: | Line 14: | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>Activates the APSY | <p>Activates the Resident Request feature for APSY precompiled procedures in storage. The parameter specifies the maximum number of 4K operating system pages to be allocated, above the bar, for procedures that are made resident. Whenever a procedure is made resident, a minimum of 16-4K pages are allocated for that procedure. If more pages are required, another chunk of 16-4K pages are allocated. These chunks of 16-4K pages facilitate more efficient management of ATB storage which the operating system allocates in 1 megabyte increments. The actual storage "used" by resident requests can be displayed with the MONITOR SUBSYS (PROCCT) <subsysname> command. Given this allocation algorithm, if you have 1000 procedures that you want to become resident, you will need to set, at a minimum, RESPAGE=16000.</p> | ||
<p>If a non-zero value is specified, then the actual number of 4K pages allocated will be rounded up to the next 1 megabyte page boundary (the next multiple of 256 4K pages).</p> | <p>If a non-zero value is specified, then the actual number of 4K pages allocated will be rounded up to the next 1 megabyte page boundary (the next multiple of 256 4K pages).</p> | ||
<p>If specified, [[RESSIZE_parameter|RESSIZE]], [[RESLTHR parameter|RESLTHR]], and [[RESTHRSH parameter|RESTHRSH]] are ignored; RESSIZE is reset to -1; RESLTHR and RESTHRSH are reset to zero.</p> | <p> | ||
If specified, [[RESSIZE_parameter|RESSIZE]], [[RESLTHR parameter|RESLTHR]], and [[RESTHRSH parameter|RESTHRSH]] are ignored; RESSIZE is reset to -1; RESLTHR and RESTHRSH are reset to zero. | |||
</p> | |||
<p> | |||
VIEW [[RESCURR parameter|RESCURR]], and [[RESHIGH parameter|RESHIGH]] will show, respectively, the current and the HWM of ATB storage allocated (even multiples of 16*4K bytes) for resident requests. | |||
</p> | |||
<p>For IBM z/OS systems only.</p> | <p>For IBM z/OS systems only.</p> | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
[[Category:System parameters]] | [[Category:System parameters]] | ||
Revision as of 19:16, 8 June 2016
Number of resident N/QTBL ATB pages
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- User 0 parameter line
- Related products
- All
- Introduced
- Model 204 version 7.5
Description
Activates the Resident Request feature for APSY precompiled procedures in storage. The parameter specifies the maximum number of 4K operating system pages to be allocated, above the bar, for procedures that are made resident. Whenever a procedure is made resident, a minimum of 16-4K pages are allocated for that procedure. If more pages are required, another chunk of 16-4K pages are allocated. These chunks of 16-4K pages facilitate more efficient management of ATB storage which the operating system allocates in 1 megabyte increments. The actual storage "used" by resident requests can be displayed with the MONITOR SUBSYS (PROCCT) <subsysname> command. Given this allocation algorithm, if you have 1000 procedures that you want to become resident, you will need to set, at a minimum, RESPAGE=16000.
If a non-zero value is specified, then the actual number of 4K pages allocated will be rounded up to the next 1 megabyte page boundary (the next multiple of 256 4K pages).
If specified, RESSIZE, RESLTHR, and RESTHRSH are ignored; RESSIZE is reset to -1; RESLTHR and RESTHRSH are reset to zero.
VIEW RESCURR, and RESHIGH will show, respectively, the current and the HWM of ATB storage allocated (even multiples of 16*4K bytes) for resident requests.
For IBM z/OS systems only.