Inspect Manual

Debugging PATHWAY Applications
Inspect Manual—429164-006
5-12
Starting the Debugging Session
Starting a Server in the Hold State
Starting a server in the hold state enables you to put breakpoints in it before it begins
executing. To start a server in the hold state, you need to set the DEBUG status of its
server class before you add the server class. The PATHCOM command SET SERVER
DEBUG sets the DEBUG status of a server class:
Example 5-3 presents an example of starting a server, highlighting the PATHCOM
command that starts the server in the hold state. Note that the example includes the
configuration commands to limit the server class to a single server and to assign the
server's home terminal to the Inspect command terminal.
If you do not use the SET SERVER HOMETERM command, Inspect will use
PATHMON's home terminal as its command terminal.
Starting to Debug a Running Server
If you want to debug a running PATHWAY server, you can start to debug it with Inspect
by entering the command interpreter DEBUG command:
This command activates Inspect, assuming that you have set the debugging attribute
of the server (or its controlling PATHMON) to INSPECT ON or SAVEABEND ON. If
you do not use the TERM clause, Inspect will use PATHMON's home terminal as the
Inspect command terminal.
To discover the process-id of the server, use the PATHCOM STATUS SERVER
command:
Provided that you have limited the server class to a single server (as discussed in
Server Versus Server Class on page 5-11.), the STATUS SERVER command will
display a single process ID.
=SET SERVER DEBUG ON
Example 5-3. Starting a Server in the Hold State
.=SET SERVER CPUS 8:9
=SET SERVER PROGRAM $pway.servers.myserver
=SET SERVER MAXSERVERS 1
=SET SERVER NUMSTATIC 1
=SET SERVER HOMETERM $mydbug
=SET SERVER DEBUG ON
=ADD SERVER debug-server
=START SERVER debug-server
17> DEBUG process-id, TERM $INSPECT-command-term
=STATUS SERVER server-class, DETAIL