HP OpenVMS Systems Documentation

If ERRFMT$_SEND_MAIL is defined to be TRUE, you receive a mail message with a subject line saying that ERRFMT is about to delete itself. The operator log file and the output displayed at the system console, OPA0:, contain more detailed information about the failure encountered and instructions on how to restart ERRFMT; however, you are often not at the console to see this information.

If you are using ERRFMT in one mode, for example, with sending mail enabled, and you want to disable sending mail, use the system manager's account to edit SYS$STARTUP:SYLOGICAL.COM, adding the following command:

$ DEFINE/SYSTEM ERRFMT$_SEND_MAIL FALSE

To reenable sending mail, use the system manager's account to edit SYS$STARTUP:SYLOGICAL.COM, adding the following command:

$ DEFINE/SYSTEM ERRFMT$_SEND_MAIL TRUE

Sending mail to the SYSTEM account is enabled by default. However, you can define ERRFMT$_SEND_TO to send mail to another user if ERRFMT is about to delete itself.

To change the user name to receive mail, use the system manager's account to edit SYS$STARTUP:SYLOGICAL.COM, adding an appropriate logical name DEFINE command. For example:

$ DEFINE/SYSTEM ERRFMT$_SEND_TO R_SMITH

Compaq recommends that you do not use distribution lists and multiple user names.

20.4 Using ERROR LOG

Use the Error Log utility (ERROR LOG) to report selectively on the contents of an error log file. You must have the SYSPRV privilege to run ERROR LOG. Starting with OpenVMS Version 7.2, before using the Error Log utility, you need to translate error log files using the Binary Error Log Translation utility, which is part of DECevent. For more information, refer to its documentation, which is included in the DECevent kit.

20.4.1 Understanding ERROR LOG

ERROR LOG supports most OpenVMS supported hardware, such as adapters, disks, tapes, CPUs, and memories, but not all communications devices. Some synchronous communications devices are supported.

The operating system automatically writes messages to the latest version of an error log file, SYS$ERRORLOG:ERRLOG.SYS, as the events shown in Table 20-3 occur.

You can use ERROR LOG to process error log entries for the following forms of optional output:

• Full report of selected entries, which is the default
• Brief report of selected entries
• Summary report of selected entries
• Register dump report of selected device entries
• Binary copy of selected entries
• Binary copy of rejected entries

Section 20.4.2 explains how to produce error log reports. Refer to the OpenVMS System Management Utilities Reference Manual for examples of error log reports.

The error reports that ERROR LOG produces are useful in two ways:

• They aid preventive maintenance by identifying areas within the system that show potential for failure.
• They aid the diagnosis of a failure by documenting the errors and events that led up to it.

The detailed contents of the reports are most meaningful to Compaq support representatives. However, you can use the reports as an important indicator of the system's reliability. For example, using the DCL command SHOW ERROR, you might see that a particular device is producing a relatively high number of errors. You can then use ERROR LOG to obtain a more detailed report and decide whether to consult your support representative.

If a system component fails, a Compaq support representative can study the error reports of the system activity leading up to and including the failure. If a device fails, you can generate error reports immediately after the failure; for example:

• One report might describe in detail all errors associated with the device that occurred within the last 24 hours.
• Another report might summarize all types of errors for all devices that occurred within the same time period.
• The summary report can put the device errors into a systemwide context.

Your support representative can then run the appropriate diagnostic program for a thorough analysis of the failed device. Using the combined error logging and diagnostic information, your support representative can proceed to correct the device.

Error reports allow you to anticipate potential failures. Effective use of the Error Log utility in conjunction with diagnostic programs can significantly reduce the amount of system downtime.

20.4.2 Producing Error Log Reports

You enter the DCL command in the following format:
ANALYZE/ERROR_LOG [/qualifier(s)][filespec[,...]]

where:

Refer to the OpenVMS System Management Utilities Reference Manual for details about the command and its parameters and for examples of error log reports.

ERROR LOG issues error messages for inconsistent error log entries. Use the Help Message facility to look up explanations and suggested user actions for these messages.

20.4.3 Producing a Full Error Log Report

The following steps show how to produce an error log report for all entries in the error log file and how to print the report:

1. Either log in to the SYSTEM account or ensure that you have the SYSPRV privilege. (You must have privilege to access the error log file.) For example:

   $ SET PROCESS/PRIVILEGE=SYSPRV

2. Set your default disk and directory to SYS$ERRORLOG:

   $ SET DEFAULT SYS$ERRORLOG

3. Examine the error log directory to see which error log file you want to analyze:

   $ DIRECTORY

4. To obtain a full report of the current error log file, enter the following command:

   $ ANALYZE/ERROR_LOG/OUTPUT=ERRORS.LIS

5. Print a copy of the report, using the file name you specified with the /OUTPUT qualifier:

   $ PRINT ERRORS.LIS

Example

$ SET PROCESS/PRIVILEGE=SYSPRV
$ SET DEFAULT SYS$ERRORLOG
$ DIRECTORY  (1)
Directory SYS$SYSROOT:[SYSERR]

ERRLOG.OLD;2  ERRLOG.OLD;1  ERRLOG.SYS;1

Total of 3 files.
$ ANALYZE/ERROR_LOG/OUTPUT=ERRORS.LIS ERRLOG.OLD (2)
$ PRINT ERRORS.LIS (3)

The following list explains the commands in the example.

1. The DIRECTORY command lists all the files in the SYS$ERRORLOG directory. The directory contains three files: two old error log files and the current error log file, ERRLOG.SYS.
2. The ANALYZE/ERROR_LOG command writes a full report to a file called ERRORS.LIS, using the most recent ERRLOG.OLD file as input.
3. The PRINT command prints ERRORS.LIS.

This section briefly explains how to specify report formats and produce a report of selected entries.

Table 20-4 contains error log report options. For more details about options and examples of error log reports using options, refer to the OpenVMS System Management Utilities Reference Manual.

The DECevent Event Management utility (DECevent) provides an interface between a system user and the operating system's event log files.

http://www.support.compaq.com/svctools

DECevent allows system users to produce ASCII reports derived from system event entries. The format of the ASCII reports depends on the command entered on the command language interpreter (CLI) with a maximum character limit of 255 characters.

DECevent uses the error log file, SYS$ERRORLOG:ERRLOG.SYS, as the default input file, unless you specify another input file.

Event reports are useful for determining preventive maintenance by helping to identify areas within the system showing potential failure. Event reports also aid in the diagnosis of a failure by documenting events that led to the failure.

The contents of the event reports are most meaningful to your Compaq support representative. However, you can use the event reports as an indicator of system reliability. For example, while using the DCL command SHOW ERROR, you might see that a particular device is producing a higher than normal number of events. You can use DECevent to obtain various detailed reports and determine if you need to contact your Compaq support representative.

If a system component fails, your Compaq support representative can use the event reports to create a history of events leading up to and including the failure.

Used in conjunction with diagnostic programs, event reports significantly reduce the amount of system down time.

DECevent Report Types

DECevent produces five types of reports:

These report types are mutually exclusive; in other words, you can select only one report type in a command.

Section 20.5.5 contains examples of types of reports. The OpenVMS System Management Utilities Reference Manual contains additional examples of the types of reports produced by DECevent.

The following sections explain how to use DECevent:

In addition, restrictions are listed in Section 20.5.6.

20.5.2 Invoking and Exiting DECevent

To invoke DECevent, enter the following DCL command:

DIAGNOSE [/primary qualifier][/secondary qualifier[,...][file-spec][,..]

Note that you do not need to enter the /TRANSLATE qualifier on the command line because it is the default primary qualifier.

A brief discussion of valid qualifiers, their uses, and their order is provided in the following sections. For a more detailed discussion, see the DECevent User's Guide. This guide is available online at the following web site:

    http://www.support.compaq.com/svctools

Select "support tools", next "DECevent", and then "documentation". The DECevent User's Guide is available in several formats.

To exit DECevent, press Ctrl/C and the Return key (to display the system prompt).

You must have SYSPRV privilege to run DECevent; however, only read access is required to access the ERRLOG.SYS file. You must have the DIAGNOSE privilege for the /CONTINUOUS primary qualifier to work, enabling the continuous display of events on a terminal screen.

20.5.3 Using DECevent Qualifiers

The DECevent qualifiers shown and described in Table 20-5 and Table 20-6 allow you to change the format of the reports that DECevent produces.

Do not use the /BINARY qualifier with any report type qualifier (/FULL, /BRIEF, /TERSE, /SUMMARY, and /FSTERR) or with the /OUTPUT qualifier.

Privileges Required

• You must have SYSPRV privilege to run DECevent; however, only read access is required to access the ERRLOG.SYS file.
• You must have the DIAGNOSE privilege for the /CONTINUOUS qualifier to work, enabling the continuous display of events on a terminal screen.

In addition to the qualifiers listed in Table 20-5 and Table 20-6, DECevent contains a set of DIRECTORY commands and a set of SHOW commands:

• DIRECTORY commands
  These commands allow you to display a list of rulesets that DECevent needs to translate events into a readable format. (A ruleset is a software routine or function that is analogous to an executable file.)
  The following DIRECTORY commands are currently implemented in DECevent:
  • DIRECTORY EVENT
    This command lists all rulesets associated with event translation.
  • DIRECTORY CANONICAL
    This command lists all rulesets associated with event reports.
• SHOW commands
  These commands allow a user to view specific settings and selections. The following SHOW commands are currently implemented in DECevent:
  • SHOW SELECT
    By appending a specific selection keyword name to the SHOW SELECT command, you view only that selection keyword.
  • SHOW SETTINGS
    By appending a specific setting's name to the SHOW SETTINGS command, you view only that setting's name and value.