TRANSFER Installation and Management Guide

Format for Log Entries
Troubleshooting
13198 Tandem Computers Incorporated 12–13
Understanding and
Using the Log Files
The TRANSFER asynchronous processes generate logs that help you solve problems
with your delivery system. You can control the logging of these processes from the
TMANAGER DYNAMIC LOG CONTROL screen, which is discussed in Section 10 of
this guide.
The Format for Log Entries The following example shows the format for log entries:
\NODEA.$TSCH 89-02-27 11:22:37 [1]: information
The entry tells you the following:
\NODEA.$TSCH is the name of the process writing the log entry. This can be a
TSCHED, a TWORK, or a TRECV process name.
89-02-27 is the date the entry was made.
11:22:37 is the time the entry was made.
[1] is the internal TAREQ thread number. The number inside the brackets is the
index to the TSCHED opener table.
This number is passed to the TWORK server, and that server also displays this
number in its log. You can, therefore, associate the TWORK log with the
TSCHED/TAREQ log when you need to.
If the TSCHED log does not have a thread number, there is no corresponding
entry in the TWORK log.
The colon (:) appears only in the TSCHED/TAREQ or the TSCHED/TFRONT log.
It indicates that the entry is really a TAREQ or TFRONT entry being written by
TSCHED. Two colons (::) indicate a Cleanup TAREQ entry.
By examining the log, you can distinguish between actual TSCHED log entries and
TAREQ or TFRONT log entries.
The entry concludes with information about a process. The data varies depending
on the entity providing the data and the type of event being processed.