Debugging COBOL when only a few parts are compiled with TEST

Example: sample COBOL program for debugging

Suppose you want to set a breakpoint at entry to COBVALU. COBVALU has been compiled with TEST but the other programs have not. z/OS® Debugger comes up with an empty Source window. You can use the LIST NAMES CUS command to determine if the COBVALU compile unit is known to z/OS Debugger and then set the appropriate breakpoint using either the AT APPEARANCE or the AT ENTRY command.

Instead of setting a breakpoint at entry to COBVALU in this example, issue a STEP command when z/OS Debugger initially displays the empty Source window. z/OS Debugger runs the program until it reaches the entry for the first routine compiled with TEST, COBVALU in this case.

Refer to the following topics for more information related to the material discussed in this topic.