![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
On Alpha systems, CLUE features are provided through System Dump Analyzer (SDA) utility commands. Refer to the OpenVMS Alpha System Dump Analyzer Utility Manual for more information.
When a system fails, physical memory is copied to the crash dump file, and CLUE automatically appends the relevant parameters to a file named CLUE$OUTPUT:CLUE$HISTORY.DATA. You can use CLUE to display and examine the data in this file.
CLUE /DISPLAY
None.
Before you run CLUE, define the CLUE command (either interactively or in a procedure such as a login command procedure), as follows:$ CLUE :== $CLUETo invoke CLUE, enter the CLUE/DISPLAY command. To terminate CLUE, enter the EXIT command at the CLUE_DISPLAY> prompt or press Ctrl/Z.
Note that you can also issue CLUE/DISPLAY commands directly from DCL, as in the following example:
$ CLUE/DISPLAY = DIR/TYPE=INVEXCEPTN/SINCE=21-NOV-1995/OUT=CLUE.LIS
Table 8-1 lists the commands described in this section.
| Command | Description |
|---|---|
| DELETE | Deletes an entry from the crash history file |
| DIRECTORY | Displays a list of entries from the crash history file |
| EXIT | Exits from CLUE |
| EXTRACT | Extracts data from an entry in the crash history file to a file |
| HELP | Provides online help for CLUE/DISPLAY commands |
| SHOW | Displays specific information for an entry in the crash history file |
Deletes an entry from the list and writes the remaining entries to a binary file.
DELETE n
n
The number of the entry that you want to delete from the crash history file. The number of the entry corresponds to the entry number shown by the DIRECTORY command.
Entries in the CLUE.BIN file can be permanently removed using the DELETE command. This command deletes the specified entry and writes the remaining entries to an output file. When an entry is deleted from the crash history file, a new history file (with a higher version number) is created.
CLUE_DISPLAY> DELETE 4
Deletes the fourth entry in the list.
Displays a brief summary of each entry in the crash history file.
DIRECTORY
/MODULE=
Lists all failures that correspond to the specified module (that is, failures that start with the specified string)./OFFSET=
Lists all failures that correspond to the specified offset (that is, failures that start with the specified string)./SINCE=
Lists all failures that have occurred since the specified date. If the /SINCE qualifier is used and no date is specified, all failures that have occurred on the current day are listed./TYPE=
Lists all failures that correspond to the specified type (that is, failures that start with the specified string).
The DIRECTORY command lists the record entries in the crash history file, beginning with the most recent entry. Six headings are displayed for each entry:
- Entry number
- Date and time of crash
- Type
- Process
- Module
- Offset
You can use one or more qualifiers for the DIRECTORY command to limit the crash entries that are displayed. You can also use more than one qualifier in the same command line. For example, the command DIRECTORY/SINCE=18-APR-1996/MODULE=NETACP lists only those crash entries that have taken place since April 18, 1996, and for which the module is NETACP.
Examples
CLUE_DISPLAY> DIRECTORY # Time Type Process name Module Offset ==== ========== ============ ====== ====== 1 11-JUL-1996 09:07:45.78 INVEXCEPTN batman NETACP 14B9 2 01-JAN-1996 11:32:55.23 SSRVEXCEPT startrek SYSLOA 10A8 3 15-MAY-1996 07:26:12.34 BADFID evolushun NONE NONE 4 22-APR-1996 10:45:20.60 INVEXCEPTN aprocess IOBUF 015D
CLUE_DISPLAY> DIRECTORY /MODULE=SYSLOA # Time Type Process name Module Offset ==== ========== ============ ====== ====== 2 01-JAN-1996 11:32:55.23 SSRVEXCEPT startrek SYSLOA 10A8
Exits from CLUE.
EXIT
This command exits from CLUE and returns you to the DCL level.
CLUE_DISPLAY> EXIT $
This example exits from CLUE.
Extracts all of the data from an entry in the crash history file to either an ASCII or a binary file.
EXTRACT n
n
The number of the entry that you want to extract to a file. The number of the entry corresponds to the entry number shown by the DIRECTORY command.
/BINARY=filename.bin
The /BINARY qualifier writes the output to a binary file./OUTPUT=filename.txt
The /OUTPUT qualifier writes the output to an ASCII file. The /OUTPUT qualifier is the default.
Use the EXTRACT command to save record entries from the crash history file to an ASCII or a binary file. If no qualifier is used, entry is written to a text file with the name CLUE$HISTORY.TXT.
CLUE_DISPLAY> EXTRACT 3 /OUTPUT=15MAYCRASH.TXT
This command writes the data from entry number 3 in the crash history file to an ASCII file named 15MAYCRASH.TXT.
Provides online help for CLUE commands.
HELP [command]
command
The command for which you want help.
CLUE_DISPLAY> HELP DIRECTORY
This command provides online help for the DIRECTORY command in CLUE.
Displays specific information for an entry in the crash history file.
SHOW info_type n
info_type
You must choose one of the following information types:
- CRASH---displays information similar to the SHOW CRASH command in the System Dump Analyzer (SDA) utility.
- STACK---displays information similar to the SHOW STACK command in SDA.
- EXEC---displays information similar to the SHOW EXEC and SHOW DEVICE commands in SDA.
- ISTREAM---displays the instruction stream around the failing PC.
- SUMMARY---displays the active processes on the system, similar to the SHOW SUMMARY/IMAGE command in SDA.
- ALL---displays all the information from the preceding types.
For more information about SDA commands, see the OpenVMS VAX System Dump Analyzer Utility Manual.
n
The number of the entry for which you want to display information. The number of the entry corresponds to the entry number shown by the DIRECTORY command.
This command lets you see all the data associated with a particular failure. This information is split into several sections; you can choose to see either individual sections or all of the information.If the crash number is not specified, information for the most recent entry in the crash history file is displayed. You must, however, specify one of the keywords for info_type.
If you request a specific entry from the crash history list (using the SHOW n command), the display will include some parameters that are useful only to Digital service representatives.
CLUE_DISPLAY> SHOW ISTREAM 4
Instructions around the failing PC:
80A9F841 RSB
80A9F842 BUG_CHECK #019C
80A9F846 BUG_CHECK #019C
80A9F84A PUSHL R4
80A9F84C MOVL R5,R4
80A9F84F BEQL 00002C88
80A9F851 JSB @#-7FFFCC48
80A9F857 MOVL (SP)+,R4
80A9F85A RSB
80A9F85B BUG_CHECK #019C
PC->80A9F85F BUG_CHECK #019C => CLUSTRLOA + 09B6F
80A9F863 MOVL #00,R1
80A9F866 MOVB #01,R0
80A9F869 RSB
80A9F86A INCL 00002301
80A9F86E TSTW 000022FF
80A9F872 BLSS 00002CA5
CLUE_DISPLAY> SHOW CRASH 4
Time of system crash: 21-MAR-1996 15:21:33.72
Version of system: VAX/VMS VERSION V7.0
System Version Major ID/Minor ID: 1/0
VAXcluster node: HERMES, a VAX 6000-420
Crash CPU ID/Primary CPU ID: 03/01
Bitmask of CPUs active/available: 0000000A/0000000A
CPU bugcheck codes: CPU 03 INCONSTATE
1 other CPUEXIT
Current Process name: OPCOM
Current IPL: 8
CPU database address: 801AA000
General registers:
R0 = 80A9F85B R1 = 00000002 R2 = 80A15B08 R3 = 00010008
R4 = 80A15AD0 R5 = 00000000 R6 = 00000001 R7 = 00000042
R8 = 00022520 R9 = 00020F18 R10 = 00021000 R11 = 00020EC0
.
.
.
DECevent uses the system event log file, SYS$ERRORLOG:ERRLOG.SYS, as the default input file, unless another input file is specified.
The DECevent utility translates the contents of one or more event log files for inclusion into a report. DECevent generates five types of reports: full (default), brief, terse, summary, and FSTERR. These report types are mutually exclusive when selected within a command; no combinations are allowed.
DIAGNOSE/TRANSLATE [/qualifier(s)][file-spec[,...]]
/qualifier(s)
The function to be performed by the DIAGNOSE/TRANSLATE command.file-spec[,...]
Specifies one or more files that contain binary error information to be translated for the specified 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 OpenVMS System Manager's Manual for information on maintaining this file).See the OpenVMS User's Manual for details on file specifications.
To invoke DECevent, enter the following DCL command:DIAGNOSE [/qualifier(s)] [file-spec][,..]Note that typing the /TRANSLATE qualifier on the command line is not necessary because it is the default qualifier. DECevent does not prompt you. To exit from DECevent, press Ctrl/C and the Return key (to receive 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 qualifier to work, enabling the continuous display of events on a terminal screen. Do not use the /BINARY qualifier with any report type qualifier (/FULL, /BRIEF, /TERSE, /SUMMARY, and /FSTERR) or with the /OUTPUT qualifier.
| Qualifier | Description |
|---|---|
| /BEFORE | Specifies that only those entries dated earlier than the stated date and time are to be selected for the event report |
| /BINARY | Controls whether the binary error log records are converted to ASCII text or copied to the specified output file |
| /BRIEF | Generates a brief report |
| /CONTINUOUS | Specifies that events are formatted in real time, as they are logged by the operating system event logger |
| /DUMP | Specifies the output to be a brief report followed by a dump of information from the input event log file |
| /ENTRY | Generates a report that includes the specified entry range or starts at the specified entry number |
| /EXCLUDE | Excludes events generated by the specified device class, device name, or error log entry type from the report |
| /FSTERR | Generates a quick, one-line-per-entry report of an event log entry for disks and tapes |
| /FULL | Generates a full report (default), which provides all available information for an event log entry |
| /INCLUDE | Includes events generated by the specified device class, device name, or error log entry type in the report |
| /INTERACTIVE | Allows users to exit from the command line interface and enter the DECevent 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 |
| /NODE | Generates a report consisting of event entries for specific nodes in an OpenVMS Cluster system |
| /OUTPUT | Specifies the output file for the report |
| /REJECTED | Allows you to specify the name of a file that will contain binary records for rejected entries |
| /SINCE | Specifies that only those entries dated later than the stated date and time are to be selected for the report |
| /SUMMARY | Generates an event report that consists of a statistical summary |
| /TERSE | Generates an event report consisting of binary event information, register values, and ASCII messages in a condensed format |
| /TRANSLATE | Translates the contents of an event log file and is the default qualifier for the DIAGNOSE command verb |
In addition to the qualifiers listed in Table 9-1, the DECevent utility contains a set of DIRECTORY commands and a set of SHOW commands.
DIRECTORY commands allow a user to display a list of rulesets that DECevent requires for translating events into user-readable format.
The DIRECTORY commands currently implemented in DECevent are DIRECTORY EVENT and DIRECTORY CANONICAL.
The SHOW commands allow a user to view specific settings and selections. The SHOW commands currently implemented in DECevent are SHOW SELECT and SHOW SETTINGS. By appending a specific selection keyword name to the SHOW SELECT command, you view only that specific selection keyword. By appending a specific setting's name to the SHOW SETTINGS command, you view only that specific setting's name and value.
Specifies that only those entries dated earlier than the stated date and time are to be selected for the report.
/BEFORE [=date-time]
date-time
Limits the report to those entries dated earlier than the specified time.
You can specify an absolute time, a delta time, or a combination of absolute and delta times. See the OpenVMS User's Manual for details on specifying times.If you omit the /BEFORE qualifier or specify /BEFORE without a date or time, all entries are processed.
$ DIAGNOSE/TRANSLATE/BEFORE=19-APR-1996:10:00 ERRLOG.OLD;5
In this example, the full (default) report generated for ERRLOG.OLD;5 contains entries that were logged before 10:00 A.M. on April 19, 1996.
Controls whether the binary error log records are converted to ASCII text or copied to the specified output file.
/BINARY [=file-spec]
file-spec
Specifies the output file selected to contain image copies of the input records.
The /BINARY qualifier creates a binary file that contains copies of the original binary event 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 event 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 /BRIEF, /FSTERR, /FULL, /OUTPUT, /SUMMARY, or /TERSE qualifiers. These qualifiers generate an ASCII report; /BINARY generates a binary file.
$ DIAGNOSE/TRANSLATE/INCLUDE=DBA1/BINARY=DBA1_ERR.DAT ERRLOG.OLD;5
In this example, the output file DBA1_ERR.DAT contains image copies of the entries that apply to DBA1.
Generates a brief report.
/BRIEF
Do not use /BRIEF with the /BINARY qualifier.Example 9-2 shows the format of a typical brief error log report.
$ DIAGNOSE/TRANSLATE/BRIEF ERRLOG.OLD;97
In this example, the brief report generated from ERRLOG.OLD;97 contains minimal information.
Allows events to be displayed on a terminal screen, in real time, as the events are logged by the operating system's event logger.
/CONTINUOUS
The /CONTINUOUS qualifier specifies that events are formatted as they are logged by the operating system event logger in real time. No input file can be specified. The real-time output is directed to the terminal screen by default. You may redirect the real-time output to a file, specified with the /OUTPUT qualifier. Use the /BRIEF report type with the /CONTINUOUS qualifier.
$ DIAGNOSE/TRANSLATE/CONTINUOUS/BRIEF/OUTPUT=ERRLOG.CONT
In this example, the brief report containing real-time event logger information, generated from the default input event log file, SYS$ERRORLOG:ERRLOG.SYS, has been directed to the output file ERRLOG.CONT.
Allows a user to dump out criteria, selected by qualifiers, from the input event log file.
/DUMP
The /DUMP qualifier allows users to selectively dump information from the input event log file. The resulting output is a brief report type, followed by a dump of the canonical buffer for the input event.
$ DIAGNOSE/TRANSLATE/DUMP/INCLUDE=(RA90) ERRLOG.OLD;97/OUTPUT=97.OUT
In this example, the brief report generated from ERRLOG.OLD;97 contains information about RA90 disk drives. The report has been directed to the output file 97.OUT.
Generates a report that includes the specified entry range or starts at the specified entry number.
/ENTRY [=(START:decimal-value[,END:decimal-value])]
(START:decimal-value[,END:decimal-value])
Specifies the range of entries to be included in the report.
If you specify /ENTRY without the entry range or omit the qualifier, the entry range defaults to START:1,END:end-of-file.
$ DIAGNOSE/TRANSLATE/ENTRY=(START:1,END:18) ERRLOG.SYS
In this example, the entry range for the full (default) report generated from file ERRLOG.SYS is limited to entry numbers 1 to 18.
6048P018.HTM OSSG Documentation 26-NOV-1996 12:42:44.18
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.