| Document revision date: 19 July 1999 | |
![]() |
|
|
|
| Previous | Contents | Index |
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.
/[NO]LOG
$ ANALYZE/ERROR_LOG/LOG ERRLOG.OLD;5
|
In this example, informational messages generated about ERRLOG.OLD;5 are sent to SYS$OUTPUT.
On Alpha systems, generates a report consisting of event log entries that occurred on the specified CPU.
/MODEL= (hexadecimal-value[,...])
hexadecimal-value
Specifies a value obtained from the system console.In an OpenVMS Cluster environment, you can specify a hexadecimal value for each member. If you specify more than one hexadecimal value, you must specify a comma-separated list of values that is enclosed in parentheses.
$ ANALYZE/ERROR_LOG/MODEL=415 ERRLOG.SYS
|
In this example, the output consists of only those entries that were logged for the system with a model type of 00000415 (hexadecimal).
Generates a report consisting of error log entries for specific nodes in an OpenVMS Cluster system.
/NODE= (node-name[,...])
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.
$ ANALYZE/ERROR_LOG/NODE=(ORANGE,NASSAU) -
_$ SYS$SYSROOT:[SYS*.SYSERR]ERRLOG.SYS)
|
In this example, the OpenVMS Cluster system consists of members BROOME, NASSAU, ORANGE, and PUTNAM. The output contains only those entries that were logged for nodes NASSAU and ORANGE.
Specifies the output file for the error log report.
/OUTPUT [=file-spec]
file-spec
Specifies the output file selected for the error log report. Refer to the OpenVMS User's Manual for details on specifying files. If you omit the output file specification, output is directed to SYS$OUTPUT.
If you omit the /OUTPUT qualifier, output is directed to SYS$OUTPUT. 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.
$ 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.
Used in conjunction with the /INCLUDE qualifier to generate, in a hexadecimal longword format, a report that consists of device register information.
/REGISTER_DUMP
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.The /REGISTER_DUMP qualifier reports register contents for memory, device error, and device timeout entries. No translation is available of any of the device register information.
Do not use /REGISTER_DUMP with the /BINARY qualifier.
$ 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.
Allows you to specify the name of a file that will contain binary records for rejected entries.
/REJECTED [=file-spec]
file-spec
Specifies the name of the file that is to contain the rejected entries. If you do not specify an output file, the rejected entries are written to the file ERRLOG.REJ in your current directory.
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 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.
$ ANALYZE/ERROR_LOG/INCLUDE=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.
On VAX systems, generates a report consisting of error log entries that occurred on the specified CPU.
/SID_REGISTER= (hexadecimal-value[,...])
hexadecimal-value
Specifies a value obtained from the system ID register. Use the $GETSYI system service to obtain this value, which is unique to each system. The OpenVMS System Services Reference Manual describes the $GETSYI system service.In an OpenVMS Cluster environment, you can specify a hexadecimal value for each member. If you specify more than one hexadecimal value, you must specify a comma-separated list of values that is enclosed in parentheses.
$ ANALYZE/ERROR_LOG/SID_REGISTER=02006148 ERRLOG.OLD;72
|
In this example, the output consists of only those entries that were logged for the system with an ID of 02006148 (hexadecimal).
Specifies that only those entries dated later than the stated date and time are to be selected for the report.
/SINCE [=date-time]
date-time
Limits the error report to those entries dated later than the specified time. If you specify /SINCE without a date and time, the default is TODAY. If you omit the /SINCE qualifier, all entries are processed.
Only absolute date and time specifications are valid. Refer to the OpenVMS User's Manual for details on specifying times.
$ ANALYZE/ERROR_LOG/SINCE=19-APR-1998: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 April 19, 1998.
Generates run-time statistical information.
/STATISTICS
Use the /STATISTICS qualifier to generate a report that consists of the page faults, buffered I/O, direct I/O, and CPU time used in the execution of the ANALYZE/ERROR_LOG command.
$ 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.
10.4 ERROR LOG Examples
Sample Error Log Report
An error log report entry contains two sections: identification and device-dependent 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 about 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 I/O database at the time of the error.
The OpenVMS System Manager's Manual contains additional information about 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.
Error Log Report Generator Version 7.1
******************************* ENTRY 904. *******************************
ERROR SEQUENCE 709. LOGGED ON: CPU_TYPE 00000002
DATE/TIME 20-AUG-1998 15:21:10.79 SYS_TYPE 00000003
SYSTEM UPTIME: 1 DAYS 01:35:47
SCS NODE: LSR3 VAX/VMS V7.1
DEVICE ERROR SYS_TYPE = 03
RZ57 SUB-SYSTEM, UNIT _LSR3$DKA0:
HW REVISION 30303035
HW REVISION = 5000
ERROR TYPE 03
COMMAND TRANSMISSION FAILURE
SCSI ID 00
SCSI ID = 0.
SCSI LUN 00
SCSI LUN = 0.
SCSI SUBLUN 00
SCSI SUBLUN = 0.
PORT STATUS 00000054
%SYSTEM-F-CTRLERR, FATAL CONTROLLER
ERROR
SCSI CMD 00000000
0000
TEST UNIT RDY
SCSI STATUS FF
NO STATUS RECEIVED
UCB$B_ERTCNT 0F
15. RETRIES REMAINING
UCB$B_ERTMAX 00
0. RETRIES ALLOWABLE
ORB$L_OWNER 00000000
OWNER UIC [000,000]
UCB$L_CHAR 1CC54008
DIRECTORY STRUCTURED
FILE ORIENTED
SHARABLE
AVAILABLE
ERROR LOGGING
ALLOCATED
CAPABLE OF INPUT
CAPABLE OF OUTPUT
RANDOM ACCESS
UCB$L_STS 56544552
INTERRUPT EXPECTED
ONLINE
TIMED OUT
BUSY
DEALLOCATE AT DISMOUNT
"MOUNT VERIFICATION" IN-PROGRESS
UCB$L_OPCNT 00000000
0. QIO'S THIS UNIT
UCB$W_ERRCNT 0001
1. ERRORS THIS UNIT
Error Log Report Generator Version 7.1
IRP$L_BCNT 00000000
TRANSFER SIZE 0. BYTE(S)
IRP$L_BOFF 00000000
TRANSFER PAGE ALIGNED
IRP$L_PID 00010042
REQUESTOR "PID"
IRP$Q_IOSB 0000014E
430A0002 IOSB, 0. BYTE(S) TRANSFERRED
|
Time Stamp, Volume Mount, and Volume Dismount Entries Examples
The following examples show 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 I/O operations and error counts for the device.
The dismount volume entry contains, in addition to the data provided in the volume mount entry, the I/O operations and error counts for the device on which the volume was mounted.
**************************** ENTRY 93. ****************************
ERROR SEQUENCE 421. LOGGED ON SID 01380101
TIME STAMP, 4-MAR-98 11:10:08.79
KA780 REV# 7. SERIAL# 7.
**************************** ENTRY 94. ****************************
ERROR SEQUENCE 422. LOGGED ON SID 01380101
MOUNT VOLUME, 4-MAR-98 11:14:12.51
KA780 REV# 7. SERIAL# 7.
UNIT _DMA0:, VOLUME LABEL "TEST"
656. QIO OPERATIONS THIS UNIT, 1. ERRORS THIS UNIT
**************************** ENTRY 95. ****************************
ERROR SEQUENCE 423. LOGGED ON SID 01380101
DISMOUNT VOLUME, 4-MAR-98 11:14:41.30
KA780 REV# 7. SERIAL# 7.
UNIT _DMA0:, VOLUME LABEL "TEST"
697. QIO OPERATIONS THIS UNIT, 1. ERRORS THIS UNIT
41. QIO OPERATIONS THIS VOLUME, 0. ERRORS THIS VOLUME
|
Machine Check Entries Examples
The following examples show 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 2. *******************************
ERROR SEQUENCE 2. LOGGED ON: CPU_TYPE 00000002
DATE/TIME 4-SEP-1998 09:39:51.19 SYS_TYPE 00000002
SYSTEM UPTIME: 90 DAYS 00:01:25
SCS NODE: COBRA6 VAX/VMS V7.1
MACHINE CHECK SYS_TYPE = 02
KERNEL EVENT HEADER
FRAME REVISION 0000
SCB VECTOR 0670
1ST MOST PRB FRU 00
FIELD NOT VALID
2ND MOST PRB FRU 00
FIELD NOT VALID
SEVERITY 0000
FIELD NOT VALID
CPU ID 0000
ERROR COUNT 0001
THRESHOLD 0000
FAIL CODE 0000
ERR FIELD LOW 00000005
00000008
CPU_0 BUS COMMAND NO-ACK
CPU_O BUS READ PARITY ERROR
CPU CYCLE ABORTED WITH HARD ERROR
ERR FIELD HIGH 00000000
00000000
RETRY/BYTE CNT 00000250
00000000
BYTE COUNT = 00000250(X)
CAN'T RETRY
PALTEMP0 00000001
00000000
PALTEMP1 000000BE
00000000
PALTEMP2 00000004
001FC0F8
PALTEMP3 00000000
00000000
PALTEMP4 805C3FC0
FFFFFFFF
PALTEMP5 00000000
00000000
PALTEMP6 84FDE000
FFFFFFFF
PALTEMP7 00004200
00000000
PALTEMP8 00000400
00000000
PALTEMP9 00000003
00000000
PALTEMP10 29CB0233
00000003
PALTEMP11 00000000
00000000
PALTEMP12 00000001
Error Log Report Generator Version 7.1
00000000
PALTEMP13 8042F4C0
FFFFFFFF
PALTEMP14 00000000
00000000
PALTEMP15 00000000
00000000
PALTEMP16 0000C000
00000000
PALTEMP17 00000000
00000000
PALTEMP18 BEBC2000
00000000
PALTEMP19 7FFBF924
00000000
PALTEMP20 00002041
00000000
PALTEMP21 40000000
00000002
PALTEMP22 00000000
00000000
PALTEMP23 00000000
00000000
PALTEMP24 805C0000
FFFFFFFF
PALTEMP25 00000000
00000000
PALTEMP26 7FF96000
00000000
|
**************************** ENTRY 6. ****************************
ERROR SEQUENCE 3. LOGGED ON SID 03003700
MACHINE CHECK, 6-MAR-1998 10:11:34.70
KA730 REV# 0. MIC# 55.
EXCEPTION PC 80038DC0
ERROR PSL 01C00000
INTERRUPT PRIORITY LEVEL = 00.
PREVIOUS MODE = USER
CURRENT MODE = EXECUTIVE
SUMMARY CODE 00000007
UNCORRECTABLE ECC ERROR
1ST PARAMETER 00166200
PAGE #2865. IN ERROR
**************************** ENTRY 60. ****************************
ERROR SEQUENCE 4872. LOGGED ON SID 02006148
MACHINE CHECK, 6-MAR-1998 03:50:08.28
KA750 REV# 72. MIC# 97.
EXCEPTION PC 80006173
ERROR PSL 00C80009
C-BIT
N-BIT
INTERRUPT PRIORITY LEVEL = 08.
PREVIOUS MODE = USER
CURRENT MODE = KERNEL
SUMMARY CODE 00000002
TRANSLATION BUFFER OR BUS ERROR
VA LAST REF 800A079E
PC AT ERROR 80006178
MDR 8009F38C
SMR 00000008
CPU MODE = KERNEL
VIRTUAL
READ
RLTO 00000000
TBER 00000007
TB G0 DATA ERROR
TB G1 DATA ERROR
TB G0 TAG ERROR
CAER 00000000
BER 00000000
MCESR 00000004
OPERAND REFERENCE
TB PARITY ERROR
**************************** ENTRY 84. ****************************
ERROR SEQUENCE 4949. LOGGED ON SID 01388525
MACHINE CHECK, 6-MAR-1998 15:09:11.31
KA780 REV# 7. SERIAL# 1317.
EXCEPTION PC 00004890
ERROR PSL 03C00000
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 00000200
VA/VIBA 7FF735D4
D REGISTER FFFFC284
TBER0 0000DC81
ENABLE MEMORY MANAGEMENT
TB HIT GROUP 1
MICRO CODE "MCT" FIELD = 07
MICRO CODE "ADS"
MICRO CODE "FS"
TBER1 00000040
LAST TB WRITE PULSE TO GROUP 1
SBITA E00B83F5
TIMEOUT CONSOLE ADDR = 002E0FD4
PROTECTION CHECKED REFERENCE
TIMEOUT REFERENCE IN USER MODE
CACHE PE REG 00004000
CP ERROR
SBIER 00001802
SBI NOT BUSY
WAITING FOR READ DATA TIMEOUT
CPU TIMEOUT
|
| Previous | Next | Contents | Index |
|
| privacy and legal statement | ||
| 6048PRO_026.HTML | ||