Inspect Manual

Debugging PATHWAY Applications
Inspect Manual—429164-006
5-7
Starting the Debugging Session
If you do not include the FILE option in the SET TERM INSPECT command, the
Inspect process uses the terminal specified in the SET TCP INSPECT command as its
command terminal.
Starting to Debug a Running Requester Program
To debug a running requester program, you must force it into the hold state, regardless
of how the requester program was started.
To put a running requester program into the hold state, use the PATHCOM INSPECT
TERM command:
This command directs the TCP to put the requester program running on the given
application terminal into the hold state, and directs Inspect to use the given command
terminal as the Inspect command terminal (provided that the TCP or the terminal has
not already specified the command terminal). The TCP puts the requester program
into the hold state after it finishes executing the current pseudocode instruction.
If you do not include the FILE option in the INSPECT TERM command, Inspect selects
its command terminal as follows:
1. The command terminal specified by the FILE option of the SET TERM INSPECT
command for the given application terminal.
2. The command terminal specified by the FILE option of the SET TCP INSPECT
command.
3. The TCP's home terminal.
If there is not an Inspect process active on the selected command terminal, $IMON
starts one automatically.
If an Inspect process is already active for the selected command terminal, PATHCOM
issues a warning and does not change the Inspect command terminal if you specify a
different command terminal in the INSPECT TERM command.
Example 5-2. Starting a Requester Program in the Hold State
=SET TERM FILE $mypway
=SET TERM INITIAL req-pgm
=SET TERM TCP debug-tcp
=SET TERM INSPECT ON (FILE $mydbug)
=ADD TERM req-term
=START TERM req-term
=INSPECT TERM application-term, FILE $INSPECT-command-term