IBM Z® Open Editor
Docs
News and Blogs
IBM Downloads
VS Code Marketplace
GitHub
Docs
News and Blogs
IBM Downloads
VS Code Marketplace
GitHub
  • Overview

    • Introduction
    • Updates and user feedback
  • Getting Started

    • Getting started with IBM Z Open Editor
    • Setting up integrations to interact with z/OS
    • Getting started with Zowe 3.0
  • Configuration

    • Setting preferences
    • Configuring your applications with ZAPP files
    • Setting property groups
    • Setting compiler options
    • Setting file associations
    • Setting language-specific tab stops and rulers
    • Enabling and disabling problems in IBM Z Open Editor
    • Enabling and disabling unreachable COBOL code warnings
    • Customizing the Outline view
    • Setting language-specific maximum line length
    • EBCDIC code pages and mappings files
    • Experimental: Formatting COBOL source code
  • Tutorials

    • Tutorial overview
    • Exploring the user interface
    • Exploring the sample files
    • COBOL editing tutorial
    • COBOL, PL/I Preprocessor tutorial
    • HLASM editing tutorial
    • REXX editing tutorial
    • Managing z/OS resources with IBM RSE API Plug-in for Zowe CLI tutorial
    • Submitting JCL to compile, link, and run jobs tutorial
  • Editing program files

    • Language References
    • Making COBOL and PL/I code changes
    • Making High Level Assembler code changes
    • Making REXX code changes
    • Making JCL code changes
    • Using and managing code snippets
    • Using the integrated Git
    • Searching for COBOL, PL/I, HLASM, and REXX components
  • Interacting with z/OS using Zowe

    • Interacting with z/OS
    • Creating a configuration profile in Zowe Explorer v3.0.0
    • Migrating your old Zowe yaml profiles for Zowe v3.0
    • Supported methods of authentication for z/OS using Zowe
    • Sharing team configuration files
    • Connecting to z/OS with Zowe Explorer walk through
    • Using the Zowe Explorer views
    • Using Zowe profiles in Z Open Editor
    • Connecting to z/OS using Zowe CLI walk through
    • Using command line to interact with z/OS
    • Interact with RSE Common Properties
  • Advanced Capabilities

    • Overview
    • Activating advanced capabilities
    • Launching a 3270 emulator from Zowe Explorer
    • z/OS Resources Table
    • Data Elements View
    • Program Control Flow Browser
    • Data Flow Browser
    • Preprocessor support
    • Custom Macros for HLASM
    • Language Detection
    • Linting with IBM ZCodeScan
    • User build with IBM Dependency Based Build (DBB)
    • Agent Mode
    • Line Hex Editor
  • Cloud-based Editing

    • Overview to using Cloud and Browser-based platforms
    • Try Z Open Editor in the Red Hat Developer Sandbox
    • Configuring Red Hat OpenShift Dev Spaces
    • Managing Developer Workspaces
    • Managing secrets
    • Create and use custom images
    • Migrating from IBM Wazi for Dev Spaces
    • Using Z Open Editor on GitHub Codespaces
    • Using Z® Open Editor with Dev Containers
  • Troubleshooting

    • Known issues and limitations
    • Troubleshooting using log files
    • Troubleshooting for User Build
    • Uninstalling CLI plugins and VS Code extensions
  • Reference

    • IBM RSE API Plug-in for Zowe CLI commands
    • IBM RSE API Plug-in for Zowe CLI as nodejs SDK package
    • IBM RSE API Plug-in for Zowe CLI as nodejs SDK reference
    • Example Zowe configuation setups
    • IBM Z Open Editor MCP Tools
    • Accessibility and Keyboard Shortcuts
    • settings.json properties
    • Message ID Reference
    • Other Visual Studio Code extensions
  • Legal information

    • Notices
    • Trademarks
    • Privacy policy considerations

Overview to using Cloud and Browser-based platforms

Z Open Editor and Zowe Explorer can be installed and used with various cloud or browser-based editing environments that utilize VS Code as the editor. Hosting development tools and editors in the Cloud can provide many advantages for developers as well as team leads and administrators, especially for hybrid z/OS® development projects that bring together different technologies, require different skill sets and knowledge about development tools:

  • Eliminate the need for developers to install and configure all development tools locally: Instead of having every developer in a development organization install tools and prerequisites themselves on their own development machines, one lead developer can produce one or many container images with all the prerequisites as well as configuration files that load the correct versions of tools and VS Code extensions that every developer can simply use to get a full development environment. This can save a lot of time, eliminate confusion about versions, ensures that everyone is on the same and latest versions as well as help developers who are not familiar with all the tools and prerequisites and how to correctly install and configure them.
  • Rapid context switching between development projects using different development tools: When you work on multiple development projects at the same time, container-based development environments enable easy switching between completely different stacks of development tools, configuration, settings and even programming languages and language versions. This is done by switching to different containers and configuration files managed by Cloud-based development tools that provides workspace templates, which can be customized for the very specific needs of each project.
  • Eliminate hardware requirements and work from anywhere: As all tools are accessed through a simple web-browser, there is no need to use a specific hardware or workstations to do development work. Instead, organizations can deploy cost-effective developer hardware and can centralize and optimize resource usage in their Cloud infrastructure. Switching between working from home or the office is as easy as connecting to a network and then using the browser to sign on and open all tools.
  • Standardize connectivity, integrations, and authentication to external systems and applications: Instead of connecting each developer machine to external systems such as z/OS systems, databases, or web servers through technologies such as VPNs, making each of these systems a potential security risk and target for external attacks. Cloud-based development environment brings control of connectivity and security back to the experts that maintain access for all developers in a central place. Developers access all tools and systems through the integrated development environment in the browser that is prepared for them and authentication secrets are stored in secure Cloud storage as well, there is lower risk of misconfiguring secure access to sensitive systems.

Quickstart tutorials

The following examples show you how you can get started very quickly with some of the most popular Cloud-based environments from different vendors to evaluate if such solutions work for you. There is more detailed guidance for our preferred solution, Red Hat OpenShift Dev Spaces, in several detailed pages of this documentation section as well.

Red Hat Dev Spaces for OpenShift

Our recommended cloud-based development environment is Red Hat OpenShift Dev Spaces that provides a cloud-based development environment that is fully integrated into Red Hat OpenShift. If you do not have access to an OpenShift cluster, you can try Z Open Editor for free by signing up for a 30-day trial of the Red Hat Developer Sandbox. We have a full tutorial for signing up and using Z Open Editor here.

GitHub Codespaces

(Note that this is a paid-for service, but the first usage hours are free.)

Z® Open Editor can also be used with all of its capabilities in Microsoft's GitHub Codespaces. For a quickstart, try it by using this link https://github.com/codespaces/new?skip_quickstart=true&machine=basicLinux32gb&repo=160883618&ref=devcontainer&geo=UsWest&devcontainer_path=.devcontainer%2Fdevcontainer.json that loads our Z Open Editor sample repository. When the workspace starts up, it automatically loads the Z Open Editor VS Code extension and applies several configuration options based on a so-called devcontainer specification.

To learn more about what you can do with Z Open Editor in Codespaces, go to Using Z Open Editor on GitHub Codespaces in this documentation section.

Pure web-based editing in vscode.dev and github.dev

Z Open Editor can be used as a pure web extension with limited capabilities when using Visual Studio Code in a browser, such as on vscode.dev or github.dev.

Go to https://vscode.dev/github/IBM/zopeneditor-sample and confirm in the dialog to install the recommended extensions by clicking Install. No language server capabilities are available, but provides syntax highlighting for all our supported languages.

Last Updated: 9/17/25, 3:58 PM
Contributors: phaumer, PETER HAUMER, Vinithanjali Selvaraj, Esther M, Swathi Sadananda, Saile Daimwood
Next
Try Z Open Editor in the Red Hat Developer Sandbox