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

Maintaining a PATHMON Environment
HP NonStop TS/MP System Management Manual—541819-007
5-30
PATHMON-Specific Problems
Version Procedure
Use the VPROC procedure to get the product version for the applicable PATHMON
components, as follows:
>VPROC
Enter filename:
>$<vol.subvol>.PATHCOM
>$<vol.subvol>.PATHMON
where $vol.subvol is the system volume and subvolume on which the desired
component resides.
Event Log and CONFLIST
Be sure to collect any PATHMON and EMS log files. Also include the
$SYSTEM.SYSnn.CONFLIST file.
Configuration and Startup Information
If you are able to reproduce the problem, give the HP representative a simple test case
illustrating the problem along with a description of how to reproduce it. Otherwise, give
the representative the object modules and data files (PATHCONF files) making up the
PATHMON configuration when the error occurred.
PATHMON-Specific Problems
Collect this information when you detect a problem with the PATHMON process itself.
PATHMON Dump
As explained in Requesting Error Dumping you can request error dumping by
specifying either the SET PATHMON, DUMP ON command or the CONTROL
PATHMON command. If you request your HP representative’s help in analyzing a
problem, the representative will likely require a DUMP file. It is therefore
recommended that DUMP be set to ON for production systems.
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