TRANSFER Programming Manual

Appendix B Processes Running Outside
PATHWAY
40970 Tandem Computers Incorporated B–1
PATHWAY is required for configuring a TRANSFER system. To configure a
TRANSFER system, you must:
Define the server classes used by the TRANSFER delivery system and the
application, including at least one copy of TISERV for use by the TRANSFER
TAREQs
Define the TAREQ SCREEN COBOL object file
Define the TRANSFER name server that handles the name directory and the
TRANSFER scheduler server that handles asynchronous processing (which must
be defined as server classes with only one member each)
Processes outside the PATHWAY environment cannot take advantage of PATHWAY
load-balancing features and provisions for fault-tolerant operation. For example:
If a requester not controlled by PATHWAY is communicating with a PATHWAY
server and the server cannot adequately handle this additional requester, the
ability of PATHWAY to maintain the system load balance might be affected.
If a server outside the PATHWAY operating environment is not running as a fault-
tolerant process and the CPU on which it is running becomes unavailable, you
must recreate the server.
If a requester not controlled by PATHWAY requires a TMF transaction restart, the
requester must handle the restart context management that is normally handled by
the PATHWAY SCREEN COBOL RESTART-TRANSACTION verb.
After the TRANSFER name and scheduler servers are running, you can start other
TRANSFER processes that run outside the PATHWAY operating environment.
TRANSFER servers running outside the PATHWAY operating environment must
communicate with the TRANSFER Name Server to locate required TRANSFER objects.
To permit this communication, the PARAM NAMESPACE must be passed to these
TRANSFER servers at startup time.