Re: AW: Re: Would HiperDispatch likely delay heavy multitasking job?

2016-09-30 Thread Horst Sinram
Peter, also within the same processor class (here CP) affinity nodes may help each other - see the IEAOPTxx CCCAWMT parameter. Therefore, the number of (unparked) logicals processors on a given affinity node does not necessarily limit the number of concurrently disptached work units of an

Re: AW: Re: Would HiperDispatch likely delay heavy multitasking job?

2016-09-29 Thread Graham Harris
Something to be aware of when looking at CPU delays being reported by RMFIII, is that in multi-tasked asids, if ANY of the subtasks is found to be in CPU wait when RMFII does it sampling sweep (once per second), then that sampled second will have a 'CPU wait' associated with it, applying to that

AW: Re: AW: Re: Would HiperDispatch likely delay heavy multitasking job?

2016-09-29 Thread Peter Hunkeler
>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

Re: AW: Re: Would HiperDispatch likely delay heavy multitasking job?

2016-09-29 Thread Greg Dyck
On 9/29/2016 10:17 AM, Peter Hunkeler wrote: So there should be enough spare capacity for the system (LPAR) to to use. But it does not. The 7 vertical low CPs are mostly parked or unparked for only a few percent. I wonder why MVS is not using more CPs and more Capacity for that job. You