SCHDOPT parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (misc cleanup)
Line 13: Line 13:
<dd><var class="product">Model 204 V6.1</var> or earlier
<dd><var class="product">Model 204 V6.1</var> or earlier
</dl>
</dl>
==Description==
==Description==
<p>
<p>
Line 27: Line 28:
<tr class="head"><th>Setting</th><th>Meaning</th></tr>
<tr class="head"><th>Setting</th><th>Meaning</th></tr>


<tr><th align="right"><var>X'00'</var></th><td>No scheduler overhead tracking, no forced offload. This is the default.</td></tr>
<tr><th align="right"><var>X'00'</var></th>
<td>No scheduler overhead tracking, no forced offload. This is the default.</td></tr>


<tr><th align="right"><var>X'01'</var></th><td>Maintain MAINTASK scheduler overhead.</td></tr>
<tr><th align="right"><var>X'01'</var></th>
<td>Maintain MAINTASK scheduler overhead.</td></tr>


<tr><th align="right"><var>X'02'</var></th><td>Do not allow the maintask to steal (run) work intended to run on an MP subtask. This parameter only has an effect if MP subtasks are defined and active ([[NMPSUBS parameter]] and [[AMPSUBS parameter]]). Setting this bit might cause increased CPU overhead because of the maintask going idle and then having to be redispatched. However, it might increase maintask responsiveness and provide somewhat better offload to MP subtasks. The maintask will always run maintask-only work before stealing any MP subtask work if this bit is not set.</td></tr>
<tr><th align="right"><var>X'02'</var></th>
<td>Do not allow the maintask to steal (run) work intended to run on a MP subtask. This parameter only has an effect if MP subtasks are defined and active (<var>[[NMPSUBS parameter|NMPSUBS]]</var> and <var>[[AMPSUBS parameter|AMPSUBS]]</var> parameters).  
<p>
Setting this bit might cause increased CPU overhead because of the maintask going idle and then having to be redispatched. However, it might increase maintask responsiveness and provide somewhat better offload to MP subtasks. The maintask always runs maintask-only work before stealing any MP subtask work if this bit is not set.</p></td></tr>


<tr><th align="right"><var>X'04'</var></th><td>Defer page releases until server swap.</td></tr>
<tr><th align="right"><var>X'04'</var></th>
<td>Defer page releases until server swap.</td></tr>


<tr><th align="right"><var>X'08'</var></th><td>Do server I/O on MP subtask.
<tr><th align="right"><var>X'08'</var></th>
<p><b>Note:</b> As of version 7.6 of Model 204, this setting is disabled (has no effect).</p></td></tr>
<td>Do server I/O on MP subtask.
<p>
<b>Note:</b> As of version 7.6 of Model 204, this setting is disabled (has no effect).</p></td></tr>


<tr><th align="right"><var>X'10'</var></th><td>In CSLICE, check maximum values even if there is an SWAIT.</td></tr>
<tr><th align="right"><var>X'10'</var></th>
<td>In CSLICE, check maximum values even if there is an SWAIT.</td></tr>


<tr><th align="right"><var>X'20'</var></th><td>Do not allow the maintask to steal (run) work intended to run on an zIIP SRB. This parameter only has an effect if zIIP SRBs are defined and active ([[NMPSUBZ parameter]] and [[AMPSUBZ parameter]]). Setting this bit might cause increased CPU overhead because of the maintask going idle and then having to be redispatched. However, it might increase maintask responsiveness and provide somewhat better offload to zIIP SRBs. The maintask will always run maintask-only work and MP subtask-only work before stealing any zIIP SRB work if this bit is not set.</td></tr>
<tr><th align="right"><var>X'20'</var></th>
<td>Do not allow the maintask to steal (run) work intended to run on a zIIP SRB. This parameter only has an effect if zIIP SRBs are defined and active (<var>[[NMPSUBZ parameter|NMPSUBZ]]</var> and <var>[[AMPSUBZ parameter|AMPSUBZ]]</var> parameters).  
<p>
Setting this bit might cause increased CPU overhead because of the maintask going idle and then having to be redispatched. However, it might increase maintask responsiveness and provide somewhat better offload to zIIP SRBs. The maintask always runs maintask-only work and MP subtask-only work before stealing any zIIP SRB work if this bit is not set.</p></td></tr>


<tr><th align="right"><var>X'40'</var></th><td>Do not allow the MP subtasks to steal (run) work intended to run on an zIIP SRB. This parameter only has an effect if both MP subtasks ([[NMPSUBZ parameter]] and [[AMPSUBZ parameter]]) and zIIP SRBs are defined and active ([[NMPSUBZ parameter]] and [[AMPSUBZ parameter]]). Setting this bit means that the MP subtasks can't pick up some of the CPU load if all zIIP SRBs are saturated. However, under Model 204 7.4 and 7.5 setting this bit would probably provide better zIIP utilization if there are MP subtasks also available. Under Model 204 7.6, even if this bit is not set, MP subtasks will only steal work from zIIP SRBs if those SRBs seem unable to keep up with the workload. As such, it is probably a bad idea to set this bit in Model 204 7.6 and later.   
<tr><th align="right"><var>X'40'</var></th>
</td></tr>
<td>Do not allow the MP subtasks to steal (run) work intended to run on a zIIP SRB. This parameter only has an effect if both MP subtasks (<var>NMPSUBS</var> and <var>AMPSUBS</var> parameters) and zIIP SRBs are defined and active (<var>NMPSUBZ</var> and <var>AMPSUBZ</var> parameters).  
<p>
Setting this bit means that the MP subtasks can't pick up some of the CPU load if all zIIP SRBs are saturated. However, under Model 204 7.4 and 7.5 setting this bit would probably provide better zIIP utilization if there are MP subtasks also available. Under Model 204 7.6, even if this bit is not set, MP subtasks only steal work from zIIP SRBs if those SRBs seem unable to keep up with the workload. As such, setting this bit in Model 204 7.6 and later <b><i>is not recommended</i></b></p></td></tr>


<tr><th align="right"><var>X'80'</var></th>
<tr><th align="right"><var>X'80'</var></th>
<td>Allow server swapping to be offloaded to zIIP processors. If you have <code>SCHDOPT=80</code> set, then you probably want to set <code>[[SCHDOPT1 parameter|SCHDOPT1]]=01</code>.
<td>Allow server swapping to be offloaded to zIIP processors. If you have <code>SCHDOPT=80</code> set, then you probably want to set <code>SCHDOPT1=01</code>.
<p><b>Note:</b> As of version 7.6 of Model 204, SCHDOPT X'80' and SCHDOPT1 X'01' are disabled (have no effect).</p>
<p><b>Note:</b> As of version 7.6 of Model 204, the <var>SCHDOPT</var> X'80' bit and the <var>[[SCHDOPT1 parameter|SCHDOPT1]]</var> X'01' bit are disabled (have no effect).</p>
<p>
<p>
The X'80' setting is only valid when CCASERVR is in memory (servers swapped into memory). If you set <code>SCHDOPT=X'80'</code> when CCASERVR is not in memory, the X'80' setting is reset and message 2914 is issued:</p>
The X'80' setting is only valid when CCASERVR is in memory (servers swapped into memory). If you set <code>SCHDOPT=X'80'</code> when CCASERVR is not in memory, the X'80' setting is reset and message 2914 is issued:</p>

Revision as of 15:30, 16 March 2015

Scheduler options

Summary

Default value
0
Parameter type
System
Where set
On User 0's parameter line or reset by system manager.
Related products
All
Introduced
Model 204 V6.1 or earlier

Description

Control of the main task scheduler operation and accounting.

  • Setting X'10' is relevant to all sites.
  • All other settings are relevant only to sites running MP/204.

Valid settings of SCHDOPT, which can be summed, are as follows:

SettingMeaning
X'00' No scheduler overhead tracking, no forced offload. This is the default.
X'01' Maintain MAINTASK scheduler overhead.
X'02' Do not allow the maintask to steal (run) work intended to run on a MP subtask. This parameter only has an effect if MP subtasks are defined and active (NMPSUBS and AMPSUBS parameters).

Setting this bit might cause increased CPU overhead because of the maintask going idle and then having to be redispatched. However, it might increase maintask responsiveness and provide somewhat better offload to MP subtasks. The maintask always runs maintask-only work before stealing any MP subtask work if this bit is not set.

X'04' Defer page releases until server swap.
X'08' Do server I/O on MP subtask.

Note: As of version 7.6 of Model 204, this setting is disabled (has no effect).

X'10' In CSLICE, check maximum values even if there is an SWAIT.
X'20' Do not allow the maintask to steal (run) work intended to run on a zIIP SRB. This parameter only has an effect if zIIP SRBs are defined and active (NMPSUBZ and AMPSUBZ parameters).

Setting this bit might cause increased CPU overhead because of the maintask going idle and then having to be redispatched. However, it might increase maintask responsiveness and provide somewhat better offload to zIIP SRBs. The maintask always runs maintask-only work and MP subtask-only work before stealing any zIIP SRB work if this bit is not set.

X'40' Do not allow the MP subtasks to steal (run) work intended to run on a zIIP SRB. This parameter only has an effect if both MP subtasks (NMPSUBS and AMPSUBS parameters) and zIIP SRBs are defined and active (NMPSUBZ and AMPSUBZ parameters).

Setting this bit means that the MP subtasks can't pick up some of the CPU load if all zIIP SRBs are saturated. However, under Model 204 7.4 and 7.5 setting this bit would probably provide better zIIP utilization if there are MP subtasks also available. Under Model 204 7.6, even if this bit is not set, MP subtasks only steal work from zIIP SRBs if those SRBs seem unable to keep up with the workload. As such, setting this bit in Model 204 7.6 and later is not recommended.

X'80' Allow server swapping to be offloaded to zIIP processors. If you have SCHDOPT=80 set, then you probably want to set SCHDOPT1=01.

Note: As of version 7.6 of Model 204, the SCHDOPT X'80' bit and the SCHDOPT1 X'01' bit are disabled (have no effect).

The X'80' setting is only valid when CCASERVR is in memory (servers swapped into memory). If you set SCHDOPT=X'80' when CCASERVR is not in memory, the X'80' setting is reset and message 2914 is issued:

SCHDOPT INDICATION OF SERVER SWAPPING DONE BY ZIIP IS ONLY VALID WHEN CCASERVR IS IN MEMORY

Initialization then continues.