TS/MP System Management Manual (H06.05+, J06.03+)

Maintaining a PATHMON Environment
HP NonStop TS/MP System Management Manual—541819-007
5-31
PATHCOM-Specific Problems
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
•
Status information; at the system prompt, perform:
STATUS /OUT <statfile>/ *, PROG <prog filename>, DETAIL
where statfile is the listing file that captures the status display in an edit file,
and prog filename is the server program’s file name.
Recovering from PATHMON Failure
If PATHMON fails, perform these steps to capture data about the failure and restart the
PATHMON process.