BMC and Compuware: Integrating to Improve Mainframe Economics
43
1 G Jay Lipovich, BMC ZSolutions Optimization Neil Blagrave, BMC ZSolutions Optimization Spencer Hallman, Compuware Corporation May 14, 2015 BMC and Compuware: Integrating to Improve Mainframe Economics
Transcript of BMC and Compuware: Integrating to Improve Mainframe Economics
1
G Jay Lipovich, BMC ZSolutions OptimizationNeil Blagrave, BMC ZSolutions OptimizationSpencer Hallman, Compuware Corporation May 14, 2015
BMC and Compuware:Integrating to Improve Mainframe Economics
2
Agenda
• Mainframe Challenges of Digital Business• Mainframe Cost Drivers• BMC and Compuware Integration for Cost
Optimization• Integration Use Cases• Summary
3
MobilityAutomationInternet of Things
PlatformComponents
Analytics
4
Mainframe: The Foundation for Digital Business
91%
5
The Disruptive ForcesDigital Business Impact on Mainframe IT
Cost Data Infrastructure
6
Key Mainframe Metrics 2005 - 2014
Cost/MIPSMF % of IT SpendHW % of spendPersonnel % of SpendMF % of IT FTEsSW % of spend
The Disruptive ForcesImpact on Mainframe IT: Cost
“Do more with less” => “Do everything, cheaper”
7
The Disruptive ForcesImpact on Mainframe IT: Data• 24x7 – zero outage• Explosion of data• New data types• Capitalize for faster time to
market and market share
“This isn’t yesterday’s DB2”
8
The Disruptive ForcesImpact on Mainframe IT: Infrastructure
• New access patterns• Unpredictable activity and volumes• Increased performance and
availability expectations• Spot, triage, fix - proactively
“We no longer know what we used to know”
9
Top IT PrioritiesIT Cost Reduction/ Optimization
Application Availability
Application Modernization
Data Privacy
Business/IT Alignment
Cloud Implementation
Data Recovery
Mobility
Big Data
Outsourcing
Other
70%
52%
48%
47%
44%
34%
34%
27%
26%
16%
3%
IT cost reduction/optimization is the #1 priority with 70% of the respondents indicating so
Application Availability (52%) and Application Modernization (48%) take the 2nd and 3rd spots
Source: BMC 2014 Mainframe Survey
Reducing resource during peak processing intervals was cited as the most important priority for reducing mainframe costs
10
What Drives Mainframe Costs?
IBM MLC cost
Hardware/software
11
Attendee Poll Which of these solutions are
you currently using? Cost Analyzer (CAzE) MainView Strobe Not sure None of them
12
BMC and Compuware Partnership
Marketing and technology partnership of two leading ISV’s - Vested interest in mainframe’s present and future
- Dedicated to innovation for customer value and ROI
Combined portfolios provide synergistic connection points without overlapping
Standardizing on each other’s products for application development and operations
13
Partnership Basis
Integration of intelligent workload (BMC) and performance management and tuning (Compuware) enables customers to discover and exploit opportunities for greater cost savings
Tuning workloads running during peak 4HRA is a top activity for reducing MSUs
14
Solutions
+Compuware Strobe
• Pinpoints application inefficiencies causing excessive CPU consumption
• Reduces hardware and software costs while increasing customer satisfaction
BMC Cost Analyzer for zEnterprise (CAzE)
• Provides transparency and insight into MLC costs with what-if capabilities to determine impact of MLC reduction activities
BMC MainView
• Provides proactive monitoring, automated problem solving and storage solutions
15
Use Case Overview
# Focus Use Case Integration
1 Proactive Cost Management
Identify MLC cost-saving tuning opportunities
Launch iStrobe directly from CAzE
2
MTTR andCost
Reduction
a) Automated, alarm-based deep dive performance analysis on abnormal app activity
MainView for z/OS triggers Strobe Analysis
b) Quickly request deep dive performance analysis on poorly performing job or app
Launch Strobe analysis directly from MainView from view JCPU
16
Identify MLC Cost-saving Tuning Opportunities
Problem- Pinpoint specific
performance tuning opportunities yielding greatest reduction in IBM MLC charges
USE CASE 1
17
Identify MLC Cost-saving Tuning Opportunities
Solution- CAzE determines biggest MLC-
impacting R4HA periods- Directly launch iStrobe during
CAzE R4HA drill down for deeper analysis into specific components contributing to CPU consumption
- iStrobe analysis combined with CAzE information reveals potential financial impact of tuning efforts
USE CASE 1
18
Identify MLC Cost-saving Tuning Opportunities
Value • Integration enables customers to
quickly identify and assess potential benefits of performance tuning efforts
• Thereby, reducing MLC expenses
USE CASE 1
19
Understand MLC cost base and investigate cost drivers
20
See primary LPARs contributing to peak and investigate workloads driving MLC costs
21
Focus in on the 4HRA peak for the month
22
Strobe Request
DB2ADB2BSJSCSJSESYSN
Launch Strobe in CAzE Workload View for detailed analysis
23
24
25
Strobe measurements captured during 4RHA
26
Strobe Advisor provides possible solution to address issue
27
Model cost savings of optimizing code with Strobe
28
Workload contribution is reduced and z/OS peak 4 hour average is reduced by 180 MSUs
29
Savings = $32K/month ($384K/year)
30
Automated Problem Identification and AnalysisUSE CASE 2a
Problem– Quickly identify and resolve
abnormal application performance activity
31
Automated Problem Identification and AnalysisUSE CASE 2a
Solution– In MainView, set alarm to check for
suspected loop criteria– Issue Alarm and WTO when initial
criteria is met– Strobe analysis is automatically launched
from MainView Alarm Manager
32
Automated Problem Identification and AnalysisUSE CASE 2a
Value – Significantly reduce MTTR
required for determining root cause of abnormal performance condition
– Automation ensures timeliness and eliminates resource restrictions
33
Problem- Customer defines criteria
in MainView where job may be looping
- Once criteria is met (e.g. CPU 95% and no I/O etc.), schedule more in-depth analysis on suspected job
Quickly Initiate Deep Dive AnalysisUSE CASE 2b
34
Solution– Use JCPU view in
MainView for z/OS • Right-click row with suspected
looping job • Select iStrobe hyperlink to
initiate Strobe analysis
Quickly Initiate Deep Dive AnalysisUSE CASE 2b
35
Quickly Initiate Deep Dive AnalysisUSE CASE 2b
Value – Initiate Strobe’s deeper
analysis with a simple point and click in MainView to determine where issue is looping in program code
36
Jobname SPHSCH0X is using a lot of CPU
Right-click on Job Tot CPU Time to launch Strobe measurement
37
38
Job name is included on iStrobe measurement screen
39
Attendee Poll
What solutions discussed today are of interest to you? Cost Analyzer (CAzE) MainView Strobe None at this time
40
What to Expect
Initial product integration planned for July delivery- CAzE to Strobe- MainView to Strobe
Long-term partnership - Other use cases in development
41
Summary Focus application tuning on areas that
will yield greatest cost savings Quantify benefits and justify tuning
efforts Dynamically spot “hot” code tuning
opportunities Simplify code monitoring process to
reduce effort and speed results
Leverage existing investments
Expand capabilities
42
Q&A
To learn more:
Cost Analyzer and MainView www.bmc.com/mco
Strobe Compuware.com/contact
42
43
Thank You
43
