Tuesday, May 6, 2014

IBM Mobile Workload Pricing for z/OS

Today IBM officially announced the pricing mechanism it already revealed during the April 8 z Anniversary event : 'IBM Mobile Workload Pricing for z/OS can reduce the cost of growth for mobile transactions (ZP14-0280)'. Before giving you the details I'd like to share this video about the First National Bank of South Africa because it illustrates so clearly what mobile is all about.

Combining mobile and mainframe is answering some real concerns or requirements of companies and people using the applications. Mobile is a rapidly growing market generating lots of transactions on lots of data. And as you could see in the video the data must always be up to date. We can no longer afford to offer copies of data, so what's better than to incorporate mobile with the company's primary data. Data that's residing on the mainframe . . . where it always has been.

Now, this new pricing mechanism makes sure you're not penalized for following just that strategy. "This enhancement to sub-capacity reporting can mitigate the impact of mobile workloads on sub-capacity license charges, specifically in the cases where higher mobile transaction volumes may cause a spike in machine utilization. This can normalize the rate of transaction growth and reduce the reported peak capacity values used for sub-capacity charges".

There are some prerequisites of course : it's limited to AWLC and AEWLC pricing which means to zEC12 and zBC12 or environments that have at least one zEC12 or zBC12. You also need to install a new reporting tool that will, in this case, replace SCRT : Mobile Workload Reporting Tool (MWRT). It's use, data collection and timing of reporting is very similar to SCRT. What's the difference ?
"MWRT will calculate the 4-hour rolling average of the reported mobile transaction general purpose processor time consumed by the Mobile Workload Pricing Defining Programs and subtract 60% of those values from the traditional sub-capacity MSUs for all sub-capacity eligible programs running in the same LPAR(s) as the mobile workloads, on an hour-by-hour basis, per LPAR. The program values for the same hour are summed across all of the LPARs (and any z/OS guest systems running under z/VM®) in which the program runs to create an adjusted sub-capacity value for the program, for the given machine, for each hour. MWRT will determine the billable MSU peak for a given program on a machine using the adjusted MSU values".
You can find all additional details in the announcement itself. And . . . you have some time to figure out how things work as MWRT becomes available on June 30, 2014 and the first report can be submitted as of July 2, 2014.

No comments: