Open System Services Programmer's Guide

menus and dialog boxes. Using Visual Inspect, you control the execution and debugging of your
program from a PC while the program runs on a NonStop server.
Visual Inspect supports high-level symbolic debugging of native and TNS processes (interpreted
and accelerated) in the Guardian and OSS environments through a PC-based graphical user
interface. Visual Inspect can also be used for debugging snapshot files.
Visual Inspect is supported on both G-series and H-series systems. G-series and H-series Visual
Inspect are identical, except that the H-series version has been enhanced with machine-level
debugging capabilities; you can use H-series Visual Inspect for low-level debugging tasks on the
PC that must be done on the NonStop server using Debug or Inspect on G-series systems.
Visual Inspect is the preferred debugger in the native environments. It offers a simpler and more
intuitive user interface and more capabilities compared to the command-line debuggers, and is
designed to work in complex distributed environments. For example, working from a PC, you can
use Visual Inspect to debug multiple processes residing on the same or on different nodes in a
network. The processes can be TNS, native TNS/R, or native TNS/E, in the Guardian or OSS
environment.
You can start Visual Inspect by entering the RUNV command, either at the TACL prompt or from
the OSS shell. The following example starts execution of a program under control of Visual Inspect
on the client PC mypc:
Example 10 Starting the Visual Inspect Debugger
> RUNV WSADDR=MYPC gprog
$ runv -wsaddr=mypc ossprog
You can also start Visual Inspect by first establishing a client connection to Visual Inspect on a PC,
then entering a run command with -inspect=on. For example, assuming a Visual Inspect client
connection exists, the following command starts a program under control of Visual Inspect:
$ run -debug -inspect=on ossprog
Visual Inspect can also be started from within the Enterprise Toolkit - NonStop Edition (ETK) PC-based
program development environment (see “Using the HP Enterprise Toolkit - NonStop Edition”
(page 52) for more information).
NOTE: Beginning with the H06.24 and J06.13 RVUs, 64-bit OSS programs are supported. The
Native Inspect debugger starts when specifying a 64-bit OSS program as the ossprog parameter
for either the run -debug or runv command, because Visual Inspect does not currently support
64-bit programs.
See the Visual Inspect online help for more information on Visual Inspect.
Porting Kit
FLOSS
Beginning with the H06.15 and J06.04 RVUs , Freeware Look for OSS (FLOSS) is supported.
FLOSS is a set of command-line utilities and libraries that aid in porting open source software to
OSS. FLOSS is required only if you are rebuilding any of the open source packages that are posted
in the ITUGLIB website or wish to use it to assist in porting your own software package. FLOSS is
not required if the pre-built software packages are installed and used. For detailed information,
refer to the FLOSS on NonStop User Manual.
Guardian Tools
The following tools are available to you from the Guardian environment at the TACL prompt.
Using the Development Tools 49