TRANSFER Installation and Management Guide

Using the X400 Logs for Troubleshooting
Troubleshooting
12–30 13198 Tandem Computers Incorporated
Using the X400 Logs for
Troubleshooting
In addition to the general suggestions for using logs given earlier in this section, you
can use the X400 logs for troubleshooting your TRANSFER X400 gateway. Tracking a
problem with either the exporter or the importer log is easiest if there was only one
process in the server class running.
When you use either of the X400 logs to solve a problem, do the following:
Set the DEBUGLOGLEVEL PARAM for the server class to 0; set OUT to where
you want the debug log to go.
When you read through the log file, notice the last thing that the server had
intended to process before it indicated there was an error. Look for that
information in the item (or message) that you tried to export (or import) to make
sure the information is correct.
Look to see if a status package was returned to the sender, if exporting, or a non-
delivery report was sent to the originator, if importing. If you find one, notice the
reported problem.
Check the following:
Did this package pass through any nodes running a version of TRANSFER
that did not support X400 names? If a TRANSFER message is sent to an
earlier version of TRANSFER, the X400 information is not sent with it. A
message that was imported cannot be sent to a node that is running an earlier
version of TRANSFER.
Are all of the recipient names correct?
Note System analysts have access to a maintenance utility, X4GWCOM, that they can use to look at the queue
file. X4GWCOM is documented in the TRANSFER softdoc file. This tool is for use only by Tandem
support personnel; it is not intended for use by customers.