TRANSFER Installation and Management Guide

12 Troubleshooting
13198 Tandem Computers Incorporated 12–1
Overview If you have a problem with the TRANSFER delivery system, you can take several steps
to determine what is wrong. This section on troubleshooting suggests what to do
when mail is not delivered or performance is poor. It describes how to use the log files
to pinpoint the difficulty. It also tells you how to isolate your node from the network
if you need to.
What to Do When Mail
Is Not Delivered
If mail is not being delivered to your node, you can take certain steps. Enter
PATHCOM; from your command interpreter, type:
1> PATHCOM $ process-name
where $ process-name is the name of PATHMON under which your TRANSFER
system is running. PATHMON is the central monitoring process in a PATHWAY
system. For most TRANSFER systems, the process name is $TRPM. (Examples in this
section use the TACL prompt n > as the command interpreter prompt.)
With PATHCOM, you can do the following:
Check the status of these servers:
A-TSCHED, which is required to schedule work
TWORK, which does the actual delivery
TRECV, which receives packages from other nodes in the network
TISERV-ASYNC, which is used by TAREQ to access the database
If a server is not running, check both the server OUT files (which default to the
console) and the server logs for error messages.
Note The SPREP server, A-STATS, is an exception. After A-STATS completes its initial run when TRANSFER
is started, it stops; therefore, it is normal for A-STATS not to be running when you check.
Only the A-TSCHED, TRECV and TWORK servers can have logs configured. If
you do not know where to find the log file or OUT file for a particular server, you
can use the PATHCOM INFO SERVER server name command. If the log is
configured, the INFO SERVER command lists PARAM LOG filename . The OUT
file is listed by the INFO SERVER command as OUT filename .