APSYPAGE parameter - Revision history

ELowell: /* Description */

2016-09-28T00:17:24Z

Description

← Older revision		Revision as of 00:17, 28 September 2016
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="warn"><b>Note:</b> As of Model 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. As of Model 204 7.7, setting <var>APSYPAGE</var> to a non-zero value results in an error and prevents the Online from coming up. </p>		<p class="warn"><b>Note:</b> As of Model 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. <br />As of Model 204 7.7, setting <var>APSYPAGE</var> to a non-zero value results in an error and <var class="term">prevents the Online from coming up</var>. </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>

JAL: feature can't be invoked in 7.7

2016-06-14T22:12:08Z

feature can't be invoked in 7.7

← Older revision		Revision as of 22:12, 14 June 2016
Line 16:		Line 16:
	==Description==		==Description==
	<p>		<p>
	~~Activates~~ the [[System requirements for Application Subsystems#Activating the APSY Precompiled Procedures in Storage feature\|APSY Precompiled Procedures in Storage feature]] by specifying a number of 4K-byte operating system pages.</p>		While the feature was available, the <var>APSYPAGE</var> parameter activated the [[System requirements for Application Subsystems#Activating the APSY Precompiled Procedures in Storage feature\|APSY Precompiled Procedures in Storage feature]] by specifying a number of 4K-byte operating system pages.</p>
	<p>		<p>
	For IBM z/OS systems only.</p>		For IBM z/OS systems only.</p>
	<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> As of Model 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 class="warn"><b>Note:</b> As of Model 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. As of Model 204 7.7, setting <var>APSYPAGE</var> to a non-zero value results in an error and prevents the Online from coming up. </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>

JAL: /* Description */ specify m204 version

2016-06-14T18:34:18Z

Description: specify m204 version

← Older revision		Revision as of 18:34, 14 June 2016
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 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>

JAL: /* Description */ restore earlier link

2016-06-14T18:10:52Z

Description: restore earlier link

← Older revision		Revision as of 18:10, 14 June 2016
Line 16:		Line 16:
	==Description==		==Description==
	<p>		<p>
	Activates the [[~~Performance monitoring and tuning~~#~~Resident Request~~ feature ~~for precompiled procedures~~\|~~Resident Request~~ feature]] ~~for APSY precompiled procedures in storage feature~~ by specifying a number of 4K-byte operating system pages.</p>		Activates the [[System requirements for Application Subsystems#Activating the APSY Precompiled Procedures in Storage feature\|APSY Precompiled Procedures in Storage feature]] by specifying a number of 4K-byte operating system pages.</p>
	<p>		<p>
	For IBM z/OS systems only.</p>		For IBM z/OS systems only.</p>

JAL: /* Description */ add "Note"

2016-06-10T19:57:31Z

Description: add "Note"

← Older revision		Revision as of 19:57, 10 June 2016
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">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> 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>		<p>
	Instead of <var>APSYPAGE</var>, you can use the following:</p>		Instead of <var>APSYPAGE</var>, you can use the following:</p>

JAL: misc formatting

2016-06-10T19:52:25Z

misc formatting

← Older revision		Revision as of 19:52, 10 June 2016
Line 16:		Line 16:
	==Description==		==Description==
	<p>		<p>
	Activates the APSY ~~Precompiled Procedures~~ in ~~Storage~~ feature by specifying a number of 4K operating system pages.</p>		Activates the [[Performance monitoring and tuning#Resident Request feature for precompiled procedures\|Resident Request feature]] for APSY precompiled procedures in storage feature by specifying a number of 4K-byte operating system pages.</p>
	<p>		<p>
	For IBM z/OS systems only.</p>		For IBM z/OS systems only.</p>
	<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) 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>~~Therefore, 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">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>
			Instead of <var>APSYPAGE</var>, you can use the following:</p>
			<ul>
			<li>The <var>[[RESPAGE parameter\|RESPAGE]]</var> parameter (recommended for performance).
			<p>
			Set <var>RESPAGE</var> to the former value of <var>APSYPAGE</var>. Both <var>RESPAGE</var> and <var>APSYPAGE</var> specify the number of 4096-byte pages allocated for the respective feature. </p></li>

	~~<p>Instead of APSYPAGE, you can use the following:</p>~~		<li>The <var>[[TEMPPAGE parameter\|TEMPPAGE]]</var> parameter.
	~~<ul>~~		<p>
	<li>The <var>[[~~RESPAGE~~ parameter\|~~RESPAGE~~]]</var> parameter ~~(recommended for performance). Set <var>RESPAGE</var> to the former value of APSYPAGE~~. ~~Both <var>RESPAGE</var> and <var>APSYPAGE</var> specify the number of 4096-byte pages allocated for the respective feature.</li>~~		<var>TEMPPAGE</var> pages are larger so fewer are needed. <var>TEMPPAGE</var> pages are 6184 bytes, with 6144 used to hold data and 40 bytes as page trailers. Divide the former <var>APSYPAGE</var> value by 1.5 before adding to <var>TEMPPAGE</var>. </p></li>
	<li>
	~~The~~ <var>~~[[TEMPPAGE parameter\|~~TEMPPAGE]]</var> ~~parameter. TEMPPAGE~~ pages are ~~bigger~~ so fewer are needed~~; divide the former APSYPAGE value by 1.5 before adding to TEMPPAGE~~. TEMPPAGE pages are 6184 bytes, with 6144 used to hold data and 40 bytes as page trailers.</li>
	</ul>		</ul>

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

ELowell: /* Description */

2016-01-15T17:29:14Z

Description

← Older revision		Revision as of 17:29, 15 January 2016
Line 23:		Line 23:
	<p>Therefore, 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>Therefore, 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>Instead of APSYPAGE, you can use ~~either of~~ the following:</p>		<p>Instead of APSYPAGE, you can use the following:</p>
	<ul>		<ul>
	<li>The <var>[[RESPAGE parameter\|RESPAGE]]</var> parameter (recommended for performance). Set <var>RESPAGE</var> to the former value of APSYPAGE. Both <var>RESPAGE</var> and <var>APSYPAGE</var> specify the number of 4096-byte pages allocated for the respective feature.</li>		<li>The <var>[[RESPAGE parameter\|RESPAGE]]</var> parameter (recommended for performance). Set <var>RESPAGE</var> to the former value of APSYPAGE. Both <var>RESPAGE</var> and <var>APSYPAGE</var> specify the number of 4096-byte pages allocated for the respective feature.</li>

ELowell: /* Description */

2016-01-14T18:06:32Z

Description

← Older revision		Revision as of 18:06, 14 January 2016
Line 25:		Line 25:
	<p>Instead of APSYPAGE, you can use either of the following:</p>		<p>Instead of APSYPAGE, you can use either of the following:</p>
	<ul>		<ul>
	<li>The <var>[[RESPAGE parameter\|RESPAGE]]</var> parameter (recommended for performance). Set <var>RESPAGE</var> to the former value of APSYPAGE. Both <var>RESPAGE</var> and <var>APSYPAGE</var> ~~are~~ 4096 ~~(hardware page size) bytes~~.</li>		<li>The <var>[[RESPAGE parameter\|RESPAGE]]</var> parameter (recommended for performance). Set <var>RESPAGE</var> to the former value of APSYPAGE. Both <var>RESPAGE</var> and <var>APSYPAGE</var> specify the number of 4096-byte pages allocated for the respective feature.</li>
	<li>		<li>
	The <var>[[TEMPPAGE parameter\|TEMPPAGE]]</var> parameter. TEMPPAGE pages are bigger so fewer are needed; divide the former APSYPAGE value by 1.5 before adding to TEMPPAGE. TEMPPAGE pages are 6184 bytes, with 6144 used to hold data and 40 bytes as page trailers.</li>		The <var>[[TEMPPAGE parameter\|TEMPPAGE]]</var> parameter. TEMPPAGE pages are bigger so fewer are needed; divide the former APSYPAGE value by 1.5 before adding to TEMPPAGE. TEMPPAGE pages are 6184 bytes, with 6144 used to hold data and 40 bytes as page trailers.</li>

ELowell: /* Description */

2016-01-14T17:27:46Z

Description

← Older revision		Revision as of 17:27, 14 January 2016
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) 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) 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>Therefore, 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~~. Then set the <var>[[RESPAGE parameter\|RESPAGE]]</var> parameter to the former value of APSYPAGE~~.</p>		<p>Therefore, 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>

	The ~~units~~ for ~~both~~ <var>RESPAGE</var> and <var>APSYPAGE</var> are 4096 (hardware page size) bytes.		<p>Instead of APSYPAGE, you can use either of the following:</p>
			<ul>
	~~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.		<li>The <var>[[RESPAGE parameter\|RESPAGE]]</var> parameter (recommended for performance). Set <var>RESPAGE</var> to the former value of APSYPAGE. Both <var>RESPAGE</var> and <var>APSYPAGE</var> are 4096 (hardware page size) bytes.</li>
			<li>
			The <var>[[TEMPPAGE parameter\|TEMPPAGE]]</var> parameter. TEMPPAGE pages are bigger so fewer are needed; divide the former APSYPAGE value by 1.5 before adding to TEMPPAGE. TEMPPAGE pages are 6184 bytes, with 6144 used to hold data and 40 bytes as page trailers.</li>
			</ul>

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

ELowell at 17:06, 14 January 2016

2016-01-14T17:06:59Z

← Older revision		Revision as of 17:06, 14 January 2016
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]]