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

Maintaining a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
5-27
Detecting Problems
These sections describe factors that can cause poor performance and steps you can
take to improve performance.
Detecting Problems
These factors might cause the PATHMON process to be busy at times other than
startup and shutdown:
•
Poor configuration
•
Creating and deleting links
•
Gathering statistics and information
•
Logging errors
•
Failures
Poor Configuration
If a link manager, such as a LINKMON process or TCP, cannot establish
communication with a server process, the link manager indicates this situation to the
screen program or Pathsend requester, and the PATHMON process writes an error
message to the log files. If you experience such a failure, you likely need to review
your configuration. The configuration size may need to be increased to handle the
load, or there may be a server class naming error.
Creating and Deleting Links
If the PATHMON process is configured so that it is constantly creating and deleting
links, it can become the busiest process in the processor.
The PATHMON process can also become busy creating and deleting links if an
application repeatedly sends Pathsend requests to a frozen server class, and the
LINKMON process has no links to that server class. The LINKMON process
repeatedly asks the PATHMON process for a link to the frozen server class, then
returns the link when the server is found to be frozen. This problem can be resolved if
the application, when notified that the server class is frozen, waits a given period of
time before trying again. For more information on configuring for optimum link
management, see Configuring Links for Optimum Performance on page 3-23.
Gathering Statistics and Information
The processor cost to maintain statistics is low. However, repeated reporting on
statistics (especially with the DETAIL option) or configuration information can impose
an added burden on the PATHMON process and its processor.