1 / 15

Mobile Workload Pricing for z/OS

Mobile Workload Pricing for z/OS. 23 July 2014 David Chase, WW IBM System z Software dchase@us.ibm.com http://ibm.com/systems/z/swprice. Trademarks. The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. AIX* BookManager*

kolya
Download Presentation

Mobile Workload Pricing for z/OS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mobile Workload Pricing for z/OS 23 July 2014 David Chase, WW IBM System z Softwaredchase@us.ibm.comhttp://ibm.com/systems/z/swprice

  2. Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. AIX* BookManager* CICS* DB2* DB2 Connect DB2 Universal Database Parallel Sysplex* QMF RACF* S/390* System z System z9* System z10* SystemPac* Tivoli* VisualAge* WebSphere* VSE/ESA Intelligent Miner Lotus* Multiprise* MQSeries NetView* OS/390* DFSORT* Domino DRDA* Encina* FICON* GDDM* HiperSockets IBM* IBM eServer IBM logo* ImagePlus* IMS zEnterprise z/Architecture z/OS* z/VM* z/VSE zSeries* * Registered trademarks of IBM Corporation The following are trademarks or registered trademarks of other companies. Java and all Java-related trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countries Linux is a trademark of Linus Torvalds in the united States and other countries.. UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation in the United States and other countries. * All other products may be trademarks or registered trademarks of their respective companies. NOTES: Any performance data contained in this document was determined in a controlled environment. Actual results may vary significantly and are dependent on many factors including system hardware configuration and software design and configuration. Some measurements quoted in this document may have been made on development-level systems. There is no guarantee these measurements will be the same on generally-available systems. Users of this document should verify the applicable data for their specific environment. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. Information is provided “AS IS” without warranty of any kind. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Prices are suggested US list prices and are subject to change without notice. Starting price may not include a hard drive, operating system or other features. Contact your IBM representative or Business Partner for the most current pricing in your geography. Any proposed use of claims in this presentation outside of the United States must be reviewed by local IBM country counsel prior to such use. The information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM makes no representation or warranty regarding third-party products or services including those designated as ServerProven, ClusterProven or BladeCenter Interoperability Program products. Support for these third-party (non-IBM) products is provided by non-IBM Manufacturers. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. Send license inquires, in writing, to IBM Director of Licensing, IBM Corporation, New Castle Drive, Armonk, NY 10504-1785 USA.

  3. Mobile Workload Pricing for z/OS • Benefits • Improves the cost of growth for mobile transactions processed in System z environments such as CICS, IMS, DB2, MQ, and WAS • Mobile Workload Pricing (MWP) for z/OS enhances Sub-Capacity pricing • Mitigates the impact of Mobile on MLC charges where higher transaction volumes cause a spike in machine utilization • Normalizes the rate of transaction growth • No major infrastructure changes required, no separate LPARs needed • It is an enhanced way of reporting sub-capacity MSUs • System runs as it always has, workload execution is not altered • Hardware requirements • Available to all enterprises running a zEC12 or zBC12 server (actual mobile work may run on any zEnterprise machine including z196 and z114) • MWP Announcement Letters – 2014-05-06 • AP14-0219 Asia Pacific • A14-0429 Canada • ZP14-0280 Europe, Middle East, Africa • JP14-0279 Japan • LP14-0279 Latin America • 214-223 United States

  4. Mobile Workload Pricing Reporting Process • New Mobile Workload Reporting Tool (MWRT) – available 30 June 2014 • A new Windows-based Java tool to report sub-capacity MSUs and make adjustments to reported LPAR MSUs based on Mobile transaction data • Standard SCRT methodology plus new feature to adjust for Mobile workload impact • New tool will replace SCRT for customers who take advantage of Mobile Workload Pricing • Customers must track mobile transactions and produce a file showing mobile CPU consumption (general purpose processors) each month • Record mobile program transaction data CPU seconds, on an hourly basis per LPAR per program • Load the resulting data file(s) into MWRT each month (IBM-specified CSV format) • Run MWRT and submit the results to IBM each month (Replaces SCRT process) • MSU adjustments and monthly peak calculation for billing • MWRT will subtract 60% of the reported Mobile MSUs from a given LPAR in each hour, adjusting the total LPAR MSU value for that hour • This will function like a partial “off-load” from a software pricing perspective (real system processing is completely unchanged) • When an LPAR value is adjusted, all software running in the LPAR will benefit from lower MSUs • Tool will calculate the monthly MSU peak for a given machine using the adjusted MSU values

  5. Example: Sample LPAR MSU values by hour • SCRT calculates the Rolling 4-Hour Average (R4HA) MSU peak • All workloads are included Peak R4HA value = 1404 MSUs

  6. LPAR MSU values adjusted for mobile contribution Original Peak R4HA value = 1404 MSUs • MWRT removes 60% of the Mobile workload billing, interval-by-interval • Non-mobile workload contribution to billing is unchanged • Billing MSUs for the month are based upon the newly calculated R4HA curve after the mobile workload has been reduced New Peak R4HA Value = 1231 MSUsMWRT savings = 173 MSUs Provides benefit when Mobile workloads contribute to monthly peak MSUs;Off-peak MSU adjustments will not affect MSUs used for billing.

  7. Example: reducing Mobile impact to LPAR peak 1 Measure LPAR MSUs: Standard SCRT methodology, SMF 70 records 5 Adjusted LPAR MSUs: Per new MWRT reporting tool Measure CICS usage: Capture SMF 89 record in new IBM reporting tool (replaces SCRT); SMF 89 is IBM usage standard 2 1,500 MSUs 1,380 MSUs Usage CICS 6 CICS, z/OS & Other Adjusted LPAR MSUs used to determine peak for month; Pricing & billing BAU based on peak 300 z/OS & Other 3 Tag Mobile transactions: e.g. Capture CICS transaction details (SMF 110 records) and filter by transaction type Transaction definitions 200 Mobile 80 Mobile Other Other 4 100 100 Subtract 60% of mobile MSUs: -60% * 200 = -120 LPAR MSUs for billing (Standard) z/OS/Other 1,500 CICS 1,500 LPAR MSUs for billing (Adjusted) z/OS/Other 1,380 CICS 1,380 Figures are for illustrative purposes only.

  8. Detailed MWRT Reporting Example Capture LPAR MSUs (SMF 70 records) 1 Customer requirement – Provide Mobile CPU seconds by interval: Customer input with IBM approval. Values provided monthly in CSV format. 2 3 Tool will subtract 60% of Mobile MSUs from LPAR original values Formula for LPAR 1, Interval 1: LPAR1 Total MSUs = 197 Mobile only MSUs = 79 Subtract 60% of Mobile = (79 * 0.60 = 47) Adjusted LPAR MSUs: 197 – 47 = 150 Adjusted LPAR totals used to determine new monthly peak. 4

  9. Identifying Mobile Transaction Workload • Customers are responsible for processing their mobile transaction data into a predefined format to be loaded into MWRT for each sub-capacity reporting period. • IBM must approve the data gathering methodology. • The data must consist of general purpose processor CPU seconds for each mobile transaction program summarized by hour by LPAR for all machines processing mobile transactions. • Detailed instructions, including CSV file format, available in the MWRT Users Guide. • Mobile Workload Pricing Defining Programs:

  10. New MWP Contract Addendum & Supplement • Mobile Workload Pricing is available for Mobile workloads running on a zEC12 or zBC12 server with AWLC or AEWLC sub-capacity pricing • Alternatively, if you install and operate a zEC12 or zBC12 in your enterprise you will be eligible for MWP when running a Mobile Workload Pricing Defining Program on a z196 or z114 server with sub-capacity pricing • There is a new contract Addendum and accompanying Supplement: • Addendum for System z Mobile Workload Pricing (Z126-6300) • Terms and conditions to receive MWP benefit for AWLC, AEWLC, zNALC billing • Supplement to the Addendum for System z MWP (Z126-6628) • Customer explains how they tag/track their Mobile application CPU time • Agreement to and compliance with the terms and conditions specified in the MWP contract Addendum is required • If the MWP Addendum is not implemented, MWRT Reports will be rejected!

  11. Supplement information • MWP Supplement necessary for each Mobile Application • Supplement Worksheet is for you to give customer to fill out, data from worksheet will be used to prepare official Supplement • IBM Community link: https://w3-connections.ibm.com/files/app/file/efd841b4-e5e2-41cf-9610-4d409aef0cda • PartnerWorld link for BPs: http://www.ibm.com/partnerworld/page/ZSJ03220USEN • Information requested: • Name of customer’s Mobile Application • List of MWP Defining Programs used by Mobile Application • For each MWP Defining program: • The SMF record or other data source used to track the general purpose processor CPU time of the mobile transactions. • Method used by Client to distinguish the general purpose processor CPU time of the mobile transactions from the general purpose processor CPU time of the other workload in the data from each MWP Defining Program, including, if applicable, the name of the data field being used. • Client’s process for capturing and processing the data to obtain the mobile general purpose processor CPU seconds per hour per LPAR per program.

  12. Worksheet example

  13. More Information • System z Mobile Solutions Mobile Workload Pricing Wiki • https://w3-connections.ibm.com/wikis/home?lang=en#!/wiki/Wba55f44d5749_4dd7_b8ad_1600cb65508e/page/Mobile%20Workload%20Pricing • Wiki has links to: • Announcement material • April 16 Seller Education • May 6 Seller Education • Q&A Document • Customer Education • Ian Mitchell’s Wiki with examples of ways to tag and track eligible workload • MWRT Tool links • MWRT Users Guide (external customer link) • MWRT Deliverable (external customer link) Download the tool. • MWP contract supplement Customer Worksheet.​doc file (internal IBM link) • For IBM approval of a customer's mobile workload tracking mechanisms, please contact Michael Shipman or Ray Jones.

  14. In Summary • Mobile Workload Pricing (MWP) Benefits • Improves the cost of growth for mobile transactions processed in System z environments such as CICS, IMS, DB2, MQ, and WAS • MWP for z/OS enhances Sub-Capacity pricing • Mitigates the impact of Mobile on MLC charges where higher transaction volumes cause a spike in machine utilization • Normalizes the rate of transaction growth • No major infrastructure changes required, no separate LPARs needed • It is an enhanced way of reporting sub-capacity MSUs • System runs as it always has, workload execution is not altered • Key requirements • Available to all enterprises running a zEC12 or zBC12 server (actual mobile work may run on any zEnterprise machine including z196 and z114) • Use a Mobile Workload Pricing Defining Program to process mobile transactions • Implement sub-capacity using AWLC or AEWLC under standard pricing terms • Meet the mobile workload tracking and reporting requirements

  15. The End

More Related