TRANSFER Installation and Management Guide

Base TRANSFER Configuration
The TRANSFER Environment
2–18 068837, Update 1 to 013198 Tandem Computers Incorporated
TRANSFER
Configuration
Overview
TRANSFER includes PATHWAY terminal control processes (TCPs), server processes,
terminals, and programs that control communications within the TRANSFER
environment. The processes required for your TRANSFER system depend, in part, on
the TRANSFER components included in your system.
The following paragraphs briefly describe the processes associated with each
TRANSFER component, dependencies for component definition, and other
requirements for a TRANSFER system.
These processes are configured in the TRANSFER PATHWAY system through
definition parameters for the components of TRANSFER. Parameter descriptions are
provided in Appendix A of this manual.
Base TRANSFER
Configuration
Base TRANSFER provides an essential set of TCPs, pseudo-terminals, servers, and
programs to control communications within TRANSFER. (A pseudo-terminal is a
PATHWAY requester process that has no user interface.) Base TRANSFER
components include the following:
TAREQ-TCP
TRANSFER asynchronous requester TCP that runs the TAREQ and TFRONT
pseudo-terminals. At least one TAREQ-TCP must be defined.
TAREQ pseudo-terminal
TRANSFER asynchronous requester. The number of TAREQ pseudo-terminals
that you define, in conjunction with your definition of the TWORK server class,
determines the number of simultaneous asynchronous local operations and
outgoing network operations that can be active at a single time. The TWORK and
TISERV-ASYNC server classes must be defined to have at least one member for
each TAREQ pseudo-terminal you define.
TFRONT pseudo-terminal
TRANSFER receiver front end. The number of TFRONT pseudo-terminals that
you define, in conjunction with your definition of the TRECV server class,
determines the number of simultaneous incoming network operations that can be
active at a single time. The TRECV server class must be defined to have at least
one member for each TFRONT pseudo-terminal you define.
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 outgoing 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.