User Environmental Test Package,
Continued
UETP Log Files
UETP stores all information generated by all UETP tests and
phases from its current run in one or more UETP.LOG files, and
it stores the information from the previous run in one or more
OLDUETP.LOG files. If a run of UETP involves multiple passes,
there is one UETP.LOG or one OLDUETP.LOG file for each pass.
At the beginning of a run, UETP deletes all OLDUETP.LOG files,
and renames any UETP.LOG files to OLDUETP.LOG. Then UETP
creates a new UETP.LOG file and stores the information from the
current pass in the new file. Subsequent passes of UETP create
higher versions of UETP.LOG. Thus, at the end of a run of UETP
that involves multiple passes, there is one UETP.LOG file for
each pass. In producing the files UETP.LOG and OLDUETP.LOG,
UETP provides the output from the two most recent runs.
If the run involves multiple passes, UETP.LOG contains
information from all the passes. However, only information from
the latest run is stored in this file. Information from the previous
run is stored in a file named OLDUETP.LOG. Using these two
files, UETP provides the output from its tests and phases from
the two most recent runs.
The cluster test creates a NETSERVER.LOG file in SYS$TEST
for each pass on each system included in the run. If the test is
unable to report errors (for example, if the connection to another
node is lost), the NETSERVER.LOG file on that node contains
the result of the test run on that node. UETP does not purge or
delete NETSERVER.LOG files; therefore, you must delete them
occasionally to recover disk space.
If a UETP run does not complete normally, SYS$TEST might
contain other log files. Ordinarily these log files are concatenated
and placed within UETP.LOG. You can use any log files that
appear on the system disk for error checking, but you must delete
these log files before you run any new tests. You may delete these
log files yourself or rerun the entire UETP, which checks for old
UETP.LOG files and deletes them.
Continued on next page
5–89
