Inspect Manual

Inspect Manual—429164-006
14-1
14
Using Inspect in an OSS
Environment

Starting an Inspect Session on page 14-1

Ending an Inspect Session on page 14-2

Inspect’s System Type on page 14-2

File Name Resolution on page 14-2

Signals on page 14-3

Source Files on page 14-4

Usage Guidelines on page 14-4
Starting an Inspect Session
You can start an Inspect session in OSS in any of these four ways:

From the TACL prompt, enter:
>RUN INSPECT or INSPECT
From the OSS shell, enter:
gtacl -p inspect

From TACL prompt, you enter:
RUND program
From the OSS shell, you enter:
run -debug -inspect=on program

Issue a debug request on a running process.

A debug event occurs in a program.
In all cases, Inspect will be started as a Guardian process.
Inspect looks for an EDIT file named INSPLOCL in the volume and subvolume
containing the Inspect program file. After reading the INSPLOCL file, the Inspect
process looks for an EDIT file named INSPCSTM in the logon volume and subvolume
of the creator of the process being debugged. All OSS users have a corresponding
Guardian logon volume and subvolume.
To avoid incompatibilities between Guardian and the OSS terminal I/O when
debugging an OSS process, change Inspect’s command terminal to an existing
Guardian terminal using the TERM command as soon as Inspect comes up.