Embrace, Evolve and Nurture - The Keys to Mainframe DevOps
March 27, 2017

Chris O'Malley
Compuware

BMC's recent 2016 Mainframe Research Report showed these systems are essential in helping drive digital transformation, with superior reliability, performance and security cited as the key factors influencing mainframe investments.

■ 58 percent of respondents report higher mainframe transaction volumes

■ 67 percent see greater use of Java on the mainframe

■ 89 percent predict long-term staying power

■ 88 percent note their companies plan to maintain or increase mainframe capacity

Another survey, conducted by Forrester and commissioned by Compuware supported these findings, showing 96 percent of new business initiatives involve the mainframe. However, the platform is not without challenges. The survey also revealed frustration and concern among development leaders, particularly when it comes to their team's ability to accommodate the speed and agility required to compete in today's digital market.

Forrester polled 182 leaders responsible for both mainframe and non-mainframe development, and found 90 percent experience challenges in developing and delivering applications on the mainframe. This leads to long release cycles for customer-facing apps, downscaling of product features to meet deadlines, and expensive workarounds using other technologies.

90 percent of respondents also reported their mainframe application development is hampered by organizational bureaucracy, internal silos that create bottlenecks, quality issues and insufficient funding.

Among the other findings:

■ 48 percent move some applications off the mainframe, but suffer from "buyer's remorse" in discovering that converted application are less secure, have higher costs, are less performant and cause even greater project delays.

■ 41 percent attempt to work around the mainframe. This leads to greater complexity, higher costs, duplicate tooling, increased technical debt and increased security risks.

■ 40 percent attempt to modernize on the mainframe platform, but struggle with long transition times, Java performance issues and inadequate tools to help with application understanding (i.e., identifying how changes made to one application or data set will impact others).

Mainframe organizations are in a state of perplexing cognitive dissonance. They understand the critical, irreplaceable role of the mainframe in supporting digital transformation and innovation. They know trying to migrate away is an exercise in futility. They know the mainframe can deliver compelling cost and performance advantages in supporting high-volume, mission-critical transactional applications.

Yet these users are still struggling to seamlessly integrate mainframes into their broader DevOps efforts, where complexity and unfamiliarity are stalling software rollouts and hurting their efforts to improve customer experiences. Exacerbating the situation, many aging mainframe experts who delayed workforce exits as a result of the "great recession" are now finally retiring, leaving a huge mentorship void for newer developers and lost tribal knowledge of an enterprises' unique mainframe systems.

There is encouraging news though. Organizations that successfully modernize the mainframe by applying DevOps best practices experience significant benefits. More than 40 percent of the Forrester survey respondents noted that such practices have resulted in shorter development cycles and faster response to business needs. In addition, 35 percent are achieving improved customer experiences while 34 percent are realizing cost savings by embracing innovations in mainframe DevOps.

There is no more avoiding reality. For enterprises adopting DevOps, there is only one logical and practical road ahead – embrace the mainframe, commit to evolving and nurturing it, and incorporate it fully into enterprise DevOps practices. There are three key requirements for doing this.

1. Efface borderlines between mainframes and other platforms

As stated above, today's applications are increasingly multi-platform, meaning they span several types of systems before ultimately landing on a mainframe for transaction completion. Consider a retail ecommerce transaction, whereby a customer accesses the site through a web server, navigates the product offerings, completes an order and shipping form and ultimately executes a transaction. Various parts of this multi-step application are executing on different platforms, but it is still a single product. To properly develop and support these applications, system and team demarcations should be virtually invisible and irrelevant, as development teams focus their collective attention on creating the most innovative, high-performing end-to-end solutions.

2. Comprehensive tool modernization

Many organizations take their first steps in eliminating borders by replacing the antiquated mainframe "green screen" with a more modern, familiar user interface. This modernized workspace should look and feel like Eclipse-style IDEs that are standard for other platforms. In doing so, development staff at all levels will be able to greatly reduce, if not eliminate the need to access their old green screen-based tools. But it doesn't stop there, as modern developers also need the tools they use in the mainframe environment to be similar to —or the same as— those they use on other platforms. This allows them to work nimbly, deftly and confidently across platforms, and includes capabilities like real automated unit testing, and visualization that enables them to easily see complex interdependencies between applications and data.

3. Successfully attract a new generation of talent

As baby boomers leave the workplace, it is largely up to new development talent (i.e. millennials) to drive ongoing innovation on mainframe systems. Mainframe skills aren't included in most university computer science programs, making new graduates with these types of skills extremely rare. Mainframe-based companies can capitalize on this, showing new developers how they can not only make a huge impact in industries that rely on mainframe technology, but also enjoy a solid career path. Attracting new developer talent is essential for large enterprises to compete, so they need to invest here – providing developers with the modern tools they love, and encouraging platform-agnostic developer-to-developer interaction. This type of collaboration is a hallmark of the DevOps movement, and excites and entices millennial workers.

Conclusion

Mainframe DevOps teams can be just as quick and agile as non-mainframe users, but with the added leverage of superior cost-efficiency and performance. Numerous studies have shown that the less centralized and more distributed a computing solution is, the higher the total cost tends to be. In fact, the x86 systems industry is constantly trying to create this more centralized view of distributed systems – a major benefit the mainframe has always provided.

Rather than ignoring or sidestepping the mainframe, most organizations would be better served by committing to their mainframes and including them fully in DevOps practices. This will require time, effort and the right leadership mindset, but the returns will be substantial. Modernization, combined with a "development without borders" approach and an emphasis on attracting and nurturing mainframe talent, can help mainframe users realize the long-term competitive advantages of their investments.

Chris O'Malley is CEO of Compuware.

The Latest

June 28, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 5, the final installment, covers how Agile improves product quality and the customer experience ...

June 26, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 4 covers how Agile impacts team productivity ...

June 23, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 3 covers how Agile enables you to grow and adapt to change ...

June 21, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 2 is all about speed ...

June 19, 2017

Earlier this year, DEVOPSdigest featured a list of expert opinions on the essential steps to become agile. Now that we have an idea on how to achieve agility, however, we have to consider why. What's the payoff? With this question in mind, DEVOPSdigest asked the experts — including analysts, consultants and vendors — for their opinions on what are the most important advantages of being Agile ...

June 15, 2017

In the development community, creating additional efficiency through improved collaboration has been prevalent for some time. But despite the head start on the rest of the corporate world when it comes to collaboration, many organizations function today as they did 15-20 years ago. Since time is money in the tech world, outdated collaboration is a huge missed opportunity ...

June 14, 2017

Given the efforts we put in these days to deconstructing monolithic applications, and using distributed microservices to make us more agile, the potential for app performance to take a nosedive because of unseen (and unanticipated) network congestion and outages is only getting greater. There is help at hand, though, in the form of new ways to program network awareness directly into your code ...

June 12, 2017

What if you discover a fatal error or an exploit in your app? What if your app is down during a crucial time? As a developer, how you react to a crisis can mean the difference between minor blip and an embarrassing or costly company blunder. Here's a crisis management plan to get things right when they go wrong ...

June 08, 2017

Recently, the results from SmartBear Software's annual survey, the State of Code Review 2017: Trends & Insights into Dev Collaboration were released. One point I found interesting is that it suggests only 66 percent of organizations can get releases out on time. Why are the other 34 percent struggling to get releases out the door? ...

June 06, 2017

Today's app development landscape is competitive and expensive. Thousands of apps are released each month, and user acquisition and retention are costing app developers millions. User abandonment is one of the main battles of every app developer — as every lost user means another wasted investment ...

Share this