TRANSFER Installation and Management Guide

TCHECK Divisions
Managing a TRANSFER System
11–28 068837, Update 1 to 013198 Tandem Computers Incorporated
TMANAGER also uses this six-digit format for item IDs. If you do not enter an item
ID, TCHECK checks the first item in the file. If you do not enter an item count,
TCHECK processes to the end of the item data file.
Note If you enter the BREAK key at the confirmation prompt, TCHECK interprets BREAK as a negative
response. TCHECK aborts the TMF transaction and all updates are backed out.
To run TCHECK, you must be running under the user ID owning the TRANSFER
PATHWAY system. All TRANSFER servers except the Name server and the Text
server must be stopped; the Name server and the Text server must be running.
To help you run TCHECK on a regular basis, you can create an obey file that starts the
Name server; see “Starting the TEXTSRV and NAMESRV Programs,” which appears
earlier in this section.
You can enter TCHECK directives either as PARAM messages or as RUN command
parameters, or you can accept the defaults for the directives. Directives in the RUN
command override directives in PARAM messages.
TCHECK puts out three types of messages: informational, progress, and
inconsistency. If you run TCHECK with the log file separate from the prompt file,
which is the recommended procedure, progress messages are written to the prompt
file and inconsistency messages are written to the log file; informational messages are
written to both files. TCHECK inconsistency messages are listed and described in
Appendix B, “Error Messages.”
The prompt file, which must be a terminal, receives informational messages indicating
the TRANSFER object that TCHECK is currently scanning and progress messages
indicating what has been checked. When the scanning is finished, TCHECK displays
statistics indicating the magnitude of the updates and then prompts you to confirm the
updates.
In the log file, informational messages break the inconsistency messages into logical
groups. The inconsistency messages contain details of what was updated or adjusted
to achieve consistency. The log file is closed and reopened immediately before the
confirmation prompt is sent to the prompt file terminal. You can then examine the log
file before deciding whether to confirm the updates. If the log file is the spooler,
TCHECK produces two spooler jobs.
TCHECK execution depends on the size of the files to be scanned, the size of the
TRANSFER name directory, and the number of inconsistencies to be corrected. If you
run TCHECK to perform only a session cleanup, it takes just a small part of the time
required for a run in which TCHECK examines all database files.