Your documentation doesn't say what you say it does. It explicitly indicates that service class periods are associated with a dispatching priority and does not say anything about differences within a service class. In short, there is nothing to indicate that individual address spaces would be subject to variations in dispatching priorities within a service class period.
Adam -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edgington, Jerry Sent: Thursday, April 5, 2018 9:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1 .ieaw200/iea3w201112.htm Dispatching Priority SRM defines dispatching priority for service class periods. All address spaces in a service class period have the same base dispatching priority. Multiple service class periods may have the same base dispatching priority. After a dispatching priority change, service class periods may be remapped to different dispatching priorities such that there is an unoccupied priority between each occupied priority. This process is referred to as priority unbunching. The dispatching priority is recorded in the subtype 2 records. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gerhard Adam Sent: Thursday, April 05, 2018 12:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority I beg to differ, but do you have documentation that supports what you say? I have looked at a lot of type 99 records and WLM most certainly assigns the DP. Sent from my iPhone > On Apr 5, 2018, at 8:44 AM, Edgington, Jerry <jerry.edging...@westernsouthernlife.com> wrote: > > WLM uses the configuration to determine what SRVCLASS a specific piece of work should be assigned upon initial job entry. After that, WLM will recommend to SRM how to adjust the dispatching priorities, based on information provided in WLM definitions. > > WLM doesn't make changes to dispatching priorities, only SRM does that. Also, SRVCLASS doesn't equal a specific dispatching priority. > > SRM still works like it always has and WLM is way of defining "business rules" to workload versus assigning specific dispatching priorities to the workload. > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gerhard Adam > Sent: Thursday, April 05, 2018 11:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > 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:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Martin Packer > Sent: Thursday, April 5, 2018 7:14 AM > To: IBM-MAIN@LISTSERV.UA.EDU > 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
