TRANSFER Installation and Management Guide

Creating the Traffic Log
Managing a TRANSFER System
11–18 068837, Update 1 to 013198 Tandem Computers Incorporated
If you get this message, resolve the problem and stop and restart the servers. The most
common problems are that the file specified does not exist or that the file name was
specified incorrectly.
If there is a problem writing to the file, the servers report the following message each
time the error occurs:
Error nnn writing to the traffic log file yyyyy .
where nnn is the file error number and yyyyy is the file name.
If you get this message, resolve the problem and stop and restart the servers. The most
common problems are that the file is full or the volume is down for some reason.
Having these messages displayed does not affect the operation of the TRANSFER
system or the network. They merely indicate that there is a problem with the traffic
log mechanism so that no traffic log can be generated. Because the traffic log is for
statistical and debugging purposes only, you might chose to remove traffic logging
from the configuration to avoid these error messages.
Configuring the Traffic Log. You configure network traffic logging using the DEFINETR
file, explained in Section 5, “Defining a TRANSFER System.” You can specify the
location of the traffic log file and the number of extents with the following parameters:
TRNetTrafficLogFile
TRNetTrafficLogFileExts
These parameters are optional and reconfigurable. They are commented out with
double hyphens (--) at the beginning of a line in the TRDEFLTS file; if you want traffic
logging, remove the hyphens from these lines.
The GTRUPDT MACRO attempts to create a new traffic log file after each redefinition.
If the file already exists, it is not purged; the create fails with an error 10.
Redefinition also configures the ASSIGNs for the TWORK and TRECV server classes.
They share the same file when the feature is configured using DEFINETR.