Inspect Manual

Debugging PATHWAY Applications
Inspect Manual—429164-006
5-6
Starting the Debugging Session
Because you can alter the configuration of a TCP only when it is stopped, the actual
sequence of commands is:
If you do not include the FILE option in the SET or ALTER command, the Inspect
process uses the TCP's home terminal as its command terminal.
After you are finished debugging the requester program, you can turn off the TCP's
Inspect capabilities using the ALTER TCP Inspect command again:
Starting the Debugging Session
After configuring the TCP for requester program debugging, you can begin debugging
requester programs in one of two ways:

Start the requester program in the Inspect hold state.

Put a running requester program into the Inspect hold state.
Starting a Requester Program in the Hold State
Starting a requester program in the hold state enables you to put breakpoints in it
before the TCP begins executing it. To start a requester program in the hold state, you
need to make it the initial program of a PATHWAY terminal, configure that terminal for
Inspect debugging, and then start the terminal. The PATHCOM commands SET TERM
INITIAL and SET TERM INSPECT enable you to do this:
Example 5-2
on page 5-7 presents an example of starting a requester program,
highlighting the PATHCOM commands that start it in the hold state. Note that the TCP
specified in this example is the one configured for requester program debugging in
Example 5-2.
=STOP TCP TCP-name
=ALTER TCP TCP-name, INSPECT ON (FILE $INSPECT-command-term)
=START TCP TCP-name
=STOP TCP TCP-name
=ALTER TCP TCP-name, INSPECT OFF
=START TCP TCP-name
Note. At one time, a TCP can control a maximum of eight terminals that are involved in
Inspect debugging. A TCP can process a total of 20 breakpoints for the set of all requester
programs being debugged with Inspect under that TCP.
=SET TERM INITIAL requester-program
=SET TERM INSPECT ON (FILE $INSPECT-command-term)