TRANSFER Installation and Management Guide

System Recovery and Maintenance
Managing a TRANSFER System
11–22 068837, Update 1 to 013198 Tandem Computers Incorporated
System Recovery and
Maintenance
Recovery of your TRANSFER system after a catastrophic failure is a two-phase
operation. The TMF autorollback or rollforward procedures must be performed to
return the audited files in the TRANSFER database to a consistent state. The files used
by the TRANSFER scheduler must then be regenerated; the TSRBLD utility is
provided with TRANSFER to perform this operation. The TCHECK utility is also
provided for maintaining consistency of the Base TRANSFER data files.
TMF Recovery When the TRANSFER database files are audited by TMF as recommended, the
database can be recovered to a consistent state after a catastrophic failure. Database
recovery is initiated by the TMFCOM command RECOVER FILES. TMF restores the
database files to the state of the last online dump and then invokes the rollforward
process, which applies the audit trails to the restored database files and brings the files
to the latest possible consistent state. The TMF recovery procedure is detailed in the
Transaction Monitoring Facility (TMF) System Management and Operations Guide.
XIINIT Utility The XIINIT program is used to initialize the database files that TRANSFER uses. The
initialization consists of inserting the version control record for each file that is empty.
XIINIT does not write version control records to files that are not empty.
XIINIT also creates the following depots if they do not exist: the asynchronous
requester depot (_TRANSFER_), the model depot, the model group depot, the PUBLIC
depot, and the X400 gateway depot (_X400_).
XIINIT is usually run for the system manager by the GTRINIT obey file when the
TRANSFER database is originally established; after this time, you can run XIINIT to
reinitialize TRANSFER database files that have been emptied for some reason. The
primary reason for rerunning XIINIT is to initialize the Ready, Time, and Net files
before running TSRBLD, which is described in the next subsection. If one of the four
special depots listed above has been deleted, you can run XIINIT to recreate that
depot. Execute a FUP PURGEDATA command for the Ready, Time, or Net files and
their alternate key files after a system failure. XIINIT inserts new version control
records into the files, and TSRBLD reconstructs the file contents.
The Text server and the Name server must be running before XIINIT is run.
XIINIT attempts to insert the control record for all files that make up the TRANSFER
database. Warnings are issued for files that have correct control records. Errors result
for any files that do not have correct control records (this should occur only if you are
using the wrong version of XIINIT).