In IBM System z9 (and successor) mainframes, the System z Integrated Information Processor (zIIP) is a special purpose processor. It was initially introduced to relieve the general mainframe central processors (CPs) of specific DB2 processing loads, but currently is used to offload other z/OS workloads as described below. The idea originated with previous special purpose processors, the zAAP and IFL, which offload Java and Linux processing, respectively. A System z PU (processor unit) is "characterized" as one of these processor types, or as a CP (Central Processor), or SAP (Service Assist Processor). These processors do not contain microcode or hardware features that accelerate their designated workloads. Instead, by relieving the general CP of particular workloads, they often lead to a higher workload throughput at reduced license fees.
DB2 for z/OS V8 was the first application to exploit the zIIP, but now there are several IBM and non-IBM products and technologies that exploit zIIP. The zIIP requires a System z9 or newer mainframe. The z/OS 1.8 and DB2 9 for z/OS support zIIPs. IBM also offers PTFs for z/OS 1.6, z/OS 1.7, and DB2 V8 to enable zIIP usage. (DB2 9 for z/OS is the first release of DB2 that has support built in.)
IBM publicly disclosed information about zIIP technology on January 24, 2006. The zIIP hardware (i.e. microcode, as the processors hardware does not currently differ from general purpose CPUs) became generally available in May, 2006. The z/OS and DB2 PTFs to take advantage of the zIIP hardware became generally available in late June, 2006.
zIIPs add lower cost capacity for four types of DB2 work:
- Remote DRDA access via TCP/IP. This category includes JDBC and ODBC access to DB2, including access across LPARs via Hipersockets, such as Linux on System z9. The exception is access to DB2 V8 stored procedures, which redirect a small portion of the work. DB2 9 native remote SQL procedures do use the zIIP.
- Parallel query operations. DB2 9 can increase the amount of parallel processing and thus use the zIIP more.
- XML parsing in DB2 can use zIIP processors or zAAP processors
- Certain DB2 utilities processing.
Support for zIIPs
Although DB2 UDB for z/OS was the first product released that exploited zIIP processors, it is not limited to just DB2 or IBM products. The zIIP speciality CPU can also be used for IPSec processing in TCP/IP, certain general XML processing, and IBM's Scalable Architecture for Financial Reporting. In August, 2007, Shadow, a mainframe middleware product, now owned by Rocket Software, introduced the first zIIP eligible integration for environments other than DB2, expanding the benefit of specialty engines to include Adabas, CICS, IMS, IDMS and VSAM. Other third-party independent software vendors (ISVs) have introduced support for execution of their products on zIIPs.
For example; the CA NetMaster Network Management for TCP/IP product can run both its main task and packet analyzer subtask on a zIIP. Rocket Software claims that their Shadow server will allow 99% of the integration processing, such as SQL to non-relational data queries and Web services/SOA workloads, to be zIIP eligible and run outside of the General Purpose Processor. Ivory Server for z/OS from GT Software, Inc. provides zIIP support for XML parsing, XML payload construction and data conversion processing. Additionally Ivory Server supports the zAAP processor using the optional IBM z/OS XML Services and the IFL processor with zLinux. Ivory Server and Ivory Studio (the Ivory IDE) provide options that allow clients to manage the workload offloaded to the zIIP Specialty CPU from the GP CPU.
Commercial software developers, subject to certain qualification rules, may obtain technical details from IBM on how to take advantage of zIIP under a Non-Disclosure Agreement.
The IBM z13 merges the zAAP functionality with zIIPs so that zAAP-eligible work now uses zIIP instead. Furthermore, IFL and zIIP processors on the IBM z13 have simultaneous multithreading (SMT) capability.
- "z Systems Application Assist Processor (zAAP)". IBM. Retrieved 2015-08-05.