Previous Topic: Debugging ProcessNext Topic: Menu Mode


Prompt Mode

Line-oriented Method

Prompt mode is the line-oriented method of communicating with the debugger. In prompt mode you can:

Initiating a Debugging Session

To initiate a debugging session in prompt mode, enter the DEBUG task code in response to the Enter Next Task Code prompt:

ENTER NEXT TASK CODE:
debug

The debugger indicates that it is in control by responding with its special prompt:

DEBUG >

Issuing a Debugger Command

You can issue debugger commands whenever the debugger responds with the DEBUG> prompt. To issue a debugger command at the same time you initiate a debugging session, enter the task code in conjunction with the DEBUG command that names the entity to be debugged. In this example, the task code DEBUG is followed by a DEBUG command that identifies TESTPROG to the debugger:

ENTER NEXT TASK CODE:
debug debug testprog

When you enter the above command, you invoke the debugging facility. The command is echoed, and the debugger responds by validating the command and displaying the next DEBUG> prompt:

DEBUG TESTPROG
DEBUG > DEBUGGING INITIATED FOR TESTPROG VERSION 1
DEBUG >

If you try to debug a program which has not been defined to a DC/UCF system, the debugger issues an error message after echoing the command, then repeats the command that cannot be completed, and redisplays the DEBUG> prompt, as in this example:

DEBUG TESTPROG
DC574902 DEBUG > LOAD OF TESTPROG FAILED - NOT FOUND
DEBUG > DEBUG TESTPROG
DEBUG >

Difference between EXIT and QUIT

To return control to the DC/UCF system, issue either the EXIT command or the QUIT command.

The EXIT command saves the debugger control blocks and allows you to continue the same debugger session.

The QUIT command clears the control blocks and terminates the debugger session completely.

How to Check Session Activity

To determine whether a debugger session exists, issue the command DCMT DISPLAY LTE *. This command lists information about your logical terminal. If you see DEBUG ACT, a debugger session is active; if you see DEBUG INACT, no debugger session is active.

To inquire for a list of modules known to the debugger, use the DEBUG INQUIRE command (see Debugger Commands).

Valid Commands

In prompt mode, you can use all commands except RESUME, IOUSER, and WHERE during setup, and all commands except DEBUG during runtime. The PROMPT command performs no function while you are in prompt mode.

For a detailed discussion of the debugger commands, see Debugger Commands.