>You have to dig into queuing theory, arrival rate, arrival pattern, and service duration of the work to understand why RMF is reporting CPU delay samples yet WLM does not unpark processors to run it.
I think I have an idea of this even without knowing the theories. >HiperDispatch is a balancing act between providing the best processor efficiency vs dispatch responsiveness. If the average CPU utilization of the 3 CPUs is not relatively high *and* the delay for work to get dispatched is small, such that the cost/delay of using the vertical low CPUs is believed to not be worth it, then the vertical low CPUs will not be unparked. After reading and thinking about HiperDispatch in depth, this was kind of my conclusion and the reason I started this thread. I still have the pre HiperDipatch way of how dispatching worked in mind and had to lear it is all completely different now. That is why I started to doubt higher priority would help. I think now it would not or not much. As always with questions about complex things where the questioner has limited knowledge, it is difficult to find out what exactly to ask. >You can always try turning HiperDispatch off and see what happens. Not really. This is a rather large environment and it is only very few jobs that show this symptom. I doubt I will be allowd to switch it off, and more yet, I trust, overall, it would hurt than not. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
