Blog
DB2utor

Categories

February 04, 2014

Additional Processes Authorized for zIIP in DB2 11

As I read this Willie Favero post about zIIP capacity, I got to wondering about additional zIIP processing capabilities in DB2 11.

My search began with this IBM summary of what's new in DB2 11. I found only one reference to zIIP:

            Cleanup of pseudo deleted index entries as part of DB2 system task cleanup is   now eligible for zIIP processing.

Then I remembered this IDUG editorial committee-produced white paper(registration required), which includes a section on zIIP processing in DB2 11.

This section features a list of the processes that are enabled to run on zIIP:

  • Asynchronous processing that's executed under enclave service request blocks (SRBs) and "charged" for CPU consumption purposes to an IBM DB2 address space (rather than to user applications), with the exception of P-lock negotiation processing. Such zIIP eligible processing includes:
    • Cleanup of pseudo deleted index entries as part of DB2 system task cleanup1
    • Cleanup of XML multi-version documents (available in DB2 10 for z/OS via APAR PM 72526)
    • Log write and log read
  • DB2 base LOAD, REORG and REBUILD INDEX utility processing of inline statistics collection (up to 30 percent offload).
  • DB2 base processing of RUNSTATS utility Column Group Distribution statistics collection (up to 80 percent offload).
  • DB2 base LOAD utility index management processing when running LOAD REPLACE.

Then I checked out the IBM Knowledge Center. By searching on the term, “cleanup of XML multi-version documents," I found this list of "Authorized uses for System z Integrated Information Processors (zIIP)":

  • SQL request workloads that use DRDA to access DB2 for z/OS over TCP/IP connections
  • Parallel query child processes
  • Utility processes
  • XML processing
  • Asynchronous SRB processing

Since substantial cost savings can be achieved when customers can use zIIP in place of the general processor, expect to see more processes authorized for zIIP in future DB2 releases. And hopefully, IBM will make it easier for us to learn which processes are being authorized for zIIP.