Inspect Manual

Inspect Concepts
Inspect Manual—429164-006
2-3
Prompting for Commands
Consequently, your system manager can customize the Inspect environment for all
Inspect sessions that run on your system.
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. However, for PATHWAY programs, Inspect uses the default volume and
subvolume of the individual who started PATHMON.
If the INSPCSTM file exists, Inspect reads and executes the Inspect commands it
contains. Consequently, you can customize your Inspect environment by creating an
INSPCSTM file that includes Inspect commands to configure the environment the way
you like it. Note that the commands in the INSPCSTM file override those in the
INSPLOCL file because Inspect processes the INSPCSTM file after the INSPLOCL
file.
Prompting for Commands
Whenever Inspect expects you to enter a command, it prints the Inspect prompt. By
default, the prompt has this form:
The dashes enclosing the program name (PRGOBJ) signify that Inspect is in high-level
mode; underscores enclosing the program name, as in _PRGOBJ_, denote low-level
mode.
The name between the dashes is the name of the program that you are currently
debugging. If you are not currently debugging any program, Inspect prompts you with
two dashes or two underscores, depending upon the current mode.
The SET PROMPT command enables you to customize the Inspect prompt to show
other types of information as well. For more information, see SET PROMPT on
page 6-178.
Reporting Events
When a debug event occurs, Inspect displays a status message that provides
information regarding the event. By default, the status message has this form:
The message begins with the text “INSPECT” to indicate that Inspect is generating the
message. Following this text is a description of the type of event that occurred. In the
example, the debug event is a break event caused by breakpoint number 1. The
definition of the breakpoint (#MAIN) follows the breakpoint number.
The second line of the message indicates where the event occurred. Inspect displays
the PID and name of the program in which the event occurred. It then shows the code
-PRGOBJ-
INSPECT BREAKPOINT 1: #MAIN
175,05,00066 TALOBJ #MAIN.#1862(TALSRC)