We are pleased to announce the general availability of IBM Z Open Development 1.0 today.
The need for speed in digital transformation drives the fundamental necessity for DevOps adoption. The critical need to replenish skills, as experienced mainframe developers retire, and the risk of not finding these skills, may pose a direct threat to an Organization’s core and critical IT assets. This risk can be transformed into an opportunity by facilitating generational renewal, thereby changing the rules of the game.
By providing modern editors, program understanding and visual debugging capabilities that allow developers to work with code on the mainframe as they would on any other platform, Z Open Development makes the first step in this transformation journey easy.
The second step is strategic and key: Git is the de-facto SCM for the open source community, and becoming the standard SCM for distributed software delivery in many enterprises. Z Open Development bundles Rocket Software’s port of Git and EGit, an Eclipse Team provider for Git. Git provides for free, the key capabilities that cannot be handled by concatenation-based library managers running on mainframe : full isolation, and true parallel development (branching and merging) are alien to legacy mainframe SCMs, and therefore perpetuate the isolation of the platform. Z Open Development eliminates this isolation through the new GIT support with Dependency Based Build (see here for New & Noteworthy in 1.0.3 release), and allows enterprises to have a standardized GIT implementation across their entire enterprise, including the Z an industry first.
The third step accelerates this transformation through the adoption of Continuous Integration. The Dependency Based Build feature (also released with IBM Developer for z Systems Enterprise Edition), provides the ability to run MVS, TSO, or ISPF commands on z/OS through Groovy scripts. Coupled with a dependency scanner to analyze the relationship between source files, these scripts can be used to compile and link-edit programs from Continuous Integration tooling such as Jenkins. This meets the mainframe software delivery team’s usual requirement to incrementally build and deploy only the changes to the application, while also allowing the full participation in a true enterprise wide continuous delivery pipeline.
Adoption and management of this transition at a process level for both SCM and Build are explained in this white paper : Develop Mainframe Software with Open Source Code Managers and IBM Dependency Based Build.Â
Z Open Development download for evaluation is available on Mainframe DEV. Dependency Based Build capability can be evaluated within a zero-install environment including Jenkins and Git running on IBM Z Development & Test through the IBM Z Trial Program.