Sitemap
Modern Mainframe

Mainframe modernization for the next generation of application developers using Visual Studio Code (VS Code), Git, and DevOps automation — automated build, test, deployment of COBOL applications & more. Features articles on Code4z, Team Build and Endevor Bridge for Git.

Adopting Code4z for z/OS Application Development: Top 5 Considerations

5 min read17 hours ago

--

Banner

The backstory…

When introduced in 2019, Code4z became a real disruptor by making VS Code a genuine option for mainframe developers. Until then, the challenges with Eclipse (rigid, difficult installation and maintenance, etc.) left mainframer leaders struggling with the IDE value proposition and adoption progressed slowly. Code4z has since opened the door to streamlined IDE adoption and contemporary workflows.

Code4z

Visual Studio Code’s ‘any platform, any language’ design and lightweight, easy-to-maintain architecture were perfect for the platform, so, not long after its introduction, Broadcom decided to go all-in and the rest is history.

While many mainframe teams have been enjoying the benefits of the Code4z / VS Code experience, the value proposition has been amplified with the introduction of AI code assistants and agentic AI. As a platform, VS Code enables the smooth introduction of these tools and the associated workflow changes.

Yet a number of teams are still struggling with how to move forward.

The traditional IDE considerations have already been addressed. For example, Code4z supports a wide range of mainframe-oriented languages including COBOL, PL/I, HLASM, JCL, Rexx, and Easytrieve, as well as specific dialects, and the rich VS Code ecosystem offers extensions for other languages used by mainframers like Python and JavaScript. Core functions like debugging, data editing, and abend analysis are robust and highly-regarded.

So what considerations remain for AppDev leaders, architects, and modernization champions considering Code4z?

Top 5 Considerations

#5 — Adoption by 3270 users

It may seem like an uphill battle, but customers are often surprised by the number of veteran programmers who welcome the opportunity to learn about and use Code4z. Peter Wassel first reported this in Confessions of a Career ISPF Programmer, and Vijay Nair offers a first-person perspective, Moving from ISPF to VS Code: My Top 5 Lessons Learned.

What gets 3270 users excited? Here’s a quote: “Being able to quickly search through millions of lines of code and use regular expressions for more complex searches completely changed my effectiveness as a developer and architect.”

While some organizations will mandate the use of VS Code, many developers find retaining access to 3270 helpful for a range of tasks.

Consideration: Mandate use of Code4z or allow developers to choose their preferred tool(s)?

#4 — DevOps Suite license creates deployment options

The Code4z extensions, which includes the Foundation starter pack, are free to use and are available in the VS Code Marketplace and the OpenVSX Registry.

While many extensions function as in standalone mode, a number of them access back-end services running on z/OS, like Debugger for Mainframe (InterTest) and Abend Analyzer (Symdump). The good news is that most of these back-end services are components of the Broadcom Mainframe DevOps Suite so many customers already have the necessary licenses. The challenge is prioritizing them. The Suite also includes 24x7 support for both Code4z and Zowe.

Get Petr Vacula’s stories in your inbox

Join Medium for free to get updates from this writer.

Consideration: Which building blocks are required for adoption, especially given existing workflows, policies, and toolsets.

#3 — Zowe is essential

Zowe acts as the plumbing and connection layer (handling security, file I/O, and job control), while Code4z serves as the application development toolkit (providing language intelligence, debugging, data editing, control flow visualization, etc.). Zowe Explorer, which is powered by the Zowe CLI, streamlines interaction with mainframe data sets, USS files, and jobs. There are three deployment options: 1) active z/OSMF (z/OS Management Facility) REST API services running, or 2) with remote SSH, as my colleague Rose explains: Zowe Explorer 3.6: A Faster Path to Productivity, or 3) an FTP extension.

While the Zowe API Mediation Layer (APIML) is not required, we recommend adoption to take advantage of the powerful SSO/MFA capabilities it enables.

The Mainframe DevOps Suite includes support for the entire Zowe framework including the Zowe CLI and APIML.

Considerations: Deploy Zowe Explorer using z/OSMF, SSH, or FTP? Include APIML-enabled SSO/MFA?

#2 — Source code repo options and toolchains

VS Code’s native Git capabilities offer a straightforward path for applications maintained in enterprise Git repos, which applies to users of the Endevor Bridge for Git as well.

For users preferring native access to Endevor, the Explorer for Endevor extension streamlines access to the full map of elements. Users of other mainframe SCMs are free to use similar extensions.

Consideration: Accommodating a potentially hybrid environment with source code in multiple SCM tools (e.g., application A in Endevor, application B in Git). This topic should take into consideration the broader DevOps toolchains and SDLC. For example, Endevor supports several scenarios:

Risk-managed Modernization

#1 — AI code assistance and agentic

Along with extraordinary opportunities, AI is also introducing a level of disruption. Claude Code, GitHub Copilot, Cursor, Devin, Gemini Code Assist, Codex, Kiro, Windsurf, Antigravity — the array of AI tools and LLMs is changing continuously, as are the range of productivity opportunities.

A critical friction point that, based on customer feedback, we’re focusing on is AI-driven application understanding and impact analysis. A beta version of Code4z Intelligence is available so if you’re interested in learning more, including how it sets the stage for full agentic development, please reach out.

Consideration: How best to evolve the developer experience with a fast-changing AI landscape.

Getting Started

Broadcom’s technical consultants have encountered all of these challenges and have helped customers navigate them successfully, taking into consideration both risk and reward. A couple of programs to consider in your Code4z adoption journey:

Mainframe Expert Program: Embeds professionals with deep experience into your existing ecosystem. You get access to best-in-class talent trained, certified, and employed by Broadcom — working at your direction, as members of your team.

Win-no-fee: We help you convert software environments using our tools and expertise — at zero cost to you. We shoulder the labor, reduce risk with automation, and accelerate your path to value. The only thing you’ll spend is less time worrying about how to get it done. If you’re considering converting from an Eclipse-based IDE, contact Broadcom.

Finally, for those still deciding if Code4z is the right solution, you can always experience Code4z in a risk-free, sandbox environment. Request a workshop for your team by visiting code4z.broadcom.com.

Written in collaboration with Ekaterina Tumanova.

--

--

Petr Vacula
Petr Vacula
Modern Mainframe
Modern Mainframe