TS/MP 2.5 System Management Manual

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 must 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.
• Requestor source code and object modules.
• For pending servers, a PATHMON dump
• Status information; at the system prompt, perform:
STATUS /OUT <statfile>/ *, PROG / *, PROG >, 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.
1. Determine whether it is in your users’ best interests to bring the PATHMON environment down
right away. A well-designed, well-tuned system might run for one or two days without the
PATHMON process. Contact users and find out whether critical applications are running as
expected. You might be able to wait before stopping the entire environment.
2. Capture data about the failure. Use VPROC to get the product version. If you are running the
PATHMON environment with DUMP ON, retrieve dumps from ZZPMnnn. Get any relevant
messages from the PATHMON log and the EMS log. Note what commands you were using
104 Maintaining a PATHMON Environment