Default language.

Submitting compiles and displaying compile diagnostics


Users can submit JCL directly from Host Explorer and from its editor, and can view compile diagnostics for COBOL and PL/I programs for currently or previously submitted compiles. Compile error messages allow the user to automatically position source code browsing sessions at the lines of code that caused errors.

To submit JCL and display compile diagnostics

  1. Ensure that the compile will be processed using the Compuware Shared Services COBOL or PL/I Language Preprocessor and that Compuware Shared Services PTFs are current. The preprocessor step is explained in the Compuware Shared Services User/Reference space.
  2. Ensure that the JOB statement includes a NOTIFY parameter with the value of the current

    Topaz Workbench

    user ID or &SYSUID.
  3. Use the Preferences dialog box's Compile Diagnostics page to set preferences for this functionality, including enabling automatic display of the latest compile diagnostics.
  4. Do either of the following to submit the JCL:
    • In the Host Explorer view, right-click the JCL member to submit and select Submit Compile.
    • Within the editor (in either browse or edit mode), right-click anywhere within the JCL source to submit and select Submit Compile.
  5. If, on the Compile Diagnostics preferences page, Prompt me is selected for where to link the diagnostics, a prompt appears. Select either Source or Source listing and click OK. A message indicates whether the job was successfully submitted.
  6. After the job completes, if the job contains multiple compile steps that meet or exceed the severity threshold and the compile diagnostics preferences are set to automatically collect/display diagnostics, a dialog box appears prompting the user to choose the step for which to collect and display diagnostics. Select the step and click OK. If, on the Compile Diagnostics preferences page, both automatic display of the latest compile diagnostics and show the Problems view when reporting compile diagnostics are enabled, the Problems view displays diagnostics if the highest severity in the compile meets or exceeds the selected threshold.
  7. Do either of the following to open the related source member or source listing in an editor and position to the line causing the diagnostic:

    • In the Problems view, double-click a problem marker. The source or source listing opens positioned to the selected problem. All diagnostics associated with this source/source listing display an icon representing the severity of the problem in the vertical ruler of the editor, and with a colored marker (also indicating the severity) in the vertical overview ruler of the editor.
    • In the Problems view, right-click a problem marker and select Go to source or Go to source listing. Doing so allows the user to view a problem that is linked to the source in the source listing and, conversely, to view a problem that is linked to the source listing in the source.

To display diagnostics for previously completed compile jobs

To collect and display compile diagnostics for compile jobs that were not submitted using Submit Compile or to display diagnostics for previously completed compile jobs, do the following:

  1. Ensure that the compile was processed using the Compuware Shared Services COBOL or PL/I Language Preprocessor. The preprocessor step is explained in the Compuware Shared Services User/Reference Guide.
  2. Right-click either a completed job in the JES view or a completed compile job in the Event History view and select Show Compile Diagnostics.
  3. If, on the Compile Diagnostics preferences page, Prompt me is selected for where to link the diagnostics, a prompt appears. Select either Source or Source listing and click OK.
  4. If the job contains multiple compile steps, a dialog box appears prompting the user to choose the step for which to collect and display diagnostics. Select the step and click OK. If, on the Compile Diagnostics preferences page, show the Problems view when reporting compile diagnostics is enabled, the Problems view displays diagnostics.
  5. Do either of the following to open the related source member or source listing in an editor and position to the line causing the diagnostic:
    • In the Problems view, double-click a problem marker. The source or source listing opens positioned to the selected problem. All diagnostics associated with this source/source listing display an icon representing the severity of the problem in the vertical ruler of the editor, and with a colored marker (also indicating the severity) in the vertical overview ruler of the editor.
    • In the Problems view, right-click a problem marker and select Go to source or Go to source listing. Doing so allows the user to view a problem that is linked to the source in the source listing and, conversely, to view a problem that is linked to the source listing in the source.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*