I think you have it right, the RG cap should be enforced, based on the goal & importance for the service class and system scope -- From the Knowledge Base:
If work in a resource group is consuming more resources than the specified maximum capacity, the system caps the associated work accordingly to slow down the rate of resource consumption. The system may use several mechanisms to slow down the rate of resource consumption, including swapping the address spaces, changing its dispatching priority, and capping the amount of service that can be consumed. Reporting information reflects that the service class may not be achieving its goals because of the resource group capping. By setting a minimum processing capacity, you create an overriding mechanism to circumvent the normal rules of importance. If the work in a resource group is not meeting its goals, then workload management will attempt to provide the defined minimum amount of CPU resource to that resource group. Minimum and maximum capacity has a system scope, that is, WLM ensures that the limits are met on each system within the sysplex. HTH, Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tracy Adams Sent: Friday, May 13, 2016 12:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Another WLM question So at what point with the service class get restricted based on the resource group settings? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
