Assuming, you're talking about a product that runs on the general
purpose CP engines, mainframe licensing is typically based on either
total processor capacity (MSU's), or, now becoming more common,
Sub-Capacity pricing based on monthly max 4-hour-average MSU usage or
MSU capped capacity of all LPARs running the product.
Licensing "per CPU" is impractical because within z9 and z10 families
increasing the MSU capacity can either increase or decrease number of
CP's depending on the speed setting of the CP's.
Licensing to a specific LPAR would also be undesirable for most
installations. New versions of vendor software are not just dropped
into a production system, but first tested and validated in a test LPAR
environment. Any aspect of the software that runs differently in a test
LPAR environment would mean some branches of the software used in
production would not get completely tested. And yes, vendors do tend to
occasionally ship bugs in their license verification code or ship
license keys that don't work.
JC Ewing
[email protected] wrote:
My company sells encoding software to large users across the world.
Recently the question came up as to whether we can license per LPAR vs
CPU.
Can anyone tell me what they feel is a standard, or what normal
practices are?
Thanks,
Fraser
----------------------------------------------------------------------
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
