Introduction › Debugging Process › Menu Mode

Menu Mode

Choosing Activities from Screens

Menu mode is designed to make your options easy to see. You can enter commands or display information by filling in the fields on a series of fixed-format screens:

• Activity screens provide fields for commands that require additional input
• Individual help screens provide detailed descriptions of each command
• The Usage global help screen summarizes debugging activities
• Two other global help screens let you display program and debugger symbols and program function key (PF-key) assignments

For a complete description of each of the screens, see Debugging in Menu Mode.

Initiating a Debugger Session

To initiate a debugging session in menu mode, issue the DEBUG task code followed by the MENU command in response to the Enter Next Task Code prompt:

ENTER NEXT TASK CODE:
debug menu

When you enter this command, you see the Usage screen, which is the top-level menu screen:

   IDMS-DC REL nn.n ONLINE DEBUGGER *** USAGE ***        SETUP    PAGE  1 OF  4
  PROGRAM:           V:          CSECT:
  ->
                     PROCEDURAL COMMANDS.

  EXIT.....RETURNS CONTROL TO IDMS-DC/UCF WITHOUT TERMINATING THE CURRENT DEBUGGER SESSION
  QUIT.....TERMINATES THE DEBUGGER SESSION AND RETURNS CONTROL TO IDMS-DC/UCF.
  PROMPT...INVOKES THE PROMPT MODE OF THE DEBUGGER.


                     RETRIEVAL COMMANDS.

  AT.......ESTABLISHES OR MODIFIES BREAKPOINTS WITHIN A USER PROGRAM.
  DEBUG....DESIGNATES, DURING THE SETUP PHASE, THE ENTITY TO BE DEBUGGED OR
           INQUIRES ABOUT ENTITIES KNOWN TO THE DEBUGGER.
  IOUSER...DISPLAYS THE USER SCREEN THAT IS CURRENT WHEN A BREAKPOINT, PROGRAM
           INTERRUPT OR TRAPPED ABEND IS ENCOUNTERED.

  NEXT _ ACTIVITY OR _ HELP:
       _ AT       _ LIST      _ SET      _ SNAP    _ RESUME     _ DEBUG  _ WHERE

       _ EXIT     _ PROMPT    _ QUIT     _ IOUSER
  HELP SCREENS:   _ USAGE     _ SYMBOLS  _ KEYS

Switching Mode

To switch from prompt mode to menu mode, issue the MENU command in response to the DEBUG> prompt:

DEBUG >
menu

Now you also see the Usage screen.

Going to a Specific Screen

To go to a specific activity screen or global help screen, issue the MENU command followed by a valid screen name. This example illustrates the use of the DEBUG task code with a MENU command that names the screen to be displayed:

ENTER NEXT TASK CODE:
debug menu at

When you enter the above command, you invoke the debugging facility in menu mode and see the At command activity screen:

   IDMS-DC REL nn.n ONLINE DEBUGGER *** AT ***           SETUP    PAGE  1 OF  1
  PROGRAM:           V:          CSECT:
  ->








  ADD BREAKPOINT AT:

  BEFORE: MAX                  AFTER: 0                    EVERY: 1


  OTHER ACTION.......:   (I-INQUIRE/D-DELETE/G-IGNORE)
  BREAKPOINT OR <ALL>:

  NEXT _ ACTIVITY OR _ HELP:
       _ AT       _ LIST      _ SET      _ SNAP    _ RESUME     _ DEBUG  _ WHERE

       _ EXIT     _ PROMPT    _ QUIT     _ IOUSER
  HELP SCREENS:   _ USAGE     _ SYMBOLS  _ KEYS

Valid Commands

Menu mode allows the same set of debugger commands as prompt mode, with the exception that the PROMPT command is allowed and the MENU command is disabled.

Leaving Menu Mode

To leave menu mode you can:

• Select the PROMPT activity
• Return to prompt mode with the associated control key
• Enter the PROMPT command on the menu DEBUG> prompt line

Note: If you leave menu mode with an EXIT command or with the CLEAR control key, the debugger remains in menu mode. Subsequently, when control returns to the debugger, the debugger is still in menu mode. The debugger remains in menu mode until you issue the PROMPT command.

Note: For a more detailed discussion of menu mode, see Debugging in Menu Mode.