TS/MP 2.5 System Management Manual

or functions you were performing at the time of the failure. Collect this information to have
available when you contact your HP representative for help.
3. Bring the PATHMON environment down using Guardian STOP commands to stop all
processes. For more information about the Guardian STOP command, see the Guardian
User’s Guide.
4. Start PATHMON again.
5. Coolstart the PATHMON environment.
Keep Development and Production Separate
HP recommends that you do not mix your development and production environments. Ideally,
maintain separate PATHMON environments for your development and production environments.
If you do not maintain separate environments, you might jeopardize the availability of your
production environment. For example, suppose there are problems with a Guardian server that
indicate the developer must use the Inspect product to debug the server. During this time, the server
is unavailable, and any processes attempting to establish links to the server could encounter an
unacceptable delay. Similarly, a TCP that handles both production and development SCREEN
COBOL requestors might not be able to respond to a user if a developer is making changes based
on development requirements.
If you cannot maintain totally separate development and production environments, try to keep as
much of your production environment separate as you can. It is highly 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 2.5 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 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 ACS subsystem processes or the TCP process.
• The last link granted by the PATHMON process is returned by a link manager that is the ACS
subsystem processes, however 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
ACS subsystem processes, and the associative server is 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 requestors continue to use
the server.
Keep Development and Production Separate 105