1 how to survive the new normal of mainframe craig hodgins

31
1 How to Survive the New Normal of Mainframe Craig Hodgins

Upload: halie-huckstep

Post on 16-Dec-2015

217 views

Category:

Documents


0 download

TRANSCRIPT

1

How to Survive the New Normal of MainframeCraig Hodgins

22

The World Has Gone Distributed But….

80% of critical data is stored on mainframes

Billions of transactions are executed daily on mainframes

“If every Mach system failed, it would befront page news in the New York Times. But if every MVSsystem failed, the New York Times would not publish. And ifevery MVS system failed for a week, the New York Timeswould never publish again. Western civilization would fallbecause western civilization runs on MVS.”

Bob Rogers, Distinguished Engineer, IBM

33

Applications: Customer-facing

Workforce: TransitioningApplications: More Complex

Transactions: Increasing

The New Normal of Mainframe

44

Applications Are Customer-Facing

55

The Problem

A slow application is considered a down application- we all seem to have ADD nowadays- see The Shallows by Nicholas Carr- see The Brain Rules by John Medina- the 3 second rule

Customers can vote with their feet (or mouse clicks)Outages cost money and make for bad PR

66

The (Potential) Problem is Ubiquitous

Amazon

BankseBay

Retailers

Government

Stock Exchanges

77

The health insurance exchanges created under the Affordable Care Act opened for business today, and people have started hitting the websites. Only one problem: The Obamacare websites weren't working. As of 9:30 a.m., Healthcare.gov informed us: "The System is down at the moment. We're working to resolve the issue as soon as possible. Please try again later."

Obamacare crashes on Oct 1 2013

99

Transactions Are Increasing – Why?

More people use computers today

More people use mobile devices to access their data today

1010

Applications Are More Complex

1212

Transitioning Workforce

COBOL

Green Screen

Record albums

Java

GUI

iTunes

1313

Boomer Statistics

Someone turns 50 every 7 seconds

77 million Boomers in the USA(35% of the population)

8.6 million Boomers in Canada

July 1 2012 the median age in Canada was 40

1st Boomer turned 65 on Jan 1 2011

For the next 20 years 8000 people a day will turn 65

Kathleen Casey-Kirschling, born one second after midnight in Philadelpia on Jan 1 1946

15

The Cost of Poor Performance

“The later performance problems are caught in the life cycle, the more costly

they are to fix. Inefficiencies introduced in design can cost twice as much to fix during programming, four

times more during system testing, and eight times more when the application

enters production.”

Accenture

Detail Design

Programming

System Test

User Test

Production

R e l a t i v e C o s t t o F i x

2x 4x 8x

1616

The Cost of Poor Performance - War Rooms

Can involve 20+ people

Can take hours to days

Finger pointing and defensiveness

Lost productivity

1717

Additional Costs of Poor Performance

• Lost revenue• Penalties in SLA’s

If you don’t monitor your applications, your customers will. Monitoring done by customers is the most expensive kind there is.

1818

The Answer

• Need visibility into the application performance before it becomes critical

• Need timely resolution (identify the root cause)

• Automated

• Intelligent

• Easy

• Integrated

19

• automatically provides the answer in one place for faster and better root cause analysis and ROI

19

We Need Something That…

2020Compuware Confidential

Txn took 295 ms

66% of Exec Time spent in call to Stored Procedure

Without the agent for z/OS, all activity on the Mainframe is a blackbox!

2121Compuware Confidential

off Mainframe Java and .NET code calling

CICS and MQ

on Mainframe Poorly performing mainframe code and SQL

Complete End-to-end Visibility From Mainframe to User

Mainframe ServersInternet/Cloud Last Mile

Real Users

MIPS Growth

Transactions

2222

Case Study: European Bank

22

Off Mainframe MIPS Savings

• Chatty distributed application driving CPU consumption. One business transaction invoked 51 CICS transactions

• Overall CPU consumption reduced by 7.5% through re- architecting the application

Annual savings = $250,000

On Mainframe MIPS Savings

• Bad performing SQL Statement was identified immediately

• Average CPU consumption: what took 3 CPU seconds before was reduced to microseconds after tuning

• 80,000 executions per year

• Associated CPU costs of $2,500 per CPU hour

Annual savings = $170,000

Situation• Company extending e-banking services

• Composite application including distributed and mainframe tiers

• Through new application architecture mainframe transactions are growing significantly

Results

• Enabling teams to resolve performance problems before customers affected

• Meeting requirements of IT auditors to monitorservice quality

• Reducing MTTR

• All performance issues captured

• Transaction details visible through all tiers, from end-user to the mainframe

23

23

Transaction Flow Diagram

24

24

56.69% of CPU at

0098A

CALL CEEGMT (LILIAN, SECONDS, FC);

25

Trend and Summary Reports

25

2626

2727

2828

29

APM Practice Commitment

Level 5Kaizen

Continually evaluate and improve the APM program

Level 4Disciplined

Establish accountability for application performance. Track, measure and report on the APM program

Level 3Processoriented

Define processes for performance evaluation at established checkpoints

Level 2Proactive

Reclaim production resources through repeatable projects

Level 1Chaos Respond to production crises

The APM Capability Maturity Model

Organizational Benefits

30

APM Capability Benefits

APM Practice Commitment

Maintain competitive edge

Level 5Kaizen

Defer upgrades and improve service levelsLevel 2Proactive

Reduce cost of achieving application efficiencyLevel 4

Disciplined

Prevent deployment of inefficient applications Level 3Processoriented

Resolve production crisesLevel 1Chaos

Organizational Benefits

3232

Thank You

• Questions?

• Comments?