Natural for Db2 for zIIP (NDZ) complements Natural for Db2 (NDB) Database Management Interface by adding the ability to run Db2 workloads on IBM System z Integrated Information Processors (zIIP).
Natural for Db2 for zIIP (NDZ) makes use of the zIIP capabilities by accessing Db2 through a remote DRDA protocol, instead of using conventional Db2 local attachments. Local calls to Db2 are not zIIP eligible, therefore accessing Db2 using the DRDA protocol enables Natural programs to run continuously on zIIP processors. Some workloads, e.g. I/O calls, are not zIIP eligible. zIIP ineligible workloads require the respective Natural programs to run temporarily on the general processors.
Java workloads running on z/OS are zIIP eligible, therefore Natural for Db2 for zIIP (NDZ) uses Java and Java Database Connectivity (JDBC) to access Db2 using the DRDA protocol. The following diagrams show an approximate comparison of the workload distribution when accessing Db2 using only NDB and when using NDB and NDZ at the same time.
Diagram X - Natural for Db2 (NDB) only:
Diagram Y - zIIP utilization - Natural for Db2 (NDB) with Natural for Db2 for zIIP (NDZ)
To benefit from Natural for Db2 for zIIP (NDZ) capabilities, you must ensure that enough System z Integrated Information Processors (zIIP) are available in the target environment. Running NDZ workloads without the required zIIP capacity can lead to increased general processor utilization, due to zIIP eligible workload running on general processors. Please refer to the section Honor Priority in the manual z/OS MVS Planning: Workload Management.
Natural for Db2 for zIIP (NDZ) runs on its own address space. An instance of the NDZ Server is capable to handle requests from multiple Natural batch jobs.
