Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Needs more information
Created by Guest
Created on Sep 9, 2026

Enhance DBB User Build to wait for COBOL language server readiness after VS Code reload

Scenario

After launching (or relaunching) VS Code, we open a simple “Hello World” COBOL batch program in IBM Z Open Editor. If we run DBB user build (or run DBB user build with full upload) immediately, the build aborts with the error below.

If we keep VS Code open for some minutes and run the same build again, it succeeds.

Steps to reproduce

  1. Launch (or relaunch) VS Code.

  2. Open a COBOL program in IBM Z Open Editor.

  3. Right-click in the editor and select Run IBM User Build or Run IBM User Build with Full Upload.

  4. Observe the build abort.

Error observed

2026-09-02T03:47:55.496Z: CRRZG5375E User Build aborted, because the COBOL language server is not running.

2026-09-02T03:47:55.497Z: CRRZG5221E Stopping User Build. An error has occurred: CRRZG5375E User Build aborted, because the COBOL language server is not running.

Environment

  • VS Code: 1.120.0

  • IBM Z Open Editor: 6.6.0/6.7.0

  • Zowe Explorer: 3.5.1

  • z/OS version: z/OS 03.02.00

Request enhancement

Please enhance DBB User Build so that when it is invoked while the COBOL language server is still initializing after VS Code launch or reload, it waits for the COBOL language server to become ready before continuing, instead of aborting immediately.

The expected outcome is that User Build does not fail during normal COBOL language server startup.

Business impact

This affects a normal user workflow. After VS Code launch or reload, the COBOL editor and User Build command are visible, so users reasonably expect the build action to be usable. The abort can make users think the build setup, IBM Z Open Editor configuration, or COBOL source file is broken, even though retrying shortly afterward succeeds with the same file and workspace.

Idea priority Low
  • Guest
    Sep 9, 2026

    Any way you argue it - this is a bug in the software.
    There is a cold-start race in IBM Z Open Editor.

    It appears that DBB User Build alone currently only checks whether the COBOL language client exists. 
    It does not start it or wait for it.
    The COBOL language server is started by something else (I think the opening of a .cbl member)

    So the events are:
    VS Code opens after reboot. IBM Z Open Editor activates.
    It notices the open .cbl document and begins starting the COBOL language server.
    That startup is asynchronous and involves the Java language server.
    Run User Build.
    User Build checks and sees no COBOL client yet then throws CRRZG5375E.
    Meanwhile, the language server finishes starting, so a second attempt obviously works.

    A developer non-friendly workaround is wait (sometime)
    Solutionising...
    For a (potential) proper fix, this is something IBM should handle in Z Open Editor. Context display of "User Build" should either await the Cobol language server readiness or start the COBOL client itself before enforcing the required-language-server check.
    Homebrew solutions do not have the same effectiveness as the underlying control is via Z Open Editor ymmv.