Using the ACUCOBOL-GT Debugger in MPE/iX Environments

The ACUCOBOL-GT run time includes a powerful and easy to use source-, symbolic-, and low-level debugger. Its capabilities and use are described in detail in Runtime Debugger. You can use the debugger via an HP terminal or from a PC running a terminal emulator (such as ScreenJet or Reflection); however, access to the debugger's menu bar may be restricted or require changes to the keyboard configuration. These issues are described below.

In every environment, the debugger includes a menu bar and command window. On systems with mouse support, the menus can be accessed directly with the mouse. On other systems, the menu bar is activated with function key F10 and the menus are navigated with the arrow keys. The Command window supports the traditional text-based command line interface. Most actions that can be initiated from the menu bar can also be specified in the command window.

On HP terminals, because the keyboard does not have several function keys that are common on PC keyboards (F10 and the arrow keys, in particular), the debugger's menu interface is not accessible. Instead, you should simply use the debugger's command window. For a list of commands and command syntax, see Debugger Commands. Functions keys F1 through F8 are available on most HP terminals and can be used to perform the actions described therein.

If you are using a PC-based system with terminal emulator software, you have the option of re-mapping the keyboard and redefining the termcap definition on the HP e3000 to enable F10 and the arrow keys and, thereby, gain access to the debugger's menu bar. Terminal emulator configuration is described in the next section.