TRANSFER Installation and Management Guide

System Installation Procedures
068837, Update 1 to 013198 Tandem Computers Incorporated 6–41
2. Execute the GxxCOOL obey files, beginning with GTRCOOL :
8> PATHCOM $pm
=OBEY GTRCOOL
where $pm is the PATHMON process name of your existing PATHWAY system.
The GTRCOOL obey file must be executed first because certain servers have to be
running before the rest of the system can be started.
3. When GTRCOOL is done, execute the remaining GxxCOOL obey files to start the
rest of the TRANSFER system.
Note If you have a CUSTCOOL file that includes customer defined components that need to be started, be sure
to execute the CUSTCOOL file also.
Stopping TRANSFER in a
Mixed PATHWAY System
There are two approaches to stopping TRANSFER in a mixed environment.
One way to stop your TRANSFER system is to bring TRANSFER down with the
rest of the PATHWAY system. To do this, you enter the following commands:
1> PATHCOM $pm
= STOP TERM *
= ABORT TERM *
= STOP TCP *
= FREEZE SERVER *
= STOP SERVER *
= SHUTDOWN, WAIT
where $pm is the PATHMON process name of your existing PATHWAY system.
A second way to stop your TRANSFER system is to bring down only the
TRANSFER portion of the mixed environment. In order to do this, you must
either manually stop each TRANSFER object or create your own PATHCOM obey
file to do the work for you.
To create an obey file to stop only the TRANSFER portion of the mixed
environment, follow these steps:
1. Duplicate the contents of each GxxSTOP obey file into one file, def, starting
with the GTRSTOP command.
2. Get the TERM names (TAREQ, TWORK, and so on) of the terminals in your
TRANSFER system from the obey file that you created in Step 1 of the
previous subsection, “Configuring TRANSFER Initially in a Mixed
PATHWAY System.” Insert STOP and ABORT commands for each terminal
at the beginning of your new obey file, def:
STOP TAREQ1
ABORT TAREQ1
. . .
. . .
Stopping TRANSFER in a Mixed PATHWAY System