On Wed, 23 Oct 2019 18:23:31 +0000, Seymour J Metz wrote: >The Dispatcher has been using timers for decades. What interrupts your >code is an external event from a timer or from a SIGP on another CPU.
>If you're running with appropriate goals, don't try to second guess WLM. I believe the OP mentioned he received complaints that his task was hogging the CPU. WLM does not cover every situation. I'm guessing that changing the WLM goals did not solve the problem since that would be the first thing most people consider when this situation occurs. The most obvious situation is with multiple active TCB's in an address space because WLM does not directly deal with TCB priority. I think the op should look at the CHAP macro and implementing WLM enclaves. CHAP would be simpler but I suspect that enclaves will probably be the more appropriate solution. CALLDISP probably won't be necessary but that really depends upon the situation. Jon. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
