Your SlideShare is downloading. ×
Did Ops Communicate the Problem? Did Dev Fix it Yet?  Get Smarter Tools for Smoother Handoffs
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Did Ops Communicate the Problem? Did Dev Fix it Yet? Get Smarter Tools for Smoother Handoffs

360
views

Published on

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 …

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/ClgjjhVLRNI

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
360
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • This title should take up the entirety of the slide.
  • It use to be in order to get an account balance, you had to call or visit someone or wait for you monthly statement. Industires are now taking those same interfaces, web-enabling them and making them more customer facing. Let’s face it, no customer want’s to bring up a 3270 screen (while possible) on their I-Device to check their account balance, they want sharp mobile app or browser-based app for getting this data and they want this data available 24/7As a result of this transaction are increasing exponentially and these transactions are hitting the mainframe. To provide this 24/7 access to data stored on the mainframe, applications are becoming more and more complex. Application Servers, Webservers, load balancers database servers, Messaging along with the mainframe have all been added to the execution chain. At the same time, the resources that support the mainframe and getting closer and closer to retirement if they have not retired already. The big gigantic vacumn sound you hear decades and decades of expertise exiting the arena. A younger breed of adminstrators has to be brought up to speed quickly and with tools they will A) Use and B) find useful. These people have grown up with the internet and the idea of “green screen” sounds to
  • Voice-over: To find out, Compuware surveyed 304 global executives. They reported short-term operational losses averaging . . .
  • This title should take up the entirety of the slide.
  • Add a tweet this stat social gesture
  • Add a tweet this stat social gesture
  • Add #TechFail to the text treatment
  • This title should take up the entirety of the slide.
  • Stark. Typographical treatment.
  • Transcript

    • 1. January 2014 Did Ops Communicate the Problem? Did Dev Fix It? Get Smarter Tools for Smoother Handoffs Spencer Hallman Jim Liebert
    • 2. The New Normal of Mainframe Applications: Customer-facing Transactions: Increasing Maintaining Applications: Complexity Resources: Transitioning The mainframe platform is under attack! 2
    • 3. 300 Wesurveyed OVER CORPORATE EXECUTIVES F R O M 3 G L O B A L C O M P A N I E S
    • 4. 1 FINDING 4 Pressure is increasing on the mainframe
    • 5. 55% 5 of enterprise applications call upon the mainframe to complete transactions.
    • 6. 91% say performance expectations are increasing… CONSEQUENCES OF POOR PERFORMANCE: • Lost revenue • Loss of employee productivity • Brand and reputation damage 6
    • 7. 2 FINDING 7 Performance problems take too long to resolve …
    • 8. 8 74% say added complexity of applications working across distributed and mainframe environments is making problem resolution take longer.
    • 9. 75% 9 being pressured to reduce mean time to resolution.
    • 10. D AY S IT TAKES 10 TO GET BACK TO NORMAL AFTER A FAILURE.
    • 11. 3 FINDING 11 Tech failures occur at alarming rates
    • 12. 48% 12 report daily performance problems.
    • 13. 81% experienced the same failure multiple times 13
    • 14. FINDING 14 4 Technology silos holding IT back
    • 15. 70% 15 of IT organizations are organized by technology silos.
    • 16. Only 31% 16 see cooperation across technology silos.
    • 17. 81% 17 believe there is a need to bridge gaps so that IT can take a more combined approach to problem solving.
    • 18. WHAT CAN YOU DO? 18
    • 19. • Better tools and processes to find and fix problems • Better collaboration and more automation between the tech silos 19
    • 20. Find: Monitor, Anal yze, Pinpoint • 24/7 transaction monitoring • Faster fault domain isolation • Better root cause analysis 20
    • 21. 29
    • 22. 30
    • 23. 31
    • 24. 32
    • 25. 33
    • 26. Smarter handoffs • Automate the sharing of information • Provide all the analysis • Jumpstart the development process 34
    • 27. 35
    • 28. 36
    • 29. 37
    • 30. 38
    • 31. Dynamic text: • Expert’s opinion on the issue. • The actual suspicious line of code! 39
    • 32. Static information: • Provided by the software (in this case iStrobe) • Answers the rest of the who/what/when questions. 40
    • 33. Static information: • Reference back to the initial problem resource. 41
    • 34. Fix: Recreate, Debug , Test • Intuitive interface • Flow seamlessly between tasks • Real-time control 42
    • 35. 43
    • 36. 44
    • 37. Find & Fix has already built a debug configuration on our behalf. Clicking on it will start a wizard just to verify the settings. 45
    • 38. 46
    • 39. 47
    • 40. Stopped at the suspicious line. Now we can use Xpediter/Eclipse to better understand this point in the code. * Note – since Compuware products share listings, line numbers remain consistent. 49
    • 41. 50
    • 42. 51
    • 43. 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
    • 44. 53
    • 45. Smarter tools for smoother handoffs 54
    • 46. http://www.compuware.com/mainframe 55

    ×