Getting the Mainframe Up to DevOps Speed
January 23, 2017

Chris O'Malley
Compuware

Until recently, many IT leaders still believed they could allow their mainframe environments to languish in two-code-drops-a-year waterfall mode, while they embraced DevOps and Agile across their distributed and cloud environments.

This so-called "Bimodal lT" strategy has proven to be dangerously flawed. The fact is, if your business has a mainframe, that's probably where your most important applications and data live. As such, there's no way your business can remain competitive unless you can quickly adapt your use of those applications and data to keep pace with your rapidly and relentlessly evolving market demands.

That's especially true given the fact that your customer-facing mobile and web systems of engagement almost universally leverage your back-end mainframe systems of record.

So how do you actually get your mainframe environment up to speed? Given the fact that your existing mainframe dev/test processes and tools are pretty entrenched, how can you integrate the platform into a truly nimble and unified cross-platform enterprise DevOps environment?

Different organizations will take different approaches to this challenge. But here are three principles to bear in mind as you go about the difficult but ultimately extremely rewarding work of bringing your mainframe into the DevOps fold:

1. Transform the developer workspace

Most mainframe dev, test and ops work is still performed in "green screen" TSO/ISPF environments that require specialized knowledge, constrain productivity, and are extremely off-putting to the kind of skilled, ambitious programmers who are the lifeblood of Agile and DevOps transformation. It is therefore essential to migrate to more modern, graphical tools within a preferred DevOps toolchain that empower staff at all experience levels to perform mainframe tasks in much the same manner as they do other non-mainframe work.

Also, mainframe applications are typically large, complex and poorly documented. These attributes are a major impediment to mainframe transformation — and they tend to make enterprise IT highly dependent on the personal/tribal knowledge of senior mainframe staff.

To overcome the skills-and-knowledge gap, it's not enough to just make mainframe workspaces more graphical. You also need tools that enable new participants in mainframe DevOps to quickly and easily "read" existing application logic, program interdependencies, and data structures.

Recent innovations in mainframe workspace technology can also give developers on-the-fly feedback on any new bugs and quality issues they inject into their code. By investing in these tools, IT can empower even mainframe-inexperienced developers to quickly produce quality work that fits within the daily requirements of an Agile process. In addition, the latest mainframe development dashboard solutions enable managers to track defects, program complexity and technical debt so they can better pinpoint issues requiring additional coaching or training.

2. Remodel mainframe processes

Once you've built a better working environment for the mainframe, you can start to aggressively shift your process from a traditional waterfall model with large sets of requirements and long project timelines to a more incremental model that allows teams to quickly collaborate on so-called user "stories" and "epics." By estimating the size of these stories and assigning them their appropriate priority, your teams can start engaging in scrums that allow them to quickly iterate towards their goals.

The move from large-scale waterfall projects to Agile scrumming represents a significant change in work culture for most mainframe teams. Training in Agile process and work culture is therefore a must. You may also want to build your initial Agile mainframe team by choosing select mainframe developers and pairing them with Agile-experienced developers from other platforms to work collaboratively on user stories and epics.

You'll obviously also need the right enabling technologies for this shift. Key requirements include Agile project management software that supports Agile methodology — as well as Agile-enabled Source Code Management (SCM). The latter is especially pivotal since traditional mainframe SCM environments are inherently designed for waterfall development, and are thus incapable of providing essential Agile capabilities — such as parallel development work on user stories.

When engaged in this re-tooling, it is generally wiser to leverage best-in-class tools rather than fall into a monolithic approach that requires all SDLC activities to be performed within a single vendor's solution set. That's because best-in-class tools allow you to avoid vendor lock-in while taking advantage of the latest innovations in Agile management.

3. Integrate mainframe workflows into the cross-platform enterprise DevOps toolchain

The target state of mainframe transformation is ultimately a de-siloed enterprise DevOps environment where the mainframe is "just another platform" — albeit an especially scalable, reliable, high-performing, cost-efficient and secure one — that can be quickly and appropriately modified as needed to meet the needs of the business by whoever is available to do so.

This requires integration between mainframe and distributed tools (typically via REST APIs) so that DevOps teams have a single point-of-control for all changes across z/OS, Windows, Unix and other platforms. An effective cross-platform toolchain will also provide cross-platform impact analysis — so your developers can see how the code they're working on in one tier of an application (e.g. a mobile app server) may potentially affect another application tier (e.g. a DB2 database).

The de-siloing of your mainframe can also lead to unified IT service management (ITSM) for both mainframe and non-mainframe applications. This unified ITSM model is for companies with large numbers of multi-tier applications that are critical to their financial performance.

Of course, it takes budget, hard work and strong leadership to turn these principles into in-the-trenches realities. It is important for mainframe users to align themselves with others that don't just pay lip service to bringing the mainframe into the DevOps fold, and are committed to actually doing what it takes to get it done, and have experience doing it within their own organizations. Getting the mainframe up to DevOps speed is possible — and is being done by enterprises that recognize the need to complement their existing advantages of scale with new advantages of speed. And the alternative of "bimodal," "two-speed," or "multi-speed" IT is simply untenable. 

Every company with a mainframe therefore needs to get with the mainframe DevOps program. Now.

Chris O'Malley is CEO of Compuware.

The Latest

May 17, 2018

The top two business priorities for CIOs of midsize enterprises (MSEs) in 2018 are growth and digital transformation. However, 57 per cent of MSEs are not yet delivering digital initiatives, according to findings from Gartner Inc.'s 2018 CIO Agenda Survey ...

May 15, 2018

Almost every company is facing the challenge of digital transformation today. This means rethinking and retooling your company to compete and succeed in an increasingly digital world. While digital transformation is not only about technology, the right tools can help. To find out what these right tools are, APMdigest asked experts from across the IT industry for their opinions on the essential tools to support digital transformation ...

May 08, 2018

With data breaches consistently being in the news over the last several years, it is no wonder why data privacy has become such a hot topic and why the European Union (EU) has put in place General Data Protection Regulation (GDPR) which will become enforceable on May 25, 2018, which is less than a month away ...

May 03, 2018

The prospect of increased workloads, combined with shrinking mainframe skillsets, has huge implications for mainframe DevOps. The only way for organizations to solve this skills gap crisis is by optimizing developer productivity. Drilling down a level further, what does this all mean for mainframe DevOps? ...

May 02, 2018

When it comes to operations and development, DevOps has changed the traditional compartmentalized style of development by eliminating silos. But what about the security team? Security is largely still siloed from operations and development. No doubt, many DevOps teams have some security controls baked into their automation processes, but a recent survey shows there are still alarming gaps ...

April 30, 2018

According to the 2018 Global Security Trends in the Cloud report, 93 percent of respondents faced challenges when deploying their current on-premises security tools in the cloud, and 97 percent lacked the tools, cross-functional collaboration and resources to gain proper insight into security across the organization. These numbers indicate a big problem in DevSecOps that needs to be addressed ...

April 26, 2018

Moving more workloads to the cloud is a top IT priority, so eventually it will be time to consider how to make those critical legacy applications cloud ready. In Part 1 of this blog, I outlined the first four of eight steps to chart your cloud journey. In addition, consider the next four steps below ...

April 25, 2018

Clearly, moving applications to the cloud delivers significant advantages. So what's standing in the way of full cloud adoption? For many companies it's those burdensome (but critically important) legacy applications. Moving more workloads to the cloud is a top IT priority. So, eventually it will be time to consider how to make those critical legacy applications cloud ready. Consider the following eight steps to chart your cloud journey ...

April 24, 2018

Developers and engineering teams are under increasing pressure to release higher quality software faster. Continuous testing has proven to be central to these efforts as it helps eliminate bottlenecks and ensures that automated testing is a constant throughout the development process, not an exercise relegated to the "last mile." The value of automated testing is more evident than ever before, with nearly half the respondents reporting that management is fully committed to automated testing and with plans to increase spending, according to the recent Sauce Labs Testing Trends for 2018 report ...

April 19, 2018

As development speed has become a competitive advantage, the DevOps team has sought to enable continuous integration and continuous delivery (CI/CD). For the CI/CD process to be successful, it must be fast and efficient. Any potential roadblocks that delay any part of the process increase cycle times and slow down delivery ...

Share this