SNAX/HLS Configuration and Control Manual

Reporting Events
Operating SNAX/HLS
5–12 104705 Tandem Computers Incorporated
The LOG Facility The log file is specified at program initiation using the LOG or LOGFILE startup
parameter. Thus, a command that starts the HLSOBJ file of the form:
> RUN HLSOBJ/ OUT $s.#log,. . . / LOG *,. . .
or
> RUN HLSOBJ/. . . / LOG $s.#log,. . .
has the effect of specifying the file $S.#LOG as the output log medium. The log file
specification can later be changed by use of the Subsystem Programmatic Interface
(SPI), which is described in the SNAX/HLS Management Programming Manual. You can
also modify it using HLSCOM. For more information, see Section 6, “Using the
HLSCOM Utility.”
The performance of SNAX/HLS is directly related to the type of file selected for
logging. You should consider the following when selecting a log file:
SNAX/HLS has no way to determine whether a reasonable choice of log file has
been made.
The log file is accessed in a wait fashion.
Any error on the log file is ignored; the message is lost.
Note that the default OUT file is usually the home terminal.
As a result of these observations, it is clear that installations should avoid selecting
terminals as LOG media in production environments. Terminals are often inaccessible
due to human intervention. An output-only terminal might be acceptable if fast
enough. A terminal could be useful, however, in a testing or demonstration
environment.