I don't see the relevance of enclaves or anything else in this. It is the service class period that matters.
So, if I assigned DB2, enclaves, TSO, and batch to the same service class, they should still all have the same dispatching priority. Workload Manager doesn't care what type of work is in the service class, since only the data related to the service class can be examined. I would expect to see different dispatching priorities for the small consumer, or an address space that has been temporarily promoted, but that should only be short-term. I would also expect to see different dispatching priorities for the MTTW usage in discretionary. However, I still don't see how a goal-managed service class period can have different dispatching priorities. It would render the goal meaningless. Adam -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Martin Packer Sent: Thursday, April 5, 2018 7:14 AM To: [email protected] Subject: Re: WLM and Dispatching Priority There is also DIST and DBM1 in there. The action will be heavily geared towards DBM1. (DIST has work in it mostly on Independent Enclaves so relatively little of the work therein is at the address space's DP.) Cheers, Martin Martin Packer zChampion, Systems Investigator & Performance Troubleshooter, IBM ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
