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
  • 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

Setting preferences

Before using IBM Z Open Editor, you can set preferences to control the characteristics of your environment. Preferences can be defined in various places depending on their scope - from user-specific settings to team project settings for files being edited. Z Open Editor distinguishes between settings provided via VS Code Preferences with settings provided in ZAPP files that are scoped to the application level and stored with your source code files. Application-specific settings, such as build flags, are typically shared with your team in ZAPP files. Personal settings, such as which Zowe profile to use for the user build, are usually in VS Code user settings.

Accessing VS Code settings for IBM Z® Open Editor

To open the settings for IBM Z Open Editor in VS Code, follow the steps below:

  1. In VS Code, open Settings.

    • On Windows, click File > Preferences > Settings.
    • On Mac, click Code > Preferences > Settings.
  2. To display the setting options for IBM Z Open Editor, expand the Extensions dropdown in the list on the left. Click on the entry IBM Z Open Editor.

  3. All the preferences shown in the visual editor are represented as JSON. Complex preferences that are not just simple values must be entered by using the JSON editor itself. To open it, select the scope tab first: User tab or Workspace tab, and then open the JSON view by clicking Edit in settings.json, or by clicking on the Open Settings (JSON) icon on the upper-right of the editor.

VS Code user preferences versus workspace preferences

In the editor panel, a list of preference groups is displayed, along with editor tabs for both the User and Workspace Preferences. Switch between these tabs to decide in which scope you want to add a preference.

User preferences

User preferences apply to the current user across different workspaces. They include not only typical user preferences related to accessibility, such as font sizes and editor behavior for code completion, but also Zowe Profiles defining z/OS® host connection information and personal high-level qualifiers. The settings are stored for the user in their home directory, apply to all the open VS Code windows, and are not shared with other users.

Workspace preferences

Workspace preferences apply to the current workspace and are stored inside the .vscode directory at the root of the workspace. If you share the workspace with other users through Git, you would also share the settings if the intent is for them to be the same across users. For example, preference settings such as tab size or file extensions would apply regardless of who edits the files.

Note: The workspace preferences always override user preferences.

VS Code also supports the concept of multi-root workspaces that can also be utilized for Z Open Editor. Multi-root workspaces allow you to work with multiple folders, each representing a workspace in Visual Studio Code. This is helpful when you are working on several related projects at one time. Each workspace can use a different Git repository and be located anywhere on your development machine. A multi-root workspace basically combines all the individual and independent folders into one tree view in the File Explorer. Settings are defined for the entire multi-root workspace in a .code-workspace file, as well as for each individual workspace. In the case of a conflict, determining which setting has precedence over another depends on the setting type.

For more details and information on types of settings available to VS Code in general, refer to the User and Workspace Settings and Multi-root Workspaces: Settings VS Code documentation pages.

Details about specific Z Open Editor settings and behavior are provided in the following section, and also in the Settings Reference.

VS Code user preferences versus ZAPP files

Some preferences in Z Open Editor are specific to the application under development and should be stored independent of the editor being used to edit the program files. Examples are the search path for folders in which include files such as COBOL copybooks are located, or what compiler options should be used to parse the programs to show syntax errors in the editor. These preferences are stored in a file called ZAPP (Z APPlication) file. The section Configure your applications with ZAPP files provides a full overview.

Switching the Display Language

The language in which menus, dialogs, and log messages are displayed as well as numbers and dates are formatted in VS Code and Z Open Editor is not determined by a user setting. Here, VS Code needs to be switched over and restarted to run in a different language through a command.

Find the details in the VS Code documentation, but the basic steps are:

  • Go to the VS Code Marketplace and search for the Microsoft language pack for your language.
  • If you are using Open-VSX you can find language packs there as well.
  • After you install the language pack, open the Command Palette and run "Configure Display Language" and select the language in the drop-down.
  • VS Code prompts you to restart and reopens in that selected language.

At the moment Z Open Editor and Zowe Explorer supports only the following languages. If you switch to a different language, you see English strings for our menus.

  • Chinese Simplified (zh-cn) and Traditional (zh-tw)
  • English US (en)
  • French (fr)
  • German (de)
  • Japanese (ja)
  • Portuguese (pt-br)
  • Spanish (es)
Last Updated: 12/5/25, 9:14 AM
Contributors: Lauren Li, Peter Haumer, Min Huang, Greg Lambert, Shi Kun Li, PrasangAPrajapati, phaumer, kmaselli, PETER HAUMER, Vinithanjali Selvaraj, Esther M
Next
Configuring your applications with ZAPP files