Inspect Manual

Debugging PATHWAY Applications
Inspect Manual—429164-006
5-14
Preparation and Configuration
Preparation and Configuration
To take full advantage of Inspect, you should ensure that your user conversion routines
include symbol information. Consequently, you must include the SYMBOLS compiler
directive in the source code or on the command line when you compile the source
code for the user conversion routines.
Starting the Debugging Session
You can start debugging user conversion routines in one of two ways:

Start the TCP in the Inspect hold state.

Put a running TCP into the Inspect hold state.
Starting a TCP in the Hold State
Starting a TCP in the hold state enables you to put breakpoints in the user conversion
routines before the TCP begins executing. To start a TCP in the hold state, you need
to set the TCP's DEBUG status before you add the TCP. The PATHCOM command
SET TCP DEBUG sets the DEBUG status of a TCP:
Example 5-4 presents an example of starting a TCP, highlighting the PATHCOM
command that configures the TCP to start in the hold state.
If you do not use the SET TCP HOMETERM command, Inspect will use PATHMON's
home terminal as its command terminal.
If the TCP is running, you can stop it, alter its DEBUG status, and then restart it by
entering these commands:
This sequence effectively restarts the TCP in the hold state.
=SET TCP DEBUG ON
Example 5-4. Starting a TCP in the Hold State
=SET TCP CPUS 8:9
=SET TCP MAXTERMS 5
=SET TCP TCLPROG $pway.reqpgms.pobj
=SET TCP HOMETERM $mydbug
=SET TCP DEBUG ON
=ADD TCP debug-conv-rtns
=START TCP debug-conv-rtns
=STOP TCP tcp-name
=ALTER TCP tcp-name, DEBUG ON
=START tcp-name