TRANSFER Installation and Management Guide

What to Do About Poor Interactive Performance
Troubleshooting
12–8 13198 Tandem Computers Incorporated
Check both the server OUT files (which default to the console) and the server logs
to see if errors or retries are causing extra work.
An error 4990 indicates timeouts and usually suggests a need for tuning or load
balancing if the number of 4990 errors is excessive. The error subcode varies
depending upon which file is experiencing the I/O timeout. You can ignore
process timeouts from TISERV to TSCHED because these are only wakeup
messages.
If an error persists, use the following command:
FUP COPY filename ,,COUNT 20
to make sure that the file can be accessed. The file might be located on a volume
with too many other heavily accessed files, or an application using the same file
might be holding record locks too long.
Ensure that all TRANSFER servers with logging enabled have access to their
logging devices and that all servers have access to their HOMETERM device. For
instance, the process server is used when you format a message with PS MAIL
6530 or PS MAIL 3270. When TGAL is the chosen formatter, it needs to open the
PROCESS-SERVER server HOMETERM, which must be a real device; otherwise,
TGAL is suspended.
Check TMF status. Because the TRANSFER delivery system uses TMF
extensively, it is important that TMF be properly configured and running
smoothly. The Transaction Monitoring Facility (TMF) Management and Operations
Guide tells you how to manage TMF.
Check system load balancing.
Make sure that the CPUs in which the TRANSFER interactive servers and terminal
TCPs run are not overloaded. If the CPU load is not balanced correctly,
reconfigure your TRANSFER system to move the interactive servers and terminal
TCPs to less heavily loaded CPUs.
Use MEASURE to determine disk activity.
The IFOLDER and SESSION files are high-access files and should not be on disk
drives with other high-access disk files. You can also improve disk performance
by partitioning certain disk files. File partitioning is discussed in the following
subsection.
If the DBSAMPL file fills up, the TSAMPLE server stops trying to write sample
records to the file. After you have added extents to DBSAMPL, the TSAMPLE
server does not automatically begin writing sample records again. To reactivate
writing sample records, FREEZE, STOP, THAW, and START the TSAMPLE
server.