Chauhan, Jasbir wrote:
One thing we found out the hard way was that the software charge for IBM
products, under soft cap setup, can really get skewed -- e.g.
-- say the charge for WAS is MSU based and it is active (runs) all day
-- also say ,on average, it uses 80 MSU
-- you then look at your SCRT at the end of the month and see WAS is
being charged at 100 MSU.. how on earth is that possible
Well, in our case we found that during the batch process, the CPU got
pegged at 100 MSU (once a month is all it takes).
You know what, just because WAS was active at the time the batch process
was chewing up CPU -- you wind up paying for the max use of CPU for WAS
too. All it takes is one CPU spike in any given month (SCRT reporting
window).
Don't confuse sub-capacity pricing with soft-capping!
The charges for sub-capacity pricing are based on the peak rolling
four-hour average for the month. With a soft-cap in place, WLM ensures
the rolling four-hour average for an LPAR -- or group of LPARs in the
case of an LPAR capacity group -- will not exceed the specified defined
capacity amount.
If you exceeded 80 MSU, it probably means that no defined capacity was
in place or it was set above 80 MSU.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
