TRANSFER Installation and Management Guide

Steps for Moving TRANSFER Data Files
Managing a TRANSFER System
11–10 068837, Update 1 to 013198 Tandem Computers Incorporated
Steps for Moving TRANSFER Data Files
To move TRANSFER data files, follow these steps (not all data files require all steps):
1. Stop TRANSFER.
2. Move the actual data files. You can use the File Utility Program (FUP) either to
rename or to duplicate the files. If you move an alternate key file (for the
DSDATA, INTGROUP, IFOLDER, NAME, NET, READY, or TIME primary key
files), use FUP to alter the affected primary key file.
If you move the name directory files, ensure that they reside on the same
subvolume and that you have not changed the actual file names. If you move
other data files, you can put them on many different volumes and subvolumes.
Distributing them on different volumes usually improves the performance of
TRANSFER.
Note When you FUP DUP a TRANSFER database file that is audited, the audit flag is removed from the file at
the new location. You must do a FUP ALTER filename, AUDIT before bringing the TRANSFER
application back up.
3. If you move any TMF audited file, perform an online dump before starting your
TRANSFER system. See “TMF Audited Files” in Section 2 for a listing of the
audited TRANSFER data files.
4. If you move the name directory files, update user-written references to the
DSDATA file in obey files that invoke a copy of the NAMESRV program (the
Name server). Update the references with the current name of the DSDATA file.
The DSDATA file is the only name directory file that is referenced by name; it is
referenced as the IN file for the NAMESRV program.
All references to the DSDATA file in the generated TRANSFER system
configuration are automatically updated when you update the TRANSFER system
definition by performing Steps 6 and 7.
5. If the data files are Base TRANSFER component data files—except for the name
directory files—run the NALOAD program as described in the following
subsection, “Storing New Names with the NALOAD Program.”
6. Edit your define files for the components whose data files have been changed to
incorporate the new names. The define files affected are:
DEFINETR for Base TRANSFER data files
DEFINEX4 for X400 gateway data files
This step ensures that the current TRANSFER definition shows the actual file
names.
7. Run the definition programs (CDxxDEF and XCNFG) for redefinition according to
the directions in Sections 6 and 8. This run ensures that the file names referenced
in the generated PATHWAY configuration are correct.