Heading Area

Debugging in Menu Mode › Screen Design › Heading Area

Heading Area

Contents

The heading area includes three lines:

Header line
Currency line
Prompt line

Header Line

The header line contains several fields:

The PF-key field provides a two-position entry area for simulation of a program-function key. For example, typing a 5 in this field and pressing [Enter] has the same effect as pressing [PF5].
The simulated PF-key field is useful when your terminal does not have program-function keys. You can specify the numerals 1 through 24, as well as EN for [Enter], CL for [Clear], P1 for [PA1], and P2 for [PA2].
Product name and release number fields supply information formatted like this:
```
IDMS-DC REL n.n ONLINE DEBUGGER
```
The screen label field indicates the name of the current screen. The screen name changes as you move from one activity or help screen to another in the debugging process. (The sample screen is the List screen.)
The session mode field indicates whether you are in the setup or runtime phase of the debugging process. (The sample screen indicates a setup phase.)
Page notations supply the current page and the total number of pages available for the given display. The sample screen indicates that you are viewing the first page of a one-page display. Typically the help screens have more than one page. You can display a different page by:
- Overwriting the current page number on the header line and pressing [Enter]
- Using the designated control key to scroll backward or forward.

Default Control Key Assignments This table presents a list of the default control key assignments for the debugger:

Key	Action	Description	Function
[PF1]	Usage	Displays the Usage screen	2
[PF2]	Unassigned		5
[PF3]	Activity	Displays the activity screen for the current command	3
[PF4]	Help	Displays the help screen for the current command	4
[PF5]	Symbols	Displays the Symbols screen	9
[PF6]	Keys	Displays the default control key assignments	6
[PF7]	Scroll up	Displays the previous page	7
[PF8]	Scroll down	Displays the next page	8
[PF9]	Prompt	Returns the debugger to prompt mode	1
[PF10]	Unassigned		15
[PF11]	Unassigned		11
[PF12]	Reserved		12
[PA1]	Refresh	Refreshes the current screen	14
[PA2]	Exit	Exits the debugger	10
[Clear]	Return	Goes back one level	16
[Enter]	Process	Processes the current screen	13

The default control key assignments can be changed at DC/UCF system generation time with the KEYS statement.

For more information on the KEYS statement used in system generation, see CA IDMS System Generation Guide.

The Keys screen displays the key assignments for your particular installation.

Currency Line

The currency line displays the current values for five variable fields:

The entity type indicates whether a program, dialog, map, table or subschema load module is currently being debugged
The entity name field displays the name of the current entity
V:version-n displays the version number associated with the current entity
The section type field indicates whether a dialog process or a program CSECT is currently being debugged.
The section name field displays the current CSECT or process name

When the current entity is a program, the currency line reads like this:

PROGRAM: PROG01 V:3 CSECT:

When the current entity is a dialog, the currency line reads like this:

DIALOG: MISINDC V: 1 PROCESS: MIS-MAIN2

The currency line remains constant until there is a change in the entity of the CSECT or process being debugged. You can change the current CSECT or process by:

Overwriting the name on the screen and pressing [Enter] to automatically initiate the QUALIFY command
Issuing the QUALIFY command on the prompt line

Prompt Line

The prompt line is prefaced by an arrow (►) and functions in the same manner as the DEBUG> prompt in prompt mode. You can use the prompt line on any screen during menu mode; you can submit a single debugger command or a string of commands at any time.

For a complete discussion of the debug expressions and commands that you can enter on the prompt line, see Expression Components in Chapter 2, "Command Considerations" and Debugger Commands.