Inspect Manual

Debugging PATHWAY Applications
Inspect Manual—429164-006
5-8
Guidelines for Debugging Requester Programs
Requester Programs Started Using the RUN PROGRAM
Command
When you start a requester program using the PATHCOM command RUN PROGRAM,
the PATHCOM command terminal usually becomes the application terminal.
PATHMON assigns the terminal a synthetic application terminal name.
In this case, you need to determine the synthetic name before you can use the
INSPECT TERM command to begin debugging the requester program. Start
PATHCOM on another terminal and enter the command:
Look for a terminal name of the form nnn-term-mmm, where nnn and mmm are
sequence numbers and term is the device name (without the leading dollar sign) of the
terminal on which the requester program is running. You use this synthetic name in
the INSPECT TERM command to debug the requester program.
Guidelines for Debugging Requester Programs
The following subsections present guidelines that make the task of debugging
requester programs easier.
Breakpoints in Requester Programs

You can set code breakpoints anywhere in an active scope unit of a requester
program, and at the entry point of any inactive scope unit.

Data breakpoints are not permitted in requester programs.

A TCP can manage a total of twenty breakpoints, regardless of the number of
requester programs it is running. For example, if one requester program has ten
breakpoints, and two others have five each, you cannot set any more breakpoints
in any of the requester programs running under that TCP until you clear one of the
existing breakpoints.

When a requester program reaches a breakpoint, the TCP places the requester
program into a debugging hold state and informs the Inspect process, which then
performs the break action (if any) associated with the breakpoint. If there is no
break action, or if the action did not restore the PATHWAY requester program to
the run state, Inspect prompts at its command terminal for a command. When you
issue a RESUME or STEP command, Inspect informs the TCP, which then places
the PATHWAY requester program back into the run state and resumes executing it.
=STATUS TERM *
Note. When you use RUN PROGRAM to start a requester program, the TCP to which you
assign that program (using the SET PROGRAM TCP command) must be configured for
Inspect debugging; otherwise, you will not be able to debug the requester program.