DEBUG

Purpose

Specifies the programs to be debugged or inquires about the debugged programs.

Syntax

ADD format

►►─── DEBug ─┬─ PROgram ◄ ──┬─ entity-name ─┬──────────────────────────┬───────►◄
             ├─ DIAlog ─────┤               └─ VERsion version-number ─┘
             ├─ MAP ────────┤
             ├─ SS ─────────┤
             └─ TABle ──────┘

INQUIRE format

►►─── DEBug ─┬─ entity-name ─┬──────────────────────────┬─┬─┬─ INQuire ─┬─────►◄
             │               └─ VERsion version-number ─┘ │ └─ OFF ─────┘
             └─ ALL ──────────────────────────────────────┘

Parameters

PROgram/DIAlog/MAP/SS/TABle

Identifies the type of load module to be debugged. Used only in ADD format. PROGRAM is the default.

entity-name

Specifies the name of the entity to be used by the debugger as the current load module. Entity-name contains a maximum of eight characters.

ALL

Specifies all modules defined to the debugger during the current session. Can be used only in INQUIRE format.

VERSION version-number

Identifies the version of the program being debugged.

If the version is not specified:

In ADD format, the debugger uses the version set with DCUF TEST, or version 1 if DCUF TEST hasn't been issued
In INQUIRE format, the debugger displays all versions if none is specified

INQuire

Requests a listing of the modules being debugged in this session.

OFF

Terminates all debugging for the specified programs for the remainder of the session.

Usage

Functions of DEBUG

The word DEBUG has several functions:

Task code used to initiate a debugging session
Prompt displayed during a debugging session in prompt mode
Command used during the setup phase to designate the programs to be debugged or to inquire about the debugged programs

You can use the DEBUG command only during the setup phase.

Special copy loaded

When you issue the DEBUG command for a module, a special copy is loaded, so that setting breakpoints and making data changes will not affect other users.

Two formats

The DEBUG command has two formats. The ADD format initially identifies the entities to be debugged; the INQUIRE format lists entities defined to the debugger in a given session.

Example 1

This example illustrates the use of the DEBUG task code in conjunction with the DEBUG command to transfer control from DC/UCF to the debugger and to define a module to the debugger; the debugger verifies the commands and displays the DEBUG> prompt in response:

ENTER NEXT TASK CODE:
debug debug testprog

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

Example 2

In this example, the DEBUG command names the load module to be debugged:

DEBUG >
debug dialog msgtext version 3

DEBUG DIALOG MSGTEXT VERSION 3
DEBUG > DEBUGGING INITIATED FOR MSGTEXT VERSION 3
DEBUG >

Example 3

This command requests a list of all programs defined to the debugger during the current session:

DEBUG >
debug all inquire

DEBUG ALL INQUIRE
PROGRAM TESTPROG VERSION 1
DIALOG MSGTEXT VERSION 3 PROCESS MSG-MAIN1 CURRENT
DEBUG >