TRANSFER Installation and Management Guide

Steps to Install the System
System Installation Example
13198 Tandem Computers Incorporated E–5
Separately changes the process names for PATHMON, the Name server, and the
TRANSFER Scheduler server by modifying the ?LET commands at the beginning
of the DEFINETR file as follows:
?LET PathmonName = $TXPM (Changed from $TRPM)
?LET TschedName = $TXTS (Changed from $TSCH)
?LET NameServName = $TXNS (Changed from $T)
DEFINEML File Modifications
Next, the system manager goes through the DEFINEML file for PS MAIL 6530 and
makes the following changes:
Sets MLUserDSV to the name of the DSV for the TRANSFER software:
$DISKX.MLDSV in the example.
Comments out MLUserTclProg by prefacing the line with two hyphens ( -- ). The
system will not use extensions to the Tandem mail client, so this parameter does
not need to be set.
Changes server process names for MLMailTcpNames to begin with TM instead of
ZC.
Changes server process names for MLTextServName to begin with TM instead of
ZC.
Step 5: Define
Base TRANSFER
The definition programs reside on the TRANSFER software DSV. The system
manager now invokes the CDTRDEF program to define Base TRANSFER on the
configuration subvolume, $DISKA.TRANCNFG:
> RUN $DISKX.TRANDSV.CDTRDEF $DISKA.TRANCNFG INITIAL
Step 6: Initialize
Base TRANSFER
The CDTRDEF program creates a file called GTRINIT in the configuration subvolume.
The system manager types the following commands at the TACL prompt to run
GTRINIT and initialize Base TRANSFER:
> VOLUME $DISKA.TRANCNFG
> OBEY GTRINIT
The following messages appear:
OPEN $TXPM; SHUTDOWN,WAIT
ERROR - FILE OPEN ERROR - $TXPM - nonexistent device (14)
STOP $TXPM
Non-existent process $TXPM
STOP $TXNS
Non-existent process $TXNS
STOP $TXXT
Non-existent process $TXXT