>Thanks Tim and Kees for your clarifications. > >The 'hour' doesn't mean anything then.. ? from the MSU definition (MSUs is an >hourly measure (A million service units (MSU) is a measurement >of the amount >of processing work a computer can perform in one hour) > >For the vendor bit... >Assuming my machine's capacity is x MSUs and a vendor's contract specifies a >usage limit of y MSUs (where y is slightly less than x), >One of these 2 things must be true - a) the vendor is probably rounding down a >bit, from the machine's capacity b) vendor has some mechanism >to check and >arrest usage real-time. > >- Vignesh >Mainframe Infrastructure
Actually, I don't expect the vendor cares. They almost certainly won't arrest usage real-time, they are more likely to be interested in you exceeding the contractual limit in order to be able to bill you additional charges. It's up to YOU (in most cases) to monitor the MSU usage (in whatever form the vendor states) and take action to avoid exceeding the contractual limit. As Tim mentioned you can use a method of capping (soft/hard, individual lpar/group etc) to prevent the limit being reached. Geoff Rousell IBM Z Client Technical Specialist, UK ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
