TRANSFER Installation and Management Guide

TSCHED Log
Troubleshooting
13198 Tandem Computers Incorporated 12–15
The TSCHED Log The TSCHED log contains not only actual TSCHED entries, but also entries for
TFRONT and TAREQ, which cannot issue requests on their own because they are
written in SCREEN COBOL.
TSCHED Entries
Entries that actually log TSCHED processing report the opens and closes of TSCHED.
In addition, the log reports errors associated with these opens and closes.
TFRONT Entries
Entries for TFRONT log the banner message and report PATHWAY SEND failures.
TAREQ Entries
Entries for TAREQ are of two types:
Entries logging the beginning and the end of an asynchronous event, telling you
when a TWORK server has completed its task.
All asynchronous events that are not incoming from another node in the network
must pass through a TAREQ pseudo-terminal thread. (Inbound events go
through TFRONT/TRECV.) When TSCHED has an event to be processed, it gives
it to an available TAREQ thread. Most asynchronous work is done by a TWORK
server on behalf of the TAREQ. For this reason, the TAREQ simply logs the
beginning and the end of the event by writing entries to the log; for example:
\NODEA.$TSCH 89-02-27 11:22:37 [1]:=[BEGIN]==============
\NODEA.$TSCH 89-02-27 11:22:37 [1]:=[END]================
If the TWORK log is enabled, you can find information about the processing of the
event in the TWORK log by checking the following:
Search all the TWORK logs for the approximate date and time of the event.
Match the thread number in the TSCHED/TAREQ and TWORK logs.
Entries reporting on the progress of local delivery of a package
As a package is delivered to correspondents who are registered on the local node,
TAREQ logs the following information:
The item ID of the item being delivered, in the format described in the
previous section
Local delivery as it occurs
The names of local recipients
If a correspondent has agents configured, the names of those agents as they
are invoked
The beginning and the end of TMF transactions
A single local delivery event can span more than one TMF transaction.