|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 DFS Tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 DFS Tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - download
Length: 2048 (0x800)
Types: HLP, TextFile
Names: »LOG.HLP«
└─⟦b4205821b⟧ Bits:30000743 8mm tape, Rational 1000, DFS, D_12_7_3 SEQ288
└─ ⟦this⟧ »LOG.HLP«
└─⟦b434774df⟧ Bits:30000528 8mm tape, Rational 1000, DFS, D_12_6_5
└─ ⟦this⟧ »LOG.HLP«
└─⟦bc1274df5⟧ Bits:30000750 8mm tape, Rational 1000, DFS backup from PAM's R1000
└─ ⟦this⟧ »LOG.HLP«
LOG
The LOG program allows the user to examine or initialize the DFS
based error log. This error log contains information about device
errors during DFS I/O, system crash history, diagnostic failures,
etc. The LOG program is interactive and is invoked by typing:
CLI> x log
Once the LOG program has been invoked it will display information
about the contents of the error log. The error log is a ring buffer
of 2048 entries. Newer information overwrites older information
in the error log. The LOG program allows selective examination of
log entries. Once you have finished examining the log you will be
asked:
Update log header [Y] ?
Answering "Y" to this question will cause all entries in the error
log to be marked as old. This allows subsequent examinations of
the error log to filter out data already seen. Entries marked as
old can still be examined until they are overwritten within the
ring buffer.
To initialiize the error log invoke the LOG program as follows:
CLI> x log initialize
The LOG program will ask if you really want to initialize the log.
This will result in all log data being discarded. The LOG should
be initialized when a new DFS is built on a system.«nul»