I was lead to understand that 'reporting period' for R4A* MSU's was 30 minutes or so. For a single CEC, your bill would be based on the highest sum of the R4A's for all LPAR's in a 30 minute period for that CEC.
Generally, IBM software is attached to a single CPU serial number. In my case, I submit two separate sub capacity reports, one for each of my qualifying CEC's. I don't see the invoices very often, but I believe we get one for each CEC. It may be important to note that some products are charged on actual product usage on the target LPAR, while some (DB2, for example) charge for total MSU's across all LPAR's on that CEC (no matter if DB2 is installed on a given LAPR or not). I'm not clear on the details, but the point is that different products may charge differently. That difference may extend to other, more complex kinds of pricing based on aggregation across CEC's. Can't speak to that. I have heard some complain that IBM's calculations are not always 100% accurate and have found it worthwhile to get independent verification. *R4A = Rolling four hour average HTH and good luck. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Gammage Sent: Wednesday, May 18, 2011 5:44 AM To: [email protected] Subject: WLC and 4HRA across CEC's ********* Cross posted to IBM-Main and LPAR-Pricing ************ Folks, I thought I had a good understanding of VWLC and how chargeable MSU's were calculated, but have recently been re-educated and it concerned me a little so I thought I'd check others understanding. The WLC announcements (linked below) and ICA attachment for WLC which include a definition of the chargeable MSU's for a product (known as Product LPAR Utilisation Capacity) as "the highest number of MSUs utilized by the by the combined LPARs in which a VWLC product runs concurrently during a reporting period. The number of MSUs is based on a rolling 4 hour average utilization." The emphasis for me was on the phrase "the combined LPARs in which a VWLC product runs concurrently", which I had interpreted to mean ALL LPAR's in which the product ran within a qualifying aggregated environment. The SCRT pages ( http://www-03.ibm.com/systems/z/resources/swprice/subcap/technology.html) support this stating "SCRT only looks at simultaneous peaks for a product running in multiple LPARs". In practice however this is not how it is applied - the Product LPAR Utilisation Capacity is calculated per CEC and then aggregated - which means it is not simultaneous peaks across all CEC's, it is simultaneous peaks within a CEC. ...snip NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- 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
