Debugging a Language Environment VS COBOL II program compiled with the NOTEST option using Terminal Interface Manager

You can use either the TEST or NOTEST compilation option to debug a VS COBOL II program. This use case is about debugging a Language Environment VS COBOL II program compiled with the NOTEST option. This method is called LangX COBOL in the z/OS Debugger manuals.

  1. In ISPF Edit or Browse, enter EQAJCL T for Terminal Interface Manager.
    Enter the EQAJCL T command.

  2. In the parameters section panel, specify the values.

    VS COBOL II programs might be linked either as Language Environment (LE) programs or non-Language Environment (non-LE) programs. In this use case, the program is linked as Language Environment enabled. Type YES in the LE Program field.

    To select an optional parameter, specify a forward slash (/) in the field.

    Although this is a Language Environment program, you still need to identify the z/OS Debugger debug libraries, and issue LDD statements for the modules that you want to debug. Optionally, you can set breakpoints for subprograms, or set the automonitor on.

    Specify optional parameters.
  3. Since you chose Debugger Libs, the z/OS Debugger Debug Libraries panel is displayed. In this panel, enter one or more names of the z/OS Debugger side files that you want to use.
    Add libraries.
  4. Since you chose to set AT ENTRY breakpoints for subprograms, the Request Sub-Program AT ENTRY Breakpoints panel is displayed. Enter one or more names of the z/OS Debugger side file data sets that you want to use.
    Set breakpoints.
  5. In the Program/Procedure Selection List panel, enter the step name or procedure that you want to debug.
    Provide the step name or procedure to debug.
  6. Since you chose LDD Programs, the z/OS Debugger LDD Generation for Non-LE Program Name panel is displayed. The z/OS Debugger LDD Generation for Non-LE Programs panel is defaulted to the LDD name provided in the z/OS Debugger LDD generation for Non-LE Program Name panel and the subprograms provided in the Request Sub-Program AT ENTRY Breakpoints panel. You can override or add more entries to this panel to depict the LANGX members that you want to use in the debug session.
    LDD name and subprograms displayed in the panel
  7. The JCL for VS COBOL II z/OS Debugger invocation is created. To define the source and debug information during the debug session, the LDD statements and EQADEBUG libraries are required.
    The JCL is generated.