Transforming the digital enterprise isn’t just about mobile apps and ‘cool’ new technologies. That’s a no brainer! Your mainframe applications aren’t going anywhere in the near future. Why? Here are three main reasons mainframes are here to stay:
- Their scalability is unmatched.
- Their security is rock solid.
- They are easy to maintain.
Read those one more time (go ahead; you can do that now). Don’t they sound ironically familiar? They should! Let’s connect the dots… they are all important in DevOps. Shocked? I’m not. There is only one thing missing for the mainframe application – speed of delivery.
So how do you speed up the delivery of changes on the mainframe? Automation. Some of the biggest changes that happen on mainframe applications today are updates/changes to timing (when to run the job), where to move files, where to pull data from, and when batch job schedule automation is executed in the application. A Jobs-as-Code approach with Control-M Automation API opens up a whole new world for mainframe developers. They can immediately shift left changes in job definitions right within the code much earlier in the software development lifecycle (SDLC). Testing and debugging happen early as well, which we all know is a huge BONUS and money saver. The code and its changes now become part of the application code base following the rest of the DevOps toolchain leveraged by the mainframe for Continuous Integration and Continuous Delivery.
Still a naysayer on Continuous Delivery when it comes to the mainframe? Check out this leadingagile.com article on The State of Mainframe Continuous Delivery for great insights.
Once the mainframe application is ready for release, developers seamlessly handoff to operations, and rework and last-minute changes to the application’s business automation are diminished. Collaboration and cultural changes are addressed organically with the Jobs-as-Code approach.
Amadeus, one of our long-time customers, is on a DevOps journey that includes varying dynamic infrastructures where Control-M is a lynchpin to their success. You can view their story from the DevOps Enterprise Summit 2017 in London here for more details
I must admit, over the last 10 years in IT I thought for sure the mainframe would be replaced with a new shiny object. But I was wrong. The resurgence of the mainframe is happening and new-aged developers see the value of keeping them around. It is our job to educate and provide guidance on how to apply DevOps principals on mainframes. It is never an all-or-nothing approach. Creativity and persistence are needed to speed up the delivery of the mainframe application.
- Gene Kim on DevOps: DevOps Cookbook Ex. Pattern #1: Deploy in Sprint
- DevOps Best Practices for Enterprise Architecture
- Getting Started with Cloud Native Applications
- 9 Steps for Building Pipelines for Continuous Delivery and Deployment
- What is Parallel Testing? Parallel Testing Explained
Forrester Study: Accelerate software delivery
When developers build business automation workflows at the same time as other application components, software delivery speed and efficiency increase while errors drop. Read this study to learn what Jobs-as-Code can mean for your business.