YOU ARE DOWNLOADING DOCUMENT

Please tick the box to continue:

Transcript
Page 1: A Pragmatic Approach to DevOps and the Mainframe

A Pragmatic Approach to DevOps and the Mainframe

April 10, 2023

Julie CraigResearch Director, Application Management

Enterprise Management Associates

Page 2: A Pragmatic Approach to DevOps and the Mainframe

Today’s Speakers

SPENCER HALLMANSubject Matter Expert

Compuware MIPS Management

JULIE CRAIGResearch Director

Enterprise Management Associates

JIM LIEBERTSubject Matter Expert

Compuware Developer Productivity

Page 3: A Pragmatic Approach to DevOps and the Mainframe

Agenda

• IT, DevOps, and Business Value• The Mainframe in the Enterprise• DevOps Challenges in the Mainframe-driven Company• “DevOps Ready” Tools in Mainframe Environments• Compuware DevOps Solution and Demonstration• Summary and wrap-up

Slide 3 © 2014 Enterprise Management Associates, Inc.

Page 4: A Pragmatic Approach to DevOps and the Mainframe

What is “DevOps”?

• DevOps defined differently by virtually everyone• EMA Definition: “The ideal intersection of people, processes, and

tools necessary to facilitate cross-functional collaboration across the application lifecycle and enable the seamless delivery of applications to the business”.

• Purpose: To optimize levels of service delivered to internal and external customers by efficiently supporting the complexities of modern application ecosystems

Slide 4 © 2014 Enterprise Management Associates, Inc.

Page 5: A Pragmatic Approach to DevOps and the Mainframe

• Per latest EMA Application Management research, 80% of companies have DevOps function*• Question: “Does your company utilize a team-based approach

leveraging specialists with cross-functional development and operational skills to address application-related issues?”

• Dedicated in 56% of companies, AdHoc in 44%

• Teams performing DevOps functions typically go by other names: “Application Support”, “Application Management”, “Infrastructure Services”

Slide 5 © 2014 Enterprise Management Associates, Inc.

DevOps Practices: Bridging Silos Across the Application Lifecycle

*Q4 2013

Page 6: A Pragmatic Approach to DevOps and the Mainframe

• Application-focused (versus silo-focused) IT• Parallels the customer’s application perspective versus IT’s infrastructure

perspective

• Improved continuity across software lifecycle stages, i.e. Dev to Prod, Prod back to Dev• Collaborative application deployment, testing, support optimize the processes

associated with delivering business services

• “Top down” approach (versus “bottom up” silo approach) reduces time and effort required for root cause analysis of application-related problems• Combining Dev and Ops skills within a single team leads to faster resolution of

code-based AND infrastructure-based production issues

• DevOps is foundation for Continuous Delivery of new software features and functions• Accelerating delivery of software-driven products and features can significantly

impact business bottom line

Slide 6 © 2014 Enterprise Management Associates, Inc.

DevOps Benefits

Page 7: A Pragmatic Approach to DevOps and the Mainframe

EMA Research: Better Interactions between Dev and Ops Translate to Higher Revenue Growth

Slide 7 © 2014 Enterprise Management Associates, Inc.

Q: “How would you describe the quality of the overall day-to-day interaction between Development and Operations generally at your company?"

87%

13%

Increased more than 10%

Excellent/Above

Average/Below

Q: “What was the YOY percentage increase or decrease of your organization’s annual revenue compared to last year?”

Page 8: A Pragmatic Approach to DevOps and the Mainframe

Agenda

• IT, DevOps, and Business Value• The Mainframe in the Enterprise• DevOps Challenges in the Mainframe-driven Company• “DevOps Ready” Tools in Mainframe Environments• Compuware DevOps Solution and Demonstration• Summary and wrap-up

Slide 8 © 2014 Enterprise Management Associates, Inc.

Page 9: A Pragmatic Approach to DevOps and the Mainframe

More than Half of Today’s Companies are Running Mainframes

Slide 9 © 2014 Enterprise Management Associates, Inc.

Which of the following technologies does your organization host on-premise?

Virtualization

Data Integration

Mainframe

Linux

Private Cloud

Enterprise Service Bus (ESB) and/or Enterprise Application In-tegration (EAI)

Middleware such as IBM WebSphere

Other UNIX (Other than Linux)

LAMP

Hadoop

72%

54%

51%

48%

43%

41%

41%

29%

8%

7%

Page 10: A Pragmatic Approach to DevOps and the Mainframe

The Mainframe is a Mainstay of Distributed Application Ecosystems

Slide 10 © 2014 Enterprise Management Associates, Inc.

Which of the following types of transactions or applications is your organization running?

Tiered, distributed transactions/applications that span both mainframe and non-mainframe servers

Hybrid mainframe/public Cloud transactions/applications

All of the above

Tiered, distributed transactions/applications that do not access a mainframe

Non-tiered transactions/applications that access mainframe only

40%

22%

18%

12%

8%

Page 11: A Pragmatic Approach to DevOps and the Mainframe

DEBUNKED

Mainframe Fallacies Debunked

Slide 11 © 2014 Enterprise Management Associates, Inc.

Doesn’t “play well with others”

“On its way out”

DEBUNKED

“Irrelevant”

Not part of the “Distributed World”DEBUNKED

“Not Cloud friendly”

DEBUNKED

DEBUNKED

Page 12: A Pragmatic Approach to DevOps and the Mainframe

Agenda

• IT, DevOps, and Business Value• The Mainframe in the Enterprise• DevOps Challenges in the Mainframe-driven Company• “DevOps Ready” Tools in Mainframe Environments• Compuware DevOps Solution and Demonstration• Summary and wrap-up

Slide 12 © 2014 Enterprise Management Associates, Inc.

Page 13: A Pragmatic Approach to DevOps and the Mainframe

Top Challenges of Application Support Professionals

Slide 13 © 2014 Enterprise Management Associates, Inc.

• The top three application-related challenges cited by application support teams include:

• Slow performance• Intermittent problems, causes unknown• High fixed costs related to application support

• A majority say “troubleshooting takes too long”• Almost 50% cite a lack of visibility to application topologies and

dependencies

Page 14: A Pragmatic Approach to DevOps and the Mainframe

Mainframe-specific Challenges

• Mainframe “isolation” • Lack of physical access to mainframe, consoles, and mainframe

execution information• Mainframe itself centralized and may well be in a different location from

support personnel

• Lack of mainframe knowledge• Mainframe know-how confined to a “select few”• Mainframe operations personnel have unique skill sets and “languages”• Mainframe developers use unfamiliar languages• Concepts such as queues, batch, time-slicing, etc. are a “foreign

language” to non-mainframe personnel

• Bottom line: Mainframe is a “black box” to most application support teams

Slide 14 © 2014 Enterprise Management Associates, Inc.

Page 15: A Pragmatic Approach to DevOps and the Mainframe

Agenda

• IT, DevOps, and Business Value• The Mainframe in the Enterprise• DevOps Challenges in the Mainframe-driven Company• “DevOps Ready” Tools in Mainframe Environments• Compuware DevOps Solution and Demonstration• Summary and wrap-up

Slide 15 © 2014 Enterprise Management Associates, Inc.

Page 16: A Pragmatic Approach to DevOps and the Mainframe

“APM” and the Mainframe: Do you Know What You are Buying?

• APM(onitoring) versus APM(anagement)• Both Monitoring and Management tools measure performance and availability

“End to end” coverage is a subjective term, based on the vendor’s coverage of the application ecosystem

• However management tools ALSO provide guidance for troubleshooting and root cause analysis of application-related issues

• Most Application Performance Management tools have little or no visibility to mainframe execution

• IT professionals tell us:• “With no mainframe support, this is NOT an enterprise tool.”• “The lack of mainframe support was a huge loss of political credibility for me.

Now, this is our #1 gap.”• “We have too many separate applications trying to interact—and they don’t

always work.”

Slide 16 © 2014 Enterprise Management Associates, Inc.

Page 17: A Pragmatic Approach to DevOps and the Mainframe

DevOps-ready Tools Have Value across the Lifecycle

Slide 17 © 2014 Enterprise Management Associates, Inc.

Stage Value Proposition

Develop Testing for performance optimization of new applications

Test Pre-prod service assurance

Deploy Release planning, post-deployment service assurance

Manage Performance & availability monitoring, management, and troubleshooting

Assess Monitor/manage and assess service levels (SLM) for continuous improvement

Design Modify existing software based on assessed service levels (or create new software) to continually improve quality of service delivered to the business

Page 18: A Pragmatic Approach to DevOps and the Mainframe

Agenda

• IT, DevOps, and Business Value• The Mainframe in the Enterprise• DevOps Challenges in the Mainframe-driven Company• “DevOps Ready” Tools in Mainframe Environments• Compuware DevOps Solution and Demonstration• Summary and wrap-up

Slide 18 © 2014 Enterprise Management Associates, Inc.

Page 19: A Pragmatic Approach to DevOps and the Mainframe

Smarter tools

Smoother handoffs

19

Page 20: A Pragmatic Approach to DevOps and the Mainframe

Application Performance Managementwith Strobe

Quality assurance

Fighting fires Improving existing production

applications

Monitoring new enhancements

Evaluating third party products

Measuring jobs during development

Page 21: A Pragmatic Approach to DevOps and the Mainframe

Based on previous data collected this Txn is exceeding the benchmark previously set

Benchmark Date

Page 22: A Pragmatic Approach to DevOps and the Mainframe

Drill down to the Profile!

Hyperlinked to the underlying iStrobe Profile

Page 23: A Pragmatic Approach to DevOps and the Mainframe
Page 24: A Pragmatic Approach to DevOps and the Mainframe
Page 25: A Pragmatic Approach to DevOps and the Mainframe

25

Page 26: A Pragmatic Approach to DevOps and the Mainframe

26

Page 27: A Pragmatic Approach to DevOps and the Mainframe

27

Page 28: A Pragmatic Approach to DevOps and the Mainframe

28

Page 29: A Pragmatic Approach to DevOps and the Mainframe

29

Page 30: A Pragmatic Approach to DevOps and the Mainframe

30

Dynamic text:

• Expert’s opinion on the issue.• The actual suspicious line of code!

Page 31: A Pragmatic Approach to DevOps and the Mainframe

31

Static information:

• Provided by the software (in this case iStrobe)• Answers the rest of the who/what/when questions.

Page 32: A Pragmatic Approach to DevOps and the Mainframe

32

Static information:

• Reference back to the initial problem resource.

Page 33: A Pragmatic Approach to DevOps and the Mainframe

33

Page 34: A Pragmatic Approach to DevOps and the Mainframe

34

Page 35: A Pragmatic Approach to DevOps and the Mainframe

35

Find & Fix has already built a debug configuration on our behalf.

Clicking on it will start a wizard just to verify the settings.

Page 36: A Pragmatic Approach to DevOps and the Mainframe

36

Page 37: A Pragmatic Approach to DevOps and the Mainframe

37

Page 38: A Pragmatic Approach to DevOps and the Mainframe
Page 39: A Pragmatic Approach to DevOps and the Mainframe

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.

39

Page 40: A Pragmatic Approach to DevOps and the Mainframe

40

Page 41: A Pragmatic Approach to DevOps and the Mainframe

41

Page 42: A Pragmatic Approach to DevOps and the Mainframe

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?

42

Page 43: A Pragmatic Approach to DevOps and the Mainframe

Smarter tools for smoother handoffs

43

Page 44: A Pragmatic Approach to DevOps and the Mainframe

Agenda

• IT, DevOps, and Business Value• The Mainframe in the Enterprise• DevOps Challenges in the Mainframe-driven Company• “DevOps Ready” Tools in Mainframe Environments• Compuware DevOps Solution and Demonstration• Summary and wrap-up

Slide 44 © 2014 Enterprise Management Associates, Inc.

Page 45: A Pragmatic Approach to DevOps and the Mainframe

Wrap-up

• Twin tools-related challenges in mainframe-driven companies• “End to end” visibility to transactions and applications• “End to end” visibility to underlying mainframe and servers

“Mainframe ready” APM tools must mesh the two

• Key considerations related to DevOps tools selections• Equipping personnel who have minimal mainframe expertise with the

knowledge they need to do application support• Facilitating smooth communication and interactions between Dev and Ops

across the lifecycle

• Tools decision making• Be aware (“beware”):

Many application-focused tools are not “mainframe ready” Many application-focused tools don’t have the “information sharing” capabilities

necessary to support mainframe DevOps practices

• Objective: Tools unify Dev and Ops to deliver quality applications and services to the business

Slide 45 © 2014 Enterprise Management Associates, Inc.

Page 47: A Pragmatic Approach to DevOps and the Mainframe

For more information on Enterprise Management Associates, please go to www.enterprisemanagement.com, or call +1 303-543-9500

Thank you for attendingtoday’s presentation

© 2014 Enterprise Management Associates, Inc.


Related Documents