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

April 27, 2017

In a movement that has gained momentum as quickly as DevOps has, it's always good to stop from time to time and evaluate where we are, where we have come from, and where we are going. We asked four industry experts some questions about the progress of ALM and DevOps ...

April 26, 2017

It's easy to ignore downtime. But ignoring downtime is a surefire way to upset your customers and your colleagues. More and more, teams need to think about shipping stellar experiences. Proper incident response is a great place to start ...

April 24, 2017

The expectation of regular software updates – it's what developers are tasked with, and what users expect and demand. Increased functionality, better performance, and fewer bugs – often in a week or less. Automation of critical processes such as QA can help meet the gargantuan task of constant updates, but it can also send your software into a death spiral of user abandonment unless deployed correctly ...

April 20, 2017

One could argue that testing is the most important phase of an IT project. It's also time-consuming and expensive. It's essential to strike a balance between an IT testing program that ensures a quality product and the cost-to-value ratio of your project. But when you're dealing with replatforming projects, how much testing is enough testing? ...

April 18, 2017

Whether through formal methods such as classroom or virtual training, job shadowing, and mentoring; or through informal methods such as team discussions or presentations, teaching needs to be a frequent element of team integration. It is a given that IT and business teams have difficulty understanding each other without a common taxonomy. Even teams within IT often fail to understand each other ...

April 17, 2017

Although DBAs fortunately have the rare ability to bridge the gap between development and operations, they have been detrimentally overlooked in many companies that deploy DevOps practices. A DBA's ability to interrogate code and construct a resilient, well–performing database environment uniquely defines the capabilities needed for DevOps – leaving me perplexed about why DBAs were not one of the first operations team members asked to join the DevOps movement ...

April 12, 2017

DEVOPSdigest asked experts across the industry — including analysts, consultants and vendors — for their opinions on the best way for a development or DevOps team to become more Agile. Part 5, the final installment in this series, provides tips on empowering people ...

April 10, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 4 covers DevOps technologies ...

April 07, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 3 provides some tips for getting started and gaining feedback ...

April 05, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 2 covers processes including automation, continuous delivery and testing ..

Share this