APSYPAGE parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (→‎Description: restore earlier link)
m (→‎Description: specify m204 version)
Line 21: Line 21:
<p>
<p>
<var>APSYPAGE</var> was implemented to take advantage of the <code>MVPG</code> machine language instruction which moved an entire hardware page (4K bytes) 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.</p>
<var>APSYPAGE</var> was implemented to take advantage of the <code>MVPG</code> machine language instruction which moved an entire hardware page (4K bytes) 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.</p>
<p class="note"><b>Note:</b> It is now recommended that customers who have been using the <var>APSYPAGE</var> parameter <var class="term">disable the APSYPAGE feature</var> by setting <var>APSYPAGE</var> to 0.</p>  
<p class="note"><b>Note:</b> As of Model&nbsp;204 7.5, it is recommended that customers who have been using the <var>APSYPAGE</var> parameter <var class="term">disable the APSYPAGE feature</var> by setting <var>APSYPAGE</var> to 0.</p>  
<p>
<p>
Instead of <var>APSYPAGE</var>, you can use the following:</p>
Instead of <var>APSYPAGE</var>, you can use the following:</p>

Revision as of 18:34, 14 June 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-byte 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 bytes) 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.

Note: As of Model 204 7.5, it is recommended that customers who have been using the APSYPAGE parameter disable the APSYPAGE feature by setting APSYPAGE to 0.

Instead of APSYPAGE, you can use the following:

  • The RESPAGE parameter (recommended for performance).

    Set RESPAGE to the former value of APSYPAGE. Both RESPAGE and APSYPAGE specify the number of 4096-byte pages allocated for the respective feature.

  • The TEMPPAGE parameter.

    TEMPPAGE pages are larger so fewer are needed. TEMPPAGE pages are 6184 bytes, with 6144 used to hold data and 40 bytes as page trailers. Divide the former APSYPAGE value by 1.5 before adding to TEMPPAGE.