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

Maintaining a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
5-30
PATHCOM-Specific Problems
If error dumping has not been specified and the PATHMON tables (showing, for
example, server states) appear to be in error, your representative may ask that you
force a dump by performing:
>PATHCOM $<pm>
=CONTROL PATHMON, DUMPMEMORY (FILE <pmdump>)
=EXIT
where pm is the name of your PATHMON process and pmdump is name of the dump
file.
Note that the DUMPMEMORY option is not a substitute for setting the DUMP option to
ON. DUMPMEMORY is primarily useful in a controlled troubleshooting situation where
you need to take a snapshot of the internal state of the PATHMON process at a
particular time—before it encounters a fatal error. You should only force a dump if
your HP representative specifically requests it.
PATHMON Configuration and Object Information
Make the PATHCTL file available to your HP representative. Also, use PATHCOM
commands to display information about PATHMON-controlled objects at the time of the
problem, as follows:
>PATHCOM $<pm>
=INFO object
=EXIT
where pm is the name of your PATHMON process and object is the name of a server
class.
SPI Data
If the PATHMON problem is SPI-related, get the source code and object module of the
DSM application process.
PATHCOM-Specific Problems
If detect a problem with PATHCOM, collect the following for your HP representative’s
review:
•
The PATHMON configuration file, PATHCTL
•
The command sequence that produced the problem
Server-Specific Problems
Collect this information if you detect a problem with a server class:
•
Server source code and object modules.
•
Requester source code and object modules.
•
For pending servers, a PATHMON dump