Troubleshooting Tools

There are several troubleshooting tools available. Some tools test and exercise the system, whereas others gather and format information.

The DEC Verifier and Exerciser Tool (DEC VET) falls into the first category. DEC VET is an online tool for verifying system installations and acceptance. It is also used to maintain and troubleshoot systems, and perform load and stress tests on single devices, systems, and networks. There are versions of DEC VET for different operating systems (OS). For more information, see the following guides:

Each OS has a specific mechanism for capturing and logging error information. To access an OS error log, click on one of the following buttons:

DIGITAL UNIX
OpenVMS

Accessing the DIGITAL UNIX Error Log

The event report formatter for DIGITAL UNIX is uerf (In the future, DECevent, a new tool, will replace uerf.) The syntax of the command is: /usr/sbin/uerf [ options ... ]

The uerf command uses the uerf.bin, uerf.hlp, and uerf.err data files. The uerf.bin file is the event information database. The uerf.hlp file is the help file. The uerf.err file is the event message file. The uerf command expects to find the data files in the /usr/sbin directory. By default, the uerf command outputs the contents of the event log file specified by the *.* entry in the /etc/binlog.conf configuration file. To report on any other event log file or if there is no *.* entry, you must use the uerf command with the -f option.

NOTE: For further information, see the uerf Man pages. (Type "man uerf" at the prompt.)


Accessing the OpenVMS Error Log

Access the OpenVMS Errorlog Report Formatter (ERF) with the ANALYZE/ERROR_LOG command.(In the future, DECevent, a new tool, will replace ERF.) The syntax is:
ANALYZE/ERROR_LOG [filespec[,...]]
For more information, see the VMS Error Log Utility Reference Manual.

EXAMPLES The following example uses all of the defaults:
$ ANALYZE/ERROR_LOG
The next example limits the entry range generated from the file ERRLOG.SYS to entries from 1 to 18:
$ ANALYZE/ERROR_LOG/ENTRY=(START:1,END:18) ERRLOG.SYS
This example shows how to exclude a given class of event information (disk information, in this case):
$ ANALYZE/ERROR_LOG/EXCLUDE=(DISK)
The following example will furnish a report containing only disk-related information:
$ ANALYZE/ERROR_LOG/INCLUDE=(DISK)