TS/MP System Management Manual (G06.24+, H06.03+)

Maintaining a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
5-32
Maintaining Associative Server Processes
recommended that you maintain separate sets of development and production server
classes. It is also desirable to define separate TCPs for development and production.
Certain types of errors, such as timeout errors, can also occur when you are
debugging servers in a Pathway application. For further information about these
errors, see the section on servers in the TS/MP Pathsend and Server Programming
Manual .
Maintaining Associative Server Processes
An associative server is a process within a server class that can be started outside of
the PATHMON environment by a process other than the the PATHMON process that
controls the server class. An associative server process is configured with this
command:
= SET SERVER PROCESS $process-name (ASSOCIATIVE ON)
The PATHMON process can change the state of an associative server process from
stopped to running without actually creating a new server process. If the PATHMON
process attempts to create an associative server process and discovers that the server
process already exists, the PATHMON process changes the server state to running
and uses the existing server process (instead of reporting an error).
Similarly, the PATHMON process can change the state of an associative server from
running to stopped even if the process is still running. This situation can occur when:
•
A STOP SERVER command is issued. The PATHMON process only waits until all
links granted by the PATHMON process are returned by the LINKMON or TCP
process.
•
The last link granted by the PATHMON process is returned by a link manager,
such as the LINKMON process, but the server was not started by the PATHMON
process.
In both of these cases, the PATHMON process changes the state to stopped without
waiting for the server to terminate.
When the last link granted by the PATHMON process is returned by a link manager,
such as the LINKMON process, and the associative server has been started the server
state is left as running (instead of being changed to pending). When the server state is
running, the PATHMON process can continue to allocate links to the server during the
period that other requesters continue to use the server.
There is an interval when the PATHMON process can grant a link to an associative
server process that is stopping itself. Although the stopped state allows you to use the
ALTER SERVER command to specify changes for configuration attributes, the
changes you specify do not take effect until the associative server is actually stopped
and then restarted from the same the PATHMON process. Changes to these