On 2/17/2014 1:42 PM, Charles Mills wrote:
It would be an interesting exercise to try to figure out an estimated dollar cost for a million instructions executed per day, using an assumed typical installation and an assumed typical mix of IBM and non-IBM software
Sub-capacity pricing for IBM MLC software products is based on peak, monthly, rolling four-hour average utilization of the LPARs in which the software products ran at any time that month. The measurement granularity is just one MSU (approximately 4-6 MIPS depending on CPU type/model).
If a program generally runs off-shift (e.g., nightly batch window) then increasing or decreasing by one MSU probably will have no effect on billing. But, if the program generally runs during peak shift (e.g., 2-4pm), then increasing or decreasing by one MSU could have a _tremendous_ impact on monthly software charges; the price for every software product in those LPARs goes up!
Things are even worse for IBM IPLA-style products. Exceeding entitled capacity by even just one MSU translates into an immediate order for additional capacity. Besides paying for the upgrade on all of the IPLA licensed products, the annual S&S contracts go up as well...
Bottom line: every developer should try to write code that runs as fast as possible. A single MSU increase at just the wrong time could translate into huge $$.
-- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
