Mainframe Developer Cockpit Simulator
By: David Mcnierney
Tags: Mainframe, Git, Github, Vscode, DevOps

To date, mainframe developers have used native source code managers like CA Endevor, and editors like the green screens of ISPF or, more recently, Eclipse. While these tools have served mainframe shops admirably for decades, the next-generation of talent knows and loves different tools, and even Eclipse is considered primitive by today’s standards.

Today, 87% of developers use Git and appreciate its collaboration-centric paradigm, derived from its open source origins. Eleven million developers use Visual Studio Code and appreciate features like syntax highlighting, intelligent code completion, snippets, and embedded Git as well as the ability to personalize the environment. These tools, when combined with CLIs, CI/CD pipelines, etc., are the engine of digital transformation.

Should the next-generation of mainframe developers be required to adopt the legacy tools?

Modern developer tooling powered by Zowe

Software engineers are in perpetually high demand so, like others, mainframe teams need to find ways to attract and retain talent. Imposing legacy tools, as effective as they may be, may not be as attractive as allowing them to use tools they already know and love. Opening the platform to these tools makes the mainframe a more appealing career choice.

Now, with enabling technologies like the open source Zowe framework, VS Code extensions like Code4z and the CA Endevor Bridge for Git, a modern toolchain is available to developers of mainframe code, including sysprogs. Critically, these tools enable mainframe teams to modernize-in-place, without lifting and shifting code and without disrupting existing developers. They also offer the ability to easily leverage enterprise CI/CD toolchains including components like Jenkins, SonarQube and Jest that are also often familiar to the next-generation. To learn how Zowe opens the door to off-platform DevOps tooling, and offers value adds like Single Sign-On (SSO) and MFA, read “Z is for Zowe, the Open Path to Mainframe DevOps”.

Developer Cockpit Simulator

These Zowe-enabled tools help new-to-mainframe team members be productive immediately — even on Day 1 — by lowering the learning curve.

In the digital age, an organization’s codebase is its ‘crowned jewels’. It defines how they deliver value and how they compete. For companies running mainframe applications written in COBOL and other mainframe-centric languages, a modern toolchain is the first step to meaningful software modernization, including robust cross-platform applications and broader polyglot development.

In addition to being attractive to the next-generation of talent, these tools also provide a degree of future-proofing. New cloud-based IDEs like Eclipse Che, Red Hat CodeReady Workspaces and GitHub Codespaces preserve not only the look and feel of VS Code but also innovations like the Language Server Protocol (LSP) and Debug Adapter Protocol (DAP).

However, for both career mainframers and new-to-mainframe developers, understanding how the technology comes together can be challenging.

Developer Cockpit Simulator

To demystifying this new toolchain, Broadcom created an interactive simulator called the Developer Cockpit [link]. Featuring Visual Studio Code, Zowe and Git, the Developer Cockpit simulates a realistic environment for a COBOL/CICS/Batch/Db2 developer complete with relevant VS Code extensions, Zowe CLI plug-ins and sample scripts. It provides visibility into the holistic experience and the open source enablers behind-the-scenes. And access to a script library provides the cockpit with “autopilot” capabilities which are especially helpful for new team members.

Try out the Developer Cockpit Simulator and let us know what you think!

See the complete set of VS Code extensions

See the complete set of Zowe CLI plugins

Learn more about Zowe

Learn more about CA Endevor Bridge for Git

Learn more about LSP

Learn more about DAP

Learn more about Eclipse Che