mopdf.com

z/OS Performance Analysis WLM Update Db2 Performance AnalysisEPV Performance University1

WLM and software pricingEPV Performance University2

Agenda Introduction Mobile workload pricing Container pricingEPV Performance University3

IntroductionEPV Performance University4

Introduction In the last years WLM has been more and more involved in the manymechanisms invented by IBM marketing people to provide ways tomitigate the z/OS environment software costs The first step was the introduction of the specialty engines (zAAP andzIIP) where WLM was marginally involved The next steps were the 4-hour rolling average mechanism and the softcapping technique implementation where WLM started playing afundamental role in major software (e.g. z/OS, CICS, IMS, and Db2) costcontrolEPV Performance University5

Introduction In 2014, IBM introduced Mobile Workload Pricing: a new pricing modeldesigned “to mitigate the impact of mobile workloads on sub-capacitylicense charges and provide a more cost-competitive software” The initial implementation was too complex for the customers tomanage so it was not very successful After a couple of years, IBM provided a much easier implementation ofthis pricing option involving again WLMEPV Performance University6

Introduction At the end of 2017, IBM announced Container Pricing. “Container Pricing makes pricing simpler and more economical forqualified solutions. It's a framework for hosting simplified and flexiblesoftware pricing for qualified solutions running on the z13 and z14 IBMprocessors, and allows specific workloads to be metered, reported on,and optionally capped, whether on a dedicated LPAR or colocated withexisting workloads on an existing LPAR with no direct impact on your 4Hour Rolling Average.”EPV Performance University7

Introduction With Container Pricing you may run qualified solutions, inside a logicalcontainer in the same LPAR where traditional workload run, and have aseparate, lower price for the workload inside the container, without anydirect impact on traditional workload pricing The burden of managing co-located qualified solutions is again chargedto WLM Unfortunately, the technical implementation in WLM is, in this case,more complex and invasiveEPV Performance University8

Introduction The last evolution of z/OS software pricing is Tailored Fit Pricing (TFP) It allows two options:– Enterprise Capacity solution– Enterprise Consumption solution Both options eliminate the need to measure the 4-hour rolling averageand the need to use the soft capping functions to manage the softwarecosts So WLM should not be involved anymoreEPV Performance University9

Mobile workloadpricingEPV Performance University10

Mobile workload pricing On May 6th 2014 IBM announced Mobile Workload Pricing for z/OS(MWP): a new pricing model designed “to mitigate the impact of mobileworkloads on sub-capacity license charges and provide a more costcompetitive software” Mobile workloads have to run in one or more of the Mobile WorkloadPricing Defining Programs (CICS, DB2, IMS, MQ and WebSphere) What is more interesting for customers is that the contribution ofmobile workloads to the monthly peak of the 4HRA is discounted by60%EPV Performance University11

Mobile workload pricing After more than 2 years IBM found that MWP had not been very successful Not in line with the “cut z/OS costs” mantra is repeated everywhere Some issues are related to an addendum to the contract and to the high levelof discretion IBM has, in accepting or not the process put in place by users, toidentify mobile workloads From the technical point the major issue is that customers have to:– collect and process a very large number of SMF (CICS, DB2, MQ andWebSphere) and IMS log records– produce CSV files, aggregating the consumption of mobile workloads inthe required format, and provide them as input to SCRT every monthEPV Performance University12

Mobile workload pricing To solve the technical problem, WLM enhancements have beenintroduced which have greatly simplified mobile workload identificationand measurement WLM classification rules allow to classify mobile transactions processedby the subsystems using a Reporting Attribute Of course IBM has still to approve your rulesEPV Performance University13

Mobile workload pricing Rule example to assign DDF transactions, processed by DB2X and havingthe Correlation Information starting with MOBTRX , to the RMOBTRXreport classEPV Performance University14

Mobile workload pricing To assign to RMOBDDF the new MOBILE Reporting Attribute you have toscroll to the right twice by using the PF11 keyEPV Performance University15

Mobile workload pricing The default value is NONEOther possible values are CATEGORYA and CATEGORYBThey are provided to classify public cloud transactions (zWPC)See ‘IBM z Systems Workload Pricing for Cloud for z/OS can reduce thecost of growth for public cloud transactions’ - IBM United StatesSoftware Announcement 216-319, dated July 26, 2016EPV Performance University16

Mobile workload pricing To allow measuring MWP with CICS and IMS, new SMF 72 metricsproviding CPU usage by transactions have been introduced from CICS5.3 and IMS 14:– R723TSUCP, SU consumed by transactions, executed on GCP– R723MSUCP, SU consumed by transactions, classified with reporting attributeMOBILE, executed on GCP– R723TSUSP, SU consumed by transactions, executed on zIIP– R723MSUSP, SU consumed by transactions, classified with reporting attributeMOBILE, executed on zIIPEPV Performance University17

Mobile workload pricing– R723TSUOCP, SU consumed by transactions, eligible to run on zIIP, but executedon GCP– R723MSUOCP, SU consumed by transactions, classified with reporting attributeMOBILE, eligible to run on zIIP, but executed on GCP SMF70LACM has been added to SMF 70 to provide the 4-hour rollingaverage MSUs consumed by transactions classified with the MOBILEreporting attribute; it’s used by SCRT to apply the discount for Mobileworkloads Similar metrics are provided for CATEGORYA and CATEGORYBEPV Performance University18

Mobile workload pricingExercise 1 A CICS region has been assigned to the CICSMOB service class and by usingthe “old” metrics you can see its CPU usage in the peak hour is 792 CPUseconds The new R723TSUCP metric will tell you that the portion of the region CPUused by transactions is 58.320.000 service units The new R723MSUCP metric will tell you that the portion of the region CPUused by mobile transactions is 32.400.000 service units The system SU rate is 90.000What is the region overhead?What is the percentage of 1 CPU used by mobile transactions?EPV Performance University19

Exercise 1 CPU seconds used by transactions is:58.320.000 SU / 90.000 SU/sec 648 sec CPU seconds used by mobile transactions is:32.400.000 SU / 90.000 SU/sec 360 sec Region overhead is:(792 sec – 648 sec) / 792 sec 18,2% Percentage of 1 CPU used by mobile transactions360 sec / 3600 sec 10%EPV Performance University20

Mobile workload pricing You have to remember that:– “old”region consumptions include transaction consumptions (R723TSUCP)– region overhead can be estimated by difference– MOBILE transaction consumptions (R723MSUCP) is included in transactionconsumptions (R723TSUCP)EPV Performance University21

Mobile workload pricingFrom the “Using IBM z/OS WLM to Measure Mobile and Other Workloads”IBM Red Paper - REDP-5359-00EPV Performance University22

Mobile workload pricingFrom the “Using IBM z/OS WLM to Measure Mobile and Other Workloads”IBM Red Paper - REDP-5359-00EPV Performance University23

Mobile workload pricing It’s very important you clearly understand the MWP discountmechanism What is really relevant is the amount of MSUs used by mobile workloadwhen the monthly peak of the 4HRA occurs This is the amount of MSUs that will be discountedEPV Performance University24

Mobile workload pricing Example showingone month ofreal data Peak of Mobile4HRA very high But not in thesame hour ofPeak 4HRAEPV Performance University25

Mobile workload pricing Only 554 MSUswill be eligiblefor discount The savingallowed byMobile WorkloadPricing for thismonth will be332 MSUsEPV Performance University26

Mobile workload pricing The adjustedvalue of the peakof 4HRA is 6.878MSUsEPV Performance University27

Mobile workload pricing 60% of mobile workloads already discounted in WLC viewsEPV Performance University28

Mobile workload pricing Report class views enhanced for mobile workloadsEPV Performance University29

Container pricingEPV Performance University30

Container pricing IBM recently introduced Container Pricing Three solutions are enabled: Application Development and Test Solution – aggressive pricing New Application Solution – highly competitive pricing for new z/OSapplications Payments Pricing Solution – business metric tied directly to payment volumesEPV Performance University31

Container pricing A new solution may be defined as being colocated with other solutionsin existing z/OS images (LPARs), in separate LPARs or multiple LPARs The colocated solution has no direct impact to the rolling four-houraverage. Therefore, introduction of a new workload in the sameproduction system has minimal or no impact on the pricing of existingworkloadsEPV Performance University32

Container pricing The colocated solution can be measured and its MSU utilizationoptionally capped, independent of other workloads The system records data about the colocated solution for accounting(SCRT reporting) purposes SCRT analyzes the recorded data and produces a report for consumptionby fulfillment systems, removing the workload’s MSU utilization fromthe rolling four-hour averageEPV Performance University33

Container pricing – Step 1 Once a solution is agreed upon with the client, with an agreed price,IBM Sales initiates a sales order, which triggers the creation of a solutionID The IBM-provided solution ID is a 64-character string representing anapproved workload with an entitled MSU capacity in the form of a fullcap pricing container used for billing purposesEPV Performance University34

Container pricing – Step 2 Tenant resource groups (and tenant report classes) have to be createdin WLM to identify the workloads that constitute the approved solutionworkload The tenant resource group also supports optional capping of theworkload’s MSU utilization When defining the tenant resource group the 64-character solution IDthat was obtained in the prior step has to be provided That is the link between the approved workload and SCRT’s evaluation,and exclusion from the R4HAEPV Performance University35

Container pricing – Step 3 When the WLM policy including the tenant resource group and tenantreport classes definitions is activated and the solution executes, WLMrecords data related to the workload RMF then writes each tenant resource group’s consumption data to SMFType 70, Subtype 1 and SMF 72 subtype 3 records SMF 89 records are also writtenEPV Performance University36