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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
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.