Why JCL is Still a Key Player in Mainframe DevOps
If you’re working with mainframes, you know that these systems are still the backbone of many critical operations. But how do you bring them into the modern DevOps world?
While newer technologies grab the spotlight, Job Control Language (JCL) is still here, proving that it’s not just some relic of the past. In fact, JCL happens to be an important part in a modern mainframe DevOps strategy.
This old-school scripting language has been running the show on mainframes for decades, and it’s still got a lot to offer in today’s development environment.
Sound unexpected? Let’s explore why JCL is still relevant, what its role is in mainframe development, and why it's essential for building a modern DevOps workflow.
JCL, the tool you taught you didn’t need for Mainframe DevOps
So, what makes JCL a great fit for DevOps on the mainframe? At some point, your DevOps pipeline will initiate a build or deploy process. The DevOps framework has gathered all the necessary information and is ready to orchestrate this process. At this stage, you need a tool that can handle the grunt work quickly and thoroughly, making JCL a perfect fit.
Here’s why you should use JCL:
- Rock-Solid Stability: JCL has been around forever, and that’s a good thing. It has proven to be reliable, which is essential for managing critical business operations that depend on solid and trustworthy compilations and promotions of your code. In a DevOps setup, where you want things to be fast but also stable, JCL is a wise choice.
- Perfectly Integrated: JCL was designed with IBM mainframes in mind, so it fits like a glove. Whether you’re working with z/OS, CICS, or DB2, JCL can handle the job. This seamless integration means you don’t have to worry about compatibility issues when you’re automating and managing mainframe jobs.
- Efficiency Master: When it comes to batch processing, JCL is hard to beat. It’s optimized for managing job schedules, resources, and error handling. In a DevOps context, this efficiency translates into fast batch job executions, making your overall system run more smoothly.
- Familiar Territory: If you’ve been in the mainframe game for a while, you already know JCL inside and out. This familiarity makes moving into a DevOps framework much easier because it means you don’t need to spend a ton of time learning new tools or retraining your team.
Modern Day Perks of JCL
You need a tool that can handle the grunt work quickly and thoroughly
Although JCL may be old, it can be retrofitted into a modern DevOps solution that incorporates contemporary tools and practices. Additionally, you might want to hold onto your existing JCL scripts rather than rewrite everything just to use another tool for compile and promote tasks.
Here’s how JCL stays relevant:
- Plays Well with Others: JCL can be used by today’s DevOps tools like Kobee, DBB, Jenkins and many more. This means you can automate job submissions, track changes in JCL scripts, and hook your mainframe jobs into your CI/CD pipelines without missing a beat.
- Cost-Effective: Replacing JCL with something new would be expensive and time-consuming. Why not stick with what works? By continuing to use JCL, you avoid the costs and headaches replacing your job management systems, while still enjoying the benefits of DevOps.
- Consistency is Key: JCL gives you a standardized way to manage jobs across your mainframe environment. This is crucial for maintaining governance and compliance, especially when you’re in a regulated industry. Plus, it simplifies audits and ensures everything runs as it should.
Making JCL work for Your DevOps Strategy
JCL is here to stay, it’s about leveraging what already works to make the mainfram development transformation from legacy SCM tools to a modern DevOps approach much easier because you already have the JCL code and in-house knowledge. JCL is an efficient tool that can help you bring your mainframe operations into the DevOps era without breaking a sweat.
About the author
Hello, my name is René De Vleeschauwer.
Throughout my career, I have been actively engaged in developing enterprise software. For the past 18 years, I have led the development of Kobee, an open CI/CD and DevOps framework that has been highly regarded in regulated enterprises.
Do you have any questions? Just ask me!