Troubleshooting for User Build

Possible reasons This issue can happen if Z Open Editor cannot find proper Java™ SDK to start Language Server Protocol. Make sure Z Open Editor is using a valid Java SDK. Follow instructions on configuring Java here.

Possible reasons

• Copybooks/Includes cannot be found by the user build.

  Make sure IBM Z® Open Editor property groups have been set up so that it can find copybooks/include files. Details on configuring property groups can be found in Setting property groups. To test whether a copybook can be resolved, open a program file in the editor and move your mouse cursor over the copybook or include file name. If a preview appears, it means the copybook/include is resolved successfully.

• IBM Z Open Editor Language Server protocol did not resolve copybooks for the user build.

  • Try closing and reopening the COBOL, PL/I, or HLASM file.

  • Try reloading the editor. In VS Code, open the command palette by pressing Ctrl+Shift+P and search for >Developer: Reload Window. Click the command to execute it.

An example output is as follows:

...
Using ssh profile myZoweSSHProfile
Using zowe profile myZoweCLIProfile
Executing ssh command: 
 mkdir -p /u/user/projects/wazi-sample/COBOL

Possible reasons

You are not authenticated through a firewall. If you have a firewall protecting your z/OS® instance, make sure you are authenticated. Check that you can issue Zowe™ SSH commands with your SSH profile. Refer to the examples on Zowe doc site.

Possible reasons

This can happen if there's an issue with the language server and it fails to fetch dependencies. Try re-loading the window. In VS Code, open the command palette by pressing Ctrl+Shift+P and search for >Developer: Reload Window. Run User Build again.

Possible reasons

This error might happen for a few reasons:

• Reason 1: Your ZAPP file is invalid. Ensure ZAPP file is valid. Review the IBM Z Open Editor Output log for more information.

• Reason 2: You defined an invalid profile under the dbbDefaultZappProfile VS Code User setting. Leave this setting blank and User Build will choose the first defined profile or define an existing valid profile.

• Reason 3: If none of the above applies, try re-loading the VS Code window. In VS Code, open the command palette by pressing Ctrl+Shift+P and search for >Developer: Reload Window. Run User Build again.

Trying to run a user build on a file produces the following error:

Could not automatically get active VS Code workspace folder for this file. Make sure you are running User Build from a file which belongs to an active workspace opened in your editor locally. You can also define localWorkspacePath setting to resolve this issue.

Possible reasons

This error might happen for two reasons:

• Reason 1: You are running a user build on a file that does not belong to an active workspace in VS Code. Make sure you import your project into VS Code properly.

  To add a folder to Workspace, select File > Add Folder to Workspace and select your project folder.

• Reason 2: Active selected file was not detected by VS Code. This happens when other windows take active focus. For example, if you have an active terminal opened in VS Code, it can take the focus away from the editor. Close other windows and terminals and try again.

Using ssh profile myZoweSSHProfile
Using zowe profile profile myZoweCLIProfile
Identified local root workspace path as c:\Users\zopeneditor-sample
Running setup to build c:\Users\zopeneditor-sample\COBOL\SAM1.cbl program.
Executing ssh command: 
 mkdir -p /u/user/zopeneditor-sample
An error occurred: All configured authentication methods failed

Possible reasons

• This error happens when your Zowe SSH profile is not valid. Make sure the profile has the correct host, user name, password, and port defined.

  Run the following command to test if that specific profile is valid. Replace the command inside the quotes with your command:

  zowe uss issue ssh --ssh-profile myZoweSSHProfile "mkdir -p /u/user/zopeneditor-sample"

• This error happens when your Zowe CLI profile is not valid. Make sure you can execute Zowe CLI commands using that profile.

To run a user build, ensure that a Zowe profile is created and defined in settings. If no credentials are found for the profile during the inital run of an IBM User Build, you will be prompted to input your credentials for the z/OS connection. Secure Credential Store Plug-in and plain text credentials are both supported.