Instruction manual

8-1
SECTION 8. FILES, PROTOCOLS, AND UTILITIES
8.1 LOG FILES
Log files are produced for several reasons.
Documenting events that occurred is a primary
reason. Logs are also useful as a diagnostic
tool. Some of the logs are optional, stored only
when enabled. Other logs are always active.
Most logs have built-in restrictions that prevent
them from consuming all available disk space
even if neglected.
Most log filenames contain a $ character in the
name. When the file reaches its maximum
allowed size, it is renamed, replacing the $ with
a single digit and the original name is reused.
When the rename is attempted, the oldest
existing file will be overwritten if all the allowable
filenames already exist.
For example, the SWF$.LOG files contain
Status, Warning, and Fault messages. When
this file is about 1.2 megabytes in size, it is
renamed to SWF0.LOG. The next time
SWF$.log is 1.2 megabytes big, it is renamed to
SWF1.log. This continues until files SWF0.log -
SWF6.log exist because only six SWF log files
can be created (see Section 8.1.1). The next
time SWF$.log gets to be 1.2 megabytes the
oldest file SWF0.log is overwritten and the
process continues. This process ensures that
the log files will not get too big to fit on a floppy
disk and that log files will not consume all hard
disk space if neglected.
8.1.1 NETADMIN AND DLSMGR
SWF$.LOG -- Creates up to six 1.2 megabyte
files containing Status, Warning, and Fault
messages. May be enabled and filtered with
the Status, Warning, Faults submenu in
Netadmin.
IO$COMx.LOG − Where x is the serial port
being logged. Contains a log of actual
communications through serial port. Enabled
and setup on NetAdmin network health screen
(main screen). Will create up to eleven 1.2
megabyte files.
CLKSET$.LOG − Log of each clockset. Does
not log clock checks. Always enabled. Will
create two files each 100k before overwriting
oldest.
LNKTEST$.LOG − Log of quality numbers from
RF link testing. Always enabled. Will create 2
files each 100k before overwriting oldest.
PROGDN$.LOG − Log of each ‘.DLD’ program
download. Always enabled. Will create 2 files
each 100k before overwriting oldest.
POSTED.LOG, HALTED.LOG,
DEADLOCK.LOG − Internal diagnostic
information. Will create one 10k file for each.
After file reaches 10k, no new information will
be logged until file is moved or renamed.
Always enabled.
8.1.2 DBSELECT
HOLE$.LOG − Log of hole collection activity.
Logs the detection, queuing, and removal of
holes from the hole queue. Primarily used as
diagnostic tool. Enable on DBSelect main
menu under FILE menu. Will create up to
eleven 1.2 meg. files.
DBSelec$.LOG − Log of all data collected by
DBSelect. May be used as diagnostic tool,
secondary data storage, or backup. These log
files are not intended to be used as a reliable
source of a complete set of data. Will create up
to eleven 1.2 megabyte files.
DBACK$.LOG − Log's indication of when data
was written to the named pipe and when it was
acknowledged. Used as a diagnostic tool.
Enabled when the Acknowledged Named pipe
is being used and the DBSelec$.LOG is
enabled. Will create up to eleven 1.2 megabyte
files.
QUEUE.DAT − DBSelect will buffer data it has
received but is unable to deliver via the named
pipe. Eventually when buffering is no longer
possible, DBSelect will append this data to
QUEUE.DAT before dumping it. When
enabled, hole collection from the dataloggers is
the primary means to recover this data. When
normal pipe operation is restored, DBSelect will
recollect all data that was not delivered through
the named pipe. If the data is no longer
available for hole collection because enough
time has elapsed that some of the datalogger
data tables have been overwritten, the user may