TRANSFER Installation and Management Guide

TWORK
Customizing a TRANSFER System
7–14 068837, Update 1 to 013198 Tandem Computers Incorporated
TRANSFER Worker Server
(TWORK)
TWORK servers are used by TAREQs to perform all local operations (except for
delivering packages and invoking agents) and to perform the receiving part of all
network operations. You must define the TWORK server class to have at least one
member for every TAREQ you define at your node; that is, the MAXSERVERS
parameter must equal or exceed the number of TAREQ pseudo-terminals you define.
The TWORK server class definition can be modified; however, you must exercise great
care to ensure that deadlocks do not occur while TRANSFER is running. The
LINKDEPTH and MAXLINKS parameters must both be set to 1. Do not set the
IOTIMEOUT parameter for this server class; TWORK operations are often very long.
The TWORK server class can be assigned a log and a debug log file. You usually
assign these files through the TRTworkServLog and TRTworkServDebugLog
parameters in the DEFINETR file. The following are sample ASSIGN parameters that
are generated in GTRCNFG:
ASSIGN DEBUGLOG, $S.#TWORK.DEBUGLOG
ASSIGN LOG, $S.#TWORK.LOG
The log file receives messages for all types of server activity. Messages related to
serious problems encountered by the server are duplicated in the server OUT file as
long as the server OUT file and the log file are not the same file. A log file is
recommended because it contains information needed to diagnose problems. The
LOGRECSPEROPEN parameter limits the size of the log file.
Other parameters that you can change through PARAM specifications are listed in
Table 7-6.