How to Survive the New Normal of Mainframe

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

2. 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 be front page news in the New York Times. But if every MVS system failed, the New York Times would not publish. And if every MVS system failed for a week, the New York Times would never publish again. Western civilization would fall because western civilization runs on MVS.” Bob Rogers, Distinguished Engineer, IBM

3. The New Normal of Mainframe Applications: Customer-facing Transactions: Increasing Applications: More Complex Workforce: Transitioning

4. Applications Are Customer-Facing

5. 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

6. The (Potential) Problem is Ubiquitous Amazon Banks eBay Retailers Government Stock Exchanges

7. Obamacare crashes on Oct 1 2013 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."

8. Transactions are Increasing

9. Transactions Are Increasing – Why? More people use computers today More people use mobile devices to access their data today

10. Applications Are More Complex

12. Transitioning Workforce COBOL Green Screen Record albums Java GUI iTunes

13. Boomer Statistics 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 Kathleen Casey-Kirschling, born one second after midnight in Philadelpia on Jan 1 1946 Someone turns 50 every 7 seconds For the next 20 years 8000 people a day will turn 65

14. 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 2x 4x 8x R e l a t i v e C o s t t o F i x

15. The Cost of Poor Performance - War Rooms Can involve 20+ people Can take hours to days Finger pointing and defensiveness Lost productivity

16. 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.

17. The Answer • Need visibility into the application performance before it becomes critical • Need timely resolution (identify the root cause) • Automated • Intelligent • Easy • Integrated

18. We Need Something That… • automatically provides the answer in one place for faster and betterroot cause analysis and ROI

19. 66% of Exec Time spent in call to Stored Procedure Txn took 295 ms Without the agent for z/OS, all activity on the Mainframe is a blackbox!

20. Complete End-to-end Visibility From Mainframe to User Internet/Cloud Real Users Mainframe Servers Last Mile Transactions MIPS Growth • off Mainframe • Java and .NET code callingCICS and MQ • onMainframe • Poorly performing mainframe code and SQL

21. Case Study: European Bank On Mainframe MIPS Savings Off 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 • Situation • Company extending e-banking services • Composite application including distributed and mainframe tiers • Through new application architecture mainframe transactions are growing significantly • 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 • 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 Annual savings = $170,000

22. Transaction Flow Diagram

23. 56.69% of CPU at 0098A CALL CEEGMT (LILIAN, SECONDS, FC);

24. Trend and Summary Reports

28. 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 3Process oriented 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 APM Practice Commitment Organizational Benefits

29. Level 5Kaizen Maintain competitive edge Level 4Disciplined Reduce cost of achieving application efficiency Level 3Process oriented Prevent deployment of inefficient applications Level 2Proactive Defer upgrades and improve service levels Level 1Chaos Resolve production crises APM CapabilityBenefits APM Practice Commitment Organizational Benefits

30. A Final Thought…. Computers are useless. They can only give you answers. Pablo Picasso

31. Thank You • Questions? • Comments?