Native Inspect Manual (H06.13+, J06.03+)

• Native Inspect does not contain formatting support for SPI buffers. You must use Visual Inspect
to display SPI buffers.
• The Inspect DISPLAY command is used in Inspect to print variable values. In Native Inspect,
the display command is defined to add variables and expressions to the automatic display
list – a list that is automatically displayed each time the program is suspended. The Native
Inspect print command and output command are equivalents to the Inspect DISPLAY
function.
COBOL-Specific Differences
The following capabilities of Inspect are not supported in Native Inspect:
• Setting breakpoints using the program-unit.label or program-unit.line-number
notation.
• Using PICTURE and FORMAT clauses for displaying items.
• Formatting records as an arbitrary type (DISPLAY AS command).
• Setting breakpoints on statement ordinals.
Process Debugging Using Native Inspect
Use Native Inspect to debug TNS/E native processes (and snapshot files) in either the Guardian
or HP NonStop Open System Services (OSS) environment.
The Native Inspect licensed object file is $SYSTEM.SYSnn.EINSPECT. Native Inspect runs as a
native, non-priv, high-pin process, separate from the process being debugged (see Comparing
Native Inspect to Debug (page 17)).
Native Inspect must always be running in the same CPU as the process you want to debug, as
shown in Figure 1 (page 19).
Languages Supported by Native Inspect
• TNS/E native C/C++
• pTAL
• TNS/E native COBOL
To debug code written in any other language for TNS/E systems or snapshot files created on a
TNS/R system, you must use Visual Inspect or Inspect.
18 Introducing Native Inspect