NMPSUBZ parameter: Difference between revisions
m (more conversion cleanup) |
m (mention XMEMOPT) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 18: | Line 18: | ||
<var class="product">Model 204</var> can run a portion of workload on IBM System z Integrated Information Processor (zIIP) engines. The only unit of work that z/OS schedules to run on a zIIP is the enclave Service Request Block (SRB). An enclave is a collection of resources, such as address spaces, TCBs, and SRBs, that are controlled by Workload Manager (WLM) as an entity. Therefore, an enclave SRB is a part of an enclave. </p> | <var class="product">Model 204</var> can run a portion of workload on IBM System z Integrated Information Processor (zIIP) engines. The only unit of work that z/OS schedules to run on a zIIP is the enclave Service Request Block (SRB). An enclave is a collection of resources, such as address spaces, TCBs, and SRBs, that are controlled by Workload Manager (WLM) as an entity. Therefore, an enclave SRB is a part of an enclave. </p> | ||
<p> | <p> | ||
<var class="product">Model 204</var> creates an enclave SRB with the same dispatching priorities as the | <var class="product">Model 204</var> creates an enclave SRB with the same dispatching priorities as the maintask. <var class="product">Model 204</var> uses an enclave SRB, in this case zIIP, in the same way as an MP subtask. The term zIIP subtask is the equivalent of enclave SRB. </p> | ||
<p> | <p> | ||
The <var>NMPSUBZ</var> parameter initiates a zIIP infrastructure. If <var>NMPSUBZ</var> is not zero, a zIIP-related infrastructure is created, and <var>NMPSUBZ</var> specifies the number of zIIP subtasks attached during initialization (enclave SRBs). </p> | |||
The <var>NMPSUBZ</var> parameter initiates a zIIP infrastructure. If <var>NMPSUBZ</var> is not zero, a zIIP-related infrastructure is created.</p> | |||
<p> | <p> | ||
As many as <var>NMPSUBZ</var> defined special subtasks (named <b>zIIP tasks</b>) are attached. The zIIP tasks are real tasks as opposed to <i>zIIP subtasks</i>, which are enclave SRBs. The zIIP tasks are used only for exception handling and enclave SRB creation and deletion. Each active zIIP task creates an enclave SRB at initialization.</p> | As many as <var>NMPSUBZ</var> defined special subtasks (named <b>zIIP tasks</b>) are attached. The zIIP tasks are real tasks as opposed to <i>zIIP subtasks</i>, which are enclave SRBs. The zIIP tasks are used only for exception handling and enclave SRB creation and deletion. Each active zIIP task creates an enclave SRB at initialization.</p> | ||
<p class="note"><b>Note:</b> MP subtasks and zIIP subtasks may be used together. Therefore, <var>[[AMPSUBS parameter|AMPSUBS]]</var>, <var>[[NMPSUBS parameter|NMPSUBS]]</var>, <var>[[AMPSUBZ parameter|AMPSUBZ]]</var>, and <var>NMPSUBZ</var> may all be greater than zero.</p> | <p class="note"><b>Note:</b> MP subtasks and zIIP subtasks may be used together. Therefore, <var>[[AMPSUBS parameter|AMPSUBS]]</var>, <var>[[NMPSUBS parameter|NMPSUBS]]</var>, <var>[[AMPSUBZ parameter|AMPSUBZ]]</var>, and <var>NMPSUBZ</var> may all be greater than zero.</p> | ||
<p> | |||
If you set <var>NMPSUBZ</var> greater than 0, the X'02' bit of the <var>[[XMEMOPT parameter|XMEMOPT]]</var> parameter (the default), must also be set. </p> | |||
<p> | <p> | ||
For more information about zIIP processing, refer to [[Performance monitoring and tuning#Offloading Model 204 work to zIIP processors|Offloading Model 204 work to zIIP processors]].</p> | For more information about zIIP processing, refer to [[Performance monitoring and tuning#Offloading Model 204 work to zIIP processors|Offloading Model 204 work to zIIP processors]].</p> | ||
Latest revision as of 17:54, 27 February 2017
Number of zIIP eligible subtasks
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- On User 0's parameter line
- Related products
- All
- Introduced
- Model 204 V7.4
Description
Model 204 can run a portion of workload on IBM System z Integrated Information Processor (zIIP) engines. The only unit of work that z/OS schedules to run on a zIIP is the enclave Service Request Block (SRB). An enclave is a collection of resources, such as address spaces, TCBs, and SRBs, that are controlled by Workload Manager (WLM) as an entity. Therefore, an enclave SRB is a part of an enclave.
Model 204 creates an enclave SRB with the same dispatching priorities as the maintask. Model 204 uses an enclave SRB, in this case zIIP, in the same way as an MP subtask. The term zIIP subtask is the equivalent of enclave SRB.
The NMPSUBZ parameter initiates a zIIP infrastructure. If NMPSUBZ is not zero, a zIIP-related infrastructure is created, and NMPSUBZ specifies the number of zIIP subtasks attached during initialization (enclave SRBs).
As many as NMPSUBZ defined special subtasks (named zIIP tasks) are attached. The zIIP tasks are real tasks as opposed to zIIP subtasks, which are enclave SRBs. The zIIP tasks are used only for exception handling and enclave SRB creation and deletion. Each active zIIP task creates an enclave SRB at initialization.
Note: MP subtasks and zIIP subtasks may be used together. Therefore, AMPSUBS, NMPSUBS, AMPSUBZ, and NMPSUBZ may all be greater than zero.
If you set NMPSUBZ greater than 0, the X'02' bit of the XMEMOPT parameter (the default), must also be set.
For more information about zIIP processing, refer to Offloading Model 204 work to zIIP processors.