making system z the center of enterprise computing€¦ ·  · 2010-08-06making system z the...

23
Making System z the Center of Enterprise Computing Mark Neft Accenture August 5 at 3:00 pm in room 305 Sessions # 7167

Upload: dongoc

Post on 21-May-2018

215 views

Category:

Documents


2 download

TRANSCRIPT

Making System z the Center of Enterprise Computing

Mark Neft Accenture

August 5 at 3:00 pm in room 305Sessions # 7167

Presentation Abstract:

• How to exploit the best aspects of z/OS and Enterprise Virtualization to

create a cost effective and highly reliable application Eco

System. The presentation will use real examples of combining z/OS

and Linux on System z to create a cost effective and highly reliable

enterprise solution. This includes leveraging DB2 with zIIP

engines, and Java, COBOL and Oracle RAC all running on Linux on

System z, to create a simplified and scalable solutions. I will also

highlight some of the cost savings models illustrating how this solution

reduced Oracle software cost by over 80% and mainframe costs by

30% or more.

• Learn how to enable z/OS workload to run on Linux for System z

• Review case studies of Oracle and COBOL application running on

System z

2Copyright © 2010 Accenture All Rights Reserved.

Objectives

• Review the value proposition of the System z in enterprise

computing

• What is Mainframe Optimization

• What are the options on the mainframe

• Uber- virtualization

• Oracle super scaling

• Enabling COBOL - z/OS workload to run on Linux for System z

• The mainframe is not dead and neither is COBOL

3Copyright © 2010 Accenture All Rights Reserved.

Mainframe Optimization (MFO)

• MFO is an approach that positions the best of z/OS to

enable Linux on System z

• Why is it important today?

• Typically the Mainframe is the single largest line-item on an

IT budget

• IT budgets are getting reduced by 10% - 50%

• The mainframe is the logical place to start

• How to reduce costs by 20%-80% without leaving the

mainframe

4Copyright © 2010 Accenture All Rights Reserved.

There are five key aspects to Mainframe Optimization:

1. Understanding your baseline costs

2. Server Consolidation – “Uber-virtualization” of distributed

platform to System z / Linux

3. Oracle Consolidation – Consolidate multiply Oracle

instances onto a smaller foot print and reduce the number

or Oracle licenses

4. Partial Migration – z/OS based applications to Linux on

System z

5Copyright © 2010 Accenture All Rights Reserved.

Mainframe Optimization

6

Copyright © 2010 Accenture All Rights Reserved.

Prioritizing the work and measuring the benefits during the journey

Show the progress using a business view Continuously prioritize the portfolio

1

2

3

4

67

8

9

10

11

12

1314

15

16

1718

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

62

63

64

67

6869

70

66

Effort

Technical

AdequateShort-Term

AdequateLong-Term

inadequate

Accommodate changes in business imperatives

Proactively understand the affects of the different levers within portfolio

Measure and monitor the progress – focus on the quantifiable results

Business focus view showing the results keeps IT

aligned with the changing business imperatives

Illustrative Key of Complexity:

Orange = High Yellow = Medium

Blue = Normal Others = not in scope

Start with Facts

SAN / NAS

Server consolidation - Running the organization in a box

7Copyright © 2010 Accenture All Rights Reserved.

Development

App -01

Development

App -02

Development

App -nn

SCM –

Build Server

Document

Repository

Requirements

Repository

Test Scripts

System Test

App -01

System Test

App -02

System Test

App -nn

UAT Test

App -01

UAT Test

App -02

UAT Test

App -nn

Prod

App -01

Prod

App -02

prod

App -nn

prod

DB-02

Prod

DB-02

Development

Database(s)

Sandbox

Misc

System Test

DB-01

System Test

DB-02

UAT Test

DB-01

UAT Test

DB-02

LP

AR

LP

AR

LP

AR

LP

AR

Virtual hardware platform

DevelopmentDevelopment

Support

System

Integration

User

Acceptance Production

• Levering the tried and true LPAR technologies enables organization to exploit cost effective, scalable,

and stable Open Source deployment

• The ability to co-locate tightly coupled solutions

• The ability to optimize hardware during functional consolidation

• The ability to prioritize (share) hardware to meet business needs now (Dev/Test/Prod)

Value Proposition: Oracle Consolidation

Global Company

• Achieve super scalability on a small footprint

• Oracle software costs reduced by 85%*

• Physical footprint reduced by 80% (3 Racks vs. 15 racks)**

• Background • 2 Node OracleRac Cluster

• >36TB

• Single tables of 3+ Billion rows

• Full primary and foreign keys

• Indexes

• Referential Integrity turned on

• Results Achieved • Over 7 hours the application averaged >240,000 TPS

• Multi-row inserts / updates

• CPU utilization was ~50% on the Oracle server

• Application is Java running on the IFL as well

* Oracle would have required 224 Intel processors to support the same load or 4 node Superdome plus equivalent hardware for just

production DR

** excluding Disk

8Copyright © 2010 Accenture All Rights Reserved.

Consolidate Multiple Oracle Databases in one RAC cluster

9

Oracle - Achieve Super Scalability on a Small Footprint

Copyright © 2010 Accenture All Rights Reserved.

Value Proposition: Application Migration

10

Small Application MigrationA small application currently costing

$1.5M/year to operate becomes $0.1M or a

five year savings of over $6M (Including the

cost of migration)

Partial Application Migration*Moving a portion of a 5,000 MIP application to an

IFL allows a cost reduction of $40-55M and a cost

avoidance savings of $70-$90M

* Patent Pending

•Migrated Application

•Migrated Application

Illustrative cost comparisons:

Example 1:

z/OS $XX/CPU Hour vs IFL $Y.Y/YCPU Hour

•Savin

gs

•Savin

gs

Illustrative cost comparisons:

Example 2:

z/OS engine $ XXX vs. IFL engine XXX / 90

Comparable Intel server required 5-10 more or 2-3x

Savings Delivered in the First Year

$6M savings $100M savings

Copyright © 2010 Accenture All Rights Reserved.

Mainframe Application Configuration Typical

11

MQ

CICS

TRAN01

TRAN0N

Mainframe

Batch

z/OS

Web Services

3270

Copyright © 2010 Accenture All Rights Reserved.

z/OS CICS

TRAN01

Batch

DB/2

sysplex

MQ

Web Services

Mainframe Application Configuration Coexistence with the IFL

12

MQ

CICS

TRAN01

TRAN0N

zIIP

DB/2

sysplex

Daemon / TRAN01IFL

Mainframe

Batch

z/OS

Web Services

DB2 Connect

3270

Copyright © 2010 Accenture All Rights Reserved.

Mainframe Application Configuration Coexistence with the IFL

13

MQ

CICS

TRAN01

TRAN0N

zIIP

DB/2

sysplex

Daemon / TRAN01IFL

Mainframe

Batch

Batch

z/OS

Web Services

DB2 Connect

3270

Copyright © 2010 Accenture All Rights Reserved.

Mainframe Application Configuration Coexistence with the IFL

14

MQ

CICS

TRAN01

TRAN0N

zIIP

DB/2

sysplex

Daemon / TRAN01IFL

Mainframe

Batch

Batch

z/OS

Web Services

Dispatched thread

DB2 Connect

3270

Web Services

Copyright © 2010 Accenture All Rights Reserved.

Mainframe Application Configuration Coexistence with the IFL

15

CICS

TRAN01

TRAN0N

zIIP

DB/2

sysplex

Daemon / TRAN01IFL

Mainframe

Batch

Batch

z/OS

Web Services

Dispatched thread

DB2 Connect

3270

Web Services

Copyright © 2010 Accenture All Rights Reserved.

MQ

MQ

Mainframe Application Configuration Coexistence with the IFL

16

zIIP

DB/2

sysplex

Daemon / TRANsIFL

Mainframe

Batch

z/OS

Dispatched thread

DB2 Connect

Web Services

Copyright © 2010 Accenture All Rights Reserved.

MQ

Mainframe Application Configuration Coexistence with the IFL

17

zIIP

DB/2

sysplex

Daemon / TRANsIFL

Mainframe

Batch

z/OS

Dispatched thread

DB2 Connect

Web Services

Copyright © 2010 Accenture All Rights Reserved.

MQ

Let z/OS enable Linux on System

z to be a safe place for Mission

Critical Enterprise Applications

Summary of CICS Workload Migration

18

• Trans ABC & EFG response time increased from .4s to 12s

• CPU utilization on CECA remained consistent

• XYPA and XYPC decreased (This is good)

• XYOA and XYUA increased (out of scope workload)

• CPU Utilization on CECB remained consistent due to growth in XYOB

and XYUB (out of scope workload)

• CPU Utilization decreased for both CICSONE and BATCHONE work

• XYPA saw largest decrease (savings of 1 engine) ~ 760 MIPS

• XYPC saw decrease (saving of .5 engines) ~ 380 MIPS

• 1705 QAZ jobs ran on 3/17 - 3525 QAZ jobs ran on 6/3

• CPU Utilization for MQ increased 5-7% on all 4 lpars

• CPU Utilization for DDFPTS increased - transactions doubled

• IFL utilization increased from 15% to 60% (This is good)

• ZIIP utilization increased (10% - 20%) (This is a good)

• Coupling Facility Utilization remained consistent

• Requests to QSP0PTSQUEUES1 decreased by 87%

Before After

Summary of CICS Workload Migration

19

• Trans ABC & EFG response time increased from .4s to 12s

• CPU utilization on CECA remained consistent

• XYPA and XYPC decreased (This is good)

• XYOA and XYUA increased (out of scope workload)

• CPU Utilization on CECB remained consistent due to growth in XYOB

and XYUB (out of scope workload)

• CPU Utilization decreased for both CICSONE and BATCHONE work

• XYPA saw largest decrease (savings of 1 engine) ~ 760 MIPS

• XYPC saw decrease (saving of .5 engines) ~ 380 MIPS

• 1705 QAZ jobs ran on 3/17 - 3525 QAZ jobs ran on 6/3

• CPU Utilization for MQ increased 5-7% on all 4 lpars

• CPU Utilization for DDFPTS increased - transactions doubled

• IFL utilization increased from 15% to 60% (This is good)

• ZIIP utilization increased (10% - 20%) (This is a good)

• Coupling Facility Utilization remained consistent

• Requests to QSP0PTSQUEUES1 decreased by 87%

Before After

Dev

SC

M

Syste

m t

est-

1

Syste

m t

est-

2

Ora

cle

–te

st

UA

T

Ora

cle

–U

AT

Perf

test

Ora

cle

–perf

Summary- Uber - Virtualization on a Small Footprint

20Copyright © 2010 Accenture All Rights Reserved.

Lin

ux

Lin

ux

Lin

ux

Lin

ux

Lin

ux

IFLIFLIFLCP CP IFL IFL IFLzIIP

Prod

z/VM

DB

Lin

ux

-D

ata

base

z/OS

IMS

DB2

MQ MQ

Batch

CICSCICS

LPAR - A LPAR - B

z/VMz/VM

Hipersockets 6GB/S

• Leverage existing floor space

• Dynamic load balancing

• Development and test can share the same hardware

• No physical network equipment required to connect internal servers

• Internal servers can remain on separate virtual LANS

• Simplified and reduce cost for DR

Things to watch out for

• Having just senior leadership sponsership is not good enough

• Agree on what the objectives are

• Reduce COST vs GP MIPS vs TOTAL MIPS vs etc…

• Pick something simple to pilot first

• Understand the current production workload and don’t get roped into

supporting things that don’t happen today

• Other things to consider

• Change the code on z/OS and validate the same code works in

both places

• Start setting up the operations early

• Don’t be surprised during testing that you find things that really

don’t work in production today

21

22

Uber-virtulizationeverything that works together under one umbrella

Syste

m z

Ha

rdw

are

Ma

na

ge

me

nt C

on

so

le (

HM

C)

with U

nifie

d R

esourc

e M

anager

zBX

Select IBM Blades

Blade HW Resources

Optimizers

IBM

Sm

art

An

aly

tics O

ptim

ize

r

z HW Resources

z/OS

z/TPF

z/VSETM

Linux onSystem z

Support Element

Linuxon

System z

z/VM

Private High Speed Data Network IEDN

Private Management Network INMNUnified Resource Manager

Private data network (IEDN)

1 All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represents goals and objectives only.

Customer Network Customer Network

System z Host

Linux on System x 1

AIX on POWER7

Data

Po

we

r1

Fu

ture

Off

eri

ng

Fu

ture

Off

eri

ng

Blade Virtualization Blade Virtualization

System z PR/SM™

Contact Information

[email protected]

• Phone: +1 (973)301 -3278

23Copyright © 2010 Accenture All Rights Reserved.