APSYPAGE parameter: Difference between revisions
No edit summary |
|||
| Line 24: | Line 24: | ||
The units for both <var>RESPAGE</var> and <var>APSYPAGE</var> are 4096 (hardware page size) bytes. | The units for both <var>RESPAGE</var> and <var>APSYPAGE</var> are 4096 (hardware page size) bytes. | ||
Alternatively, you can use <var>[[TEMPPAGE parameter|TEMPPAGE]]</var> instead of APSYPAGE. TEMPPAGE units are 6184 bytes, so you would use the APSYPAGE value, divided by 1.5. | |||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Revision as of 17:06, 14 January 2016
APSYPAGE is obsolete as of 7.6
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- On User 0's parameter line
- Related products
- All
- Introduced
- Model 204 V5.1
Description
Activates the APSY Precompiled Procedures in Storage feature by specifying a number of 4K operating system pages.
For IBM z/OS systems only.
APSYPAGE was implemented to take advantage of the MVPG machine language instruction which moved an entire hardware page (4K) with a single instruction and which, at the time, had significantly better performance than the stream-oriented moves used by standard APSY load. However, recent hardware models actually seem to have better performance for the stream-oriented moves.
Therefore, it is now recommended that customers who have been using the APSYPAGE parameter disable the APSYPAGE feature by setting APSYPAGE to 0. Then set the RESPAGE parameter to the former value of APSYPAGE.
The units for both RESPAGE and APSYPAGE are 4096 (hardware page size) bytes.
Alternatively, you can use TEMPPAGE instead of APSYPAGE. TEMPPAGE units are 6184 bytes, so you would use the APSYPAGE value, divided by 1.5.