[OpenVMS documentation]
[Site home] [Send comments] [Help with this site] [How to order documentation] [OpenVMS site] [Compaq site]
Updated: 11 December 1998

OpenVMS System Management Utilities Reference Manual


Previous Contents Index

/INCLUDE

Includes events generated by the specified device class, device name, or event log entry type in the report.

Format

/INCLUDE= [device-class | device-name | entry-type ] [,...]


Parameters

device-class

device-name

entry-type

Specifies one or more keywords denoting the device class, device name, or entry type. If you specify more than one keyword, you must specify a comma-separated list of values that is enclosed in parentheses.

Device Class Keywords

Examples of Device Name Constructs
DB Group of devices
DBA1 Specific device/unit number
(DBA1,HSC1$DUA1,DYA0) List of devices
(DB,DR,XF) List of device groups

Entry-Type Keywords
ATTENTIONS Include device attention entries in the report.
BUGCHECKS Include all types of bugcheck errors in the report.
CONFIGURATION Include system configuration entries in the report.
CONTROL_ENTRIES Include control entries in the report. Control entries include the following entry types:
  • System power failure restarts
  • Time stamps
  • System startups
  • $SNDERR messages (system service to send messages to error log)
  • Operator messages
  • Network messages
  • ERRLOG.SYS created
CPU_ENTRIES Include CPU-related entries in the report. CPU entries include the following entry types:
  • SBI alerts/faults
  • Undefined interrupts
  • MBA/UBA adapter errors
  • Asynchronous write errors
  • UBA errors
DEVICE_ERRORS Include device errors in the report.
ENVIRONMENTAL_ENTRIES Include environmental entries in the report.
MACHINE_CHECKS Include machine check errors in the report.
MEMORY Include memory errors in the report.
SNAPSHOT_ENTRIES Include snapshot entries in the report.
SYNDROME Include console-generated entries that describe a symptom set used by Compaq support representatives to identify problems.
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 or class.
UNSOLICITED_MSCP Include unsolicited MSCP entries in the output report.
VOLUME_CHANGES Include volume mount and dismount entries in the report.


Description

You can specify one or more devices by device class, device name, or one or more keywords that identify entry types.

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.


Examples

#1

DIAGNOSE/TRANSLATE/INCLUDE=MTA0
      

In this example, the full (default) report consists of entries for the device MTA0, which are in the default error log file ERRLOG.SYS.

#2

DIAGNOSE/TRANSLATE/INCLUDE=MTA0/EXCLUDE=TAPES
      

In this example, the device MTA0 is included in the full (default) report for the file ERRLOG.SYS. All other magnetic tape devices are excluded from the report.

#3

DIAGNOSE/TRANSLATE/INCLUDE=(MTA0,VOL)
      

In this example, the full (default) report consists of all entries and volume mounts and dismounts for the device MTA0, which are in the default error log file ERRLOG.SYS.

#4

DIAGNOSE/TRANSLATE/INCLUDE=(DISKS,VOLUME_CHANGES)
      

In this example, the full (default) report consists of all entries for all disks and all entries for volume information, which are in the default error log file ERRLOG.SYS.

#5

DIAGNOSE/TRANSLATE/INCLUDE=(DISKS,VOLUME_CHANGES,DEVICE_ERROR)
      

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

#6

DIAGNOSE/TRANSLATE/INCLUDE=(DISKS,VOLUME_CHANGES,DEVICE_ERROR,BUGCHECK)
      

In this example, the full (default) report consists of all entries for disks, all entries for volume changes, all entries for device error information on disks, and all entries for bugcheck events. These entries are in the default error log file ERRLOG.SYS.

/INTERACTIVE

Allows users to exit the command line interface (CLI) and enter the DECevent interactive command shell.

Format

/INTERACTIVE


Description

All commands valid from the CLI are valid from within the interactive command shell. You do not need to precede qualifiers with DIAGNOSE/TRANSLATE when in the interactive command shell. In addition to CLI commands, the interactive command shell accepts SET, SAVE, and RESTORE commands.

Example


$ DIAGNOSE/TRANSLATE/INTERACTIVE 
      

In this example, a user has requested to exit the command line interface and enter the DECevent interactive command shell.

The DIAG> prompt is displayed when in the interactive command shell.

/LOG

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

Format

/[NO]LOG


Example


$ DIAGNOSE/TRANSLATE/LOG ERRLOG.OLD;5
      

In this example, informational messages generated about ERRLOG.OLD;5 are sent to SYS$OUTPUT.

/NODE

Generates a report consisting of error log entries for specific nodes in an OpenVMS Cluster system.

Format

/NODE= (node-name[,...])


Parameter

node-name

Specifies the names of one or more OpenVMS Cluster members. Names cannot exceed six characters. If more than one node name is entered, you must specify a comma-separated list of node names that is enclosed in parentheses.

Example


$ DIAGNOSE/TRANSLATE/NODE=(GARCIA,LESH) SYS$SYSROOT:[SYS*.SYSERR]ERRLOG.SYS
      

In this example, the cluster system consists of members BROOME, GARCIA, LESH, and PUTNAM. The output full (default) report contains only those entries that were logged for nodes GARCIA and LESH.

/OUTPUT

Specifies the output file for the report.

Format

/OUTPUT [=file-spec]


Parameter

file-spec

The output file selected for the report. Refer to the OpenVMS User's Manual for details on specifying files.

Description

If you omit the /OUTPUT qualifier, output is directed to SYS$OUTPUT. If you specify /OUTPUT=file-spec, the selected output file contains the 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


$ DIAGNOSE/TRANSLATE/OUTPUT=ERROR_LOG.LIS ERRLOG.OLD;72
      

In this example, the default full report ERROR_LOG.LIS contains entries generated from ERRLOG.OLD;72.

/REJECTED

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

Format

/REJECTED [=file-spec]


Parameter

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 event log entry. If the event 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 not translated because they fall into one of the following categories:

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


$ DIAGNOSE/TRANSLATE/INCLUDE/BINARY=MTA0/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;5, with the exception of those entries that apply to the MTA0 device. Note the use of the /BINARY qualifier.

/SINCE

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

Format

/SINCE [=date-time]


Parameter

date-time

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

Description

Only absolute date and time specifications are valid. Refer to the OpenVMS User's 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


$ DIAGNOSE/TRANSLATE/SINCE=19-APR-1998:15:00 ERRLOG.OLD;56
      

In this example, the full (default) report generated from ERRLOG.OLD;56 contains entries that have been logged since 15:00 on April 19, 1998.

/SUMMARY

Generates summary information of all events in the event log.

Format

/SUMMARY


Description

The /SUMMARY qualifier generates a summary report from the specified input event log file.

Do not use the /BINARY qualifier with /SUMMARY.


Example


$ DIAGNOSE/TRANSLATE/SUMMARY ERRLOG.OLD;5
      

The output generated by the command in this example is a summary report of all entries in ERRLOG.OLD;5.

/TERSE

Generates a terse report.

Format

/TERSE


Description

The /TERSE qualifier specifies that the registers and header of each event entry be formatted in the standard report type format, but the contents of each register are not translated into readable messages.

Do not use the /TERSE report qualifier with the /BINARY qualifier.

Section 9.4 shows the format of a typical terse report.


Example


$ DIAGNOSE/TRANSLATE/TERSE ERRLOG.OLD;97
      

In this example, the terse report generated from ERRLOG.OLD;97 contains register and header information.

/TRANSLATE

Translates the contents of an event log file. This qualifier is the default qualifier to the DIAGNOSE verb.

Format

/TRANSLATE [qualifier(s)][infile][,...]


Description

The /TRANSLATE qualifier translates the contents of the default event log file, SYS$ERRORLOG:ERRLOG.SYS, or a selected input event log file.

Example


$ DIAGNOSE/TRANSLATE/BRIEF ERRLOG.OLD;97
      

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

9.4 DECevent Examples

Sample Event Log Reports

The DECevent event management utility provides the following five report types:

The following sections show examples of each report type with a brief explanation of each.

Full Report Example

To produce a full report, use the /FULL qualifier. The full report format provides a translation of all available information for each entry in the event log. The full report is the default report type if a report type is not specified in the command line; /TRANSLATE is the default qualifier.

Either of the following commands will produce a full report format:


$ DIAGNOSE/TRANSLATE/FULL 
 
$ DIAGNOSE   

The following example shows the format of a full report.


******************************** ENTRY    1 ******************************** 
Logging OS                        1. OpenVMS 
System Architecture               2. Alpha 
OS version                           V7.1 
Event sequence number          1583. 
Timestamp of occurrence              18-APR-1998 09:21:18 
System uptime in seconds      58004. 
Error mask                x00000000 
Flags                         x0001  Dynamic Device Recognition present 
Host name                            COGENT 
 
Alpha HW model                       DEC 3000 Model 400 
System type register      x00000004  DEC 3000 
Unique CPU ID             x00000002 
mpnum                     x000000FF 
mperr                     x000000FF 
 
Event validity                   -1. Unknown validity code 
Event severity                   -1. Unknown severity code 
Entry type                      100. 
Major Event class                 3. IO Subsystem 
 
IO Minor Class                    1. MSCP 
IO Minor Sub Class                5. Logged Message 
 
---- Device Profile ---- 
Vendor 
Product Name                         RAID 0 - Host Based 
Unit Name                            COGENT$DPA 
Unit Number                      10. 
Device Class                  x0001  Disk 
 
---- IO SW Profile ---- 
VMS DC$_CLASS                     1. 
VMS DT$_TYPE                    175. 
 
---- MSCP Logged Msg ---- 
 
Logged Message Type Code         22. RAID Message 
RAID Event Type                   8. Remove Member 
Distinguished Member              0. 
Member Index                      1. 
RAID Urgency                      4. Global Disk Error 
RAID Status               x00180009  Bit 00 - Reduced 
                                     Bit 03 - Striped 
                                     Bit 19 - FE Dis FE 
                                     Bit 20 - BC Buff Copy Off 
RAIDset Name                         KGB 
 
**************************************************************************** 
 

Brief Report Example

To produce a brief report, use the /BRIEF qualifier. The brief report format provides translation of key information for each entry in the event log.

For a brief report format, enter the following command:


$ DIAGNOSE/TRANSLATE/BRIEF 

The following example shows the format for a brief report.


******************************** ENTRY    1 ******************************** 
 
Logging OS                        1. OpenVMS 
System Architecture               2. Alpha 
OS version                           V7.1 
Event sequence number          1583. 
Timestamp of occurrence              18-APR-1998 09:21:18 
System uptime in seconds      58004. 
Error mask                x00000000 
Host name                            COGENT 
 
Alpha HW model                       DEC 3000 Model 400 
System type register      x00000004  DEC 3000 
Unique CPU ID             x00000002 
mpnum                     x000000FF 
mperr                     x000000FF 
 
Event validity                   -1. Unknown validity code 
Event severity                   -1. Unknown severity code 
Major Event class                 3. IO Subsystem 
 
IO Minor Class                    1. MSCP 
IO Minor Sub Class                5. Logged Message 
 
---- Device Profile ---- 
Vendor 
Product Name                         RAID 0 - Host Based 
Unit Name                            COGENT$DPA 
Unit Number                      10. 
Device Class                  x0001  Disk 
 
 
 
Logged Message Type Code         22. RAID Message 
RAID Event Type                   8. Remove Member 
Distinguished Member              0. 
Member Index                      1. 
RAID Urgency                      4. Global Disk Error 
RAID Status               x00180009  Bit 00 - Reduced 
                                     Bit 03 - Striped 
                                     Bit 19 - FE Dis FE 
                                     Bit 20 - BC Buff Copy Off 
RAIDset Name                         KGB 
                                       
***************************************************************************** 

Terse Report Example

To produce a terse report, use the /TERSE qualifier. The terse report format provides binary event information and displays register values and other ASCII messages in a condensed format.

For a terse report format, enter the following command:


$ DIAGNOSE/TRANSLATE/TERSE 

The following example shows the format for a terse report.


******************************** ENTRY    1 ******************************** 
 
Logging OS                           1. 
System Architecture                  2. 
OS version                  V7.1 
Event sequence number             1583. 
Timestamp of occurrence     1998041809211800 
System uptime in seconds         58004. 
Error mask                   x00000000 
Flags                            x0001 
Host name                   COGENT 
Alpha HW model               DEC 3000 Model 400 
System type register         x00000004 
Unique CPU ID                x00000002 
mpnum                        x000000FF 
mperr                        x000000FF 
Event validity                      -1. 
Event severity                      -1. 
Entry type                         100. 
Major Event class                    3. 
IO Minor Class                       1. 
IO Minor Sub Class                   5. 
---- Device Profile ---- 
Vendor 
Product Name                RAID 0 - Host Based 
Unit Name                   COGENT$DPA 
Unit Number                         10. 
Device Class                     x0001 
 
---- IO SW Profile ---- 
VMS DC$_CLASS                        1. 
VMS DT$_TYPE                       175. 
---- MSCP Logged Msg ---- 
 
Logged Message Type Code            22. 
RAID Event Type                      8. 
Distinguished Member                 0. 
Member Index                         1. 
RAID Urgency                         4. 
RAID Status                  x00180009 
RAIDset Name                KGB 
 
********************************************************************** 

Summary Report Example

To produce a summary report, use the /SUMMARY qualifier. The summary report format provides a statistical summary of the event entries in the event log.

For a summary report format, enter the following command:


$ DIAGNOSE/TRANSLATE/SUMMARY 

The following example shows the format for a summary report.


*************************************************************************** 
 
 SUMMARY OF ALL ENTRIES LOGGED ON NODE COGENT 
 
     IO Subsystem 
       MSCP                                  9. 
       Host Based RAID                       3. 
 
 DATE OF EARLIEST ENTRY                18-APR-1998 09:21:18 
 DATE OF LATEST ENTRY                  12-MAY-1998 10:44:54 
 
*************************************************************************** 

FSTERR Report Example

To produce a FSTERR report, use the /FSTERR qualifier:


$ DIAGNOSE/TRANSLATE/FSTERR 

The FSTERR report provides a quick, one-line-per-entry report of your event log for a variety of disks and tape devices. This makes event analysis and system troubleshooting much easier by eliminating extraneous event information.

The FSTERR report includes only the information that Compaq support representatives need when troubleshooting a problem with a tape or disk device.

The following example shows the format for a FSTERR report.


                                                                      Drive/ 
                                  MSCP               Physical     HSC Volume 
  Drive Name  yymmdd hhmmss Entry Evnt LED   LBN    Cyl Hd Sec RA  RP Serial 
============= ============= ===== ==== === ======= ==== == === === == ====== 
  LUKE$DUA070 921119 160754     3 00EB         255             70  71 V00717 
  LUKE$DUA070 921119 160754     4 00EB         255             70  71 V00717 
HSC015$DUA028 910323 113204     5 00EB                         70  51 V15039 
HSC015$DUA028 910323 113204     6 00EB                         71  51 V15039 
 BATES$DUA197 921118 002116     7 00EB                         72  32 V17524 
CHEWIE$DUA101 911205 114908     8 00EB                         73  81 V   17 
PMASON$DUA006 921207 165007    15 00EB         255             90  42 D23387 
PMASON$DUA006 921207 165007    16 00EB         255             90  42 D23387 
  C3P0$DUA242 870218 060031    17 01AB                         90  40 D48575 
  CHER$DU2132*901008 231053    18 00EB                         92  81 D 2345 
 


Previous Next Contents Index

[Site home] [Send comments] [Help with this site] [How to order documentation] [OpenVMS site] [Compaq site]
[OpenVMS documentation]

Copyright © Compaq Computer Corporation 1998. All rights reserved.

Legal
6048PRO_024.HTML