Essential reading from Rocket Enterprise. Straight to the source.
Our opening briefing: batch interoperability, developer tooling, and the scope of Enterprise Server. Drawn from Rocket’s Enterprise Developer 12.0 documentation for Eclipse on Windows.
IN FOCUSEnterprise Server 12.0 documents Java invocation through IBM-style interoperability and JZOS batch-launcher emulation, plus a JCL-initiated Python launcher. These capabilities let existing batch applications call additional tooling. Support covers subsets of the JZOS and zoautil toolkits; check the detailed documentation before relying on a particular API.
Developer toolsThe 12.0 documentation describes a Rocket Explorer project view in Visual Studio Code for existing build and debug configurations. It also lists unit-test code coverage, enhanced JCL editing, and MCP tooling for COBOL. These are documented release capabilities, rather than announcements made today.
Runtime architectureRocket describes Enterprise Server as a transaction monitor and runtime with application-level support for workloads using interfaces such as CICS, IMS, VSAM, and JCL. Its documentation distinguishes this compatibility from the underlying IBM systems. That distinction helps define the scope of a replatforming evaluation.