Inspect Manual

Introduction
Inspect Manual—429164-006
1-6
Inspect Command Modes
Although there are no TNS OSS processes on TNS/E systems, you can use Inspect to
debug a TNS OSS snapshot on a TNS/E system.
Inspect Command Modes
Inspect provides two command modes: high-level mode and low-level mode. High-
level mode provides source-level access to your program, while low-level mode
provides machine-level access.
Each mode has its own set of commands, but they offer many of the same functions.
Besides display, modify, break, and trace capabilities, both modes provide
convenience commands such as HELP, FC, LOG, and OBEY.
High-Level Mode
To take full advantage of high-level Inspect, you should ensure that your program file
includes symbol information. Consequently, you must include the SYMBOLS compiler
directive in the source code or on the command line when you compile the source
code.
High-level Inspect provides features that let you:

Refer to code and data locations using source identifiers.

Modify the value or values of a data item.

Display the value or values of a data item, with extensive control of the display
format.

Step through your program in source or machine oriented increments.

Provide aliases for command strings.

Suspend program execution and automatically perform a specified action.

Save an image of a process for later examination.
Low-Level Mode
Low-level Inspect resembles Debug. To use either effectively, you must understand
the architecture of HP NonStop computer systems.
Your program file does not need to include symbol information to use low-level (or
high-level) Inspect. If it does have this information, you can use the high-level INFO
command instead of compiler listings or binder maps to discover the address,
addressing mode, and size of any symbol in your program. However, if your object
code does not contain symbols, you can point Inspect at a corresponding version of
the object.
Note. You can debug SCREEN COBOL programs in high-level mode only.