As was mentioned, ABSMSUCapping may be useful in that you can limit the entire group to a specific number of MSUs. I.E. if you defined the group of 4 LPARs in a capacity group at 24 MSUs (or whatever) and enabled ABSMSUCapping on all of them, all 4 LPARs would be capped (in total) at that 24 MSUs.
The Absolute CP Capping can work too, but you can't set the limit across the 4 LPARs, so they can't borrow capacity from each other. I.E. if you want the limit to be a combined 24 MSUs but you want each to be able to consume up to 24 MSUs, then a group cap with Absolute MSU Capping is the way to go. If you want to limit individual workloads within the LPARs, then WLM resource groups can do that for you. That's at a service class by service class basis and most often are specified by SU/s (not the same as MSUs). So assign the SAS work to a specific SC (BATHOGS?) and make sure that SC has a resource group that limits how much CPU the work can consume. Scott Chapman ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
