TRANSFER Installation and Management Guide

TSRBLD Utility
Managing a TRANSFER System
11–24 068837, Update 1 to 013198 Tandem Computers Incorporated
TSRBLD Utility The Ready, Time, and Net files are used by the TRANSFER scheduler in the process of
delivering packages. These files are not TMF audited files; the entries in these files
must be regenerated after a failure that requires TMF recovery. The TSRBLD utility,
which is run after the TMF rollforward or autorollback process has been completed,
rebuilds the three scheduler files.
Your TRANSFER system must be running when you run the TSRBLD utility, which
means that the scheduler files must have been created properly and must have the
correct control records. If necessary, you can create these files before running TSRBLD
by executing the appropriate FUP commands and then recreate the control records by
running the TRANSFER XIINIT program. The Text server and the Name server must
be running. TSCHED does not have to be running; however, a message informing the
operator of the absence of TSCHED is displayed in the OUT file and log file if it is
enabled.
TSRBLD scans the TRANSFER database for packages that have either or both of the
Submitted and Canceled flags set and requests the scheduler to perform the
appropriate operations for those packages. This procedure generates entries for the
Ready, Time, and Net files; entries already in the files are not duplicated. Operations
that were previously completed are not repeated. TSRBLD also causes the scheduler
to schedule deletion of any item that neither belongs to a package nor is stored in a
folder. It also reschedules automatic unsaving of items saved in folders with an
unsave time set and deletes extraneous records from the Session file.
You can assign a log file to contain detailed output of item, folder, depot, and session
IDs. The format of the ASSIGN statement is:
ASSIGN LOG, $ location-name
$ location-name can be a disk file, spooler, or terminal.
The log is useful when TSRBLD has failed and you need information for debugging
purposes. If you do not specify a log file, no detailed output is written.
Always run TSRBLD first without a log file. If a failure occurs, you can then run
TSRBLD with the log. On a large database, the log file is very large and might fill up a
spooler collector. You can send the output to a terminal with multiple display pages
to avoid problems because of the log file’s size. The OUT file contains progress
messages and the final tally output. The progress messages are displayed when
multiples of 1000 item descriptors, folder records, and session records have been read.
The counter is reset for item descriptors and for folder records.
TSRBLD displays a list of item IDs and indicates the action taken for each item. A
summary is also displayed when TSRBLD has completed regenerating the entries in
the scheduler files.