did ops communicate the problem? did dev fix it yet? get smarter tools for smoother handoffs
DESCRIPTION
Improve the way IT and DevOps teams collaborate when resolving application exceptions and performance problems. Unprecedented levels of integration now enable the automated capture of detailed information about an issue, enabling development teams to jumpstart the resolution process and accelerate the delivery of IT services. Watch the full webcast at: http://youtu.be/ClgjjhVLRNITRANSCRIPT
Did Ops Communicate the Problem? Did Dev Fix It?Get Smarter Tools for Smoother Handoffs
Spencer HallmanJim Liebert
January 2014
The New Normal of Mainframe
The mainframe platform is under attack!
Applications: Customer-facing Transactions: Increasing
Maintaining Applications: Complexity Resources: Transitioning
2
300CORPORATEEXECUTIVESFROM GLOBAL COMPANIES
We surveyed
3
OVER
1 Pressure is increasing on the mainframe
FINDING
4
55% of enterprise applications call upon the mainframe to complete transactions.55%
5
91% say performance expectations are increasing…
CONSEQUENCES OF POOR PERFORMANCE:
• Lost revenue• Loss of employee productivity• Brand and reputation damage
6
2 Performance problems take too long to resolve …FINDING
7
74% say added complexity of applications working across distributed and mainframe environments is making problem resolution take longer.
8
75% being pressured to reduce mean time to resolution.
9
21IT TAKES
TO GET BACK TO NORMALAFTER A FAILURE.
DA
YS
10
3 Tech failures occur at alarming rates
FINDING
11
12
48% report daily performance problems.
13
81% experienced the same failure multiple times
4 Technology silos holding IT back
FINDING
14
15
70% of IT organizations are organized by technology silos.
16
31% see cooperation across technology silos.
Only
17
81%believe there is a need to bridge gaps so that IT can take a more combined approach to problem solving.
WHAT CAN YOU DO?
18
• Better tools and processes
to find and fix problems• Better collaboration
and more automation between the tech silos
19
Find: Monitor, Analyze, Pinpoint• 24/7 transaction monitoring• Faster fault domain isolation• Better root cause analysis
20
29
30
31
32
33
Smarter handoffs
• Automate the sharing of information• Provide all the analysis • Jumpstart the development process
34
35
36
37
38
39
Dynamic text:
• Expert’s opinion on the issue.• The actual suspicious line of code!
40
Static information:
• Provided by the software (in this case iStrobe)• Answers the rest of the who/what/when questions.
41
Static information:
• Reference back to the initial problem resource.
Fix: Re-create,
Debug, Test
• Intuitive interface• Flow seamlessly
between tasks• Real-time control
42
43
44
45
Find & Fix has already built a debug configuration on our behalf.
Clicking on it will start a wizard just to verify the settings.
46
47
Stopped at the suspicious line. Nowwe can use Xpediter/Eclipse to better understand this point in the code.
* Note – since Compuware products share listings, line numbers remain consistent.
49
50
51
Well on our way to fixing this problem:
1. Does the COBOL function need to be in a loop?2. Why is the paragraph executed 500 times in one transaction?
52
53
54
Smarter tools for
smoother handoffs
QUESTIONS?
55
http://www.compuware.com/mainframe