Viewing the dependencies of a program

You can determine the dependencies that a certain COBOL, PL/I, or Assembler program has.

Before you begin

If you are checking the dependencies of a remote program, you must be connected to the remote system.

About this task

You can perform a show dependencies operation on the following resource types:
  • COBOL and PL/I source files in a local z/OS® project on Windows platforms.
  • COBOL source files in a local z/OS project on Linux® platforms.
  • COBOL, PL/I, and Assembler source files in a partitioned data set in an MVS™ subproject or on a remote system.
The show dependencies action is not supported for sequential data sets.
If your program depends on a file that cannot be found, the file is simply ignored (skipped without warning). To ensure that files are not skipped, run a local syntax check on your program; if the syntax check does not produce any errors, all the dependencies can be located, and no files are skipped.
Limitations:
  • Local syntax check is deprecated. This action is available only on Windows.
  • Local syntax checking does not support shift-out-shift-in (SOSI) sources. The importer that is used to do the local syntax check supports only UTF-8 encoding. Translating CP-930 and other SOSI sources into UTF-8 alters the column locations for some characters, and this alteration results in unexpected errors.

The Show Dependencies action is not supported for sequential data sets.

Information specific to LinuxInformation specific to LinuxIBM® Developer for z/OS does not support the following functions on Linux and macOS: bidirectional enablement with remote debugging, workstation-based debugging, local COBOL or PL/I builds, local preprocessors for PL/I files, local syntax check, and show dependencies for PL/I files.

Procedure

  • To check the dependencies of a program, right-click the program and click Show Dependencies.
  • To check the dependencies of all programs in a local project, right-click the project name and click Show Dependencies.

Results

If a JCL error occurs or the job ends abnormally, an error message displays to help you solve the problem. From this message window, you can do one of the following steps:
  • Open the job output to view the error messages and return codes.
  • Open the property group that is associated with the file to view the build properties currently in use.
If the job executes successfully, a window opens listing all dependencies for the program or project.