Debugging in Menu Mode › Activity Screens › Debug Screen

Debug Screen

Two Sections

The specification area of the Debug screen also has two sections:

• The first section designates the load module to be debugged:

  DEBUG LOAD MODULE...:     TYPE: P (P-PGM/D-DIALOG/M-MAP/T-TABLE/S-SS)
  VERSION.............:
  

• The second section inquires about certain debugged modules or removes modules from the debugging process:

  OTHER ACTION........:   (I-INQUIRE/D-DELETE)
  LOAD MODULE OR <ALL>:
  VERSION.............:
  

You can submit both types of requests at the same time.

Field Options

These are the field options for this area:

DEBUG LOAD MODULE...:

Identifies the name of the entity to be debugged. The entity name can be up to eight characters long.

TYPE: P (P-PGM/D-DIALOG/M-MAP/T-TABLE/S-SS)

Identifies the type of module to be debugged:

• P (the default) identifies a program
• D identifies a CA ADS dialog
• M identifies a map
• T identifies an edit or code table
• S identifies a subschema

VERSION......:

Identifies the version of the load module to be debugged. If the version is not specified, the debugger uses the version you have set with DCUF TEST, or if none, version 1.

OTHER ACTION....: (I-INQUIRE/D-DELETE)

• Irequests a display of the load module(s) being debugged in this session
• D requests that the specified module(s) be removed from the list of load modules known to the debugger

LOAD MODULE OR <ALL>:

Indicates the load module(s) affected by the specified Other Action value. An entity-name identifies the single load module for which I or D is requested. Using All requests I or D for all load modules being debugged.

VERSION......:

Identifies the version of the load module for which I or D is requested. If no version is specified and there is more than one version of the load module being debugged, the debugger displays or deletes all versions. If a version is specified, the debugger displays or deletes only the specified version.