Digital PDFs

AA-LA37A-TE

December 1988

53 pages

Original

1.4MB

Document:	VMS 5.0 Error Log Utility Manual 198804
Order Number:	AA-LA37A-TE
Revision:
Pages:	53
Original Filename:	http://bitsavers.org/pdf/dec/vax/vms/5.0/AA-LA37A-TE_VMS_5.0_Error_Log_Utility_Manual_198804.pdf

OCR Text

VMS

VMS Error Log Utility Manual

Order Number AA-LA37A-TE

VMS Error Log Utility
Manual
Order Number: AA-LA3 7 A-TE

April 1988
The Error Log Utility selectively reports the contents of an error log file.

Revision/Update Information:

This document supersedes the
VAX/VMS Error Log Utility Reference
Manual, Version 4.2.

Software Version:

VMS Version 5.0

digital equipment corporation
maynard, massachusetts

April 1988
The information in this document is subject to change without notice and should
not be construed as a commitment by Digital Equipment Corporation. Digital
Equipment Corporation assumes no responsibility for any errors that may appear
in this document.
The software described in this document is furnished under a license and may be
used or copied only in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment
that is not supplied by Digital Equipment Corporation or its affiliated companies.
Copyright © 1988 by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document
requests the user's critical evaluation to assist in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-10
DECSYSTEM-20
DECUS
DECwriter

DIBOL
EduSystem
IAS
MASSBUS
PDP
PDT
RSTS
RSX

UNIBUS
VAX
VAXcluster
VMS
VT

~urnua~oTM
ZK4542

HOW TO ORDER ADDITIONAL DOCUMENTATION
DIRECT MAIL ORDERS
USA & PUERTO Rico*

CANADA

INTERNATIONAL

Digital Equipment Corporation
P.O. Box CS2008
Nashua. New Hampshire
03061

Digital Equipment
of Canada Ltd.
100 Herzberg Road
Kanata, Ontario K2K 2A6
Attn: Direct Order Desk

Digital Equipment Corporation
PSG Business Manager
c/o Digital's local subsidiary
or approved distributor

In Continental USA and Puerto Rico call 800-258-1710.
In New Hampshire, Alaska, and Hawaii call 603-884-6660.
In Canada call 800-267-6215.
*Any prepaid order from Puerto Rico must be placed with the local Digital subsidiary (809-754-7575).
Internal orders should be placed through the Software Distribution Center (SOC), Digital Equipment
Corporation, Westminster, Massachusetts 01473.

Production Note
This book was produced with the VAX DOCUMENT electronic publishing
system, a software tool developed and sold by DIGITAL. In this system,
writers use an ASCII text editor to create source files containing text and
English-like code; this code labels the structural elements of the document,
such as chapters, paragraphs, and tables. The VAX DOCUMENT software,
which runs on the VMS operating system, interprets the code to format the
text, generate a table of contents and index, and paginate the entire document.
Writers can print the document on the terminal or line printer, or they can use
DIGITAL-supported devices, such as the LN03 laser printer and PostScript®
printers (PrintServer 40 or LN03R ScriptPrinter), to produce a typeset-quality
copy containing integrated graphics.

PostScript is a trademark of Adobe Systems, Inc.

Contents
PREFACE

vii

NEW AND CHANGED FEATURES

ERROR LOG Description

ERR-1

ERROR LOG Usage Summary

ERR-3

ERROR LOG Qualifiers

ERR-4
/BEFORE
/BINARY
/BRIEF
/ENTRY
/EXCLUDE
/FULL
/INCLUDE
/LOG
/OUTPUT
/REGISTER_DUMP
/REJECTED
/SID_REGISTER
/SINCE
/STATISTICS
/SUMMARY

ERROR LOG Examples

ERR-5
ERR-6
ERR-7
ERR-8
ERR-9
ERR-12
ERR-13
ERR-16
ERR-17
ERR-18
ERR-19
ERR-20
ERR-21
ERR-22
ERR-23
ERR-25

INDEX

Preface
Intended Audience
The Error Log Utility (ERROR LOG) is intended for use as a system
management and maintenance :vol to determine the source, frequency,
and type of recurrent system and device errors.

Document Structure
This document consists of the following four sections:
•

Description-Provides a full description of the Error Log Utility.

•

Usage Summary-Outlines the following ERROR LOG information:
-Invoking the utility
-Exiting from the utility
-Directing output
-Restrictions or privileges required

•

Qualifiers-Describes ERROR LOG qualifiers, including format,
parameters, and examples.

•

Examples-Provides additional ERROR LOG examples.

Associated Documents
The following manuals offer additional information:

•

Guide to Using VMS Command Procedures

•

VMS DCL Dictionary

•

Guide to Maintaining a VMS System

•

VMS System Messages and Recovery Procedures Reference Manual

vii

Preface

Conventions
Convention

Meaning
In examples, a key name (usually abbreviated)
shown within a box indicates that you press
a key on the keyboard; in text, a key name is
not enclosed in a box. In this example, the key
is the RETURN key. (Note that the RETURN
key is not usually shown in syntax statements
or in all examples; however, assume that you
must press the RETURN key after entering a
command or responding to a prompt.)

viii

CTRL/C

A key combination, shown in uppercase with a
slash separating two key names, indicates that
you hold down the first key while you press the
second key. For example, the key combination
CTRL/C indicates that you hold down the key
labeled CTRL while you press the key labeled C.
In examples, a key combination is enclosed in a
box.

$SHOW TIME
05-JUN-1988 11 :55:22

In examples, system output (what the system
displays) is shown in black. User input (what
you enter) is shown in red.

$ TYPE MYFILE.DAT

In examples, a vertical series of periods, or
ellipsis, means either that not all the data that
the system would display in response to a
command is shown or that not all the data a
user would enter is shown.

input-file, ...

In examples, a horizontal ellipsis indicates
that additional parameters, values, or other
information can be entered, that preceding
items can be repeated one or more times, or
that optional arguments in a statement have
been omitted.

[logical-name]

Brackets indicate that the enclosed item is
optional. (Brackets are not, however, optional
in the syntax of a directory name in a file
specification or in the syntax of a substring
specification in an assignment statement.)

quotation marks
apostrophes

The term quotation marks is used to refer
to double quotation marks (" ) . The term
apostrophe ( · ) is used to refer to a single
quotation mark.

New and Changed Features
This section summarizes the main technical changes in the Error Log Utility
(ERROR LOG) since Version 4.0.
The Examples section contains the following new examples of error log
reports:
•

Summary reports generated with the /SUMMARY qualifier using the
DEVICE, ENTRY, HISTOGRAM, MEMORY, and VOLUME keywords

•

A brief report generated with the /BRIEF qualifier

ERROR LOG Description
The Error Log Utility (ERROR LOG) is a system management tool that
selectively reports the contents of one or more error log files.
ERROR LOG supports most VMS-supported hardware, such as disks, tapes,
CPUs, and memories, but not all communications devices (for example, the
DEQNA). Some synchronous communications devices are supported.
The VMS system automatically writes messages to the latest version of an
error log file named SYS$ERRORLOG:ERRLOG.SYS as the following events
occur:
•

Errors-Device errors, device timeouts, machine checks, bus errors,
memory errors (hard or soft error correcting code (ECC) errors),
asynchronous write errors, undefined interrupts, and bugchecks

•

Volume changes-Volume mounts and dismounts

•

System events-Cold start-ups, warm start-ups, system failure (crash)
start-ups, messages from the Send Message to Error Logger ($SNDERR)
system service, and time stamps

ERROR LOG processes error log entries by selection to produce the following
six forms of optional output:
•

Full report of selected entries, which is the default

•

Brief report of selected entries

•

Summary report of selected entries

•

Binary copy of selected entries

•

Binary copy of rejected entries

These forms of output can be directed to a terminal for display or to a disk
or magnetic tape file with the /OUTPUT qualifier. By default, the output is
directed to the SYS$0UTPUT device. The report formats can be changed by
specifying /FULL, /BRIEF, /SUMMARY, /REGISTER_DUMP, /REJECTED,
or /BINARY.
Error log en tries are processed by selection for the interval specified by the
/SINCE, /BEFORE, or /ENTRY qualifiers. Use of the selection qualifiers
/INCLUDE and /EXCLUDE form a filter that is used to determine which
error log entries are selected or rejected.
ERROR LOG reports are 72 columns wide, so they can be displayed at the
terminal. These reports are primarily intended for use by DIGITAL Field
Service personnel to identify hardware problems. System managers may find
error log reports useful in identifying recurrent system failures that require
outside attention.
ERROR LOG issues error messages for inconsistent error log entries. The
VMS System Messages and Recovery Procedures Reference Manual lists these
messages and provides explanations and suggested user actions.

ERR-1

ERROR LOG Description

By default, when an unknown (to ERROR LOG) device, CPU, or error log
entry is encountered by ANALYZE/ERROR_LOG, the utility produces the
entry in hexadecimal longword format. (See the Unknown Entries Example
in the Examples section). Exclude these entries from the report by specifying
/EXCLUDE=UNKNOWN _ENTRIES in the command line.
See the Guide to Maintaining a VMS System for additional details about using
error logs.
The Examples section shows the format of a typical error log report.

ERR-2

ERROR LOG Usage Summary
The Error Log Utility (ERROR LOG) selectively reports the contents of an
error log file.

FORMAT

ANALYZE/ERROR_LQG

PARAMETERS

/qualifier(s)

[/qualifier(s)] [file-spec[, ... }]

The function to be performed by the ANALYZE/ERROR_LOG command.

file-spec[, ... ]
Specifies one or more files that contain binary error information to be
interpreted for the error log report. You can include wildcard characters
in the file specification. If you omit the file specification, the default file is
SYS$ERRORLOG:ERRLOG.SYS (see the Guide to Maintaining a VMS System
for information on maintaining this file).
See the VMS DCL Concepts Manual for details on file specifications.

usage summary

To invoke ERROR LOG, enter the following DCL command:
ANALYZE/ERROR_LOG [/qualifier (s)] [file-spec] [, ... ]

ERROR LOG does not prompt you. To exit from ERROR LOG, press
CTRL/C. You also exit the utility when end-of-file (EOF) is detected. To
direct output, use the /OUTPUT, /BINARY, and /REJECTED qualifiers with
the ANALYZE/ERROR_LOG command.
You must have SYSPRV privilege to run ERROR LOG. However, only read
access is required to access the file ERRORLOG.SYS. (It is not necessary
to rename the file ERRORLOG.SYS to ERRORLOG.OLD before using
ERROR LOG.) Do not use the /BINARY qualifier with the /FULL, /BRIEF,
/OUTPUT, /REGISTER_DUMP, or /SUMMARY qualifiers.

ERR-3

ERROR LOG
ERROR LOG Qualifiers

ERROR LOG
QUALIFIERS

ERR-4

The qualifiers for the ANALYZE/ERROR_LOG command are described in
this section.

ERROR LOG
/BEFORE

/BEFORE
Specifies that only those entries dated earlier than the stated date and
time are to be selected for the error report.

FORMAT
PARAMETERS

/BEFORE

[=date-time]

date-time
Limits the error report to those entries dated earlier than the specified time.

DESCRIPTION

You can specify an absolute time, a delta time, or a combination of absolute
and delta times. See the VMS DCL Concepts Manual for details on specifying
times.
If you omit the /BEFORE qualifier or specify /BEFORE without a date or
time, all entries are processed.

EXAMPLE
$ ANALYZE/ERROR_LOG/BEFORE=31-DEC-1988:10:00 ERRLOG.OLD;5

In this example, the error log report generated for ERRLOG.OLD;S contains
entries that were logged before 10:00 A.M. on December 31, 1988.

ERR-5

ERROR LOG
/BINARY

/BINARY
Used to control whether the binary error log records are converted to
ASCII text or copied to the specified output file.

FORMAT

PARAMETERS

/BINARY {=file-spec]
/NOBINARY
file-spec
Specifies the output file selected to contain image copies of the input records.

DESCRIPTION

The /BINARY qualifier creates a binary file that contains copies of the original
binary error log entry if the command line also specifies an interval (/SINCE,
/BEFORE, or /ENTRY qualifier) or a filter (/INCLUDE or /EXCLUDE
qualifier). If no interval or filter is specified, all error log entries are copied.
If you specify /BINARY=file-spec, the selected output file contains image

copies of the binary input records (the records are not translated to ASCII).
If you omit the device or directory specification, the current device and the
default directory are used. If you omit the file name, the file name of the

input file is used. If you omit the file type, the default file type is DAT.
Do not use /BINARY with the /FULL, /BRIEF, /OUTPUT, /REGISTER_
DUMP, or /SUMMARY qualifiers. These qualifiers generate an ASCII report;
/BINARY generates a binary file.

EXAMPLE
$ ANALYZE/ERROR_LOG/INCLUDE=DBA1/BINARY=DBA1_ERR.DAT ERRLOG.OLD;5

In this example, the output file DBAl_ERR.DAT contains image copies of the
entries that apply to DBAl.

ERR-6

ERROR LOG
/BRIEF

/BRIEF
Generates a brief report.

FORMAT

/BRIEF

DESCRIPTION

Do not use /BRIEF with the /BINARY qualifier.
The Examples section shows the format of a typical brief error log report.

EXAMPLE
$ ANALYZE/ERROR_LOG/BRIEF ERRLDG.OLD;97

In this example, the error log report generated from ERRLOG.OLD;97
contains minimal information.

ERR-7

ERROR LOG
/ENTRY

/ENTRY
Generates an error log report that includes the specified entry range or
starts at the specified entry number.

FORMAT
PARAMETERS

/ENTRY [=(START:decimal-va/ue{,END:decimal-valuej)]
(START:decimal-value[,END:decimal-value])
The range of entries to be included in the error log report.

DESCRIPTION

If you specify /ENTRY without the entry range or omit the qualifier, the
entry range defaults to START:l,END:end-of-file.

EXAMPLE
$ ANALYZE/ERROR_LOG/ENTRY=(START:1,END:18) ERRLOG.SYS

In this example, the entry range for the error log report generated from file
ERRLOG.SYS is limited to entry numbers 1 through 18.

ERR-8

ERROR LOG
/EXCLUDE

/EXCLUDE
Excludes errors generated by the specified device and error log entry type
from the error log report.

FORMAT
PARAMETERS

/EXCLUDE

=(device-or-entry-type{, ... })

device-or-entry-type[, ... ]
The device and entry type to be excluded from the error log report.

DESCRIPTION

You can specify one or more devices by device class, device name, or one or
more keywords that identify entry types.
Device Class Keywords
BUSES
DISKS
LINE_PRINTER
REAL TIME
SYNC_COMMUNICATIONS
TAPES
WORKSTATION

Examples of Device Name Constructs
DB

Group of devices

DBA1

Specific device/unit number

(DBA 1,HSC 1$DUA1,DY AO)

List of devices

(DB,DR,XF)

List of device groups

Entry Type Keywords
ATTENTIONS

Exclude device attention entries from the output
report.

BUGCHECKS

Exclude all types of bugcheck entries from the
report.

ERR-9

ERROR LOG
/EXCLUDE

CONTROL _ENTRIES

CPU_ENTRIES

Exclude control entries from the report. Control
entries include the following entry types:
•

System power-fail restarts

•

Time stamps

•

System startups

•

$SNDERR messages (system service to send
messages to error log)

•

Operator messages

•

Network messages

•

ERRLOG.SYS created

Exclude CPU-related entries from the report. CPU
entries include the following entry types:

•
•
•

SBI alerts/faults

•

Asynchronous write errors

•

UBA errors

Undefined interrupts
MBA/UBA adapter errors

DEVICE _ERRORS

Exclude device error entries from the report.

ENVIRONMENT AL_
ENTRIES

Exclude environmental entries from the report.

MACHINE_CHECKS

Exclude machine check entries from the report.

MEMORY

Exclude memory errors from the report.

SNAPSHOT_ENTRIES

Exclude snapshot entries from the report.

TIMEOUTS

Exclude device timeout entries from the report.

UNKNOWN_ENTRIES

Exclude any entry that had either an unknown entry
type or an unknown device type/class.

UNSOLICITED_MSCP

Exclude unsolicited MSCP entries from the output
report.

VOLUME_CHANGES

Exclude volume mount and dismount entries from
the report.

Unless you specify the UNKNOWN _ENTRIES keyword to explicitly exclude
from a report any entries from unsupported (unknown) devices, any unknown
device is reported.
Any known information for the entry is translated; the remaining information
is output in hexadecimal longwords.
If you specify a device class keyword or a device name construct with both

the /INCLUDE and /EXCLUDE qualifiers, the /INCLUDE qualifier takes
precedence.
The BUSES keyword also excludes error log entries for the BI bus. The
DEVICE_ERRORS keyword also excludes entries for the BI adapter.

ERR-10

ERROR LOG
/EXCLUDE

EXAMPLES

$ ANALYZE/ERROR_LOG/EXCLUDE=MTAC

In this example, the error log entries for the device MTAO are excluded from
the error log report for the file ERRLOG.SYS.

$ ANALYZE/ERROR_LOG/EXCLUDE=(MTAO,DRA5) ERRLOG.OLD

In this example, the devices MTAO and DRAS are excluded from the error log
report for the file ERRLOG.OLD.
~

$ ANALYZE/ERROR_LOG/EXCLUDE=(DISKS,BUGCHECKS)

In this example, all disk devices and all bugcheck entries are excluded from
the error log report for the file ERRLOG.SYS.
~

$ ANALYZE/ERROR_LOG/EXCLUDE=TAPES/INCLUDE=MTAO

In this example, the device MTAO is included in the error log report for the
file ERRLOG.SYS. All other magnetic tape devices are excluded from the
report.
~

$ ANALYZE/ERROR_LOG/EXCLUDE=(DISK,VOLUME_CHANGES)

In this example, entries for disk volume information are excluded from the
error log report for the file ERRLOG.SYS.
~

$ ANALYZE/ERROR_LOG/EXCLUDE=(DISK,VOLUME_CHANGES,DEVICE_ERROR)

In this example, entries for volume and device error information on disks are
excluded from the error log report for the file ERRLOG.SYS.

$ ANALYZE/ERROR_LOG/EXCLUDE=(DISK,VOLUME_CHANGES,DEVICE_ERROR,BUGCHECK)

In this example, entries for volume and device error information on disks,
and bugcheck errors are excluded from the error log report for the file
ERRLOG.SYS.

ERR-11

ERROR LOG
/FULL

/FULL
Generates a full report, which provides all available information for an error
log entry. This is the default report format.

FORMAT

/[NO] FULL

DESCRIPTION

Do not use /FULL with the /BINARY qualifier.

EXAMPLES
iJ

$ ANALYZE/ERROR_LOG/FULL ERRLOG.OLD;72

The command in this example produces a full report.
~

$ ANALYZE/ERROR_LOG ERRLOG.OLD;72

The command in this example produces a full report. The default report type
is /FULL; it is not necessary to specify it in the command line.

ERR-12

ERROR LOG
/INCLUDE

/INCLUDE
Includes errors generated by the specified device and error log entry type
in the error log report.

FORMAT
PARAMETERS

/I NCLU DE=(device-or-entry-type[, .. .})
device-or-entry-type[.,,,]
The device and entry type to be included in the error log report.

DESCRIPTION

Examples of Device Name Constructs
DB

Group of devices

DBA1

Specific device/unit number

(OBA 1,HSC 1$DUA1,DY AO)

List of devices

(DB,DR,XF)

List of device groups

Entry Type Keywords
ATTENTIONS

Include device attention entries in the output
report.

BUGCHECKS

Include all types of bugcheck errors in the report.

ERR-13

ERROR LOG
/INCLUDE

CONTROL _ENTRIES

CPU_ENTRIES

Include control entries in the report. Control entries
include the following entry types:
•

System power-fail restarts

•

Time stamps

•

System startups

•

$SNDERR messages (system service to send
messages to error log)

•

Operator messages

•

Network messages

•

ERRLOG.SYS created

Include CPU-related entries in the report. CPU
entries include the following entry types:

•

SBI alerts/faults

•
•

Undefined interrupts

•
•

Asynchronous write errors

MBA/UBA adapter errors

UBA errors

DEVICE_ERRORS

Include device errors in the report.

ENVIRONMENT AL_
ENTRIES

Include environmental entries in the report.

MACHINE_CHECKS

Include machine check errors in the report.

SNAPSHOT_ENTRIES

Include snapshot entries in the report.

MEMORY

Include memory errors in the report.

TIMEOUTS

Include device timeout errors in the report.

UNKNOWN_ENTRIES

Include any entry that had either an unknown entry
type or an unknown device type/class.

UNSOLICITED_MSCP

Include unsolicited MSCP entries in the output
report.

VOLUME _CHANGES

Include volume mount and dismount entries in the
report.

Use the UNKNOWN_ENTRIES keyword to obtain a report that contains the
contents of the device registers logged by unsupported devices.
Any known information for the entry is translated; the remaining information
is output in hexadecimal longwords.
If you specify a device class keyword or a device name construct with both

the /INCLUDE and /EXCLUDE qualifiers, the /INCLUDE qualifier takes
precedence.
The BUSES keyword also includes error log entries for the BI bus. The
DEVICE_ERRORS keyword also includes entries for the BI adapter.

ERR-14

ERROR LOG
/INCLUDE

EXAMPLES

$ ANALYZE/ERROR_LOG/INCLUDE=MTAO

In this example, the report consists of error log entries for the device MTAO,
which are in the default error log file ERRLOG.SYS.
~

$ ANALYZE/ERROR_LOG/INCLUDE=MTAO/EXCLUDE=TAPES

In this example, the device MIAO is included in the error log report for the
file ERRLOG.SYS. All other magnetic tape devices are excluded from the
report.
~

$ ANALYZE/ERROR_LOG/INCLUDE=(MTAO,VOL)

In this example, the report consists of error log entries and volume mounts
and dismounts for the device MTAO, which are in the default error log file
ERRLOG.SYS.
~

$ ANALYZE/ERROR_LOG/INCLUDE=(DISK,VOLUME_CHANGES)

In this example, the report consists of error log entries for disk volume
information, which are in the default error log file ERRLOG.SYS.
~

$ ANALYZE/ERROR_LOG/INCLUDE=(DISK,VOLUME_CHANGES,DEVICE_ERROR)

In this example, the report consists of error log entries for volume and
device error information on disks, which are in the default error log file
ERRLOG.SYS.
~

$ ANALYZE/ERROR_LOG/INCLUDE=(DISK,VOLUME_CHANGES,DEVICE_ERROR,BUGCHECK)

In this example, the report consists of error log entries for volume and device
error information on disks, and bugcheck errors. These entries are in the
default error log file ERRLOG.SYS.

ERR-15

ERROR LOG
/LOG

/LOG
Controls whether informational messages that specify the number of
entries selected and rejected for each input file are sent to SYS$0UTPUT.
By default, these messages are not displayed.

FORMAT

/[NO]LOG

EXAMPLE
$ ANALYZE/ERROR_LOG/LOG ERRLOG.OLD;5

In this example, informational messages generated about ERRLOG.OLD;S are
sent to SYS$0UTPUT.

ERR-16

ERROR LOG
/OUTPUT

/OUTPUT
Specifies the output file for the error log report.

FORMAT
PARAMETERS

/OUTPUT

[=file-spec]

file-spec
The output file selected for the error log report. See the VMS DCL Concepts
Manual for details on specifying files.

DESCRIPTION

If you omit the /OUTPUT qualifier, output is directed to SYS$0UTPUT. If
you specify /OUTPUT=file-spec, the selected output file contains the error
log report. If you omit the device or directory specification, the current device
and default directory are used. If you omit the file name, the file name of the
input file is used. If you omit the file type, the default file type is .LIS.

Do not use /OUTPUT with the /BINARY qualifier.

EXAMPLE
$ ANALYZE/ERROR_LOG/OUTPUT=ERROR_LOG.LIS ERRLOG.OLD;72

In this example, the ouput file ERROR_LOG.LIS contains entries generated
from ERRLOG.OLD;72.

ERR-17

ERROR LOG
/REGISTER_DUMP

/REGISTER_DUMP
Used in conjunction with the /INCLUDE qualifier to generate, in a
hexadecimal longword format, a report that consists of device register
information.

FORMAT

/REGISTER_DUMP

DESCRIPTION

Use the /REGISTER_DUMP qualifier to get a report that lists the
hexadecimal contents of the device registers for the device specified by
the /INCLUDE qualifier. The /INCLUDE qualifier must be used with the
/REGISTER_DUMP qualifier.
/REGISTER_DUMP reports register contents for memory, device error, and
device timeout entries. There is no translation of any of the device register
information.
Do not use /REGISTER_DUMP with the /BINARY qualifier.

EXAMPLE
$ ANALYZE/ERROR_LOG/INCLUDE=DB/REGISTER_DUMP ERRLOG.OLD;72

In this example, the output is in the format of a REGISTER-DUMP report
containing entries that apply only to the DB device.

ERR-18

ERROR LOG
/REJECTED

/REJECTED
Allows you to specify the name of a file that will contain binary records for
rejected entries.

FORMAT
PARAMETERS

/REJECTED

[=file-spec}

file-spec
Specifies the name of the file that is to contain the rejected entries.

DESCRIPTION

The /REJECTED qualifier creates a binary file that contains copies of the
original binary error log entry. If the error log entry is rejected because the
command line also specifies an interval (/SINCE, /BEFORE, or /ENTRY
qualifier) or a filter (/INCLUDE or /EXCLUDE qualifier), the entry is written
to the specified file.
Rejected entries are those entries that are not translated because they fall into
one of the following categories:
•

All entries specified with the /EXCLUDE qualifier

•

All entries not specified with the /INCLUDE qualifier

•

Any entry that does not occur within the period specified by the /SINCE
and /BEFORE qualifiers

•

Any entry that is not in the range of entries specified by the /ENTRY
qualifier

If you specify /REJECTED=file-spec, the output file contains image copies
of the rejected records. If you omit the device or directory specification, the
current device and default directory are used. If you omit the file name, the
file name of the input file is used. If you omit the file type, the default file
type is .REJ.

EXAMPLE
$ ANALYZE/ERROR_LOG/INCLUDE=MTAO/REJECTED=REAL_ERRS.DAT ERRLOG.OLD;5

In this example, the output file REAL_ERRS.DAT contains image copies of all
entries from ERRLOG.OLD;S, with the exception of those entries that apply
to the MTAO device.

ERR-19

ERROR LOG
/SID_REGISTER

/SID_REGISTER
Generates a report consisting of error log entries that occurred on the
specified CPU.

FORMAT
PARAMETERS

/SI D_REG I STER

[=%Xhexadecimal-value]

%Xhexadecimal-value
Specifies the value obtained from the system ID register. Use the $GETSYI
system service to obtain this value, which is unique to each system. The VMS
System Services Reference Manual describes the $GETSYI system service.

EXAMPLE
$ ANALYZE/ERROR_LOG/SID_REGISTER=%X02006148 ERRLOG.OLD;72

In this example, the output consists of only those entries that were logged for
the system with the system ID of 02006148 (hexadecimal).

ERR-20

ERROR LOG
/SINCE

/SINCE
Specifies that only those entries dated later than the stated date and time
are to be selected for the report.

FORMAT
PARAMETERS

/SINCE

[=date-time}

date-time
Limits the error report to those entries dated later than the specified time.

DESCRIPTION

Only absolute date and time specifications are valid. See the VMS DCL

Concepts Manual for details on specifying times.
If you omit the /SINCE qualifier, all entries are processed. If you specify

/SINCE without a date and time, the default is TODAY.

EXAMPLE
$ ANALYZE/ERROR_LOG/SINCE=31-DEC-1988:15:00 ERRLOG.OLD;56

In this example, the error log report generated from ERRLOG.OLD;56
contains entries that have been logged since 15:00 on December 31, 1988.

ERR-21

ERROR LOG
/STATISTICS

/STATISTICS
Generates run-time statistical information.

FORMAT

/STATISTICS

DESCRIPTION

Use the /STATISTICS qualifier to generate a report that consists of the page
faults, buffered 1/0, direct 1/0, and CPU time used in the execution of the
ANALYZE/ERROR_LOG command.

EXAMPLE
$ ANALYZE/ERROR_LOG/STATISTICS ERRLOG.OLD;4

In this example, the output generated by this command consists of a full
report of all entries in ERRLOG.OLD;4 and the run-time statistics for the
execution of the command.

ERR-22

ERROR LOG
/SUMMARY

/SUMMARY
Generates an error log report that consists of a statistical summary.
The Examples section shows the format of several error log summary
reports.

FORMAT

/SUMMARY [=summary-type[, ... ]}
/NOSUMMARY
summary-type

QUALIFIER
PARAMETER

The keyword for the selected type of summary.

PARAMETERS

Keywords

DESCRIPTION

DEVICE

Include the device summary section in the report.

ENTRY

Include the summary of entries logged section in the report.

HISTOGRAM

Include the processed entries hour of day histogram in the
report.

MEMORY

Include the summary of memory errors section in the report.

VOLUME

Include the volume label section in the report.

Select the type of summary by specifying one or more keywords.

Note: If you specify /SUMMARY without a summary type, the report contains
all of the summary types listed above. If you want only a summary
report, specify both the /NOFULL and the /SUMMARY qualifiers in the
command line.
Do not attempt to correlate the error counts reported by the DCL command
SHOW ERROR and the /SUMMARY qualifier. A discrepancy in these figures
could be due to several system events and would be difficult to track.
If the DEVICE keyword is specified, device entries are correlated with device

mount information in an attempt to identify the volume that was mounted
at the time the entry was logged. This correlation should help determine
whether errors can be attributed generically to the device or specifically to
a given volume. However, no correlation can be made under the following
conditions:
•

The device is not file-structured.

•

Volume information is not available. Either of the following conditions
can result in volume information not being available:
The device entry is contained in an error log file created after the
mount information was logged (SYS$ERRORLOG:ERRLOG.SYS was
renamed).

ERR-23

ERROR LOG
/SUMMARY

Volume shadowing is enabled. (Mount information pertains to the
virtual device, while device entry information pertains to the physical
device.)
In these instances, device entries are charged against a null volume name.
UCB ERROR COUNT and UCB OPERATION COUNT fields reflect the UCB
information according to the time of the most recent entry for the given
volume.
Do not use the /BINARY qualifier with /SUMMARY.

EXAMPLES
[I

$ ANALYZE/ERROR_LOG/SUMMARY ERRLOG.OLD;5

The output generated by the command in this example includes a full report
and a summary report of all entries in ERRLOG.OLD;S.

$ ANALYZE/ERROR_LOG/NOFULL/SUMMARY ERRLOG.OLD;5

The output generated by the command in this example consists of a summary
report of all entries in ERRLOG.OLD;S.
~

$ ANALYZE/ERROR_LOG/SUMMARY=(ENTRY,DEVICE)

The output generated by the command in this example includes the Entry
and Device sections of the summary report from the default input file
ERRLOG.SYS.
~

$ ANALYZE/ERROR_LOG/INCLUDE=DBA4/NOFULL/SUMMARY ERRLOG.OLD;5

The output generated by the command in this example includes the summary
report. The report contains the entries that apply to the DBA4 device: device
error, device timeout, and device attention.

ERR-24

ERROR LOG
ERROR LOG Examples

ERROR LOG
EXAMPLES

Sample Error Log Report

An error log report entry contains two sections: identification and devicedependent data. The identification section consists of the first four lines
and is generated for all reports. The device-dependent data section, which
follows the identification section, contains information on the selected error
log entries.
The first line of the identification section gives the error entry number. This
number can be used to refer to a particular error log entry in an error log
file. The second line contains the error sequence number and the system
identification value. The error sequence number is a value assigned by the
operating system to an error log entry to help determine if error log entries
are being lost. This sequence number value is reset to zero only when the
system is rebooted. The third and fourth lines of this section specify the type
of error log entry being reported, the date and time the entry was made, the
processor type and revision level, and the system serial number.
The first line of the device-dependent data section identifies the device
or subsystem on which the error occurred. The remainder of this section
consists of hardware information, which shows the contents of the device
registers, and software information, which shows the contents of the 1/0
database at the time of the error.
The Guide to Maintaining a VMS System contains additional information
on error log reports, including descriptions of error log entries. These
descriptions specify the action recommended for specific entries.
The following output report is an example of the report generated by device
errors, device attention, and device timeouts from a disk on the system.

V A X I V MS

SYSTEM ERROR REPORT

COMPILED 6-MAR-88 14:39
PAGE 1.

**************************** ENTRY

ERROR SEQUENCE 42.
DEVICE ERROR,

****************************
LOGGED ON SID 01380101

5-MAR-88 14:42:16.93
KA780 REV# 7. SERIAL# 257.

MASSBUS SUB-SYSTEM, UNIT _DBB1:
RH780 CSR
00000020
ADAPTER IS MBA
RH780 CR

00000004

RH780 SR

00003080

INTERRUPT ENABLE
11
MASSBUS 11 EXCEPTION
DATA TRANSFER ABORTED
DATA TRANSFER COMPLETED

RH780 VAR

0000003C
60. BYTE, PAGE OFFSET
MAPPING REGISTER #0. SELECTED

RH780 BCR

FEOOFE18
11
11

SBI 11 BYTE COUNT, 488.
MASSBUS 11 BYTE COUNT, 512.

ERR-25

ERROR LOG
ERROR LOG Examples

RH780 MPR #0.

800034F1
VALID
TRANSFER PAGE, 6776.5. K

RPCS

00000830
WRITE DATA
DRIVE AVAILABLE

RPDS

000059CO
VOLUME VALID
DRIVE READY
DRIVE PRESENT
WRITE PROTECTED
MEDIUM ON-LINE
COMPOSITE ERROR

RPER1

00000800

RPMR
RPAS
RPDA

00000100
00000000
00000105

WRITE LOCK ERROR

SECTOR= 5.
TRACK = 1.
RPDT

00002012
DRIVE TYPE RP06
MOVING HEAD

RPLA

00000110
SECOND QUARTER
SECTOR COUNTER= 4.

RPER2
RPOF

00000000
00009800
ECC INHIBIT
16-BIT FORMAT
SIGN CHANGE

RPDC

00000001

RPCC

00000001

DESIRED CYLINDER= 1.
CURRENT CYLINDER= 1.
V A X I V M S

SYSTEM ERROR REPORT

RPSN
RPER3
RPEC1
RPEC2
UCB$B_ERTCNT

00000247
00000000
00000000
00000000
08

UCB$B_ERTMAX

UCB$L_OWNUIC

00000000

UCB$L_CHAR

1CC54008

COMPILED 6-MAR-88 14:39
PAGE 2.

8. RETRIES REMAINING
8. RETRIES ALLOWABLE
OWNER UIC [000,000]
DIRECTORY STRUCTURED
FILE ORIENTED
SHARABLE
AVAILABLE
ERROR LOGGING
ALLOCATED
CAPABLE OF INPUT
CAPABLE OF OUTPUT
RANDOM ACCESS
UCB$W_STS

0910
ONLINE
BUSY
SOFTWARE VALID

UCB$L_OPCNT

ERR-26

OOOOOOOE

ERROR LOG
ERROR LOG Examples

14. QIO'S THIS UNIT
UCB$W_ERRCNT

0001

UCB$L_MEDIA

00010104

1. ERRORS THIS UNIT
FUNCTION START ADDRESS,
- CYLINDER #1 . ,
- TRACK #1.,
- SECTOR #4.
IRP$W_FUNC

OOOB

IRP$W_BCNT

0200

IRP$W_BOFF

001C

IRP$L_PID

0003003D

IRP$Q_IOSB

0000025C
00000000

WRITE PHYSICAL BLOCK
TRANSFER SIZE 512. BYTE(S)
28. BYTE PAGE OFFSET
REQUESTOR "PID"
IOSB, 0. BYTE(S) TRANSFERRED

Time Stamp, Volume Mount, and Volume Dismount Entries Examples

Following are entry examples of a system time stamp, volume mount, and
volume dismount. The time stamp entry contains only an identification
section, which is logged by the operating system at 10 minute intervals. If no
other error log entries are made during the 10 minute period, the previous
time stamp is overwritten with the current time stamp.
The mount volume entry contains an identification section followed by a
device-dependent data section. The device-dependent data section shows
the name of the device the volume is mounted on, the volume label (if the
volume has a label), and the 1/0 operations and error counts for the device.
The dismount volume entry contains, in addition to the data provided in the
volume mount entry, the 1/0 operations and error counts for the device on
which the volume was mounted.

**************************** ENTRY

ERROR SEQUENCE 421.

93. ****************************
LOGGED ON SID 01380101

TIME STAMP, 4-MAR-88 11:10:08.79
KA780 REV# 7. SERIAL# 7.
**************************** ENTRY
ERROR SEQUENCE 422.

94. ****************************
LOGGED ON SID 01380101

MOUNT VOLUME, 4-MAR-88 11:14:12.51
KA780 REV# 7. SERIAL# 7.
UNIT _DMAO:, VOLUME LABEL "TEST"
656. QIO OPERATIONS THIS UNIT, 1. ERRORS THIS UNIT
95. ****************************
ERROR SEQUENCE 423.
LOGGED ON SID 01380101

**************************** ENTRY

DISMOUNT VOLUME, 4-MAR-88 11:14:41.30
KA780 REV# 7. SERIAL# 7.
UNIT _DMAO: , VOLUME LABEL "TEST"
697. QIO OPERATIONS THIS UNIT, 1. ERRORS THIS UNIT
41. QIO OPERATIONS THIS VOLUME, 0. ERRORS THIS VOLUME

ERR-27

ERROR LOG
ERROR LOG Examples

Machine Check Entries Examples

Following are examples of machine check error reports. Each report consists
of three sections: the identification section, the program counter and summary
code section, and an error-dependent section.
The program counter and summary code section of the report displays the
contents of the program counter, the processor status longword, and the
summary code. The contents of the processor status longword and the
summary code are described in the text on the right side of the report.
The error-dependent section consists of CPU-dependent information that was
logged as a result of the machine check.

**************************** ENTRY

ERROR SEQUENCE 3.
MACHINE CHECK,

****************************

LOGGED ON SID 03003700

6-MAR-1988 10:11:34.70
KA730 REV# 0. MIC# 55.

EXCEPTION PC

80038DCO

ERROR PSL

01COOOOO
INTERRUPT PRIORITY LEVEL = 00.
PREVIOUS MODE = USER
CURRENT MODE = EXECUTIVE

SUMMARY CODE

00000007

1ST PARAMETER

00166200

UNCORRECTABLE ECC ERROR

**************************** ENTRY

ERROR SEQUENCE 4872.

PAGE #2865. IN ERROR
60. ****************************
LOGGED ON SID 02006148

MACHINE CHECK, 6-MAR-1988 03:50:08.28
KA750 REV# 72. MIC# 97.
EXCEPTION PC

80006173

ERROR PSL

OOC80009
C-BIT
N-BIT
INTERRUPT PRIORITY LEVEL = 08.
PREVIOUS MODE = USER
CURRENT MODE = KERNEL

SUMMARY CODE

00000002

VA LAST REF
PC AT ERROR
MOR
SMR

800A079E
80006178
8009F38C
00000008

RLTO
TBER

00000000
00000007

TRANSLATION BUFFER OR BUS ERROR

CPU MODE = KERNEL
VIRTUAL
READ
TB GO DATA ERROR
TB G1 DATA ERROR
TB GO TAG ERROR

CAER
BER
MCESR

00000000
00000000
00000004

**************************** ENTRY

ERROR SEQUENCE 4949.

ERR-28

OPERAND REFERENCE
TB PARITY ERROR
84. ****************************
LOGGED ON SID 01388525

ERROR LOG
ERROR LOG Examples

MACHINE CHECK,

6-MAR-1988 15:09:11.31
KA780 REV# 7. SERIAL# 1317.

EXCEPTION PC

00004890

ERROR PSL

03COOOOO
INTERRUPT PRIORITY LEVEL = 00.
PREVIOUS MODE = USER
CURRENT MODE = USER

SUMMARY CODE

00000000
CP READ TIMEOUT
- OR ERROR CONFIRMATION FAULT

CES

00010084
SUPERVISOR AST PENDING
ALU C31
NESTED ERROR

MICRO PC
VA/VIBA
D REGISTER
TB ERO

00000200
7FF735D4
FFFFC284
OOOODC81
ENABLE MEMORY MANAGEMENT
TB HIT GROUP 1
MICRO CODE "MCT" FIELD = 07
MICRO CODE "ADS"
MICRO CODE "FS"

TBER1

00000040

SB I TA

EOOB83F5

LAST TB WRITE PULSE TO GROUP 1
TIMEOUT CONSOLE ADDR = 002EOFD4
PROTECTION CHECKED REFERENCE
TIMEOUT REFERENCE IN USER MODE
CACHE PE REG

00004000

SB I ER

00001802

CP ERROR
SBI NOT BUSY
WAITING FOR READ DATA TIMEOUT
CPU TIMEOUT

**************************** ENTRY
82. ****************************
ERROR SEQUENCE 1077.
LOGGED ON SID 04FFFFFF
MACHINE CHECK 30-MAR-1988 20:55:17.41
KA86 REV# 255. SERIAL# 4095. MFG PLANT 7.
EHMSTS
40000802
VMS ERROR CODE = EBOX
MICRO TRAP VECTOR = 08 (X)
EHM ENTERED
EVMQSAV
00000004
VIRTUAL ADDRESS FOR EBOX PORT
_ REQUESTS
EBCS
00000800
ECS PARITY ERROR
EDP SR
00000000

ERR-29

ERROR LOG
ERROR LOG Examples

CS LINT

04183D1F
C BUS ADDRESS = 1F (X)
C BUS DATA = 3D (X)
INTERRUPT PRIORITY REQUEST = 8.
INTERNAL SOURCE
I/O ADAPTER = 0.
INTERVAL TIMER

IBESR

00004000
UDP SEL = IBOX REGISTER SELECT
UTPR <2:0> = EBOX PORT
ENABLE ETRAP

EBXWD1

00000004
TOP OF "SP STACK"
CONTENT IS ONE OF THE LAST
_ LONGWORDS WRITTEN TO MBOX

EBXWD2

7FF593DO
TOP OF "SP STACK" MINUS ONE
CONTENT IS ONE OF THE LAST
_ LONGWORDS WRITTEN TO MBOX

VASAV

7FF593F8
VIRTUAL ADDRESS FOR OP FETCH
_ PORT REQUEST ADDRESS
CALCULATION FOR OPERAND
PRE-FETCH AND RESULT DELIVERY

VIBASAV

OOOOE7FF
VIRTUAL ADDRESS OF NEXT IBUF
_ PORT REQUEST TO FILL IBUFFER

ESASAV

OOOOE7F2
PC OF INSTRUCTION DURING EBOX
EXECUTION AND RESULT STORAGE

ISASAV

OOOOE7F2
PC OF INSTRUCTION WHICH VA
_ CALCULATION UNIT IS DOING ADDRESS
_ CALCULATION OR OPERAND PRE-FETCH
_ OR IS PASSING OPERAND DATA

CPC

OOOOE7F4
PC OF INSTRUCTION IN
DECODE UNIT

MSTAT1

84006004
CO TAG MISS
BLOCK HIT
ABUS ADAPTER = 0.
WORD COUNT = 0.
CYCLE TYPE = READ REGISTER
DEST CP = EBOX

MSTAT2

00004FOO
DIAGNOSTIC STATUS FROM SBIA
RD COM/MSK <3:0> = F (X)
RD DAT L/S <1:0> = 0 (X)
ABUS BAD DATA CODE
PAMM DATA= ARRAY #0. ,SLOT #1.

MDECC

00066200

MERG

04000100

CSHCTL

00000003

(* DATA NOT VALID *)

MEMORY MANAGEMENT ENABLE
CACHE 0 ENABLE
CACHE 1 ENABLE
MEAR

0000007C
PHYSICAL ADDRESS IN PA LATCH
AT TIME OF ERROR = 0000007C

ERR-30

ERROR LOG
ERROR LOG Examples

MEDR

0000001F

FBXERR

FFFFFFFF

CSES

1BD73E01

DATA WORD USED DURING ERROR
(*

DATA NOT VALID *)

CS CODE = EBOX CONTROL STORE PARITY ERROR
CS SYNDROME = 3E (X)
CS ADDRESS = 1BD7 (X)
ERROR PC

OOOOE7F2

ERROR PSL

03C00004
Z-BIT
INTERRUPT PRIORITY LEVEL = 00.
PREVIOUS MODE = USER
CURRENT MODE = USER

IDA ES

00000000
(* DATA NOT VALID *)

AN/ER/INC=MACH ERR:ERRLOG.SYS_31MAR1988/ENT=S=82/0UT=DP.

Memory Error Entries Example

Memory error log entries consist of two types: fatal and nonfatal. A nonfatal
memory error indicates that a single bit has failed within a memory location,
and that the ECC (error code correctable) was able to compensate for the error
and correct the data. A fatal error indicates that multiple bits were erroneous,
and that the ECC could not correct the data.
Both the fatal and nonfatal memory entries are similar in their format. The
memory error log reports can be divided into two logical areas of information.
The first section of a memory error log report is the identification area. The
second section contains memory controller-specific information. This data
represents the information contained within the memory controller registers
at the time of the memory error. Bit-to-text translation of the registers is
performed and then listed on the right side of the report.

**************************** ENTRY

ERROR SEQUENCE 4.
MEMORY ERROR,

****************************

LOGGED ON SID 03003700

6-MAR-1988 10:11:34.70
KA730 REV# 0. MIC# 55.

CSRO

00166200
ERROR SYNDROME = 7F
CORRECTED ERROR, BIT #31.
ARRAY #1. IN ERROR

CSR!

18000000
MEMORY MAPPING ENABLE
ENABLE "CRD" REPORTING

CSR2

8100000F

**************************** ENTRY

ERROR SEQUENCE 342.

MEMORY SIZE = 2048.K
64K RAMS PRESENT
91. ****************************
LOGGED ON SID 0138207A

FATAL MEMORY ERROR, 4-MAR-88 08:16:45.20
KA780 REV# 7. SERIAL# 122.
CONTROLLER AT TR #5.

ERR-31

ERROR LOG
ERROR LOG Examples

PRTCFNG

00000040
ADAPTER IS MULTI-PORT MEMORY
PORT NUMBER = 0.

PRTCR

00000003
MASTER INTERRUPT ENABLE
PORT INTERFACE INTERRUPT ENABLE
RAM COUNT 0.

PCSR

07870003

IVDTCR

01870001

AER

16A70005

CSRO

OOOOC2C8

ERROR INTERRUPT ENABLE
INVALIDATE CACHE DEVICE ID = 0.
8. ARRAY BOARD(S) PRESENT
MEMORY BASE ADDRESS = 6144.K
ERROR SYNDROME = 05
RDS ERROR
ARRAY #6. IN ERROR
ARRAY BANK #1. IN ERROR
ERROR LOG REQUEST
MEMORY CONTAINS VALID DATA
PORT #2. POWERED DOWN
PORT #3. POWERED DOWN
ERROR INTERRUPT FROM PORT #1.
PORT #2. OFFLINE
PORT #3. OFFLINE
CSR1

0000380A

oooocooo

MAT

PORT #0. CONNECTED TO AN SBI
PORT #1. CONNECTED TO AN SBI
PORT #2. NOT PRESENT
PORT #3. NOT PRESENT
INVALIDATION MAP PRESENT
PORT #0. INVALIDATION ACK RECEIVED
PORT #1. INVALIDATION ACK RECEIVED

Nonfatal and User Bugchecks Entry Example

Following is an example of a fatal bugcheck. Nonfatal and user bugcheck
reports have the same format. These reports consist of three sections:
identification, bugcheck reason and process information, and system register
information.

**************************** ENTRY

58. ****************************
LOGGED ON SID 03003700

ERROR SEQUENCE 1129.

FATAL BUGCHECK, 21-FEB-1988 11:06:53.49
KA730 REV# 0. MIC# 55.
ACPMBFAIL, ACP failure to read mailbox
PROCESS NAME
PROCESS ID

00000000

ERROR PC

0000033C

ERROR PSL

OODF0008
N-BIT
INTERRUPT PRIORITY LEVEL= 31.
PREVIOUS MODE = USER
CURRENT MODE = KERNEL

STACK POINTERS
KSP 7FFE7D84

ERR-32

ESP 7FFE9EOO

SSP 7FFED04E USP 7FF7F194

ISP 80140000

ERROR LOG
ERROR LOG Examples

GENERAL REGISTERS
RO 00000001
R5 00000001
R10 00000000

R1 00000000 R2
R6 7FFED78A R7
R11 7FFE3FCO AP

7FFDFD80 R3
7FFED78A R8
00000000 FP

80000F10
7FFED052
7FFE7DDO

R4
R9
SP

00000001
7FFED25A
7FFE7DC8

SYSTEM REGISTERS
POBR

80199000

POLR

00000003

P1BR

7F9A8AOO

P1LR

001FFBE5

SBR

001FA600

SLR

00001680

PCBB

00024874

SCBB

001F8400

ASTLVL

00000002

SISR

00000000

recs

800000C1

PO PTE BASE (VIRT ADDR)
TOTAL PO PAGES
P1 PTE BASE (VIRT ADDR)
TOTAL NON-EXISTENT P1 PAGES
SYSTEM PTE BASE (PHY ADDR)
TOTAL PAGES 'SYSTEM' VIRT MEM
PCB BASE (PHY ADDR)
SCB BASE (PHY ADDR)
SUPERVISOR MODE AST PENDING
INTERRUPT REQUEST ACTIVE = 0.
RUN
INTERRUPT ENABLE
INTERRUPT
ERROR
ICR

FFFFF89D

TODR

396FEB84

INTERVAL COUNT REGISTER

Unknown Entries Examples

Following are sample reports for error log entries of unknown type. Each
report has an identification section and an error log record section. The
error log record section contains two types of records: interpretable and
noninterpretable. If ERROR LOG can interpret the fields of the record, the
utility gives the name of the field, its contents, and interprets what the field
is. If the utility cannot interpret the fields of a record, it gives the longword
value of the field and its contents in hexadecimal format.

**************************** ENTRY

ERROR SEQUENCE 2.

"UNKNOWN DEVICE" ENTRY,

95. ****************************
LOGGED ON SID 03003600

4-MAR-88 10:12:12.44
KA730 REV# 0. MIC# 54.

ERROR LOG RECORD
ERF$L_SID

03003600
SYSTEM ID REGISTER

ERL$W_ENTRY

0062
ERROR ENTRY TYPE

ERR-33

ERROR LOG
ERROR LOG Examples

EXE$GQ_SYSTIME

C9764980
008C2F30
ERL$GL_SEQUENCE
0002

64 BIT TIME WHEN ERROR LOGGED
UNIQUE ERROR SEQUENCE = 2.

UCB$W_STS

0110
DEVICE STATUS

UCB$B_DEVCLASS

UCB$B_DEVTYPE

DEVICE CLASS = 66.
DEVICE TYPE = 66.
UCB$W_UNIT

0000

UCB$W_ERRCNT

0001

UCB$L_OPCNT

00000001

ORB$L_OWNER

00010004

UCB$L_DEVCHAR

OC440007

PHYSICAL UNIT NUMBER = 0.
UNIT ERROR COUNT= 1.
UNIT OPERATION COUNT= 1.
OWNER UIC = [001,004]
DEVICE CHARACTERISTICS
UCB$B_SLAVE

DDB$T_NAME

41515403
00000000
00000000
00000000

LONGWORD 1.

00000008

LONGWORD 2.

00000007

LONGWORD 3.

00000502

LONGWORD 4.

04000000

LONGWORD 5.

00010000

LONGWORD 6.

00000000

LONGWORD 7.

00000080

LONGWORD 8.

00000000

LONGWORD 9.

00000000

DEVICE SLAVE CONTROLLER= 0.

/.TQA ............ /

**************************** ENTRY

ERROR SEQUENCE 213.

161. ****************************
LOGGED ON SID 070001FF

"UNKNOWN ENTRY", 4-MAR-88 11:35:15.73
UVAX1 REV# 255. MIC# 1.
ERROR LOG RECORD
ERF$L_SID

070001FF
SYSTEM ID REGISTER

ERL$W_ENTRY

0008
ERROR ENTRY TYPE

EXE$GQ_SYSTIME
ERL$GL_SEQUENCE

89953F20
008C3E2A

64 BIT TIME WHEN ERROR LOGGED

OOD5
UNIQUE ERROR SEQUENCE = 213.

LONGWORD 1.

00000001

LONGWORD 2.

00410001

I .... /
I . . A./

ERR-34

ERROR LOG
ERROR LOG Examples

Example of a Brief Report

Following is an example of a report generated with the /BRIEF qualifier.
V A X I V MS

SYSTEM ERROR REPORT

**************************** ENTRY
ERROR SEQUENCE 11.
DATA/TIME 18-JUL-1988 22:53:41.57

COMPILED 25-AUG-1988 09:42
PAGE
1.

****************************

LOGGED ON:

SID 08000000
SYS_TYPE 00000000

DEVICE ERROR KA630
RD32 SUB-SYSTEM, UNIT _RICHIE$DUAO:
DMA ADDRESS

000000

DSECT
06

CHEAD
14

DHEAD
14

CCYL
9C

DCYL
9C

SCNT
01

RTCNT
FO

CSTAT
08

MODE

DST AT
B2

TERM
BD

ISTAT
28

CMD
56

Summary Report Examples

Following are examples of summary reports generated with the /SUMMARY
qualifier using the DEVICE, ENTRY, HISTOGRAM, MEMORY, and VOLUME
keywords.
Sample Device Summary Report (/SUMMARY=DEVICE)
DEVICE SUMMARY LOGGED BY SID 0484FOOB
ERRORS
[HARD] [SOFT]

TIMEOUTS
[HARD] [SOFT]

UCB ERROR
COUNT

UCB OPERATION
COUNT

_HSC001$DUA1:

25.

1027.

35.

243.

"WORK_1A"
"WOKR_1B"
------- -------

TOTALS

------------ -------------

------- -------

243.

Sample Entry Summary Report (/SUMMARY=ENTRY)
SUMMARY OF ALL ENTRIES LOGGED BY SID 0484FOOB
MACHINE CHECK
SBIA ERROR
SYSTEM START-UP
ERRLOG.SYS CREATED
FATAL BUGCHECK
TIME-STAMP
VOLUME MOUNT
VOLUME DISMOUNT
DEVICE ATTENTION
ERL$LOGSTATUS
ERL$LOGMESSAGE
ERL$LOGMSCP

10.
7.
3.
6.

223.
678.
194.
19.
7.

1254.
431.

ERR-35

ERROR LOG
ERROR LOG Examples

DATE OF EARLIEST ENTRY
DATE OF LATEST ENTRY

1-AUG-1988 09:54:51.52
27-AUG-1988 12:11:29.26

Sample Histogram Summary Report (/SUMMARY=HISTOGRAM)
PROCESSED ENTRIES HOUR-OF-DAY HISTOGRAM LOGGED BY SID 0484FOOB
00:00
01 :00
02:00
03:00
04:00
05:00
06:00
07:00
08:00
09:00
10:00
11 :00
12:00
13:00
14:00
15:00
16:00
17:00
18:00
19:00
20:00
21 :00
22:00
23:00

449. **************************************************
47. ***********************************************
35. ***********************************
19. *******************
33. *********************************
25. *************************
51. **************************************************
110. **************************************************
77. **************************************************
111. **************************************************
124. **************************************************
113. **************************************************
197. **************************************************
119. **************************************************
34. **********************************
52. **************************************************
70. **************************************************
195. **************************************************
171. **************************************************
108. **************************************************
169. **************************************************
139. **************************************************
39. ***************************************
354. **************************************************

Sample Memory Summary Report (/SUMMARY=MEMORY)

The format of memory summary reports varies slightly across the range of
CPU /memory subsystem configurations.
SUMMARY OF MEMORY ERRORS LOGGED BY SID 0484FOOB
ARRAY#

BIT#

WORD
COUNT

CORRECTED
ERRORS

02.

12.

00.

173.

02.

DBL BIT

00.

04.

00.

UNCORRECTED
ERRORS

Sample Volume Summary Report (/SUMMARY=VOLUME)
VOLUME LABEL(S) LOGGED BY SID 0484FOOB
QIO (S)

ERROR(S)

MOUNT(S)

"WORK_1A"
_HSC001$DUA1:
51.
_HSC001$DUA2:
65.

---------TOTALS

ERR-36

116.

---------- ----------

Index
Examples (cont'd.)

A
ANAL YZE/ERROR_LOG DCL command• ERR-3

B
/BEFORE qualifier• ERR-5
/BINARY qualifier• ERR-6
/BRIEF qualifier• ERR-7
Buffered 1/0 • ERR-22

D
Devices
excluding• ERR-9
including• ERR-13
Direct 1/0 • ERR-22

E
/ENTRY qualifier• ERR-8
Entry types
excluding• ERR-9
including• ERR-13
Error Log Utility (ERROR LOG)
directing output• ERR-3
examples• ERR-25 to ERR-36
exiting from• ERR-3
invoking• ERR-3
qualifiers• ERR-4 to ERR-24
restrictions• ERR-3
Events reported• ERR-1
Examples
/BEFORE qualifier• ERR-5
/BINARY qualifier• ERR-6
/BRIEF qualifier• ERR-7
brief report• ERR-35
/ENTRY qualifier• ERR-8
/EXCLUDE qualifier• ERR-11
/FULL qualifier• ERR-12, ERR-24

/INCLUDE qualifier •-ERR-15, ERR-18, ERR-19,
ERR-24
/LOG qualifier• ERR-16
machine check• ERR-28
memory error • ERR-3 1
nonfatal and user bugchecks • ERR-32
/OUTPUT qualifier• ERR-17
/REGISTER_DUMP qualifier• ERR-18
/REJECTED qualifier• ERR-19
sample error log report• ERR-25
/SID_REGISTER qualifier• ERR-20
/SINCE qualifier• ERR-21
/ST A TISTICS qualifier• ERR-22
/SUMMARY qualifier• ERR-24
summary report• ERR-35
time stamp• ERR-27
volume dismount• ERR-27
volume mount• ERR-27
/EXCLUDE qualifier• ERR-9
unknown entries• ERR-10
Execution time• ERR-22

F
/FULL qualifier• ERR-1 2

I
1/0
buffered• ERR-22
direct• ERR-22
/INCLUDE qualifier• ERR-13
unknown entries• ERR-14

L
/LOG qualifier• ERR-16

lndex-1

Index

Messages• ERR-1

/REGISTER_DUMP qualifier• ERR-18
/REJECTED qualifier• ERR-19

/OUTPUT qualifier• ERR-17
Output reports• ERR-1

p
Page faults• ERR-22

a
Qualifiers• ERR--4 to ERR-24

lndex-2

/SID_REGISTER qualifier• ERR-20
/SINCE qualifier• ERR-21
/ST A TISTICS qualifier• ERR-22
/SUMMARY qualifier• ERR-23

u
Unknown entries• ERR-2

Reader's Comments

VMS Error Log Utility

Manual
AA-LA37 A-TE

Please use this postage-paid form to comment on this manual. If you require a written reply to a software
problem and are eligible to receive one under Software Performance Report (SPR) service, submit your
comments on an SPR form.
Thank you for your assistance.

I rate this manual's:
Accuracy (software works as manual says)
Completeness (enough information)
Clarity (easy to understand)
Organization (structure of subject matter)
Figures (useful)
Examples (useful)
Index (ability to find topic)
Page layout (easy to find information)

Excellent

Good

Fair

Poor

D
D
D
D
D
D
D
D

I would like to see more /less

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

I am using Version _ _ _ of the software this manual describes.

Name/Title

Dept.

Company

Date

Mailing Address
Phone

- Do Not Tear - Fold Here and Tape -------------------~lllr--------------
No Postage

~nmnamn™

~;~=~=~y
in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POST AGE WILL BE PAID BY ADDRESSEE

DIGIT AL EQUIPMENT CORPORATION
Corporate User Publications-Spit Brook
ZKO 1-3 / J35 110 SPIT BROOK ROAD
NASHUA, NH 03062-9987

111 ..... 11.11 .... 11 .... 1.11.1 .. 1.1 .. 1•• 1.1 ••• 1.11 .. 1
- Do Not Tear - Fold Here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Reader's Comments

VMS Error Log Utility

Manual
AA-LA37 A-TE

Excellent

Good

Fair

Poor

D
D
D
D
D
D
D
D

I would like to see more /less

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page
Description

Additional comments or suggestions to improve this manual:

I am using Version _ _ _ of the software this manual describes.

Name/Title

Dept.

Company

Date

Mailing Address
Phone

--;;~t;~~;:d Here and Tape ------------------~1nr-------~~5~~---

I
I
I
I
I
I

in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POST AGE WILL BE PAID BY ADDRESSEE

DIGIT AL EQUIPMENT CORPORATION
Corporate User Publications-Spit Brook
ZK01-3/J35 110 SPIT BROOK ROAD
NASHUA, NH 03062-9987

111 ..... 11.11 .... 11 .... 1.11.1 .. 1.1 .. 1•• 1.1 ... 1.11 .. 1
·- Do Not Tear - Fold Here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

""'

..cc

Is
..s
<II!