IBM United States
Software Announcement 203-263
September 30, 2003
New sub-capacity charging for select IBM WebSphere programs on z/OS For flexibility and improved cost of computing
Sub-capacity charging is announced for select IBM International Program License Agreement (IPLA), one-time charge (OTC) WebSphere® programs that run on z/OS®. Customers who qualify may elect to pay for select WebSphere programs at less than full capacity, under these new sub-capacity charging terms.
Sub-capacity charging for select WebSphere programs can offer customers both financial benefits and technical flexibility. Customers may now deploy a select WebSphere program in a logical partition (LPAR) and pay for the select WebSphere program based on the capacity of the LPAR. LPAR capacity is determined by measuring the highest observed rolling four-hour average utilization of the LPAR. Under sub-capacity charging, customers may:
Sub-capacity charging for select WebSphere programs is available to customers who have already met the conditions for and implemented sub-capacity charges for their IBM monthly license charge (MLC) programs. Sub-capacity MLC metrics include sub-capacity Entry Workload License Charges (EWLC) or sub-capacity Workload License Charges (WLC).
For a list of the select WebSphere programs for z/OS, which are licensed under the IPLA and eligible for sub-capacity charging, refer to the Description section.
Additionally, the Entry Option (for details on the original announcement, refer to Software Announcement 203-093 , dated April 8, 2003) is withdrawn from marketing effective immediately. Refer to the Entry Option withdrawn section for details.
The term sub-capacity generally describes a situation where an IBM customer may pay for software at less than full-machine capacity. In the case of sub-capacity WLCs, sub-capacity EWLCs, and sub-capacity charging for select WebSphere programs, IBM determines the sub-capacity charges based on the capacity of a LPAR where a program executes. The LPAR capacity is determined by measuring the highest observed rolling four-hour average utilization of an LPAR during a reporting period (second day of the month through the first day of next month).
Example 1 WebSphere Application Server running in a 40 MSU LPAR on a 2064-112 (rated at 372 MSUs) running z/OS in 64-bit mode
The customer wishes to run WebSphere Application Server in a single LPAR. The selected LPAR has a defined capacity of 40 MSUs. Based on LPAR configuration, the recommended approach is for the customer to request 40 MSUs of WebSphere Application Server. This equates to a 20-Value-Unit entitlement. Utilization of the LPAR may exceed 40 MSUs temporarily but one z/OS Workload manager will ensure that the rolling 4-hour average utilization is less than or equal to 40 MSUs. The customer's sub-capacity reports will show a value of 40 MSUs or less, as long as the LPARs-defined capacity remains set at 40 MSUs.
Example 2 WebSphere Application Server running in an LPAR with 4 logical engines on a 2064-112 (rated at 372 MSUs) running z/OS in 64-bit mode
The customer wishes to run WebSphere Application Server in a single LPAR. The selected LPAR has four logical engines assigned but no defined capacity. There are two approaches to estimate the number of MSUs of WebSphere required:
To assess previous LPAR utilizations, review the Detail LPAR data section of previous sub-capacity reports. Keep in mind that the rolling four-hour average utilization of the specified LPAR may increase or decrease in the future. Increases will result in IBM automatically billing the customer for additional Value Unit entitlements.
To assess the maximum potential capacity of the LPAR, consider the number
of logical engines assigned to the specified LPAR as compared to the
total physical engines of the machine. This LPAR has 4 logical engines
assigned and a total of 12 physical engines (2064-112). Therefore, the
utilization of the LPAR may not exceed 4/12ths (33%) of the machine, or
approximately 124 MSUs.
Customer responsibilities under sub-capacity charging
Entry Option withdrawn
Effective immediately, the Entry Option for following selected WebSphere platform programs is withdrawn from marketing:
Program Description number WebSphere Application Server 5655-I35 for z/OS V5 WebSphere Application Server V4.01 5655-F31 WebSphere Portal for z/OS and 5655-K12 OS/390 V4.1 WebSphere Host Publisher V4 5655-I03 for zSeries WebSphere MQ Integrator(R) Broker 5655-I58 for z/OS V2.1 WebSphere MQ Integrator for z/OS V2.1 5655-G97 WebSphere MQ Workflow for z/OS V3.4 5655-BPM WebSphere Data Interchange 5655-I40 for z/OS V3.2 WebSphere Business Integration Message 5655-K60 Broker for z/OS V5 WebSphere Business Integration Message 5697-I11 Broker with Rules and Formatter Extension for z/OS WebSphere Business Integration Event 5655-K57 Broker for z/OS V5
Eligible programs for sub-capacity charging
The following list of the select WebSphere programs are licensed under the IPLA and eligible for sub-capacity charging:
Program Description number WebSphere Application Server 5655-I35 for z/OS V5 WebSphere Application Server V4.01 5655-F31 WebSphere Portal for z/OS 5655-K12 and OS/390 V4.1 WebSphere Host Publisher V4 5655-I03 for zSeries WebSphere MQ Integrator Broker 5655-I58 for z/OS V2.1 WebSphere MQ Integrator for 5655-G97 z/OS V2.1 WebSphere MQ Workflow for z/OS V3.4 5655-BPM WebSphere Data Interchange 5655-I40 for z/OS V3.2 WebSphere Business Integration 5655-K60 Message Broker for z/OS V5 WebSphere Business Integration 5697-I11 Message Broker with Rules and Formatter Extension for z/OS WebSphere Business Integration 5655-K57 Event Broker for z/OS V5 WebSphere Studio Asset Analyzer 5655-I49 WebSphere Studio Workload 5655-I14 Simulator WebSphere Studio Application 5655-J67 Monitor
The list of select WebSphere programs eligible for sub-capacity charging is maintained on the following Web site: