RCTLACS contains the current running average for the LPAR. Assuming a single LAPR, it is possible to monitor and adjust the cap by changing the WLM policy (V WLM,policyname). This requires at least 2 policies. 1 with no caps and 1 without caps. You may need another with tighter caps in order to force the value down.
If this is a multiple LPAR CEC you need to look at the value for all LPARS. I have use CA/OPS to do this. Dennis Roach, CISSP, PMP AIG IAM Access Administration – Consumer | Identy & Access Management 2929 Allen Parkway, America Building, 3rd Floor | Houston, TX 77019 Phone: 713-831-8799 [email protected] | www.aig.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tim Hare Sent: Thursday, July 21, 2016 9:59 AM To: [email protected] Subject: Resource Group Limits as a cost containment method? There's a system where their 4-hour rolling average maximum is always during their batch window, when they routinely reach their defined capacity limit, which in turn affects what they pay in a chargeback system. Because of scheduling dumbness (another story) they have several gaps in their batch window where nothing runs, giving some leeway for jobs to increase their elapsed time - not the usual thing you want to do, but bear with us. Would it be worth investigating setting a resource group limit for the batch service class(es) to hold the total 4HRA down as a cost-saving measure, or are resource group limits going to cause more trouble than they are worth? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
