vasanthz
Global Moderator
Joined: 28 Aug 2007
Posts: 1689
Location: Tiruppur, India
|
|
|
|
Just thought of sharing an year old article, but came across only today.
At first glace about IIPHONORPRIORITY option, it might be a no brainer to set it as NO.
IIPHONORPRIORITY is a parameter in the IEAOPTxx member of the z/OS data set called SYS1.PARMLIB. The value of the parameter can be set to NO or YES. Essentially, those two settings have the following meanings:
YES - Honor the priority of zIIP-eligible tasks (per the z/OS LPAR's workload manager policy), so that in the event that such a task is ready for dispatch and the LPAR's zIIP engines are busy, allow the task to be dispatched to a general-purpose engine so that wait-for-dispatch time for the task will not be too high.
NO - Regardless of the priority of zIIP-eligible tasks, limit the processing of such tasks to zIIP engines. If a zIIP-eligible task is ready for dispatch and the LPAR's zIIP engines are busy, require that the task wait until a zIIP engine becomes available.
But after reading more detail into it from this link -
robertsdb2blog.blogspot.com/2019/05/db2-for-zos-iiphonorpriority-and-ziip.html
when IIPHONORPRIORITY=NO is in effect, "Db2 does not allow system tasks to become eligible for zIIP processing." |
|
