TRANSFER Installation and Management Guide

Glossary
13198 Tandem Computers Incorporated Glossary–13
TRANSFER asynchronous requester (TAREQ). A collection of SCREEN COBOL programs
that handles the actual delivery of a package to a depot. These programs are supplied
by Tandem and run within a standard PATHWAY TCP. The asynchronous requester
locates the recipients of a package, delivers the package to local depots, and transports
the package to remote nodes for delivery by their asynchronous requesters.
TRANSFER database. A set of internal files that contain information related to local
correspondents and packages in transit. The database is completely controlled by
TRANSFER.
TRANSFER interactive server (TISERV). A TRANSFER server that starts and terminates
sessions, services item and package handling requests, and handles administrative
requests.
TRANSFER name directory. A directory of all names of correspondents, interest groups,
distribution lists, and folders defined at the local node. TRANSFER uses this directory
whenever a local name is supplied by a correspondent.
TRANSFER X400 gateway. The application that allows TRANSFER correspondents to
exchange packages with users on other host systems that support the international
X.400 message-system standards.
Transporting. The TRANSFER action of sending a package to a remote node for local
delivery at that node.
TRAN-TCP. TRANSFER requester TCP that runs the ADMIN and TMANAGER
programs. At least one TRAN-TCP must be defined; you never need to have more
than one.
TRECV. TRANSFER network receiver server. TRECV servers are allocated by
TFRONTs to handle all incoming network operations. The TFRONTs assign a TRECV
for remote TWORKs as needed. You must define the TRECV server class to have at
least one member for every TFRONT pseudo-terminal you define at your node.
TSAMPLE. TRANSFER asynchronous system management server, which takes samples
of the TRANSFER database and scheduler queues for system monitoring.
TSCHED. TRANSFER scheduler that schedules, controls, and tracks all TRANSFER
activities that are performed independently of an application request. For example,
TSCHED controls delivery of packages and cleanup of ended sessions.
TSRBLD utility. The program you run after a system failure that rebuilds the three
scheduler files, Ready, Time, and Net.
TWORK. TRANSFER worker server. TWORK servers are used by TAREQ pseudo-
terminals to perform all local operations, except for package delivery and agent
invocation, and to perform the local portion of all network operations. You must
define the TWORK server class to have at least one member for every TAREQ pseudo-
terminal you define at your node.