Inspect Manual

Inspect Concepts
Inspect Manual—429164-006
2-4
Ending an Inspect Session
location where the event occurred: line number 1862 within the scope unit MAIN,
whose source file is TALSRC.
The SET STATUS command enables you to customize Inspect event reporting. For
more information, see SET STATUS ACTION on page 6-186 and SET STATUS
LINE25 and SET STATUS SCROLL on page 6-187.
Ending an Inspect Session
An Inspect session can be stopped in several ways:

You exit, either by using the EXIT command or the RESUME * EXIT command

Your last program has completed

Your program is stopped by someone else
When you use EXIT to end an Inspect session, Inspect will prompt you for
confirmation. If you have not removed all breakpoints from the programs you have
been debugging before attempting to exit Inspect, Inspect will mention that all
breakpoints have not been removed and prompt you for confirmation.
What Inspect Debugs
You can debug or examine any of these program types with Inspect:

Processes

Save files

PATHWAY servers

PATHWAY requester programs
Inspect groups these four types under the common term “program.”
Processes
Processes are running machine-code programs. More specifically, a process is the
unique executing entity that is created when:

Someone runs object code from a program file by entering an explicit or implicit
TACL RUN command.

An existing process runs object code from a program file by calling the
NEWPROCESS, NEWPROCESSNOWAIT, PROCESS_CREATE_, or
PROCESS_LAUNCH_ system procedure.
Note. Inspect’s usage of the term program differs slightly from the general usage. Inspect
defines program as a file that contains a series of instructions. In this manual, such a file is
called a program file, and the term program is used to mean “a process, a save file, a
PATHWAY server, or a PATHWAY requester program.”