Sure, if you want to avoid capping, RG's are the method to limit hungry workloads.
Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Hunkeler Sent: 22 July, 2016 9:51 To: [email protected] Subject: AW: Re: Resource Group Limits as a cost containment method? >I am not quite sure what you are aiming at. Speaking for our environment and our paint points, only. It is true that the cost is under conrtol with Defined Capacity or Group Capacity Limit set. The problem is the huge amount of capacity that you might loose once your system is capping. If this happend during the batch window, that's under control and not really an issue. However, the online workload does not cope well with capping, this is the period we want to avoid capping as best as we can. Proper Service Class make sure important work gets resources first. But if there is no online such as during the batch window, batch takes it all and thereby is driving the R4HA towards the Defined Capacits or Group Capacity limits, leaving no spare for the online window. Service Classes cannot limit resource access when spare resources are available. Resource Groups can, this is what they have been invented for. So at critical times such as month ends, we're limiting what batch can take, effectively a kind of capping within a z/OS instance but only for certain types of workload, i.e. batch. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
