SCHDOFLZ parameter - Revision history

DCameron: /* Description */

2017-05-24T12:05:14Z

Description

← Older revision		Revision as of 12:05, 24 May 2017
Line 35:		Line 35:
	<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB <var>[[MP/204#Multiprocessing_.28MP.2F204.29\|MP]]</var> subtasks. <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB <var>[[MP/204#Multiprocessing_.28MP.2F204.29\|MP]]</var> subtasks. <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>
	<p>		<p>
	~~Before~~ Model 204 7.7, the minimum allowed value for <var>SCHDOFLZ</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFLZ</var> to 0 unless the <var>[[MPDELAYZ parameter\|MPDELAYZ]]</var> parameter is set to a non-zero value.		Prior to Model 204 7.7, the minimum allowed value for <var>SCHDOFLZ</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFLZ</var> to 0 unless the <var>[[MPDELAYZ parameter\|MPDELAYZ]]</var> parameter is set to a non-zero value.
	</p>		</p>

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

DCameron: /* Description */

2017-05-24T12:03:01Z

Description

← Older revision		Revision as of 12:03, 24 May 2017
Line 33:		Line 33:
	If <var>AMPSUBZ</var> is 1, a zIIP subtask is activated as soon as there is any offloadable work, and it then runs until there is no more offloadable work for it to process. So with <var>AMPSUBZ</var> set to 1, <var>SCHDOFLZ</var> does not affect any zIIP subtask activation decisions. However, under Model 204 7.5 and 7.6, it would affect non-SRB MP subtask activation and zIIP assistance decisions. Under Model 204 7.7 and later, this aspect of <var>SCHDOFLZ</var> is subsumed by <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var>.</p>		If <var>AMPSUBZ</var> is 1, a zIIP subtask is activated as soon as there is any offloadable work, and it then runs until there is no more offloadable work for it to process. So with <var>AMPSUBZ</var> set to 1, <var>SCHDOFLZ</var> does not affect any zIIP subtask activation decisions. However, under Model 204 7.5 and 7.6, it would affect non-SRB MP subtask activation and zIIP assistance decisions. Under Model 204 7.7 and later, this aspect of <var>SCHDOFLZ</var> is subsumed by <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var>.</p>
	<p>		<p>
	<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks. <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB <var>[[MP/204#Multiprocessing_.28MP.2F204.29\|MP]]</var> subtasks. <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>
	<p>		<p>
	Before Model 204 7.7, the minimum allowed value for <var>SCHDOFLZ</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFLZ</var> to 0 unless the <var>[[MPDELAYZ parameter\|MPDELAYZ]]</var> parameter is set to a non-zero value.		Before Model 204 7.7, the minimum allowed value for <var>SCHDOFLZ</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFLZ</var> to 0 unless the <var>[[MPDELAYZ parameter\|MPDELAYZ]]</var> parameter is set to a non-zero value.

DCameron: /* Summary */

2017-05-24T11:52:05Z

Summary

← Older revision		Revision as of 11:52, 24 May 2017
Line 9:		Line 9:
	<dd>On User 0's parameter line or reset by system manager.		<dd>On User 0's parameter line or reset by system manager.
	<dt>Related products		<dt>Related products
	<dd>~~All~~		<dd><var>[[Performance_monitoring_and_tuning#Offloading_Model_204_work_to_zIIP_processors\|M204 HPO]]</var>
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Model 204 V7.4</var>		<dd><var class="product">Model 204 V7.4</var>

JAL: add `s`

2016-08-02T18:54:21Z

add <var>s

← Older revision		Revision as of 18:54, 2 August 2016
Line 35:		Line 35:
	<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks. <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks. <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>
	<p>		<p>
	Before Model 204 7.7, the minimum allowed value for <var>SCHDOFLZ</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFLZ</var> to 0 unless the [[MPDELAYZ parameter]] is set to a non-zero value.		Before Model 204 7.7, the minimum allowed value for <var>SCHDOFLZ</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFLZ</var> to 0 unless the <var>[[MPDELAYZ parameter\|MPDELAYZ]]</var> parameter is set to a non-zero value.
	</p>		</p>

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

Alex: /* Description */

2016-08-02T05:31:02Z

Description

← Older revision		Revision as of 05:31, 2 August 2016
Line 34:		Line 34:
	<p>		<p>
	<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks. <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks. <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>
			<p>
			Before Model 204 7.7, the minimum allowed value for <var>SCHDOFLZ</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFLZ</var> to 0 unless the [[MPDELAYZ parameter]] is set to a non-zero value.
			</p>
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

JAL: minor formatting

2016-07-28T19:27:30Z

minor formatting

← Older revision		Revision as of 19:27, 28 July 2016
Line 31:		Line 31:
	</ul>		</ul>
	<p>		<p>
	If <var>AMPSUBZ</var> is 1, a zIIP subtask is activated as soon as there is any offloadable work, and it then runs until there is no more offloadable work for it to process. So with <var>~~AMPSUB~~</var>=1, <var>SCHDOFLZ</var> does not affect any zIIP subtask activation decisions. However, under Model 204 7.5 and 7.6, it would affect a non-SRB MP subtask activation and zIIP assistance decisions. Under Model 204 7.7 and later, this aspect of <var>SCHDOFLZ</var> ~~as been~~ subsumed by <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var>.</p>		If <var>AMPSUBZ</var> is 1, a zIIP subtask is activated as soon as there is any offloadable work, and it then runs until there is no more offloadable work for it to process. So with <var>AMPSUBZ</var> set to 1, <var>SCHDOFLZ</var> does not affect any zIIP subtask activation decisions. However, under Model 204 7.5 and 7.6, it would affect non-SRB MP subtask activation and zIIP assistance decisions. Under Model 204 7.7 and later, this aspect of <var>SCHDOFLZ</var> is subsumed by <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var>.</p>
	<p>		<p>
	<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks~~, and~~ <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help zIIP subtasks ~~out~~, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks. <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>

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

JAL: minor formatting

2016-07-28T16:45:34Z

minor formatting

← Older revision		Revision as of 16:45, 28 July 2016
Line 33:		Line 33:
	If <var>AMPSUBZ</var> is 1, a zIIP subtask is activated as soon as there is any offloadable work, and it then runs until there is no more offloadable work for it to process. So with <var>AMPSUB</var>=1, <var>SCHDOFLZ</var> does not affect any zIIP subtask activation decisions. However, under Model 204 7.5 and 7.6, it would affect a non-SRB MP subtask activation and zIIP assistance decisions. Under Model 204 7.7 and later, this aspect of <var>SCHDOFLZ</var> as been subsumed by <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var>.</p>		If <var>AMPSUBZ</var> is 1, a zIIP subtask is activated as soon as there is any offloadable work, and it then runs until there is no more offloadable work for it to process. So with <var>AMPSUB</var>=1, <var>SCHDOFLZ</var> does not affect any zIIP subtask activation decisions. However, under Model 204 7.5 and 7.6, it would affect a non-SRB MP subtask activation and zIIP assistance decisions. Under Model 204 7.7 and later, this aspect of <var>SCHDOFLZ</var> as been subsumed by <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var>.</p>
	<p>		<p>
	<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks, and <var>[[SCHDOFLS ~~parameter\|SCHDOFLS]]~~</var> controls how aggressively MP subtasks are started to help zIIP subtasks out, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks, and <var>SCHDOFLS</var> controls how aggressively MP subtasks are started to help zIIP subtasks out, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>

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

JAL: misc formatting

2016-07-28T16:43:21Z

misc formatting

← Older revision		Revision as of 16:43, 28 July 2016
Line 13:		Line 13:
	<dd><var class="product">Model 204 V7.4</var>		<dd><var class="product">Model 204 V7.4</var>
	</dl>		</dl>

	==Description==		==Description==
	<p>~~Applies~~ to z/OS only</p>		<p>
	<p>On a z/OS system, <var class="product">Model 204</var> zIIP support enables you to offload <var class="product">Model 204</var> work from regular processors to zIIP processors.</p>		This parameter applies to z/OS only.</p>
	<p>SCHDOFLZ specifies the target number of threads on the zIIP offload queue per active task. Setting this parameter makes the <var class="product">Model 204</var> zIIP subtask scheduler more responsive to instantaneous increases in load.</p>		<p>
	<p>The default value of 2 means that if there are more than twice as many units of zIIP offloadable work waiting to be processed in a zIIP subtask as there are active subtasks, and fewer than AMPSUBZ subtasks are currently running, another zIIP offload subtask is activated. </p>		On a z/OS system, <var class="product">Model 204</var> zIIP support enables you to offload <var class="product">Model 204</var> work from regular processors to zIIP processors.</p>
	<p><var>SCHDOFLZ</var> has no effect if zIIP SRBs are not in effect in an Online (<var>NMPSUBZ</var>=0) ~~or if the~~ number of active SRBs (<var>AMPSUBZ</var>) is set to 0. If <var>AMPSUBZ</var>=1, a zIIP subtask is activated as soon as there is any offloadable work and then runs until there is no more offloadable work for it to process. So with <var>AMPSUB</var>=1, <var>SCHDOFLZ</var> does not affect any zIIP subtask activation decisions. However, under Model 204 7.5 and 7.6, it would affect a non-SRB MP subtask activation and zIIP assistance decisions. Under Model 204 7.7 and later, this aspect of <var>SCHDOFLZ</var> as been subsumed by <var>SCHDOFLS</var>.</p>		<p>
	<p>~~The~~ [[SCHDOFL parameter]] performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks and ~~the~~ [[SCHDOFLS parameter]] controls how aggressively MP subtasks ~~will be~~ started to help zIIP subtasks out ~~and~~ how aggressively MP subtasks ~~will~~ take work from zIIP subtasks.		<var>SCHDOFLZ</var> specifies the target number of threads on the zIIP offload queue per active task. Setting this parameter makes the <var class="product">Model 204</var> zIIP subtask scheduler more responsive to instantaneous increases in load.</p>
			<p>
			The default value, 2, means that if there are more than twice as many units of zIIP offloadable work waiting to be processed in a zIIP subtask as there are active subtasks, and fewer than <var>AMPSUBZ</var> subtasks are currently running, another zIIP offload subtask is activated. </p>
			<p>
			<var>SCHDOFLZ</var> has no effect if either of these is true: </p>
			<ul>
			<li>zIIP SRBs are not in effect in an Online (<var>[[NMPSUBZ parameter\|NMPSUBZ]]</var> is 0).</li>

			<li>The number of active SRBs (<var>[[AMPSUBZ parameter\|AMPSUBZ]]</var>) is set to 0. </li>
			</ul>
			<p>
			If <var>AMPSUBZ</var> is 1, a zIIP subtask is activated as soon as there is any offloadable work, and it then runs until there is no more offloadable work for it to process. So with <var>AMPSUB</var>=1, <var>SCHDOFLZ</var> does not affect any zIIP subtask activation decisions. However, under Model 204 7.5 and 7.6, it would affect a non-SRB MP subtask activation and zIIP assistance decisions. Under Model 204 7.7 and later, this aspect of <var>SCHDOFLZ</var> as been subsumed by <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var>.</p>
			<p>
			<var>[[SCHDOFL parameter\|SCHDOFL]]</var> performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks, and <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help zIIP subtasks out, as well as how aggressively MP subtasks take work from zIIP subtasks. </p>

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

Alex: /* Description */

2016-07-28T06:31:11Z

Description

← Older revision		Revision as of 06:31, 28 July 2016
Line 18:		Line 18:
	<p>SCHDOFLZ specifies the target number of threads on the zIIP offload queue per active task. Setting this parameter makes the <var class="product">Model 204</var> zIIP subtask scheduler more responsive to instantaneous increases in load.</p>		<p>SCHDOFLZ specifies the target number of threads on the zIIP offload queue per active task. Setting this parameter makes the <var class="product">Model 204</var> zIIP subtask scheduler more responsive to instantaneous increases in load.</p>
	<p>The default value of 2 means that if there are more than twice as many units of zIIP offloadable work waiting to be processed in a zIIP subtask as there are active subtasks, and fewer than AMPSUBZ subtasks are currently running, another zIIP offload subtask is activated. </p>		<p>The default value of 2 means that if there are more than twice as many units of zIIP offloadable work waiting to be processed in a zIIP subtask as there are active subtasks, and fewer than AMPSUBZ subtasks are currently running, another zIIP offload subtask is activated. </p>
	<p>SCHDOFLZ has no effect if zIIP SRBs are not in effect in an Online (NMPSUBZ=0) or if the number of active SRBs (AMPSUBZ) is set to 0 ~~or 1~~. (If AMPSUBZ=1, a zIIP subtask is activated as soon as there is any offloadable work and then runs until there is no more offloadable work for it to process.)</p>		<p><var>SCHDOFLZ</var> has no effect if zIIP SRBs are not in effect in an Online (<var>NMPSUBZ</var>=0) or if the number of active SRBs (<var>AMPSUBZ</var>) is set to 0. If <var>AMPSUBZ</var>=1, a zIIP subtask is activated as soon as there is any offloadable work and then runs until there is no more offloadable work for it to process. So with <var>AMPSUB</var>=1, <var>SCHDOFLZ</var> does not affect any zIIP subtask activation decisions. However, under Model 204 7.5 and 7.6, it would affect a non-SRB MP subtask activation and zIIP assistance decisions. Under Model 204 7.7 and later, this aspect of <var>SCHDOFLZ</var> as been subsumed by <var>SCHDOFLS</var>.</p>
	<p>The [[SCHDOFL parameter]] performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks and the [[SCHDOFLS parameter]] controls how aggressively MP subtasks will be started to help zIIP subtasks out and how aggressively MP subtasks will take work from zIIP subtasks.		<p>The [[SCHDOFL parameter]] performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks and the [[SCHDOFLS parameter]] controls how aggressively MP subtasks will be started to help zIIP subtasks out and how aggressively MP subtasks will take work from zIIP subtasks.
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Alex: /* Description */

2016-07-28T00:31:01Z

Description

← Older revision		Revision as of 00:31, 28 July 2016
Line 19:		Line 19:
	<p>The default value of 2 means that if there are more than twice as many units of zIIP offloadable work waiting to be processed in a zIIP subtask as there are active subtasks, and fewer than AMPSUBZ subtasks are currently running, another zIIP offload subtask is activated. </p>		<p>The default value of 2 means that if there are more than twice as many units of zIIP offloadable work waiting to be processed in a zIIP subtask as there are active subtasks, and fewer than AMPSUBZ subtasks are currently running, another zIIP offload subtask is activated. </p>
	<p>SCHDOFLZ has no effect if zIIP SRBs are not in effect in an Online (NMPSUBZ=0) or if the number of active SRBs (AMPSUBZ) is set to 0 or 1. (If AMPSUBZ=1, a zIIP subtask is activated as soon as there is any offloadable work and then runs until there is no more offloadable work for it to process.)</p>		<p>SCHDOFLZ has no effect if zIIP SRBs are not in effect in an Online (NMPSUBZ=0) or if the number of active SRBs (AMPSUBZ) is set to 0 or 1. (If AMPSUBZ=1, a zIIP subtask is activated as soon as there is any offloadable work and then runs until there is no more offloadable work for it to process.)</p>
			<p>The [[SCHDOFL parameter]] performs the same function as <var>SCHDOFLZ</var> for non-SRB MP subtasks and the [[SCHDOFLS parameter]] controls how aggressively MP subtasks will be started to help zIIP subtasks out and how aggressively MP subtasks will take work from zIIP subtasks.
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

SCHDOFLZ parameter - Revision history

DCameron: /* Description */

DCameron: /* Description */

DCameron: /* Summary */

JAL: add s

Alex: /* Description */

JAL: minor formatting

JAL: minor formatting

JAL: misc formatting

Alex: /* Description */

Alex: /* Description */

JAL: add `s`