Inspect Manual

Debugging PATHWAY Applications
Inspect Manual—429164-006
5-11
Preparation and Configuration
Preparation and Configuration
To take full advantage of Inspect, you should ensure that the server's program file
includes symbol information. Consequently, you must include the SYMBOLS compiler
directive in the source code or on the command line when you compile the server's
source code.
Debugging Attributes
As with a process, the debugging attributes of a server and of its creator determine
which debugger (Inspect or DEBUG) is used to debug the server. A server's creator is
always PATHMON, so you probably cannot control its debugging attributes (unless, of
course, you create your own PATHMON specifically for server debugging). As a result,
you should compile the server with the Inspect or SAVEABEND debugging attribute on.
For more information about debugging attributes and how to set them, see The
Debugging Attributes of a Process on page 4-4.
Server Versus Server Class
From an application standpoint, the PATHWAY environment manages server classes,
starting and stopping servers in a class as usage demands rise and fall. Inspect, on
the other hand, debugs a single server process. You must insure that the server
process you are debugging is the same one that PATHWAY will link to your requester.
You may want to configure (or reconfigure) the server class so that it represents a
single server process, using the PATHCOM commands:
If the server is running, you can freeze the server class, stop it, reconfigure it, and then
restart it:
Starting the Debugging Session
You can start debugging a server in one of two ways:

Start the server in the Inspect hold state.

Put a running server into the Inspect hold state.
=SET SERVER MAXSERVERS 1
=SET SERVER NUMSTATIC 1
=FREEZE SERVER server-class, WAIT
=STOP SERVER server-class
=ALTER SERVER server-class, MAXSERVERS 1
=ALTER SERVER server-class, NUMSTATIC 1
=START SERVER server-class