2824 ibm mobile workload pricing: five ways to tag and track your mobile workloads

© 2015 IBM Corporation

IBM Mobile Workload Pricing::Five ways to tag and track your mobile workloadsIan J Mitchell,

IBM Distinguished Engineer,

IBM Hursley, UK

Notices and DisclaimersCopyright © 2015 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.

Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS document is distributed "AS IS" without any warranty, either express or implied. In no event shall IBM be liable for any damage arising from the use of this information, including but not limited to, loss of data, business interruption, loss of profit or loss of opportunity. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.

Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.

Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business.

Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.

It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law.

Notices and Disclaimers (con’t)

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of 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. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM expressly disclaims all warranties, expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose.

The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right.

• IBM, the IBM logo, ibm.com, Bluemix, Blueworks Live, CICS, Clearcase, DOORS®, Enterprise Document Management System™, Global Business Services ®, Global Technology Services ®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, SoDA, SPSS, StoredIQ, Tivoli®, Trusteer®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.

http://www.ibm.com/legal/copytrade.shtml

4

Background info

● Thanks to the following people for their contributions to this chart deck:– Nigel Williams, IBM Client Center Montpellier

– Aymeric Affouard, IBM Client Center Montpellier

– Fabrice Jarassat, IBM Client Center Montpellier

– Peter Siddell, IBM Hursley

– Richard Gamblin

– David Rhoderick

– Jeffrey Miller

– Roberto Calderon

– Guillaume Arnold

– Hendrik Woerner

– Dominique Richard

– Satish Tanna

– Adham Sidhom

– Alasdair Turner

5

Agenda

● What is the problem

● What has been announced for Mobile Workload Pricing (MWP)

● Mobile Workload Reporting Tool (MWRT)

● Tagging and tracking mobile transactions– Different methods – Use cases (insurance and banking)

● Summary

● More information

6

Mobile workload growth

Business as usual

Mobile

Driving back-end transactions

Increasing capacity growth

Higher proportion of inquiry

7

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, WAS and MQ

– 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 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• But you do need to be able to tag and track mobile transactions

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)

8

Sub-capacity Workload Licence Charges

z/OS &other

programs

Full capacity 2000 MSUS

Sub capacity 1500 MSUS

LPARS

Month

2000 MSUS

1000 MSUS

Peak R4HA = 1500 MSUS

Sub-capacity Reporting Tool (SCRT) calculates a rolling four hour average utilisation for each LPAR in each hourly interval

SCRT determines peak utilisation across all the LPARS in which a program runs

SCRT report is submitted monthly to set monthly licence charges

9

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 each month

• Record mobile program transaction data, including CPU seconds, on an hourly basis per LPAR

• Load the resulting data file 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

10

Example: how MWP can reduce LPAR peak MSUs

z/OS &Other

CICS

Measure LPAR MSUs: Standard SCRT methodology, SMF 70 records

1,500

Usage

Tag Mobile transactions:e.g. Capture CICS transaction details (SMF 110 records) and filter by transaction type

Other

Mobile

Other

1,380 MSUs

Subtract 60% of mobile MSUs:-60% * 200 = -120

Measure CICS usage:Capture SMF 89 record in new IBM reporting tool (replaces SCRT); SMF 89 is IBM usage standard

CICS,z/OS &Other

200

100 100

80

Adjusted LPAR MSUs: Per new MWRT reporting tool

Transactiondefinitions

Adjusted LPAR MSUs used to determine peak for month; Pricing & billing BAU based on peak

MSUs

1

2

3

4

5

6

300

Mobile

LPAR MSUs for billing (Standard)z/OS/Other 1,500CICS 1,500

LPAR MSUsfor billing (Adjusted)z/OS/Other 1,380CICS 1,380Figures are for illustrative purposes only.

11

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

12

LPAR MSU values adjusted for mobile contribution

MWRT removes 60% of the Mobile workload, interval-by-interval– Non-mobile workload 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 MSUs MWRT savings = 173 MSUs

Provides benefit when Mobile workloads contribute to monthly peak MSUs;Off-peak MSU adjustments will not affect MSUs used for billing.

Original Peak R4HA value = 1404 MSUs

13

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 user's guide. Mobile Workload Pricing Defining Programs:

5655-S97 CICS TS for z/OS V4 5655-DSQ IMS DB VUE V125655-Y04 CICS TS for z/OS V5 5655-DSM IMS DB VUE V135722-DFJ CICS VUE V5 5655-TM1 IMS TM VUE V125635-DB2 DB2 V9 for z/OS 5655-TM2 IMS TM VUE V135605-DB2 DB2 10 for z/OS 5655-L82 WS MQ for z/OS V65615-DB2 DB2 11 for z/OS 5655-R36 WS MQ for z/OS V75697-P12 DB2 VUE V9 5655-W97 WS MQ for z/OS V85697-P31 DB2 10 VUE 5655-VUE WS MQ VUE V75697-P43 DB2 11 VUE 5655-VU8 WS MQ VUE V85635-A02 IMS V11 5655-N02 WebSphere App Server for z/OS V75635-A03 IMS V12 5655-W65 WebSphere App Server for z/OS V85635-A04 IMS V13

14

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:– 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!

15

Tagging and tracking mobile transactions

16

Tagging and Tracking for Mobile Workload Pricing - Overview

Clear Definition Here! “Transactions that are

triggered on a Mobile Device”

“A Mobile Device is a Tablet or a Smartphone”

“Both mobile Browser or mobile App comply with MWP.”

Tagging - The Unknown!

How to forward a 'Mobile Tag' all the way through to a z/OS Defining Program?

Clear Definition Here!

“z/OS Defining Programs: WAS, MQ, CICS, IMS, DB2”

“GCP CPUs that are used in the Defining Programs to process Mobile workload are eligible for MWP”

Tracking Examples

“SMF Report”

“WLM Report”

“Customer Reporting Tool”

Overhead of some SMF classes might be a concern...

MWRT Tool is available now

End-User Middleware Z/OS Sysplex MWP Reporting

1717

Overview of Tagging and Tracking Process

1818

Which Tracking mechanisms can be used with MWP?

Use an individual LPAR for mobile-only workloads. All defining programs in here can report their GCP CPUs as mobile CPUs.

Build individual subsystems of the defining programs for mobile-only workloads. These can then report their GCP CPUs as mobile CPUs.

Use same subsystems for mobile and non-mobile but createdifferent CPU reports for mobile CPU.

Charging realms

Service Consumers

Service Providers

Single charging realm

Data

Application

Today's model assumes a largely homogenous single charging realm.

Implementing mobile service containers - granularity

Service Providers

Data

Application

Use an individual LPAR for mobile-only workloads. All defining programs in here can report their GCP CPUs as mobile CPUs.

Assume correct routing of red workload to the correct container.

z/OS LPARSMF MWRT

Service Providers

Data

Application


● Build individual subsystems of the defining programs for mobile-only workloads. These can then report their GCP CPUs as mobile CPUs.

z/OS LPAR

IMS

CICS

SMF MWRT


● Use same subsystems for mobile and non-mobile but createdifferent CPU reports for mobile CPU.

z/OS LPAR

IMS CICS

TRNA

TRNB

TRNA

TRNB

SMF MWRT

2323

Which Tracking mechanisms can be used with MWP?

Use same subsystems for mobile and non-mobile but createdifferent CPU reports for mobile CPU.

How could this be done? Examples:

– CICS: Transaction id, TCP/IP port, User id → SMF110 Report– IMS: LTERM, IMS Transaction Name, User id → Transaction Level Statistics

x'56FA'– MQ: Connection Type, Queue Name → SMF 116 Report– DB2: JDBC stats like 'Program Name' → SMF 102 Report– WAS: unique URL for mobile → SMF 120.9 Report

Note: this presentation contains examples of mobile tracking for CICS

2424

mobilegateway

webserver

DB2

DB2

CICS

CICS

JEEserver

AppBrws

Customer creates a Mobile CPUreport for CPUs / Hour / LPAR

SMF110Report

Tool

MWRT

Mobile

SCRT

MWRT Tool requiresnormal SMF 70 and 89 data

plus the new Mobile CPUreport.

Standard SCRTreport is created

with MWP adjustments

CICS SMF 110 datacontains mobile Tx IDs

Example of Tagging and Tracking Process

SMF 70, 89

2525

Format for Customer CSV file mobile transaction input to MWRT

The first row is the Product row containing the product id (or ids) for all the versions of a particular product family the customer is using for mobile workload processing.

The Header row contains the date and the LPAR names Column one of the mobile transaction data rows is the date. The date must be in ISO-8601

format (e.g. “2014-03-21T03:00:00” to indicate three AM on March 21, 2014)Then each cell in the mobile transaction data row must have CPU seconds for that hour in that

LPAR as a floating point number

2626

How do customers track their mobile workload today?

Mobile Devices usually terminate at a web-server, JEE server, mobile gateway (e.g DataPower) or Worklight Server

From there, back-ends – including z/OS applications and data – are accessed At the back-end level, typically a lot of services have shared-access from different

service requesters Some customers have middleware components that are channel-aware and call

back-end systems based on channel context (but most do not have this)

DB2

DB2

CICS

CICS

Mobilegateway

Webserver

JEEserver

AppBrws

'Browser OS' usuallydropped at this point.

Mobile ‘flag’ usuallydropped at this point.

2727

How to forward a 'Mobile Tag'

Network layer: route certain requests (from mobile gateway for example) to specific TCP/IP ports

SOA Layer: in ESB / IIB / etc. route incoming SOA requests from mobile to a specific web service (different URI)

JEE Layer: change web application programs to change context of back-end request (e.g transaction id) when session was established by a mobile device.

mobilegateway

webserver

DB2

DB2

CICS

CICS

JEEserver

AppBrws

'Browser OS' forwardedto JEE server

Route request to specific TCP/IP port

JEE application logiccalls specific CICS trans id if session init was

from mobile

Examples:

2828

Example use cases

General insurance application (GENAPP)– The GENAPP Mobile Application Sample demonstrates how to create a mobile

application which is used to check insurance policies and make claims on policies.

It is delivered with CICS TS SupportPact CA0D http://www.ibm.com/support/docview.wss?uid=swg24035181

Smarter banking showcase– The IBM Smarter Banking showcase is a simulation of a real bank. The banking

systems that are used in the showcase run a mixed workload of real-world financial transactions, including cash withdrawals, deposits, mortgages, and car loans. The core banking systems are accessed through a multi-channel environment (internet, mobile, ATM, branch...). The COBOL core banking application runs on CICS and stores customer and account records in DB2 for z/OS.

See here for more information on the banking showcase http://www.ibm.com/ibm/clientcenter/montpellier/sbs.shtml

http://www.ibm.com/support/docview.wss?uid=swg24035181

http://www.ibm.com/support/docview.wss?uid=swg24035181

http://www.ibm.com/ibm/clientcenter/montpellier/sbs.shtml

29

GENAPP use case

30

MOBILE

Web service clients

WAS

CICS

DB2 z/OSDB2 z/OS

IBM Worklight

GenApp

http/json

http/SOAP

http/SOAP

3270

GENAPP architecture

GENAPP CICS application is accessed from 3 client types– Emulated 3270 sessions using Telnet – Clients that use GENAPP web services – Mobile devices that connect to Worklight server which

then uses the same GENAPP web services

31

Web service clients

CICS

DB2 z/OSDB2 z/OS

GenApp

3270

SSC1,SSP1

CW

XN,C

PIH

MOBILE

WAS

IBM Worklighthttp/

json

9.212.136.76

9.212.131.52

GENAPP architecture – more details

These trans are not eligible for MWP

Some of these transare eligible for MWP


Some of these transare eligible for MWP

http://9.212.143.123:4321/GENAPP/LGICUS01

http://9.212.143.123:4321/GENAPP/LGIPOL02

http://9.212.143.123:4322/GENAPP/LGICUS01

32

WEBSERVICE

URIMAP

CICSMOB1

TCPIPSERVICE

CPIHCWXN

URIMAPmatching

CSOL

Pipeline

handlers

handlers

handlers

data mapping

PIPELINE

Port

4322

Web service client

WAS

IBM Worklight

GenApp

3270

SSP1 SSC1

DB2 z/OSDB2 z/OS

http/SOAP

GENAPP – closer look inside CICS

Port

4321

33

CEDA DEFi ne TCpi pservi ce( GENATCP1 ) TCpi pservi ce : GENATCP1 GROup : GENAWSRV DEscr i pt i on ==> TCPI PSERVI CE f or GENAPP mobi l e r equest s

Ur m ==> NONE POrt number ==> O4321 1- 65535 STat us ==> Open Open ! Cl osed PROt ocol ==> Ht t p I i op ! Ht t p ! Eci ! User TRansact i on ==> CWXN Backl og ==> 00005 0- 32767 TSqpr ef i x ==> HOST ==> ANY I paddr ess ==> ANY

. . .

TCPIPSERVICE

34

I NQUI RE URIMAP RESULT - OVERTYPE TO MODI FY Ur i map( $115270) Usage( Pi pe) Enabl est at us( Enabl ed ) Avai l st at us( Not appl i c) Scheme( Ht t p) Redi r ect t ype( None ) Tcpi pser vi ce( ) Por t ( ) Host ( * ) Pat h( /GENAPP/LGICUS01) Anal yzer st at ( Noanal yzer ) Host t ype( ) I pr esol ved( 0. 0. 0. 0) I pf ami l y( Unknown) Socket c l ose( ) Sockpool si ze( ) Transact i on( CPIH) Conver t er ( )

URIMAP

35

CICS Performance Analyzer overview

36

CICSMOB1

SMF DS 1SMF DS 2

SMF DS 3SMF 110

HDBHDB

CICS Explorer with CICS PA

View and analyse mobile transaction CPU

CWXN

CPIH

SSC1

SSP1

Non-Mobile Trans

Non-Mobile Trans

Mobile Trans

Building a history of CICS transaction activity

CICS PA plugin for CICS Explorer

37

CICS PA plugin sample CPU analysis

38

CICSMOB1

CWXN

CPIH

SSC1

SSP1

SMF DS 1SMF DS 2

SMF DS 3SMF 110

CSV file

MWRT csv file

CICS PA ISPF interface

Build batch reports

Extract report to csv file

Add header records for MWRT csv file

CICS PA batch reports

Non-Mobile Trans

Non-Mobile Trans

Mobile Trans

39

Example list report form

File Edit Confirm Upgrade Options Help

EDIT LIST Report Form - MOBILE Row 1 of 396 More: > Description . . . List Report Form Version (VRM): 690 Selection Criteria: Performance Page width . . 132 Field / Name + Type Fn Description TRAN Transaction identifier CPU TIME CPU time CPUONCP TIME CPU time on standard CP ORIGIN Transaction origin type OCLINTIP Originating Client or Telnet IP address OTCPSRVC Originating TCP/IP Service Name EOR ---------------- End of Report ---------------- EOX ---------------- End of Extract ---------------

40

CICS PA performance list report

The Performance List report provides a detailed list of the CMF performance class records You can request a list of all available records, or specify selection criteria to list only the

information that meets specific requirements The example report below shows a performance list report for the GENAPP transactions with

selected report fields (trans id, user cpu, cpu time on standard CP, transaction origin type, originating client or telnet ip address and originating TCPIPSERVICE name)

Tran User CPU Time

CPUonCP Time

Origin OClintIP OTCPIPSr

SSC1 .0007 .0007 TERM 9.143.31.40

CWXN .0002 .0002 SOCKET 9.143.31.40 GENATCP2

CPIH .0014 .0014 WEB 9.143.31.40 GENATCP2

CWXN .0003 .0003 SOCKET 9.212.136.76 GENATCP1

CPIH .0013 .0011 WEB 9.212.136.76 GENATCP1

SSP1 .0001 .0001 TERM 9.143.31.40

These transactions qualify for MWP and this is the transaction CPU utilization eligible for MWP

Disclaimer: Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. There is no guarantee that these measurements will be the same on other systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary.

41

CICS PA List Report Set * Report Set =LIST* Description=CICS PA Report Set* Reports for System=CICSMOB1* Image =ZT01* Description=System added by take-up CICSPA IN(SMFIN001), APPLID(CICSMOB1), LINECNT(60), FORMAT(':','/'), PRECISION(4), SELECT(PERFORMANCE( INC(TRAN(CWXN, CPIH, SSC1, SSP1)))), LIST(OUTPUT(LIST0001), FIELDS(TRAN, CPU(TIME), CPUONCP(TIME), ORIGIN, OCLINTIP, OTCPSRVC)), LIST(OUTPUT(EXPT0001), DDNAME(CPAOEX01), DELIMIT(','), LABELS, FIELDS(TRAN, CPU(TIME), CPUONCP(TIME), ORIGIN, OCLINTIP, OTCPSRVC))/*

42

Example summary report form for MWP

File Edit Confirm Upgrade Profiling Options Help EDIT SUMMARY Report Form - MWPSUM5 Row 1 of 9 More: > Command ===> Scroll ===> CSR Description . . . Summary Report Form for MWP (v5) Version (VRM): 680 Selection Criteria: Performance Page width . . 132 Field Sort / Name + K O Type Fn Description MVSID K A MVS SMF ID CECMTYPE K A CEC machine type and model number STOP K A DATEISO Task stop time STOP K A TIMES Task stop time TASKTCNT Total Task Termination count TRAN K A Transaction identifier CPU TIME TOT CPU time CPUONCP TIME TOT CPU time on standard CP EOR ---------------- End of Report ---------------- EOX ---------------- End of Extract ---------------

43

Example of selection criteria for MWP form

File Edit Lists Options Help MWPSUM5 - Performance Select Statement Row 1 of 9 More: > Command ===> Scroll ===> CSR Active Report Interval Inc Start From To Exc Stop YYYY/MM/DD HH:MM:SS.TH YYYY/MM/DD HH:MM:SS.TH Inc Field --- Value or Range --- / Exc Name + Type Value/From To List + INC TRAN CPIH INC TRAN CWXN INC OTCPSRVC GENATCP1

If you have one originating TCPIP service then you can specify

this as the value

If you have more than one originating TCPIP Service then you need to create a resource

list and specify it here

44

Example of summary report for MWP form

File Systems Options Help MWPSUM5 - Performance Summary Report More: +System Selection: Report Output: APPLID . . CICSMOB1 + DDname . . . . . . . . . SUMM0001 Image . . ZT01 + Print Lines per Page . . (1-255) Group . . + Report Focus: Report by time interval: Form . . . MWPSUM5 + Interval . . . 01:00:00 (hh:mm:ss) Alert . . + Override Form + Eligible transactions only Timestamp . . . + Reporting Options: Totals Level . . 3 (blank or 0-8) Title . . Summary report for mobile workload

Totals level is based on number of Summary keys in FORM

Specify hourly interval as required by MWRT

4545

CICS PA performance summary report

The Performance Summary report is a summary of the CMF performance class records You can request a report that summarizes all available records, or you can specify selection

criteria to summarize only the information that meets specific requirements The example report below shows a performance summary report for the GENAPP mobile-

initiated transactions (CWXN and CPIH transactions that have GENATCP1 as originating TCPIPSERVICE) with selected report fields (mvs id, CEC model, interval data, tran id, number of tasks, total user cpu, total cpu time on standard CP)

This is the total CPU utilization eligible for MWP collected during the 1 hour recording interval


Total TotalMVS ID CECMType Stop Stop Tran #Ttasks User CPU CPUonCP Interval Interval Time Time ZT01 2827-733 2014-08-28 13:00:00 CPIH 10882 15.6652 11.9606ZT01 2827-733 2014-08-28 13:00:00 CWXN 10882 1.5271 1.5271 Total 21764 17.1923 13.2177

Smarter banking showcase use case

50

Smarter banking showcase

2%Bill Payments

1%Loan applications

3%Single Cheque Deposit (not-on-us)

7%Single Cheque Deposit (on-us)

5%Cash Deposits (Branch/Counter)

5%Transfer

(Beneficiary account is external to the institution)

7%Transfer

(Account to account within the institution)

16%Cash Withdrawals

5%Customer Arrangement/Account List

What is their relationship with the institution?

5%Mini-statement

Posting Inquiry

10%Customer statement at the Branch

Posting Inquiry

35%Balance Inquiry

% mix*1

Operation Type

2%Bill Payments

1%Loan applications

3%Single Cheque Deposit (not-on-us)

7%Single Cheque Deposit (on-us)

5%Cash Deposits (Branch/Counter)

5%Transfer

(Beneficiary account is external to the institution)

7%Transfer

(Account to account within the institution)

16%Cash Withdrawals

5%Customer Arrangement/Account List

What is their relationship with the institution?

5%Mini-statement

Posting Inquiry

10%Customer statement at the Branch

Posting Inquiry

35%Balance Inquiry

% mix*1

Operation Type

Branch

Internet Banking

Retail payments & ATM

Partners

Mobile

51

Banking showcase architecture

TORA AORA DB2A

LPARA

TORB AORB DB2B

LPARB

Integration platform

Retail payments

Mobile platform

MOBILE

BRANCH

INTERNET

ATM

VISA

SOAP/HTTP

CTG

1.

2.

Banking services are accessed by mobile clients in two ways:

1. Mobile apps connect to mobile platform which then calls CICS web services

2. Mobile web apps connect to integration platform that serves multiple web channels, integration platform then uses CTG (CICS Transaction Gateway) to connect to CICS

Both of these types of mobile request qualify for MWP

MQ

52

Banking showcase architecture – mobile classification

TORA AORA DB2A

LPARA

TORB AORB DB2B

LPARB

Integration platform

(WebSphere)

Mobile platform

(DataPower)

MOBILE

BRANCH

INTERNET

ATM

VISA

SOAP/HTTP

CTG

MQ

All of these transare eligible for MWP so we include transaction cpu for all transactions

that arrive from DataPower.

Some of these transare eligible for MWP.

Integration platform must pass mobile context to CICS. The WebSphere

application specifies CICS trans id on CTG ECI request.


10.6.25.242

Retail payments

53

CTG ECI request – setting the CICS transaction id

CICSTG

WebSphere Application Server

ApplicationMobile

z/OS

JCA resource adapter

IPICECI

CICS

Tran TBI

The CICS transaction id can be set by the WebSphere application depending on the type of client device

This determines the name of the attached mirror transaction that requests run under in CICS The trans id can be set by the WebSphere application using the ECIInteractionSpec methods

setTPNName() or setTranName() It call also be set as the custom property TPNName in the JCA connection factory

54

CICS PA performance list report - mobile


information that meets specific requirements The example report below shows an extract of a performance list report for the mobile

banking transactions Z* ‘posting inquiry’ and various types of ‘account transfer’ that are processed by the mobile platform and use CICS web services. It shows the selected report fields trans id, user cpu, cpu time on standard CP, transaction origin type, originating client or telnet ip address and originating TCPIPSERVICE name.

Tran User CPU Time

CPUonCP Time

Origin OClintIP OTCPIPSr

ZPI .0008 .0008 WEB 10.6.25.242 DPXI50Z

ZPI .0006 .0006 RZINTR 10.6.25.242 DPXI50Z

ZTB .0133 .0133 WEB 10.6.25.242 DPXI50Z

ZZTB .0014 .0014 WEB 10.6.25.242 DPXI50Z

ZZTB .0009 .0009 RZINTR 10.6.25.242 DPXI50Z

ZTE .0009 .0009 WEB 10.6.25.242 DPXI50Z

ZTE .0006 .0006 RZINTR 10.6.25.242 DPXI50Z

CWXN .0003 .0003 SOCKET 10.6.25.242 DPXI50Z

These transactions qualify for MWP

55

CICS PA performance list report – mobile web


information that meets specific requirements The example report below shows an extract of a performance list report for the mobile

banking TBI transaction ‘balance inquiry’ that is invoked by a WebSphere application via the CTG. It shows the selected report fields trans id, user cpu, cpu time on standard CP, transaction origin type, originating network name.

Tran User CPU Time

CPUonCP Time

Origin Netname

TBI .0014 .0014 MRO CTG800

TBI .0012 .0012 MRO CTG800

TBI .0016 .0016 MRO CTG800

TBI .0009 .0009 MRO CTG800

These transactions qualify for MWP


5757

CICS PA performance summary report – mobile


criteria to summarize only the information that meets specific requirements The example report below shows an extract of a performance summary for the mobile

banking transactions which represent ‘posting inquiry’ and various types of ‘account transfer’. These are processed by the mobile platform and use CICS web services to call the banking services. It shows the selected report fields mvs id, CEC model, interval data, number of tasks, total user cpu, total cpu time on standard CP.



Total TotalMVS ID CECMType Stop Stop #Ttasks User CPU CPUonCP Interval Interval Time Time ZB01 2827-733 2014-09-11 15:00:00 56850 95.0485 95.0485 ZB02 2827-733 2014-09-11 15:00:00 47322 78.0216 78.0216 Total 104172 173.0701 173.0701

5858

CICS PA performance summary report – mobile web


criteria to summarize only the information that meets specific requirements The example report below shows an extract of a performance summary for the mobile

banking TBI transaction ‘balance inquiry’ that is invoked by a WebSphere application via the CTG. It shows the selected report fields mvs id, CEC model, interval data, tran id, number of tasks, total user cpu, total cpu time on standard CP.



Total TotalMVS ID CECMType Stop Stop Tran #Ttasks User CPU CPUonCP Interval Interval Time Time ZB01 2827-733 2014-09-11 15:00:00 TBI 29940 21.5355 21.5355 ZB02 2827-733 2014-09-11 15:00:00 TBI 62749 42.3592 42.3592 Total 92689 63.8947 63.8947

60

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, and WAS

– No infrastructure changes required, no separate LPARs needed

– But you do need to be able to tag and track mobile transactions

Tagging and tracking mobile transactions– Customer must provide evidence a transaction is eligible for MWP and quantify the GP

CPU consumed

– The challenge is to flow a mobile context either implicitly or explicitly with the transaction request and preserve its evidence into the CPU consumption data

– CPU consumption will normally be calculated using data from RMF or SMF

The scenarios in this presentation demonstrates some example ways of tracking CICS mobile transactions and calculating mobile CPU consumption

More information

62

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.

63

Worksheet example

64

Detailed MWRT Reporting Example

Tool will subtract 60% of Mobile MSUs from LPAR original values

5655-S97 CICS TS for z/OS V4

Processor Type Serial 2817-XXXX

Date Time of Interval LPAR Total MSUs Machine

LPAR1 LPAR2 LPAR3 LPAR4 LPAR5 Total02 Nov 2013 - 00:00 UTC 197 354 28 143 198 92002 Nov 2013 - 01:00 UTC 205 329 27 131 180 87202 Nov 2013 - 02:00 UTC 182 280 25 114 143 74402 Nov 2013 - 03:00 UTC 136 213 21 75 81 52602 Nov 2013 - 04:00 UTC 105 172 21 54 68 42002 Nov 2013 - 05:00 UTC 96 184 22 65 84 45102 Nov 2013 - 06:00 UTC 107 181 24 72 90 47402 Nov 2013 - 07:00 UTC 123 183 24 78 100 508

Mobile MSUs Machine

LPAR1 LPAR2 LPAR3 LPAR4 LPAR5 Total79 142 11 57 79 368 82 132 11 52 72 349 73 112 10 46 57 298 54 85 8 30 32 210 42 69 8 22 27 168 38 74 9 26 34 180 43 72 10 29 36 190 49 73 10 31 40 203

1

2

3

Adjusted LPAR Values for Billing Machine

LPAR1 LPAR2 LPAR3 LPAR4 LPAR5 Total150 269 21 109 150 699 156 250 21 100 137 663 138 213 19 87 109 565 103 162 16 57 62 400 80 131 16 41 52 319 73 140 17 49 64 343 81 138 18 55 68 360 93 139 18 59 76 386

Formula for LPAR 1, Interval 1:LPAR1 Total MSUs = 197Mobile only MSUs = 79Subtract 60% of Mobile =(79 * 0.60 = 47)

Adjusted LPAR MSUs:197 – 47 = 150

Adjusted LPAR totals used to determine new monthly peak.

Capture LPAR MSUs(SMF 70 records)

Customer requirement – Provide Mobile MSUs by interval: Customer input with IBM approval. Values provided monthly in CSV format.

4

https://w3-connections.ibm.com/files/app/file/efd841b4-e5e2-41cf-9610-4d409aef0cda

http://www.ibm.com/partnerworld/page/ZSJ03220USEN

© 2014 IBM Corporation65

System z: A first class platform for mobile

Extra

MWP Announcement Letters – 2014-05-06

JP14-0279 JapanLP14-0279 Latin America214-223 United States

AP14-0219 Asia PacificA14-0429 CanadaZP14-0280 Europe, Middle East, Africa

Thank YouYour Feedback is

Important!

Access the InterConnect 2015 Conference CONNECT Attendee Portal to complete your session surveys from your smartphone,

laptop or conference kiosk.

2824 ibm mobile workload pricing: five ways to tag and track your mobile workloads

Technology

ibm hursley

views of ibm

ibm distinguished engineer

customers business

legal advice

legal requirements

services available

disclaimers cont information