Overloading zIIPs consists of 2 phases. 1. work is getting queued for the zIIP, delaying the work. 2. when queuing is getting to large, the CPs are asked to assist in processing zIIP work (if allowed by IEAOPT parameters)
The first phase is not reported externally. The second phase is visible, because this CPU is reported as zIIP-eligible CPU. This CPU will also be charged as license CP MSUs. So when you have zIIP-elibible CPU, you know you have problems of the second category and you already had the problems of the first category before. Some DB2 problems due to zIIP work queuing were resolved by disabling the zIIP, at the cost of CP MSUs of course. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Hunkeler Sent: 19 July, 2016 19:51 To: [email protected] Subject: AW: Re: DFsort and zIIP >You are correct that the ZIIP dispatcher is not as sophisticated as the >regular dispatcher. I dare to contradict, not intending to question you expertise. It is my understanding that there is only one dispatcher in MVS. It handles work on the CP WUQ as well as work on the zIIP WUQ. The reason for the wait time mechanism is explained in Init&Tuning Ref, IEAOPTxx. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
