>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
