content_image/983802.jpg
Each input queue is a unique type of workload, and has unique service and processing requirements. The IWQ function allows z/OS to preassign the appropriate processing resources for each input queue. This approach allows multiple concurrent z/OS processing threads to process each unique input queue (workload), which avoids traditional resource contention. 

IWQ reduces the conventional z/OS processing that is required to identify and separate unique workloads. This advantage results in improved overall system performance and scalability. 

A primary objective of IWQ is to provide improved performance for business-critical interactive workloads by reducing contention that is created by other types of workloads. In a heavily mixed workload environment, this “off the wire” network traffic separation is provided by OSA-Express6S, OSA-Express5S, or OSA-Express4S$^{9}$ features that are defined as CHPID type OSD. OSA IWQ is shown in Figure 7-5. 

<img src='content_image/983802.jpg'>

The following types of z/OS workloads are identified and assigned to unique input queues: 

GLYPH<SM590000> z/OS Sysplex Distributor traffic: Network traffic that is associated with a distributed virtual Internet Protocol address (VIPA) is assigned to a unique input queue. This configuration allows the Sysplex Distributor traffic to be immediately distributed to the target host. 

GLYPH<SM590000> z/OS bulk data traffic: Network traffic that is dynamically associated with a streaming (bulk data) TCP connection is assigned to a unique input queue. This configuration allows the bulk data processing to be assigned the appropriate resources and isolated from critical interactive workloads. 

GLYPH<SM590000> EE (Enterprise Extender / SNA traffic): IWQ for the OSA-Express features is enhanced to differentiate and separate inbound Enterprise Extender traffic to a dedicated input queue. 

The supported operating systems are listed in Table 7-8 on page 255 and Table 7-9 on page 257. 

