 If that particular CPU is busy, HiperDispatch will, at first, wait for it to finish its other task, even if another less favorable CPU is idle.However, there are limitations to how patient HiperDispatch will be, as governed by Workload Manager goals.If z/OS Workload Manager senses that there's a risk the pending task will miss its service level (responding within a certain number of milliseconds to a user request for example), Workload Manager and HiperDispatch will send the task over to an idle CPU for processing, even if that CPU must fetch data from slower main memory.