The Error Log Viewer (ELV) selectively reports the contents
of an error log file. ELV is most useful with error logs written
on systems running OpenVMS Version 7.3 and later.
For more detailed information about ELV, refer to the ELV
chapter in the HP OpenVMS System Management Utilities Reference Manual: A--L.
Understanding
the Error Log Viewer (ELV) The Error Log Viewer (ELV) utility allows you to quickly examine,
from the command line, an error log file in a user-readable format.
You can do this prior to making a decision that the data warrants
a more comprehensive analysis with a tool such as the System Event
Analyzer (SEA).
ELV provides detailed information for all events belonging
to the event types shown in
Types of Events That ELV Fully Supports.
Event types are grouped by the event classes shown in the same table.
Table 3 Types of Events That ELV Fully Supports
Event Class
Event Types
Control entries
System startups, time stamps,
operator and network messages, indictment events, ERRLOG.SYS created
messages, and messages from the Send Message to Error Logger ($SNDERR)
system service
Volume changes
Volume mounts and dismounts
Bugchecks
System bugchecks, user bugchecks,
and crash restarts
ELV provides detailed information for some events belonging
to the event types shown in
Types of Events That ELV Partially Supports.
Event types are grouped by the event classes shown in the same table.
Table 4 Types of Events That ELV Partially Supports
Event Class
Event Types
Machine checks
620 system correctable errors, 630 processor
correctable errors, 660 system uncorrectable errors, 670 processor
uncorrectable errors, 680 system events, console data logs
Invoking
ELV To invoke ELV, enter the following DCL command:
$ ANALYZE/ERROR_LOG/ELV
If you do not enter an ELV command, the utility enters interactive
shell mode and displays the ELV prompt:
ELV>
You can then enter an ELV command. After ELV executes the
command, it again displays the ELV> prompt.
To return directly to DCL after executing an ELV command from
the ELV prompt, use the /NOINTERACTIVE qualifier.You can also enter
an ELV command directly from DCL; for example:
$ ANALYZE/ERROR_LOG/ELV TRANSLATE ERRLOG.SYS;42
After ELV executes the command, you are returned to the DCL
prompt by default.
To enter interactive shell mode after executing an ELV command
directly from DCL, use the /INTERACTIVE qualifier.
Principal
ELV Commands The commands shown in
Principal ELV Commands represent
the principal ELV operations.
Table 5 Principal ELV Commands
Command
Description
CONVERT
Converts and writes events from one or
more binary error log files written in the newer format to a single
new error log file written in the older format. The new file can
then be read by ANALYZE/ERROR_LOG.
This command is primarily
used to enable translation of older error log events whose translation
is not supported by ELV.
DUMP
Writes events from one or more binary
error log files to a single new ASCII output file in an OpenVMS
dump-style format.
TRANSLATE
Performs a bit-to-text translation of
events from one or more binary error log files and writes the resulting
reports to the terminal or to a single new ASCII output file.
WRITE
Performs an image copy of events from
one or more binary error log files to a single new binary error
log file.
Using various qualifiers that are common to all of these commands,
you can select or reject the events to be processed by one of these
commands. For example, if you specify TRANSLATE /SINCE=YESTERDAY,
you translate all valid events that have occurred since yesterday.
Standard
Reports Using the TRANSLATE Command You can use the TRANSLATE command to produce standard reports
of various detail levels. This is the primary function of the ELV
utility.
To specify the detail level of a standard report, you can
use the /BRIEF, /FULL, or /ONE_LINE qualifier with the TRANSLATE
command, as outlined in
Standard Report Detail Levels,
or you can accept the default report by omitting a detail level
qualifier. In addition to these qualifiers, you can use the /TERSE
qualifier to obtain a standard report that contains less interpretation
of the data, regardless of detail level.
Table 6 Standard Report Detail Levels
Detail Level
Qualifier
Description
One-line
/ONE_LINE
The header information is the only information
that is included in the standard report.
Brief
/BRIEF
Only the most essential information is included
with the header information.
Default
(None)
Only the most commonly useful event information
is included with the header information.
Full
/FULL
All event information is included with the
header information.
Example
of a Standard Report Standard and Summary Reports shows a standard
report followed by a summary report. To produce only the standard
report (and omit the summary report, which is included by default),
use the /NOSUMMARY qualifier. To produce only the summary report
(and omit the standard report, which is included by default), use
the /SUMMARY qualifier.
Example 1 Standard and Summary Reports
Output for SYS$COMMON:[SYSEXE.ERRLOGS]EXAMPLE.DAT;1EVENT EVENT_TYPE___________________TIMESTAMP________________NODE__EVENT_CLASS_______________
1 Volume Mount 14-AUG-2003 13:31:39.12 FRANZ VOLUME_CHANGES
DESCRIPTION__________________________RANGE___ VALUE___________TRANSLATED_VALUE___________
Hardware Architecture 4 Alpha
Hardware System Type 35 Wildfire
Logging CPU 3
Number of CPU's in Active Set 4
System Marketing Model 1968 COMPAQ AlphaServer GS160
Error Mask <31:00>: 0x00000003
Seconds Since Boot 17
Error Sequence Number 46
DSR String AlphaServer GS160 6/731
Operating System Version X9WY-SSB
Owner UIC of the Volume 65537
Unit Operation Count 378
Device Unit Number 200
Device Generic Name FRANZ$DKB
Volume Number within Set 0
Number of Volumes within Set 0
Volume Label OPAL_X9WY
ERROR_LOG_SUMMARY________________________________________________
Total number of events: 1
Number of the first event: 1
Number of the last event: 1
Earliest event occurred: 14-AUG-2003 13:31:39.12
Latest event occurred: 14-AUG-2003 13:31:39.12
Number of events by event class:
VOLUME_CHANGES 1