Debugging Process

What to Define

You cannot debug an Assembler, COBOL, or PL/I program until you define it to the DC/UCF system. For example, you cannot debug a program until it is defined in the PROGRAM statement at system generation time or defined dynamically with the DCMT VARY DYNAMIC PROGRAM statement.

Similarly, you must define the program task code either in the TASK statement at system generation or dynamically with the DCMT VARY DYNAMIC TASK statement.

Important! You don't have to define the task code for the initial stage of the debugging process, but you must define it before executing the program.

You don't have to define CA ADS dialogs, subschemas, maps, and tables.

Debugger Structure

You can conduct a debugger session in one of two modes or a combination of both:

Prompt mode enables you to issue debugger commands line by line
Menu mode enables you to issue commands from a series of activity and tutorial screens

Debugging a module takes place in two phases:

The setup phase, invoked before a program is executed
The runtime phase, occurring during program execution and dependent on actions taken during setup

DEBUG and QUIT

A debugger session begins when you issue the first DEBUG task code. A session ends when you either issue the debugger QUIT command or terminate the DC/UCF session by signing off.

Debugger session modes and phases are discussed in detail below.