User build advanced error reporting
Starting with Z Open Editor v4.0.0, user build compilation errors will be parsed and reported in VS Code's Problems view. This is an advanced capability that requires an activation kit to be imported into VS Code. Learn how to enable Z Open Editor's advanced capabilities here. If advanced capabilities are disabled, problems will not be displayed in VS Code's Problems tab. You can still check compilation errors by viewing the output log. The output log will be downloaded to the repository from which you run user build under the logs directory. You can change the directory in the VS Code user setting.
"zopeneditor.userbuild.userSettings": {
"localLogDir": "/Users/logs"
}Compilation message generation
Compilation messages are generated by DBB user build when --errorPrefix <unique-id> parameter is passed into the script. zAppBuild generates an MVS dataset that contains the compilation messages. Z Open Editor user build reads those messages and displays them in the Problems panel. Z Open Editor deletes the compilation message datasets after each user build run.
User build problems view
When user build has compilation messages, they will be displayed in VS Code's problems panel. When user build runs, the Output panel is automatically opened in the IBM User Build view. Switch to the Problems panel. If you cannot find it, press Ctrl + Shift + M on Windows or Shift + Cmd + M on Mac to open it.
Using problems panel
Problems are listed under each file with a code name that starts with IBM user build. Click the message and it will take you to the line of code that causes the problem. If the line of code cannot be determined, the error will show on the first line of the file.
Clearing problems
Each time you run the user build, the messages will be cleared in the corresponding file in the problems panel. You can also clear user build messages manually by hovering over the light bulb icon at the beggining of the message and choosing "Clear all user build problems for this file".