<snip> > If the two parties are running in different address spaces then a > complaint could only be that the address space is consuming a lot of CPU > and that is exactly what WLM goals and priorities are for. Only true if you ignore mixed workload address spaces </snip>
Perhaps you did not read that my sentence started with an "if". Yes, specifically because of the "if", I am ignoring mixed workload address spaces. <snip> The OP has a known rogue TCB in a multi-tasking address space otherwise why did he ask the question. </snip> That was specifically not the case according to one post. The poster had a CPU-intensive process and was trying to be a responsible program. The question of how to deal with intra-address space priorities could be things such as CHAP and enclaves. And even then, a "rogue TCB" within an address space will not take more than its share of all tasks of that address space because, all other things being equal, ready tasks within in address space are dispatched in a round-robin fashion. A time slice is a time slice. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
