TRANSFER Installation and Management Guide

What to Do When Mail Is Not Delivered
Troubleshooting
12–2 13198 Tandem Computers Incorporated
If you have used TMANAGER to change the server log file, the PARAM LOG
location does not reflect the current log file; check TMANAGER instead.
1> pathcom $trpm
= info server a-tsched
SERVER A-TSCHED
.
.
.
OUT \XYZ.$TLOG
PARAM LOGRECSPEROPEN "10000"
ASSIGN LOG "$S.#LOG.TSCHED"
PARAM NAMESPACE "$T.CORR"
.
.
=
Common problems include:
The A-BASE-TEXT and A-NAME servers are not running.
The database files do not have enough space.
TMF is not running.
Understanding the log files is discussed later in this section.
If a problem is apparent, resolve it and restart any server that is not running. If
more than one server needs to be started, the easiest way to ensure that the servers
are restarted in the correct sequence is to use the START SERVER * command from
PATHCOM.
If errors 1003 and 3115 appear, you can ignore them.
Check the terminal status, using the PATHCOM STATUS TERM * command.
TAREQ terminals must be running to pass work to TWORK. Each TWORK server
must have one TAREQ configured. In addition, TFRONT terminals must be
running to pass work to TRECV, and each TRECV server must have one TFRONT
configured.
Restart any TAREQ or TFRONT terminal that is not running.
Check TWORK network status.
If you are running TRANSFER on more than one node, some of the TWORKs can
get tied up while trying to complete an OPEN request to a server on the
designated node. You can identify any TWORKs that are in this state by printing
the contents of the ROPENCTL file, which is the control file used by the TWORK
servers to control network OPEN requests. (The ROPENCTL file must reside on
the same subvolume as the PROFILE file.) If a TWORK has an entry in this file
that is older than five minutes, that TWORK is not available for delivery until the
network problem is solved.