Limitations and troubleshooting

General

User builds with the zBuilder do not support Assembler source files.

Dependency Based Build Preferences

  • The Dependency Based Build Preferences page contains a field, User build high-level qualifier, for setting a value for the high-level qualifier for user build files on the z/OS system. If you specify a value for a high-level qualifier variable in the ZAPP User Variables preference page, the ZAPP User Variables value is the one that is used for the user build operation.
  • If you do not see updated log files in the local log folder, it might be because the folder is added to the .gitignore file in the repository. You can see the log files by doing one of these steps:
    • Look for the folder in the Git Repositories view.
    • Remove the folder name from the .gitignore file. This action results in the addition of many log files in the log folder.

ZAPP file

  • If there are unsupported options or invalid syntax in the zapp.yaml file, the user build might not run successfully. Symptoms of invalid or unsupported zapp.yaml options can include:
    • The property group definitions in the zapp.yaml file are not added to the Property Group Manager.
    • Errors may be logged when you try to edit the zapp.yaml file.
    • An error message window opens when you try to run a user build.
    To resolve the issue, use the error log messages to determine how the zapp.yaml file is in error and remove or comment out the flagged option.
  • A z/OS project must contain only one ZAPP file. If the project contains more than one ZAPP file, there might be issues with the generated property group and with running a user build.
  • If you attempt to edit the ZAPP file and encounter any issues with the Eclipse YAML editor, you can open a bug report at https://github.com/eclipse-wildwebdeveloper/wildwebdeveloper.
  • The dependencyFile argument of the user lifecycle is not supported.

Troubleshooting user builds

  • If you see the message Missing argument for option: hlq in the DBB console and the User build high-level qualifier option on the Dependency Based Build Preferences page contains a valid high-level qualifier, check that the variable name in the zapp.yaml file is --hlq ${dbbHlq} and not something else, such as --hlq ${dbb_HLQ} or --hlq ${teamHlq}.
  • If you see the message Unable to find the main build source file fileName on MVS. Check the DBB Console for possible host build problems, it might indicate a conflict with the high-level qualifier that is set in the ZAPP file. Check the ZAPP file to make sure that a high-level qualifier is not hard-coded. If it is, report this issue to the build engineer.
    The high-level qualifier can be set in these places:
    • The User build high-level qualifier field of the Dependency Based Build preference page. If you specify a value in this field, that value is used for the user build high-level qualifier.
    • The ZAPP User Variables preference page. If you specify a value for a high-level qualifier variable in the ZAPP User Variables preference page, the ZAPP User Variables value is the one that is used for the user build operation.
  • If you see the message Error uploading fileName java.lang.NullPointerException: Cannot invoke "org.eclipse.rse.subsystems.files.core.subsystems.IRemoteFile.getParentPath()" because "parent" is null in the DBB console, it might be caused by an invalid user build workspace path in the Dependency Based Build Preferences page. Check the z/OS UNIX file system to ensure that the path specified in the User build workspace field exists and is valid.