DECevent Translation and Reporting Utility for OpenVMS User and Reference Guide Order Number: AA-Q73KD-TE Date: January 1997 DECevent Version V2.3 OpenVMS Alpha Version V6.2 or higher OpenVMS VAX Version V6.2 This manual is intended for users of the translation and re- porting features of the DECevent event management utility on OpenVMS[TM] operating systems. Digital Equipment Corporation Maynard, Massachusetts ________________________ 1997 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. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subpara- graph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Copyright © Digital Equipment Corporation 1997 Printed in the United States of America. All Rights Reserved. DEC, DECevent, DIGITAL UNIX, KDM70, OpenVMS, RA, RF, RZ, TA, VAX, VAXcluster, V and the DIGITAL logo are trademarks of Digital Equipment Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT Version 2.1. Contents PREFACE vii CHAPTER 1 DECEVENT EVENT MANAGEMENT UTILITY OVERVIEW 1-1 1.1 INTRODUCTION 1-1 1.2 DECEVENT AND THE TRANSLATION OF EVENTS 1-1 1.2.1 Necessary Privileges 1-2 1.3 DECEVENT ANALYSIS AND NOTIFICATION 1-2 1.4 THE DECEVENT GRAPHICAL USER INTERFACE 1-3 CHAPTER 2 THE HELP COMMAND 2-1 2.1 OVERVIEW 2-1 2.2 DECEVENT HELP 2-1 2.2.1 Exiting DECevent Help 2-2 2.3 VMS HELP 2-2 CHAPTER 3 THE DECEVENT BIT-TO-TEXT TRANSLATION FEATURE 3-1 3.1 INTRODUCTION 3-1 3.2 NECESSARY PRIVILEGES 3-1 3.3 COMMAND VERB 3-2 3.4 TRANSLATING EVENT FILES 3-2 3.4.1 Selecting an Alternate Input File 3-2 3.4.2 Translating Multiple Input Files 3-2 3.4.3 Using Wildcard Characters 3-3 3.4.4 Redirecting the Report to an Output File 3-3 3.4.5 Reversing the Order of Input Events 3-3 3.4.6 Creating a Binary Output File 3-3 3.5 FILTERING INPUT EVENTS 3-4 3.5.1 Filtering Events by Event Types 3-4 3.5.2 Filtering Events by Date and Time 3-4 3.5.3 Filtering Events by Entry Number 3-5 3.6 SELECTING ALTERNATIVE REPORTS 3-5 3.6.1 Producing a Full Report 3-6 3.6.2 Producing a Brief Report 3-8 3.6.3 Producing a Terse Report 3-9 3.6.4 Producing a Summary Report 3-10 3.6.5 Producing a FSTERR Report 3-11 3.7 TRANSLATING EVENTS AS THEY OCCUR 3-12 3.7.1 Halting the Continuous Display of Events 3-12 iii Contents CHAPTER 4 CUSTOMIZING YOUR ENVIRONMENT 4-1 4.1 COMMANDS TO CUSTOMIZE YOUR ENVIRONMENT 4-1 4.1.1 Customizing the Default Event Log File 4-1 4.1.2 Customizing the Locale Parameter 4-1 4.1.3 Saving Customized Settings 4-2 4.1.4 Restoring Customized Settings 4-2 4.1.4.1 Restoring Default System Settings 4-2 CHAPTER 5 THE DECEVENT DIAGNOSE COMMAND VERB 5-1 5.1 INTRODUCTION 5-1 5.1.1 The DIAGNOSE/TRANSLATE Command 5-1 5.1.1.1 Qualifiers and Parameters for the /TRANSLATE Qualifier 5-2 5.1.2 The DIAGNOSE/BINARY Command 5-2 5.1.2.1 Qualifiers and Parameters for the /BINARY Qualifier 5-3 5.1.3 The DIAGNOSE/CONTINUOUS Command 5-3 5.1.3.1 Qualifiers and Parameters for the /CONTINUOUS Qualifier 5-3 5.1.3.2 Halting Continuous Display Mode 5-4 5.1.4 The DIAGNOSE/DUMP Command 5-4 5.1.4.1 Qualifiers and Parameters for the /DUMP Qualifier 5-4 CHAPTER 6 THE DIAGNOSE/INTERACTIVE COMMAND 6-1 6.1 DESCRIPTION 6-1 6.1.1 Entering the Interactive Command Shell 6-1 6.1.2 Exiting Interactive Mode 6-2 6.1.3 Qualifiers and Parameters 6-2 6.1.4 Interactive Command Examples 6-2 6.2 SET COMMANDS 6-3 6.2.1 SET EVENT Command 6-3 6.2.2 SET LOCALE Command 6-4 6.2.3 RESTORE SETTINGS Command 6-4 6.2.4 SAVE SETTINGS Command 6-5 CHAPTER 7 THE DIRECTORY COMMANDS 7-1 7.1 DESCRIPTION 7-1 7.2 DIRECTORY COMMANDS 7-1 7.2.1 DIRECTORY EVENT Command 7-1 7.2.2 DIRECTORY CANONICAL Command 7-2 iv Contents CHAPTER 8 THE SHOW COMMANDS 8-1 8.1 DESCRIPTION 8-1 8.2 SHOW COMMANDS 8-1 8.2.1 SHOW SELECT Command 8-1 8.2.2 SHOW SELECT [select-name] Command 8-3 8.2.3 SHOW SETTINGS Command 8-4 8.2.4 SHOW SETTINGS [setting] Command 8-5 8.2.5 SHOW KNL Command 8-6 APPENDIX A DECEVENT DIRECTORIES AND FILES A-1 A.1 SYS$COMMON:[SYSEXE] A-1 A.2 SYS$COMMON:[SYSHELP] A-1 A.3 SYS$COMMON:[SYSLIB] A-1 A.4 DIA$LIBRARY A-1 A.5 SYS$LOGIN A-3 A.6 SYS$COMMON:[SYSMGR] A-4 APPENDIX B SYSTEM SETTINGS B-1 APPENDIX C BIT-TO-TEXT QUICK REFERENCE C-1 APPENDIX D DECEVENT QUALIFIERS AND PARAMETERS FOR BIT-TO-TEXT TRANSLATION D-1 D.1 /BRIEF QUALIFIER D-1 D.2 /ENTRY QUALIFIER D-2 D.3 /EXCLUDE QUALIFIER D-3 D.3.1 /EXCLUDE Keywords D-3 D.3.2 Combining /EXCLUDE and /INCLUDE Qualifiers D-6 D.4 /FSTERR QUALIFIER D-7 D.5 /FULL QUALIFIER D-7 D.6 /INCLUDE QUALIFIER D-10 D.6.1 /INCLUDE keywords D-10 D.6.2 Combining /INCLUDE and /EXCLUDE Qualifiers D-14 D.7 /LOG QUALIFIER D-14 D.8 /OUTPUT QUALIFIER D-14 D.9 /REVERSE QUALIFIER D-15 D.10 /NODE QUALIFIER D-15 v Contents D.11 /SINCE AND /BEFORE QUALIFIERS D-16 D.12 /SUMMARY QUALIFIER D-17 D.13 /TERSE QUALIFIER D-18 EXAMPLES 3-1 Full Report Format 3-7 3-2 Brief Report Format 3-8 3-3 Terse Report Format 3-9 3-4 Summary Report Format 3-10 3-5 FSTERR Report Format 3-11 7-1 Event Knowledge Library List 7-2 7-2 Canonical Knowledge Library List 7-4 8-1 Selection Information List 8-3 8-2 SHOW SELECT VOLUME_CHANGES Command Example 8-4 8-3 Current Setting Information 8-5 8-4 SHOW SETTING CURRENT_CLI Command Example 8-6 D-1 Brief Report Format D-1 D-2 FSTERR Report Format D-7 D-3 Full Report Format D-9 D-4 Summary Report Format D-17 D-5 Terse Report Format D-18 TABLES 1 Conventions vii 2 Associated Documents ix 3-1 Date and Time Code Definitions 3-5 3-2 Report Formats 3-6 6-1 SET, RESTORE, and SAVE Commands 6-3 7-1 DIRECTORY Commands 7-1 8-1 SHOW Commands 8-1 A-1 DECevent Independent Directory Files A-2 C-1 List of DECevent Commands and Qualifiers C-1 D-1 Date and Time Code Definitions D-16 vi ___________________________________________________________________ Preface The DECevent Translation and Reporting Utility for OpenVMS User and Reference Guide contains all DECevent command features re- lated to translating and reporting events on OpenVMS operating systems. Command Symbols Various symbols are used in command expressions to indicate what information is optional and when a value or parameter is required. Symbols such as brackets ([ ]) and parentheses () are used extensively. These symbols are used only for informa- tional purposes and should never be typed in the command line. In general, the command expressions use the symbols shown in Table 1. Table_1:_Conventions___________________________________________ Symbols_Purpose________________________________________________ { } In format command descriptions, braces indicate re- quired elements. You must include one of the elements. () In format descriptions, parentheses indicate that if you choose more than one option, you must enclose the choices in parentheses. [ ] In format descriptions, brackets indicate that what- ever is enclosed within the brackets is optional; you can select one, none, or all of the choices. (However, brackets are not optional in the syntax of a directory name, in a file specification, or in the syntax of a substring specification in an assignment statement.) [,...] When an ellipsis appears in square brackets, it means that multiple optional values, separated by commas, may be used. . . . Vertical ellipsis points indicate the omission of information from an example or command format. The in- formation has been omitted because it is not critical to the topic being discussed. italic Italic type emphasizes important information and in- type dicates variables, complete titles of manuals, and parameters for system information. vii Preface Table_1_(Cont.):_Conventions___________________________________ Symbols_Purpose________________________________________________ Ctrl/x Hold down the key labeled Ctrl (Control) and the spec- ________ified_key_simultaneously_(such_as_Ctrl/Z)._____________ viii Preface ___________________________________________________________________ Associated Documents The following documents are associated with the DECevent docu- mentation. Table_2:_Associated_Documents__________________________________ Document________________________Order_No.______________________ DECevent Event Management AA-Q73JD-TE Utility for OpenVMS Installation Guide DECevent Analysis and AA-Q73LD-TE Notification Utility for OpenVMS User and Reference Guide The DECevent Graphical User AA-QE26C-TE Interface User's Guide OpenVMS System Manager's AA-PV5MB-TK Manual: Essentials OpenVMS System Manager's AA-PV5NB-TK Manual: Tuning, Monitoring, and_Complex_Systems____________________________________________ ix Chapter 1 DECevent Event Management Utility Overview 1.1 Introduction The DECevent event management utility provides the inter- face between a user and the operating system's event logger. DECevent provides the following two main functions: o Translation-DECevent allows you to translate events into ASCII reports derived from system event entries (bit-to-text translations). o Analysis and Notification-DECevent constantly monitors sys- tem events in an effort to identify failing device com- ponents through analysis, and can notify the proper in- dividuals of a potential problem. Analysis and notifica- tion information can be found in the DECevent Analysis and Notification Utility for OpenVMS User and Reference Guide. An overview of these two main functions is contained in this chapter. 1.2 DECevent and the Translation of Events You can request the translation of events from specific event logs into a variety of ASCII reports. The format and contents of the ASCII reports are determined by commands, with quali- fiers, parameters, and selection keywords appended, entered on the command line interface (CLI). The maximum command line character limit allowed is 255 characters. DECevent translation has the following features: o Translating event log entries into readable reports o Selecting input and output sources DECevent Event Management Utility Overview 1-1 o Filtering and selecting input events o Selecting alternate reports o Translating events as they occur The user can also maintain and customize the user environment with the interactive shell commands. 1.2.1 Necessary Privileges OpenVMS system users need the SYSPRV privilege to access the system's event log file. Also, the DIAGNOSE privilege is re- quired to use the /CONTINUOUS qualifier. 1.3 DECevent Analysis and Notification The added value function of DECevent provides constant mon- itoring of a system's event logger. When a significant num- ber of events have occurred so that a DECevent threshold has been crossed, automatic analysis of the events is performed. Automatic analysis can result in the generation of DIGITAL spe- cific theory codes, which enables DIGITAL Multivendor Customer Services to identify one or more failing field replaceable units (FRU). Depending upon the theory codes generated from analysis, repair actions may be suggested. Also, depending upon the results of analysis, the proper individuals are notified of the event. The DECevent analysis and notification command options allow the following features: o Event analysis o Event notification o Customization of the DECevent environment In addition to automatic analysis and notification, DECevent allows you to perform manual analysis on a user-supplied event log. Manual analysis also results in the generation of DIGITAL- specific theory codes, which enables Multivendor Customer Services to determine a failing FRU. A product authorization key (PAK) license is required to enable both automatic and manual analysis. 1-2 DECevent Event Management Utility Overview NOTE A product authorization key (PAK) license is required in order to utilize the DECevent analysis and notifica- tion added-value options. The license is obtained by a DIGITAL Customer Services engineer through the techni- cal information management architecture (TIMA) and must be installed on your system prior to kit installation. To find the DECevent service PAK in TIMA, select the TIMA tools database and search for "DECEVENT PAK". The title of the tool you need is "Service Tools Product Authorization Key (PAK) Distribution Tool". Refer to TIMA documentation for specifics. In addition, customers may acquire the PAK information through DSNlink by requesting the PAK through DSNlink hardware support. You may also refer to the DSNlink for OpenVMS Users's Guide (AA-PBL4D-TE) for further information about DSNlink. Licenses are verified at run time by the License Management Facility (LMF). For more information on LMF concepts and operation, enter the HELP LICENSE command at the DCL ($) prompt. Refer to the DECevent Analysis and Notification Utility for OpenVMS User and Reference Guide for information on the analy- sis and notification features of DECevent. 1.4 The DECevent Graphical User Interface In addition to entering commands on the CLI, you have the op- tion of using the DECevent graphical user interface, (GUI) to perform translation and analysis. The DECevent Graphical User Interface User's Guide (AA-QE26A-TE) contains all the infor- mation necessary for you to use the GUI. Please note that this guide was originally produced for use on DIGITAL Unix operating systems. The commands, examples and results shown in the The DECevent Graphical User Interface User's Guide depict use on DIGITAL Unix systems. You must use OpenVMS commands to use the GUI on OpenVMS Alpha systems. DECevent Event Management Utility Overview 1-3 Chapter 2 The HELP Command 2.1 Overview Help is provided for DECevent commands both through an internal DECevent help utility and through the VMS help utility. 2.2 DECevent Help The DECevent HELP command provides you with help based on a topic string. If the help utility contains information for that topic string, the information is presented to you. If no infor- mation is available for that topic string, a warning message is displayed, and you are prompted to enter another topic string. Once help has been presented, you will be prompted to enter another topic string. Each help topic can have zero or more subtopics that provide more information on the main topic. Syntax Use the following syntax for the DECevent HELP command: $ DIAGNOSE HELP [ [/] help_req] The help_req Parameter The help_req parameter is a topic string for which help has been requested. Example $ DIAGNOSE HELP /BINARY This example provides help for the /BINARY qualifier. The HELP Command 2-1 2.2.1 Exiting DECevent Help There are three ways to exit from DECevent help. You can enter Ctrl/Z to exit help immediately, enter Ctrl/C followed by a carriage return, or type nothing at the Topic? prompt and enter several carriage returns until the system prompt reappears. 2.3 VMS Help Help for DECevent commands is also available through the VMS help utility. Type HELP at the system prompt, and respond to the Topic? prompt with DIAGNOSE. A DIAGNOSE Subtopic? prompt is then displayed. Respond to this prompt with /BINARY, for in- formation on the /BINARY qualifier, or with any valid DECevent help topic. Further subtopic prompts are displayed from which you can request more information related to any valid DECevent qualifier. 2-2 The HELP Command Chapter 3 The DECevent Bit-to-Text Translation Feature 3.1 Introduction The DECevent utility allows you to produce bit-to-text ASCII reports derived from system event entries or user supplied event logs. The format of the ASCII reports is determined by commands, with qualifiers, parameters, and selection keywords appended, entered on the command line interface (CLI). The maximum command line allowed is 255 characters. The DECevent bit-to-text feature has the following features: o Translating event log files into readable reports o Selecting input and output sources o Filtering input events o Selecting alternate reports o Translating events as they occur NOTE Refer to Appendix A for a list of DECevent utility di- rectories and files. 3.2 Necessary Privileges OpenVMS system users need the SYSPRV privilege to use the DECevent utility. Also, the DIAGNOSE privilege is required to use the /CONTINUOUS qualifier. The DECevent Bit-to-Text Translation Feature 3-1 3.3 Command Verb The DECevent utility command verb that allows the translation of system event entries is the following: $ DIAGNOSE/TRANSLATE The /TRANSLATE qualifier is the default translation qual- ifier and does not need to be entered on the command line. Simply entering DIAGNOSE performs the same function as typing DIAGNOSE/TRANSLATE on the command line. 3.4 Translating Event Files To produce a translated event report using the default system event log file, SYS$ERRORLOG:ERRLOG.SYS, enter the following command: $ DIAGNOSE The DIAGNOSE command allows DECevent to use built-in de- faults. This command produces a full report, directed to the terminal screen by default, from input event log file SYS$ERRORLOG:ERRLOG.SYS. The /TRANSLATE qualifier is understood on the command line and does not need to be entered. Refer to Example 3-1 for an example of a full report. 3.4.1 Selecting an Alternate Input File To select an alternate input file for translation other than the default system event log file, enter the following command: $ DIAGNOSE ERRORLOG.OLD In the above example, ERRORLOG.OLD has been selected as the alternate event log to be translated. The file name can contain directory or path specifications if needed. 3.4.2 Translating Multiple Input Files DECevent can translate multiple input files, as shown in the following example: $ DIAGNOSE/TRANSLATE ERRORLOG.SYS, MY_ERROR.SYS 3-2 The DECevent Bit-to-Text Translation Feature 3.4.3 Using Wildcard Characters You may use asterisks (*) as wildcard characters to specify multiple input files. For example, if you wish to translate all event log files located in the SYS$MANAGER, you could translate ERRLOG_1.SYS, ERRLOG_2.SYS, and ERRLOG_3.SYS with one file name, ERR*.SYS, as shown in the following example: $ DIAGNOSE/TRANSLATE SYS$MANAGER:ERR*.SYS You also may use wildcard characters to translate multiple event log files in multiple directories, as shown in the fol- lowing example: $ DIAGNOSE/TRANSLATE SYS$ERRORLOG:ERR*.SYS,SYS$MANAGER:ERR*.SYS 3.4.4 Redirecting the Report to an Output File To redirect the translated output to a file rather than to a terminal, enter the following command: $ DIAGNOSE/OUTPUT=ERRLOG_OLD.TXT In the above example, ERRLOG_OLD.TXT is the output text file into which the translated event information is written. 3.4.5 Reversing the Order of Input Events To reverse the order of the input event log file being read by the DECevent utility, use the following qualifiers: $ DIAGNOSE/TRANSLATE/REVERSE This command allows events to be displayed in reverse chrono- logical order, with the most recent events displayed first. The default is to display events in forward chronological or- der. Note that the output is presented in reverse order but the entry numbers in the report are 1-N. 3.4.6 Creating a Binary Output File This qualifier is used to create a smaller binary event log file from a larger log file using selection criteria. The following command creates a binary output file: $ DIAGNOSE/BINARY=ERROR_SUBLOG.BIN/INCLUDE=(DISK=RZ25) As shown, this command typically is used in conjunction with some selection criteria to select only those entries of inter- est. Only a file is created with this command; no text report output is generated. In the above example, the output file contains binary event entries related to the RZ25 disk drive. The DECevent Bit-to-Text Translation Feature 3-3 3.5 Filtering Input Events There are times when you do not want all the information con- tained in the input event log file. The /INCLUDE and /EXCLUDE qualifiers allow you to filter input event log files to tailor your event information. Refer to Appendix D for more informa- tion about the /INCLUDE and /EXCLUDE qualifiers. 3.5.1 Filtering Events by Event Types To include only certain event types in the output report, use the /INCLUDE qualifier: $ DIAGNOSE/TRANSLATE/INCLUDE=(DISK=RZ,DISK=RA92,CPU) In the above example, only the RZ[TM] disks, RA92[TM] disks, and CPU entries are output. To exclude certain event types in the output report, use the /EXCLUDE qualifier: $ DIAGNOSE/TRANSLATE/EXCLUDE=(MEMORY) In the above example, memory entries are excluded from the output report. Refer to Appendix D for more examples of how to use the /INCLUDE and /EXCLUDE qualifiers, and for information about combining the qualifiers. 3.5.2 Filtering Events by Date and Time Date and time qualifiers allow you to filter events by date and time occurrences. Use the /BEFORE and the /SINCE qualifiers to select events that occurred before or after a certain time, as shown in the following examples: $ DIAGNOSE/TRANSLATE/BEFORE=15-JAN-1993:10:30:00 or $ DIAGNOSE/TRANSLATE/SINCE=15-JAN-1993:10:30:00 These selection qualifiers can be combined to select a certain period of time as follows: $ DIAGNOSE/TRANSLATE/SINCE=15-JAN-1993/BEFORE=20-JAN-1993 If no value is supplied with the /SINCE or /BEFORE qualifiers, DECevent will default to TODAY. TODAY and YESTERDAY are ac- ceptable values and may be abbreviated to TOD and YES. /SINCE with no value displays todays entries. /BEFORE with no value displays all entries previous to today. TOMORROW is not a sup- ported keyword. 3-4 The DECevent Bit-to-Text Translation Feature The date and time value is specified in the following time format and defined in Table 3-1. DD-MMM-YYYY[:HH:MM:SS] Table_3-1:_Date_and_Time_Code_Definitions______________________ Time Code______Meaning________________Example_______________________ DD Day of month 01 MMM Month JAN YYYY Year 1995 HH Hours 06 MM Minutes 35 SS________Seconds________________08____________________________ 3.5.3 Filtering Events by Entry Number If the entry position within the event log file is known, a range of entries can be specified. In the following example, entries 20 through 60 inclusive are translated: $ DIAGNOSE/TRANSLATE/ENTRY=(START:20,END:60) The end parameter is optional. 3.6 Selecting Alternative Reports In the previous sections, the report type produced by the com- mands has been the full report type. This is the default report format and does not need to be specified on the command line. However, you can select other report types by typing one of the report types shown in Table 3-2 on the command line. Table 3-2 describes the different report type formats. These report types are mutually exclusive when selected within a command. No combinations are allowed. The DECevent Bit-to-Text Translation Feature 3-5 Table_3-2:_Report_Formats______________________________________ Report Type________Report_Description_________________________________ /FULL Provides translation of all available information for each entry in the event log. /BRIEF Provides translation of key information for each entry in the event log. /TERSE Provides binary event information and displays register values and other ASCII messages in a condensed format. /SUMMARY Provides a statistical summary of the event en- tries in the event log. /FSTERR Provides a one-line-per-entry report of an error ____________log_for_RA_disk_types._____________________________ 3.6.1 Producing a Full Report To produce a full report, use the /FULL qualifier. The /FULL qualifier provides a translation of all available information for each entry in the event log. The full report is the default report type and does not need to be typed on the command line. Both of the following commands will produce a full report from the default system event log file: $ DIAGNOSE/TRANSLATE/FULL $ DIAGNOSE Example 3-1 shows the format of a full report. Line two of a full report shows you the system architecture, Alpha or VAX. Line three of a full report shows you the operating system version number of your system. Reports for OpenVMS Alpha and reports for OpenVMS VAX will differ slightly. 3-6 The DECevent Bit-to-Text Translation Feature Example 3-1: Full Report Format ___________________________________________________________________ ********************** ENTRY 2 ******************************** Logging OS 1. OpenVMS System Architecture 2. Alpha OS version V7.0 Event sequence number 10. Timestamp of occurrence 16-MAY-1996 09:49:33 Time since reboot 0 Day(s) 0:10:44 Host name garcia System Model Entry type 0. Unknown Entry Type ---- Device Profile ---- Unit ATRGON$DKA300 Product Name RZ26 ---- UNKNOWN DEVICE ---- ----- Not Decoded ----- x00000000 ----- Software Info ----- UCB$x_ERTCNT 0. Retries Remaining UCB$x_ERTMAX 4. Retries Allowable IRP$Q_IOSB x4108000000000002 UCB$x_STS x4F475254 Error Logging In-Progress Online Timed Out Mount In-Progress Unload At Dismount "Mount Verification" In-Progress Delete this UCB when Reference Count reaches zero Volume is Valid on the local node Suppress "Success" Mount Verification Message Write-locked Mount Verification in progress Unit is busy via Alternate STARTIO path Restart Validation is in progress Unit cannot have channels assigned to it Unit supports the Extended Function bit VMS DC$_CLASS 1. VMS DT$_TYPE 93. IRP$L_PID x00010022 Requestor "PID" IRP$x_BOFF 272. Byte Page Offset IRP$x_BCNT 32768. Transfer Size In Byte(s) UCB$x_ERRCNT 1. Errors This Unit ___________________________________________________________________ Example 3-1 (continued on next page) The DECevent Bit-to-Text Translation Feature 3-7 Example 3-1 (Cont.): Full Report Format ___________________________________________________________________ UCB$L_OPCNT 4986. QIO's This Unit ORB$L_OWNER x08000011 Owners UIC UCB$L_DEVCHAR1 x1DCD4008 Directory Structured File Oriented Sharable Available Mounted Error Logging Allocated Foreign Capable of Input Capable of Output Random Access ___________________________________________________________________ 3.6.2 Producing a Brief Report To produce a brief report, use the /BRIEF qualifier. The /BRIEF qualifier provides translation of key information for each entry in the event log. The following command produces a brief report: $ DIAGNOSE/TRANSLATE/BRIEF Example 3-2 shows the format for a brief report. Line two of a brief report shows you the system architecture, Alpha or VAX. Line three of a brief report shows you the operating system version number of your system. Reports for OpenVMS Alpha and reports for OpenVMS VAX will differ slightly. Example 3-2: Brief Report Format ___________________________________________________________________ ********************** ENTRY 2 ******************************** Logging OS 1. OpenVMS System Architecture 2. Alpha OS version V7.0 Event sequence number 10. Timestamp of occurrence 16-MAY-1996 09:49:33 Host name garcia System Model ___________________________________________________________________ Example 3-2 (continued on next page) 3-8 The DECevent Bit-to-Text Translation Feature Example 3-2 (Cont.): Brief Report Format ___________________________________________________________________ ---- Device Profile ---- Unit ATRGON$DKA300 Product Name RZ26 ___________________________________________________________________ 3.6.3 Producing a Terse Report To produce a terse report, use the /TERSE qualifier. The /TERSE qualifier provides binary event information and displays regis- ter values and other ASCII messages in a condensed format. The following command produces a terse report: $ DIAGNOSE/TRANSLATE/TERSE Example 3-3 shows the format for a terse report. Example 3-3: Terse Report Format ___________________________________________________________________ ********************** ENTRY 2 ******************************** Logging OS 1. System Architecture 2. OS version V7.0 Event sequence number 10. Timestamp of occurrence 1992111609493300 Time since reboot 0 Day(s) 0:10:44 Host name garcia System Model Entry type 0. ---- Device Profile ---- Unit ATRGON$DKA300 Product Name RZ26 ___________________________________________________________________ Example 3-3 (continued on next page) The DECevent Bit-to-Text Translation Feature 3-9 Example 3-3 (Cont.): Terse Report Format ___________________________________________________________________ ---- UNKNOWN DEVICE ---- ----- Not Decoded ----- x00000000 ----- Software Info ----- UCB$x_ERTCNT 0. UCB$x_ERTMAX 4. IRP$Q_IOSB x0000000000000002 UCB$x_STS x4F475254 VMS DC$_CLASS 1. VMS DT$_TYPE 93. IRP$L_PID x00010022 IRP$x_BOFF 272. IRP$x_BCNT 32768. UCB$x_ERRCNT 1. UCB$L_OPCNT 4986. ORB$L_OWNER x08000011 UCB$L_DEVCHAR1 x1DCD4008 ___________________________________________________________________ 3.6.4 Producing a Summary Report To produce a summary report, use the /SUMMARY qualifier. The /SUMMARY qualifier provides a statistical summary of the event entries in the event log. The following command produces a summary report: $ DIAGNOSE/TRANSLATE/SUMMARY Example 3-4 shows the format for summary reports on several nodes. Example 3-4: Summary Report Format _______________________________________________________________ SUMMARY OF ALL ENTRIES LOGGED ON NODE garcia unknown major class Unrecognized Minor Class 2. SUMMARY OF ALL ENTRIES LOGGED ON NODE lesh unknown major class MSCP 1. SUMMARY OF ALL ENTRIES LOGGED ON NODE weir _______________________________________________________________ Example 3-4 (continued on next page) 3-10 The DECevent Bit-to-Text Translation Feature Example 3-4 (Cont.): Summary Report Format _______________________________________________________________ unknown major class MSCP 2. SUMMARY OF ALL ENTRIES LOGGED ON NODE hart unknown major class MSCP 1. SUMMARY OF ALL ENTRIES LOGGED ON NODE WELLNICK unknown major class MSCP 1. SUMMARY OF ALL ENTRIES LOGGED ON NODE KREUTZMAN unknown major class MSCP 2. CRD Entry 3. 660 Entry 1. _______________________________________________________________ 3.6.5 Producing a FSTERR Report To produce a FSTERR report, use the /FSTERR qualifier. The /FSTERR qualifier provides a one-line-per-entry report of your event log for a variety of disk and tape devices. The following command produces a FSTERR report: $ DIAGNOSE/TRANSLATE/FSTERR The /FSTERR report provides the base information for disk de- vices that the Multivendor Customer Services engineer needs for troubleshooting a problem with a disk device. Example 3-5 shows an example of an FSTERR report. Example 3-5: FSTERR Report Format ___________________________________________________________________ ___________________________________________________________________ Example 3-5 (continued on next page) The DECevent Bit-to-Text Translation Feature 3-11 Example 3-5 (Cont.): FSTERR Report Format ___________________________________________________________________ Drive/ MSCP Physical HSC Volume Drive Name yymmdd hhmmss Entry Evnt LED LBN Cyl Hd Sec RA RP Serial =========== ============= ===== ==== === === ==== == === === == ====== RUBY6$DUA022 921112 150138 62 01AB 92 00 D19295 PMASON$DUA006 921207 165009 63 00EB 7C 236 2 90 42 D23387 PMASON$DUA006 921207 165011 64 00EB 7C 236 2 90 42 D23387 PMASON$DUA006 921207 165050 65 00EB 1C 55 11 90 42 D23387 PMASON$DUA006 921207 165052 66 00EB 12 55 11 90 42 D23387 ___________________________________________________________________ 3.7 Translating Events as They Occur Events can be translated as they occur. The /CONTINUOUS quali- fier provides this capability. The /CONTINUOUS qualifier sets up the operating system's event logging facility as the input to the DECevent utility. This enables you to see the translated events immediately on the terminal, or place translated events into an output file. NOTE You need the DIAGNOSE privilege to use the /CONTINUOUS qualifier. To monitor real time events, enter the following command: $ DIAGNOSE/CONTINUOUS In order to produce concise reports in real time, DIGITAL recommends that you use the /BRIEF report qualifier with the /CONTINUOUS qualifier. 3.7.1 Halting the Continuous Display of Events To halt the continuous display of events as they are occur, enter CTRL/Y. This stops the display and the system prompt ap- pears on the screen. At the system prompt, enter STOP followed by a carriage return (). 3-12 The DECevent Bit-to-Text Translation Feature Chapter 4 Customizing Your Environment 4.1 Commands to Customize Your Environment You can customize your system environment from within the in- teractive command shell. The customized settings must be saved before exiting the interactive command shell. 4.1.1 Customizing the Default Event Log File To set the event log file to a file other than the default file, enter the following command: DIA> SET EVENT WORK3:[ERROR]ERROR_LOG.OLD In this example, ERROR_LOG.OLD replaces the default event log file for translation. 4.1.2 Customizing the Locale Parameter The locale file determines the natural language used when DECevent returns error messages. To set the default locale file pointer in the DECevent utility, enter the following command: DIA> SET LOCALE AMERICAN_ENGLISH NOTE Only the American_English locale file is currently sup- ported by DECevent. Customizing Your Environment 4-1 4.1.3 Saving Customized Settings To save your custom settings, enter the following command: DIA> SAVE SETTINGS NOTE You must save the customized settings before exiting the interactive command shell or the system default settings become valid again. This command changes the knowledge library file (KNL) located in your SYS$LOGIN directory. 4.1.4 Restoring Customized Settings To restore the last saved customized settings in the DECevent utility, enter the following command: DIA> RESTORE SETTINGS This uses the settings in your local settings file SYS$LOGIN:FMG_ LOCAL_PARAM_LIBRARY.KNL 4.1.4.1 Restoring Default System Settings To restore default system settings in the DECevent utility, enter the following command: DIA> RESTORE SYSTEM SETTINGS This restores the settings in DIA$LIBRARY:FMG_GLOBAL_PARAM_ LIBRARY.KNL. Refer to Appendix B for a list of all default system settings. 4-2 Customizing Your Environment Chapter 5 The DECevent DIAGNOSE Command Verb 5.1 Introduction The main DECevent command verb that allows the translation of an event log file is DIAGNOSE. DECevent allows you to append four main qualifiers to the DIAGNOSE command verb, each accom- plishing different functions on an input event log file. The following are the four main qualifiers: o /TRANSLATE-Allows the translation of events into a report. This is the default qualifier. o /BINARY-Allows smaller binary event log files to be created from larger event log files. file. o /CONTINUOUS-Allows events to be formatted as they are logged by the operating system event logger. o /DUMP-Allows the canonical format of events to be output in hexidecimal dump format. Each main qualifier is discussed in this chapter. 5.1.1 The DIAGNOSE/TRANSLATE Command The DIAGNOSE/TRANSLATE command allows you to use the default system event log file or to choose another event log file for translation and reporting. The DIAGNOSE command always defaults to the /TRANSLATE qualifier if no qualifier is specified. The DIAGNOSE/TRANSLATE command is the equivalent of the DIAGNOSE command. Use the following syntax for the DIAGNOSE/TRANSLATE command: DIAGNOSE/TRANSLATE [/qualifier][...] [infile[,...]] The DECevent DIAGNOSE Command Verb 5-1 5.1.1.1 Qualifiers and Parameters for the /TRANSLATE Qualifier The following list presents the valid qualifiers and parameters for the DIAGNOSE/TRANSLATE command. Refer to Appendix D for descriptions and examples of the qualifiers and parameters. [infile [,...]] [/BRIEF] [/ENTRY=(START:start[,END:end])] [/EXCLUDE=(keyword[=val][,...])] [/FSTERR] [/FULL] [/INCLUDE=(keyword[=val][,...])] [/[NO]LOG] [/OUTPUT=output_file] [/REVERSE] [/NODE=node_name[,...]] [/SINCE=time][/BEFORE=time] [/SUMMARY] [/TERSE] The [infile] Parameter The DIAGNOSE/TRANSLATE command allows you to use the optional [infile] parameter. This allows you to choose one or more al- ternative input event log files for translation. Reporting is done in sequential order. If you do not supply a file name for this parameter, the default file is used. The default file is defined as either the default system event log file for each operating system, or a file specified using the SET EVENT command. The default system event log file on an OpenVMS operating sys- tem is SYS$ERRORLOG:ERRLOG.SYS. 5.1.2 The DIAGNOSE/BINARY Command The DIAGNOSE/BINARY command allows you to copy all or part of an input event log file into a binary output file. This command is typically used in conjunction with the /INCLUDE or /EXCLUDE qualifiers and selection keywords to select only those entries that are of interest. The binary output file contains all event entries meeting the selection criteria. Use the following syntax for the DIAGNOSE/BINARY command: DIAGNOSE/BINARY=bin_outputfile.BIN [/qualifier][...][infile[,...]] 5-2 The DECevent DIAGNOSE Command Verb 5.1.2.1 Qualifiers and Parameters for the /BINARY Qualifier The following list presents the valid qualifiers and parame- ters for the DIAGNOSE/BINARY command. Refer to Appendix D for descriptions and examples of the qualifiers and parameters. [infile[,...]] [/ENTRY=(START:start[,END:end])] [/EXCLUDE=(keyword[=val][,...])] [/INCLUDE=(keyword[=val][,...])] [/[NO]LOG] [/NODE=(node_name[,...])] [/REJECTED[=rej_file]] [/REVERSE] [/SINCE=time][/BEFORE=time] The bin_outputfile Parameter The DIAGNOSE/BINARY command creates a binary output file using the bin_outputfile parameter. You must supply a name for the binary output file with the .BIN extension as shown in the DIAGNOSE/BINARY example in section Section 5.1.2. 5.1.3 The DIAGNOSE/CONTINUOUS Command The DIAGNOSE/CONTINUOUS command specifies that events are to be translated as they are logged by the operating system event logger, therefore no input file is specified. The output goes to the terminal by default. You may redirect the output to a file. It is recommended that you use the brief report type with the /CONTINUOUS qualifier. Use the following syntax for the DIAGNOSE/CONTINUOUS command: DIAGNOSE/CONTINUOUS [/qualifier [...]] NOTE You need the DIAGNOSE privilege to use the /CONTINUOUS qualifier. 5.1.3.1 Qualifiers and Parameters for the /CONTINUOUS Qualifier The following list presents valid qualifiers and parameters for the DIAGNOSE/CONTINUOUS command. Refer to Appendix D for descriptions and examples of the qualifiers and parameters. [/BRIEF] [/EXCLUDE=(keyword[=val][,...])] [/FSTERR] [/FULL] [/INCLUDE=(keyword[=val][,...])] The DECevent DIAGNOSE Command Verb 5-3 [/OUTPUT=output_file] [/TERSE] 5.1.3.2 Halting Continuous Display Mode To halt the continuous display of events as they occur, enter Ctrl/Y. This stops the display and the system prompt appears on the screen. At the system prompt, enter STOP followed by a carriage return (). 5.1.4 The DIAGNOSE/DUMP Command The DIAGNOSE/DUMP command allows you to dump out selected events, dictated by qualifiers, from the input event log file. The resulting output is a brief report type output, followed by a generic dump for each event. Use the following syntax for the DIAGNOSE/DUMP command: DIAGNOSE/DUMP [/qualifier [...] [infile[,...]] 5.1.4.1 Qualifiers and Parameters for the /DUMP Qualifier The following list presents valid qualifiers and parameters for the DIAGNOSE/DUMP command. Refer to Appendix D for descriptions and examples of the qualifiers and parameters. [infile[,...]] [/ENTRY=(START:start[,END:end])] [/EXCLUDE=(keyword[=val][,...])] [/INCLUDE=(keyword[=val][,...])] [/[NO]LOG] [/OUTPUT=output_file] [/NODE=(node_name[,...])] [/REVERSE] [/SINCE=time][/BEFORE=time] The [infile] Parameter The DIAGNOSE/DUMP command allows you to use the optional [in- file] parameter. This allows you to choose one or more alterna- tive input event log files for translation. Separate multiple input event log files with a comma. If you do not supply a file name for this parameter, the default file is used. The default file is defined as either the default system event log file for each operating system, or a file specified using the SET EVENT command. The default system event log file on an OpenVMS operating sys- tem is SYS$ERRORLOG:ERRLOG.SYS. 5-4 The DECevent DIAGNOSE Command Verb Chapter 6 The DIAGNOSE/INTERACTIVE Command 6.1 Description The DIAGNOSE/INTERACTIVE command allows you to enter the DECevent interactive command shell. When you are in the DECevent interactive command shell, the DIA> prompt is dis- played on the screen. NOTE All commands valid from the CLI are also valid from the interactive command shell without first entering the DIAGNOSE command verb. Some commands, such as the SET commands, are only valid from within the interactive command shell and may not be entered on the CLI. SET commands are documented in this chapter because they are only valid from within the interactive command shell. 6.1.1 Entering the Interactive Command Shell To enter the interactive command shell from an OpenVMS system, at the system prompt type: $ DIAGNOSE/INTERACTIVE The DECevent interactive command shell prompt, DIA>, appears. The format for entering a command at the DIA> prompt is the following: DIA> AAA XXXX YYYY Where: AAA is a valid DECevent interactive command shell command. XXXX is the specific subject the command applies to. YYYY is the parameter associated with the command. The DIAGNOSE/INTERACTIVE Command 6-1 For example: DIA> SET LOCALE AMERICAN_ENGLISH 6.1.2 Exiting Interactive Mode To exit from the interactive command shell, at the DIA> prompt type EXIT, followed by a carriage (). 6.1.3 Qualifiers and Parameters Although there are no specific qualifiers or parameters for the DIAGNOSE/INTERACTIVE command, all commands that are valid from the CLI are also valid from within the interactive command shell. 6.1.4 Interactive Command Examples The following examples show how to enter the interactive com- mand shell, how to issue a command from within the interactive command shell, and how to exit the interactive command shell. Example: Entering the Interactive Command Shell To enter the interactive command shell, enter the following command at the system prompt: $ DIAGNOSE/INTERACTIVE The DECevent interactive command shell prompt, DIA>, appears. Example: Issuing a Command from the Interactive Command Shell The following shows how to issue a SET command from the DECevent interactive (DIA>) prompt: DIA> SET LOCALE AMERICAN_ENGLISH In the previous example, the SET LOCALE command was issued from within the interactive command shell prompt. This command is described in detail in Section 6.2.2. Example: Exiting the Interactive Command Shell To exit the interactive command shell, enter the following command at the interactive (DIA>) prompt: DIA> EXIT 6-2 The DIAGNOSE/INTERACTIVE Command 6.2 SET Commands SET commands work only from within the interactive command shell, and therefore, are described in this chapter. The SET commands allow you to customize, change, or save system set- tings. Refer to Section 8.2.3 for information about how to display settings using the SHOW SETTINGS command. Refer to Appendix B for a list of DECevent system settings. Table 6-1 lists each SET command, as well as commands related to the SET commands. Table_6-1:_SET,_RESTORE,_and_SAVE_Commands_____________________ Command_________________Action_________________________________ SET EVENT file Allows you to define the default event log file from which event reports are formatted. SET LOCALE location Allows you to change the locale file for internationalization reasons. RESTORE SETTINGS Allows you to cancel customizations previously set in the customer local settings file and restores to the last saved settings. SAVE SETTINGS Allows you to store the current cus- ________________________tomization_settings_in_a_default_file._ 6.2.1 SET EVENT Command The SET EVENT command allows you to define an event log file from which event reports are formatted. This allows you, in the interactive command shell, to use an event log file other than the default system event log file without specifying the file name on all subsequent commands. Before exiting the interactive command shell, you must save this setting or system default settings become valid once again. DECevent supports defined logical names of event log files. Syntax Use the following syntax for the SET EVENT command: SET EVENT file The DIAGNOSE/INTERACTIVE Command 6-3 The file Parameter The file parameter is the name of an event log file used for translation. You must enter a full file specification file name with this command. Example The following is an example of the SET EVENT command: DIA> SET EVENT GARCIA$ERRLOG.OLD 6.2.2 SET LOCALE Command The SET LOCALE command allows you to override the locale file previously set for the current system. This is done for inter- nationalization reasons so natural language conventions can be added in the future. NOTE DECevent currently supports only the AMERICAN_ENGLISH locale file. However, the following information de- scribes how to change locale files. Syntax Use the following syntax for the SET LOCALE command: SET LOCALE location The location Parameter The location parameter is a string defining the location of the user in terms of the locale preferences available. An example is AMERICAN_ENGLISH. You must provide a location parameter with this command. Example The following is an example of the SET LOCALE command: DIA> SET LOCALE AMERICAN_ENGLISH 6.2.3 RESTORE SETTINGS Command The RESTORE SETTINGS command allows you to restore previous settings in the local customization file. This command cancels customizations set since the last time the local customization file was saved. 6-4 The DIAGNOSE/INTERACTIVE Command Syntax Use the following syntax for the RESTORE SETTINGS command: RESTORE SETTINGS Example The following is an example of the RESTORE SETTINGS command: DIA> RESTORE SETTINGS 6.2.4 SAVE SETTINGS Command The SAVE SETTINGS command allows you to store the current local customization settings in a default file. DECevent then uses these defaults in subsequent interactive sessions. Syntax Use the following syntax for the SAVE SETTINGS command: DIA> SAVE SETTINGS Example The following is an example of the SAVE SETTINGS command: DIA> SAVE SETTINGS The DIAGNOSE/INTERACTIVE Command 6-5 Chapter 7 The DIRECTORY Commands 7.1 Description The DIRECTORY commands allow you to display all requested rulesets listed in a knowledge library. Rulesets contain in- structions necessary for the translation of events. A knowledge library contains rulesets. 7.2 DIRECTORY Commands Table 7-1 lists each DECevent DIRECTORY command. Table_7-1:_DIRECTORY_Commands__________________________________ Command____________________Action______________________________ DIRECTORY EVENT Lists all event rulesets. DIRECTORY_CANONICAL________Lists_all_canonical_rulesets._______ 7.2.1 DIRECTORY EVENT Command The DECevent DIRECTORY EVENT command lists all event rulesets contained in DIA$LIBRARY:FMG_ETC__DEF_RULE_LIB.KNL. Syntax Use the following syntax for the DIRECTORY EVENT command: DIAGNOSE DIRECTORY EVENT This command provides a directory listing of the Event Knowledge Library shown in Example 7-1. The DIRECTORY Commands 7-1 Example 7-1: Event Knowledge Library List ___________________________________________________________________ Knowledge Library: Ruleset Name Path ================================================================= ARCHCTRL ROOT AXP_EV ROOT BUGCHECK_EV ROOT MSCP_EV ROOT VMS_CLASSIFY_DEVICE ROOT HEADER_EV ROOT DEVERR_ATTEN_TIMEO ROOT MEMORY_EV ROOT PWR_EV ROOT SCSI2_CTRLATTEN ROOT SCSI2_DEVERR ROOT SWI_EV ROOT UTIL ROOT . . . DEC_7000_SUBPKT_LMA_EV ROOT.AXP_EV.DEC_7000_EV.DEC_7000_SUBPKTS_EV DEC_7000_SUBPKT_LOG_ADAP_ROOT.AXP_EV.DEC_7000_EV.DEC_7000_SUBPKTS_EV DEC_7000_SUBPKT_XMI_EV ROOT.AXP_EV.DEC_7000_EV.DEC_7000_SUBPKTS_EV . . . DEC_3000_SPEC_EV ROOT.AXP_EV.DEC_3000_EV SCSI2_DISP ROOT.ARCHCTRL UNKNOWN_DEV_ERR_TIM_ATT ROOT.ARCHCTRL XMI_DISP ROOT.ARCHCTRL ___________________________________________________________________ 7.2.2 DIRECTORY CANONICAL Command The DECevent DIRECTORY CANONICAL command allows you to list all canonical rulesets contained in DIA$LIBRARY:FMG_RPT__DEF_RULE_ LIB.KNL. 7-2 The DIRECTORY Commands Syntax Use the following syntax for the DIRECTORY CANONICAL command: DIAGNOSE DIRECTORY CANONICAL This command provides a listing of the knowledge library shown in Example 7-2. The DIRECTORY Commands 7-3 Example 7-2: Canonical Knowledge Library List ___________________________________________________________________ Knowledge Library: Ruleset Name Path ===================================================================== HEADER_CA ROOT MSCP_CA ROOT DUMP_EVENT_CA ROOT DUMP_VECTOR_CA ROOT IO_SCSI2_DEV ROOT IO_SCSI2_CTRL ROOT IO_SCSI2_SW ROOT N53C710_SCSI ROOT.IO_SCSI2_CTRL N53C94 ROOT.IO_SCSI2_CTRL HSZ10_ASC_ASCQ ROOT.IO_SCSI2_DEV CTLR_ID ROOT.MSCP_CA LM_FMT_DISP ROOT.MSCP_CA UNIT_ID ROOT.MSCP_CA MSCP_CTLR_DEP ROOT.MSCP_CA MEDIA_LDR_ID ROOT.MSCP_CA MSCP_DEV_DEP ROOT.MSCP_CA MSCP_LW_HEX_DUMP ROOT.MSCP_CA MSLG_LBN_DECODER ROOT.MSCP_CA SSP_310 ROOT.MSCP_CA RA72_LBN_DECODE ROOT.MSCP_CA.MSLG_LBN_DECODER RA73_LBN_DECODE ROOT.MSCP_CA.MSLG_LBN_DECODER RA90_LBN_DECODE ROOT.MSCP_CA.MSLG_LBN_DECODER RA92_LBN_DECODE ROOT.MSCP_CA.MSLG_LBN_DECODER RF35_LBN_DECODE ROOT.MSCP_CA.MSLG_LBN_DECODER RF73_LBN_DECODE ROOT.MSCP_CA.MSLG_LBN_DECODER RA72_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP RA73_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP RA7X_COMMON_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP RA90_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP RA92_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP RA9X_COMMON_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP TA78_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP TA79_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP TA7X_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP TA81X_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP TA81_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP TA90E_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP TA90_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP TA91_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP TA9X_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP ___________________________________________________________________ Example 7-2 (continued on next page) 7-4 The DIRECTORY Commands Example 7-2 (Cont.): Canonical Knowledge Library List ___________________________________________________________________ TF857_DEV_DEP ROOT.MSCP_CA.MSCP_DEV_DEP TA9X_SENSE_DATA ROOT.MSCP_CA.MSCP_DEV_DEP.TA9X_DEV_DEP TA857_MEDIA_LDR_ID ROOT.MSCP_CA.MEDIA_LDR_ID TA867_MEDIA_LDR_ID ROOT.MSCP_CA.MEDIA_LDR_ID TAD85_MEDIA_LDR_ID ROOT.MSCP_CA.MEDIA_LDR_ID TAD86_MEDIA_LDR_ID ROOT.MSCP_CA.MEDIA_LDR_ID ___________________________________________________________________ The DIRECTORY Commands 7-5 Chapter 8 The SHOW Commands 8.1 Description The SHOW commands allow you to view a specific DECevent onfor- mation. 8.2 SHOW Commands Table 8-1 lists each DECevent SHOW command. Table_8-1:_SHOW_Commands_______________________________________ Command____________________Action______________________________ SHOW SELECT Shows all keywords associated with selection information for the /INCLUDE and /EXCLUDE qualifiers. SHOW SELECT [select-name] Shows only the single entry for the select-name chosen. SHOW SETTINGS Shows all possible settings. SHOW SETTINGS [setting] Shows only the single entry for the setting chosen. SHOW KNL Shows the version information for the data contained in each knowl- ___________________________edge_library_file.__________________ 8.2.1 SHOW SELECT Command The DECevent SHOW SELECT command shows all keywords associ- ated with selection information for the /INCLUDE and /EXCLUDE qualifiers. The information is contained in DIA$LIBRARY:FMG_ ETC__DEF_SEL_LIB.KNL. The SHOW Commands 8-1 Syntax Use the following syntax for the SHOW SELECT command: DIAGNOSE SHOW SELECT Example The following is an example of the SHOW SELECT command: $ DIAGNOSE SHOW SELECT This SHOW SELECT command gives a list of selection information similar to the one in Example 8-1. 8-2 The SHOW Commands Example 8-1: Selection Information List _______________________________________________________________ Selection Information: Key Item-Name Value =============================================================== ATTENTIONS DEF_SEL__ATTENTION BUGCHECKS CA_EVT_BC_MINOR_CLASS BUSES DEF_SEL__BUS CACHE CA_EVT_CPU_MINOR_CLASS 4 CONFIGURATIONS CA_EVT_SWI_MINOR_CLASS 3 CONTROL_ENTRIES CA_EVT_CONTROL_CLASS CPUS CA_EVT_CPU_MINOR_CLASS DATES CA_HD_GEN_X__EVENT_TIME DEVICE_ERRORS DEF_SEL__DEVICE_ERROR . . . MCHKS CA_EVT_CPU_MINOR_CLASS 1 MACHINE_CHECKS CA_EVT_CPU_MINOR_CLASS 1 MEMORY CA_EVT_MEM_MINOR_CLASS NODES CA_HD_GEN_T__SCS_NAME OS CA_HD_GEN_B__FM_OS_ID_CODE OPERATING_SYSTEMS CA_HD_GEN_B__FM_OS_ID_CODE PWR CA_EVT_PWR_MINOR_CLASS POWER CA_EVT_PWR_MINOR_CLASS SEQUENCE_NUMBERS CA_HD_GEN_W__ERRSEQ SWI CA_EVT_SWI_MINOR_CLASS SOFTWARE_INFORMATIONALS CA_EVT_SWI_MINOR_CLASS SYNC_COMMUNICATIONS DEF_SEL__SYNC_COMM TAPES DEF_SEL__TAPE TIMEOUTS DEF_SEL__TIMEOUT UNKNOWN_ENTRIES DEF_SEL__UNKNOWN UNSOLICITED_MSCP DEF_SEL__UNSOLICITED_MSCP_MSG VMS_ENTRY CA_HD_EVT_W__VMS_ENTRY VOLUME_CHANGES CA_EVT_VOLUME_CLASS _______________________________________________________________ 8.2.2 SHOW SELECT [select-name] Command When the SHOW SELECT command is issued with a [select-name] parameter, the command shows only the single entry for the [select-name] chosen. The [select-name] must be spelled out in full and must be a valid selection type. The SHOW Commands 8-3 Syntax Use the following syntax for the SHOW SELECT command: DIAGNOSE SHOW SELECT [select-name] The [select-name] Parameter The select-name parameter must be one of the selection types displayed when the SHOW SELECT command is issued. Example The following is an example of the SHOW SELECT command with a specific [select-name] parameter: $ DIAGNOSE SHOW SELECT VOLUME_CHANGES Abbreviation of the [select-name] parameter is not allowed. This SHOW SELECT command gives the message shown in Example 8-2. Example 8-2: SHOW SELECT VOLUME_CHANGES Command Example _______________________________________________________________ Selection Information: Key Item-Name Value ============================================================= VOLUME_CHANGES CA_EVT_VOLUME_CLASS _______________________________________________________________ 8.2.3 SHOW SETTINGS Command The DECevent SHOW SETTINGS command shows all parameters and their current settings. Syntax Use the following syntax for the SHOW SETTINGS command: DIAGNOSE SHOW SETTINGS 8-4 The SHOW Commands Example 8-3: Current Setting Information _______________________________________________________________ Current Settings Information: Name Value ========================================================= ANA_TRACE 0 CMD_TRACE 0 CTR__DMP_RUL ROOT.DUMP_EVENT_CA CTR__RUL_LIB CTR__DEF_RUL_LIB CTR__SUM_LIB CTR__DEF_SUM_LIB CTR_TRACE 0 CURRENT_CLI VMS DEF_CTR_RULE ROOT.HEADER_CA DEF_ETC_RULE ROOT.HEADER_EV DEF_EVT_LOG SYS$ERRORLOG:ERRLOG.SYS DEFAULT_REPORT FULL_RE ETC_TRACE 0 . . . RPT__RUL_LIB RPT__DEF_RUL_LIB RULE_MAX_BYTECNT 100000 STREAM_SIZE 20 SYS_ACT_LOG_NAME ERT_ACTIVITY.LOG FMG_VERSION 2.0 NOT__DEF_CSC_PHONE SICL_STATE OFF SICL_PROTOCOL_VERS 1 NOT__RUL_LIB NOT__DEF_RUL_LIB NOT__MAIL_LIB NOT__DEF_MAIL_LIB _______________________________________________________________ Example The following is an example of the SHOW SETTINGS command: $ DIAGNOSE SHOW SETTINGS This command results in the message shown in Example 8-3. 8.2.4 SHOW SETTINGS [setting] Command When the SHOW SETTINGS command is issued with a [setting] pa- rameter, the command displays only the single entry for the [setting] chosen. The SHOW Commands 8-5 Syntax Use the following syntax for the SHOW SETTING [setting] com- mand: DIAGNOSE SHOW SETTINGS [setting] The [setting] Parameter The [setting] parameter must be one of the valid settings dis- played when the SHOW SETTINGS command is issued. Example The following is an example of the SHOW SETTINGS [setting] command: $ DIAGNOSE SHOW SETTINGS CURRENT_CLI This command displays the message shown in Example 8-4. Example 8-4: SHOW SETTING CURRENT_CLI Command Example _______________________________________________________________ Current Settings Information: Name Value ============================================================ CURRENT_CLI VMS _______________________________________________________________ 8.2.5 SHOW KNL Command The DECevent SHOW KNL command shows versioning information for each knowledge library file. This information determines the version information for the device support contained in each KNL file. Syntax Use the following syntax for the SHOW KNL command: SHOW KNL 8-6 The SHOW Commands Example The following is an example of the SHOW KNL command: $ SHOW KNL The output from the SHOW KNL command is as follows: Knowledge File Information File name Version Build Date Platform ===================================================================== FMG_AMERICAN_ENGLISH__HELP_STRINGS.KNL KNL022.0 Mon Apr 15 00:36:09 1996 FULL FMG_AMERICAN_ENGLISH__MESSAGES.KNL KNL022.0 Sun Apr 14 23:51:40 1996 FULL FMG_ANA__DEF_RUL_LIB.KNL KNL022.0 Mon Apr 15 00:03:22 1996 FULL FMG_CTR__DEF_RUL_LIB.KNL KNL022.0 Mon Apr 15 00:27:47 1996 FULL FMG_ETC__DEF_RUL_LIB.KNL KNL022.0 Mon Apr 15 00:31:12 1996 FULL FMG_ETC__DEF_SEL_LIB.KNL KNL022.0 Mon Apr 15 00:35:33 1996 FULL FMG_FACTORY_GLOBAL_PARAM_LIBRARY.KNL KNL022.0 Sun Apr 14 23:48:29 1996 FULL FMG_GLOBAL_PARAM_LIBRARY.KNL KNL022.0 Sun Apr 14 23:48:29 1996 FULL FMG_NOT__DEF_EXTERNAL_LIB.KNL KNL022.0 Mon Apr 15 02:09:09 1996 FULL FMG_NOT__DEF_MAIL_LIB.KNL KNL022.0 Mon Apr 15 02:07:59 1996 FULL FMG_NOT__DEF_RUL_LIB.KNL KNL022.0 Mon Apr 15 02:08:51 1996 FULL FMG_RPT__DEF_RUL_LIB.KNL KNL022.0 Mon Apr 15 00:02:26 1996 FULL FMG_UNIX_COMMAND.KNL KNL022.0 Mon Apr 15 02:11:35 1996 FULL FMG_VMS_COMMAND.KNL KNL022.0 Mon Apr 15 02:07:32 1996 FULL FMG_ANA__FAC_STATE_DB.KNL KNL022.0 Mon Apr 15 02:16:13 1996 FULL FMG_ANA__PRM_STATE_DB.KNL KNL022.0 Mon Apr 15 02:16:13 1996 FULL The SHOW Commands 8-7 Appendix A DECevent Directories and Files The following sections describe the three DECevent directories that reside in the common area, SYS$COMMON, and the files that reside in those directories. The directories must contain the files listed for DECevent to perform correctly. A.1 SYS$COMMON:[SYSEXE] The directory SYS$COMMON:[SYSEXE] has one file, DIA.EXE. DIA.EXE is the main fault management image. A.2 SYS$COMMON:[SYSHELP] The directory SYS$COMMON:[SYSHELP] has one file, FMG_HELP_ FILE__AMERICAN_ENGLISH.HLB, which is the DECevent help file. A.3 SYS$COMMON:[SYSLIB] The directory SYS$COMMON:[SYSLIB] contains two sharable exe- cutable images used to execute the CLI or the GUI. They are: DECEVENT$SHARE.EXE XDECEVENT$SHARE.EXE A.4 DIA$LIBRARY The directory DIA$LIBRARY contains several files containing rules necessary for the translation of events. Table A-1 lists these files. DECevent Directories and Files A-1 Table_A-1:_DECevent_Independent_Directory_Files________________ File_Name_______________________File_Description_______________ FMG_AMERICAN_ENGLISH__HELP_ Internal help library file in STRINGS.KNL American English. FMG_AMERICAN_ENGLISH__MESSAGES.KInternal error message library file in American English. FMG_FACTORY_GLOBAL_PARAM_ Default settings library file LIBRARY.KNL provided for the main image. FMG_GLOBAL_PARAM_LIBRARY.KNL Present settings library file. Contains DECevent environmen- tal settings. FMG_DEF__SEL_RUL_LIB.KNL Selection criteria library containing selection keys through which input events are filtered. FMG_ETC__DEF_RUL_LIB.KNL File containing rules for converting the operating sys- tem specific events to the DECevent canonical form. FMG_ETC__DEF_SEL_LIB.KNL File containing rules for event to canonical transla- tion. FMG_CTR__DEF_RUL_LIB.KNL File containing rules to translate the DECevent canon- ical events into readable text. FMG_RPT__DEF_RUL_LIB.KNL Report format library file containing rules for out- putting different reports. FMG_VMS_COMMAND.KNL Command style library file containing rules to parse OpenVMS commands. FMG_ANA__DEF_RUL_LIB.KNL File containing rules for analysis. FMG_ANA__FAC_STATE_DB.KNL File containing factory state analysis database. FMG_ANA__PRM_STATE_DB.KNL File containing permanent state analysis database. FMG_NOT__DEF_EXTERNAL_LIB File containing external noti- fication list. FMG_NOT__DEF_MAIL_LIB.KNL File containing notification mailing lists. A-2 DECevent Directories and Files Table_A-1_(Cont.):_DECevent_Independent_Directory_Files________ File_Name_______________________File_Description_______________ FMG_NOT__DEF_RUL_LIB.KNL File containing notification rules. AXP_SYS12_EV5.BIN Binary file containing analy- sis rules for AXP CPUs. AXP_SYS17_EV4.BIN Binary file containing analy- sis rules for AXP CPUs. AXP_SYS27_EV45.BIN Binary file containing analy- sis rules for AXP CPUs. AXP_SYS9_EV4.BIN Binary file containing analy- sis rules for AXP CPUs. AXP_SYS9_EV5.BIN Binary file containing analy- sis rules for AXP CPUs. DEC_4000.BIN Binary file containing anal- ysis rules for the DEC 4000 CPU. DEC_7000.BIN Binary file containing anal- ysis rules for the DEC 7000 CPU. DSA.BIN Binary file containing analy- sis rules for DSA devices. HSAC.BIN Binary file containing analy- sis rules for HSC devices. KDM70.BIN Binary file containing anal- ysis rules for the KDM70 de- vice. RFXX.BIN Binary file containing analy- ________________________________sis_rules_for_RF_devices.______ A.5 SYS$LOGIN In addition to the files in the DECevent independent direc- tory, a knowledge library file, FMG_LOCAL_PARAM_LIBRARY.KNL, is created in your SYS$LOGIN directory to be used when cus- tomized settings are saved. This library is created, if it doesn't already exist, whenever DECevent is executed. You need not be logged into your local directory for this library to be created. Type DIR SYS$LOGIN:*.KNL at the system prompt to see the li- brary in your local directory. DECevent Directories and Files A-3 A.6 SYS$COMMON:[SYSMGR] The directory SYS$COMMON:[SYSMGR] has one file, DECEVENT$DEINSTALL.COM. DECEVENT$DEINSTALL.COM is the deinstallation command file. A-4 DECevent Directories and Files Appendix B System Settings The following lists the system settings displayed with the SHOW SETTINGS command and their default values for OpenVMS. Current Settings Information: Name Value =============================================================== CMD_TRACE 0 CTR_TRACE 0 DEBUG_STATE 0 ETC_TRACE 0 FMG__DEBUG_STATE 0 FMG__TRACE_STATE 0 RPT_TRACE 0 TRACE_STATE 0 CTR__DMP_RUL ROOT.DUMP_EVENT_CA CTR__RUL_LIB CTR__DEF_RUL_LIB CTR__SUM_LIB CTR__DEF_SUM_LIB DEF_CTR_RULE ROOT.HEADER_CA DEF_ETC_RULE ROOT.HEADER_EV ETC__DMP_RUL ROOT.DUMP_EVENT_EV ETC__RUL_LIB ETC__DEF_RUL_LIB ETC__SEL_LIB ETC__DEF_SEL_LIB RPT__RUL_LIB RPT__DEF_RUL_LIB HELP_FILE FMG_HELP_FILE CURRENT_CLI VMS VMS_DEFAULT /TRANSLATE UNIX_DEFAULT UNIX_DEFAULT CHEROKEE_VMS_DEFAULT /TRANSLATE DEF_EVT_LOG SYS$ERRORLOG:ERRLOG.SYS LOCALE AMERICAN_ENGLISH PRINT_MESSAGES 7 STREAM_SIZE 20 SYS_ACT_LOG_NAME ERT_ACTIVITY.LOG KNL__DEF_ENTRIES 32 KNL__LIB_DIRECTORY DIA$LIBRARY: System Settings B-1 KNL__LIB_PREFIX FMG_ KNL__LIB_SUFFIX .KNL VAX_VMS_STACK_SIZE 10 VAX_VMS_GUARD_SIZE 3 ALPHA_VMS_STACK_SIZE 50 ALPHA_VMS_GUARD_SIZE 30 RULE_MAX_BYTECNT 100000 DEFAULT_REPORT FULL_RE ANA_TRACE 0 NOT_TRACE 0 ANA__FAC_DB ANA__FAC_STATE_DB ANA__PRM_DB ANA__PRM_STATE_DB ANA__RUL_LIB ANA__DEF_RUL_LIB ANA__TMP_DB ANA__TMP_STATE_DB NOT__RUL_LIB NOT__DEF_RUL_LIB NOT__MAIL_LIB NOT__DEF_MAIL_LIB NOT__EXTERNAL_LIB NOT__DEF_EXTERNAL_LIB FMG__CUST_PROFILE FMGPROFILE FMG_VERSION 2.0 SICL_STATE OFF SICL_PROTOCOL_VERS 1 AUTO_COPY OFF ANALYSIS_TRIGGER_AUTOMATIAUTOMATIC ANALYSIS_TRIGGER_MANUAL MANUAL NOT__DEF_CSC_PHONE 1-800-354-9000 NOT__MAX_DSNLNK_MSG 59 MAIL_DEBUG 0 User-Modifiable System Settings Currently, the only user-modifiable system settings are the following: o VMS_DEFAULT o DEF_EVT_LOG o LOCALE Refer to Chapter 6 for instructions on how to change user modi- fiable settings and to Chapter 8 for information on how to show these settings. B-2 System Settings Appendix C Bit-to-Text Quick Reference Table C-1 shows all the DECevent commands and qualifiers that are available for the bit-to-text translation of events. Table_C-1:_List_of_DECevent_Commands_and_Qualifiers____________ Commands___________________Qualifiers__________________________ HELP [help_req] DIAGNOSE/TRANSLATE ([in- file][,...]) /BRIEF /ENTRY[=(START:start[,END:end])] /EXCLUDE=(keyword[=val][,...]) /FSTERR /FULL /INCLUDE=(keyword[=val][,...]) /[NO]LOG /OUTPUT[=output_file] /REVERSE /NODE=(node_name[,...]) /SINCE[=time] /BEFORE[=time] /SUMMARY /TERSE DIAGNOSE/BINARY=bin_ outputfile.BIN ([in- file][,...]) /ENTRY[=(START:start[,END:end])] Bit-to-Text Quick Reference C-1 Table_C-1_(Cont.):_List_of_DECevent_Commands_and_Qualifiers____ Commands___________________Qualifiers__________________________ /EXCLUDE=(keyword[=val][,...]) /INCLUDE=(keyword[=val][,...]) /[NO]LOG /REJECTED[=rej_file] /REVERSE /NODE=(node_name[,...]) /SINCE[=time] /BEFORE[=time] DIAGNOSE/CONTINUOUS /BRIEF /EXCLUDE=(keyword[=val][,...]) /FSTERR /FULL /INCLUDE=(keyword[=val][,...]) /OUTPUT[=output_file] /TERSE DIAGNOSE/DUMP ([in- file][,...]) /ENTRY[=(START:start[,END:end])] /EXCLUDE=(keyword[=val][,...]) /INCLUDE=(keyword[=val][,...]) /[NO]LOG /OUTPUT[=output_file] /NODE=(node_name[,...]) /REVERSE /SINCE[=time] /BEFORE[=time] DIRECTORY EVENTS DIRECTORY CANONICAL SHOW SELECT SHOW SELECT [select-name] SHOW SETTINGS SHOW SETTINGS [setting] DIAGNOSE/INTERACTIVE___________________________________________ All commands used at the command line interface are also valid within the interactive command shell. The following commands C-2 Bit-to-Text Quick Reference are only valid from within an interactive command shell ses- sion: SET EVENT file SET LOCALE location RESTORE SETTINGS SAVE SETTINGS Bit-to-Text Quick Reference C-3 Appendix D DECevent Qualifiers and Parameters for Bit-to-Text Translation This appendix contains descriptions and examples of all qual- ifiers and parameters associated with bit-to-text translation for DECevent. D.1 /BRIEF Qualifier The /BRIEF qualifier specifies that a minimal amount of infor- mation for each event report is provided by DECevent. Syntax Use the following syntax for the /BRIEF qualifier: DIAGNOSE/TRANSLATE/BRIEF [infile] Example The following is an example using the /BRIEF qualifier: $ DIAGNOSE/TRANSLATE/BRIEF FOO.SYS Example Output Example D-1 shows a sample brief report. Example D-1: Brief Report Format _______________________________________________________________ ********************** ENTRY 2 ******************************** Logging OS 1. OpenVMS System Architecture 2. Alpha OS version V7.0 Event sequence number 10. Timestamp of occurrence 16-MAY-1996 09:49:33 Host name garcia _______________________________________________________________ Example D-1 (continued on next page) DECevent Qualifiers and Parameters for Bit-to-Text Translation D-1 Example D-1 (Cont.): Brief Report Format _______________________________________________________________ System Model ---- Device Profile ---- Unit ATRGON$DKA300 Product Name RZ26 _______________________________________________________________ D.2 /ENTRY Qualifier The /ENTRY qualifier selects event entries by number. The num- ber is an incrementing number assigned to all event entries as they are put into the event log file. This number is not stored in the event itself. This qualifier selects event entries having numbers equal to or between the starting and ending number. Syntax Use the following syntax for the /ENTRY qualifier: DIAGNOSE/TRANSLATE/ENTRY[=(START:start[,END:end])] [infile] Start Parameter The start parameter is a decimal integer specifying the se- quence number of the first event entry to select. End Parameter The end parameter is a decimal integer specifying the sequence number of the last event entry to select. Example The following is an example using the /ENTRY qualifier: $ DIAGNOSE/TRANSLATE/ENTRY=(START:5,END:30) filename.dat The above command translates entries five through 30, including entries five and 30. NOTE With this command, you must always specify a starting number. The ending number is optional, but if no ending number is specified, all event entries from the starting number to the end of the file are selected. An ending number can never be specified by itself. D-2 DECevent Qualifiers and Parameters for Bit-to-Text Translation D.3 /EXCLUDE Qualifier The /EXCLUDE qualifier allows users to exclude event entries meeting specific selection criteria. The criteria can be speci- fied as a device name or as a keyword as shown in the following example. Only event entries meeting the selection criteria are excluded from processing. Syntax The following shows command syntax for the /EXCLUDE qualifier: DIAGNOSE/TRANSLATE/EXCLUDE=keyword[=val][,...] [infile] Examples Refer to Section D.3.1 for examples of commands using the /EXCLUDE qualifier. D.3.1 /EXCLUDE Keywords You can use keywords to exclude information from the output report. Keywords are listed in this section. The abbreviated forms of the keywords, shown in parentheses, are also accept- able. For example, you may exclude Environmental_entries with the following command: $ DIAGNOSE/TRANSLATE/EXCLUDE=(ENV)/OUTPUT=FILENAME.OUT The output is directed to the FILENAME.OUT file. The following selection keywords are available: o Attentions: (ATT) Event entries that contain the device attention entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(ATT)/OUTPUT=FILENAME.OUT o Bugchecks: (BUG) Event entries that contain crash re-start, system bugcheck, or user bugcheck entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(BUG)/OUTPUT=FILENAME.OUT o Buses: (BUS) Event entries that contain all bus class en- tries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(BUS)/OUTPUT=FILENAME.OUT $ DIAGNOSE/TRANSLATE/EXCLUDE=(buses=DEMNA)/OUTPUT=FILENAME.OUT o Cache: (CAC) Event entries that contain all cache entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(CAC)/OUTPUT=FILENAME.OUT DECevent Qualifiers and Parameters for Bit-to-Text Translation D-3 o Configurations: (CONF) Event entries that contain the con- figuration entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(CONF)/OUTPUT=FILENAME.OUT o Control_entries: (CONT) Event entries that contain new er- rorlog created, system startup, or timestamp of occurrence entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(CONT)/OUTPUT=FILENAME.OUT o CPUs: (CPU) Event entries that contain entries of a machine check (670 entry), a 660 entry, or a 630 entry for Alpha. $ DIAGNOSE/TRANSLATE/EXCLUDE=(CPU)/OUTPUT=FILENAME.OUT o Device_error: (DEVICE_ER) Event entries that contain entries of device error, device attention, device timeouts, logged message (MSCP[TM]), logged status (MSCP), or logged MSCP messages. $ DIAGNOSE/TRANSLATE/EXCLUDE=(DEVICE_ER)/OUTPUT=FILENAME.OUT o Device_name: (DEVICE_NA) Event entries that contain the device name specified. $ DIAGNOSE/TRANSLATE/EXCLUDE=(DEVICE_NA=DUA)/OUTPUT=FILENAME.OUT o Device_node: (DEVICE_NO) Event entries that contain the device node specified. $ DIAGNOSE/TRANSLATE/EXCLUDE=(DEVICE_NO=CLOSUS)/OUTPUT=FILENAME.OUT o Device_number: (DEVICE_NU) Event entries that contain the device number specified. $ DIAGNOSE/TRANSLATE/EXCLUDE=(DEVICE_NU=100)/OUTPUT=FILENAME.OUT o Disk: (DIS) Event entries that contain all disk class en- tries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(DIS)/OUTPUT=FILENAME.OUT $ DIAGNOSE/TRANSLATE/EXCLUDE=(DIS=RZ25,DIS=RZ26)/OUTPUT=FILENAME.OUT o Environmental_entries: (ENV) Event entries that contain power entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(ENV)/OUTPUT=FILENAME.OUT o Hosts: (HOS) Event entries that contain the host specified. $ DIAGNOSE/TRANSLATE/EXCLUDE=(HOS=LESH)/OUTPUT=FILENAME.OUT D-4 DECevent Qualifiers and Parameters for Bit-to-Text Translation o Informationals: (INF) Event entries that contain ONLY logged message entries with the MSCP flags field having bit 1 set- meaning informational. $ DIAGNOSE/TRANSLATE/EXCLUDE=(INF)/OUTPUT=FILENAME.OUT o IOS OR IO_subsystems: (IOS OR IO_) Event entries that con- tain device errors, device timeouts, device attentions, logged status (MSCP), logged message (MSCP), or logged MSCP message entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(IOS)/OUTPUT=FILENAME.OUT o MCHKS or Machine_checks: (MCH or MAC) Event entries that contain machine check information. $ DIAGNOSE/TRANSLATE/EXCLUDE=(MCH)/OUTPUT=FILENAME.OUT o Memory: (MEM) Event entries that contain soft error (CRD), extended (CRD), or memscan entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(MEM)/OUTPUT=FILENAME.OUT o Nodes: (NOD) Event entries that contain the node name speci- fied. $ DIAGNOSE/TRANSLATE/EXCLUDE=(NOD=GARCIA)/OUTPUT=FILENAME.OUT o OS or Operating_systems: (OS or OPE) Event entries that include operating system entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(OS)/OUTPUT=FILENAME.OUT o PWR or Power: (PWR OR POW) Event entries that contain DEC 7000[TM] CPU power entries only. $ DIAGNOSE/TRANSLATE/EXCLUDE=(PWR)/OUTPUT=FILENAME.OUT o Sequence_numbers: (SEQ) Event entries that contain the event sequence number specified. $ DIAGNOSE/TRANSLATE/EXCLUDE=(SEQ=10)/OUTPUT=FILENAME.OUT o SWI or Software_informationals: (SWI or SOF) Event entries that contain lastfail, system startup, system configuration, volume mounts, volume dismounts, new errorlog created, or timestamp entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(SWI)/OUTPUT=FILENAME.OUT o Sync_communications: (SYN) Event entries that contain all sync communication devices. $ DIAGNOSE/TRANSLATE/EXCLUDE=(SYN)/OUTPUT=FILENAME.OUT DECevent Qualifiers and Parameters for Bit-to-Text Translation D-5 o Tapes: (TAP) Event entries that contain all tape class en- tries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(TAP)/OUTPUT=FILENAME.OUT $ DIAGNOSE/TRANSLATE/EXCLUDE=(TAP=TLZ06)/OUTPUT=FILENAME.OUT o Timeouts: (TIM) Event entries that contain entries of device timeout. $ DIAGNOSE/TRANSLATE/EXCLUDE=(TIM)/OUTPUT=FILENAME.OUT o Unknown_entries: (UNK) Event entries that contain entries for device types that have not been classified by the cur- rent set of rules. $ DIAGNOSE/TRANSLATE/EXCLUDE=(UNK)/OUTPUT=FILENAME.OUT o Unsolicited_MSCP: (UNS) Event entries that contain entries logging an MSCP message. $ DIAGNOSE/TRANSLATE/EXCLUDE=(UNS)/OUTPUT=FILENAME.OUT o VMS_entry: (VMS) Event entries that contain values by entry number type. For example, the command DIAGNOSE/TRANSLATE /INCLUDE=(VMS ="100") would select all entry types that equal 100, with 100 being the logged message entry. The command (DIAGNOSE/TRANSLATE/EXCLUDE=(VMS ="100") would not show the VMS entries the item name matched. $ DIAGNOSE/TRANSLATE/EXCLUDE=(VMS="50")/OUTPUT=FILENAME.OUT o Volume_changes: (VOL) Event entries that contain volume mount and volume dismount entries. $ DIAGNOSE/TRANSLATE/EXCLUDE=(VOL)/OUTPUT=FILENAME.OUT D.3.2 Combining /EXCLUDE and /INCLUDE Qualifiers You may combine /EXCLUDE and /INCLUDE qualifiers in the same command line to further narrow the selection scope. An /INCLUDE /INCLUDE combination or an /EXCLUDE /EXCLUDE combination will result in an error message. Example The following example shows how to use /EXCLUDE and /INCLUDE qualifiers together: $ DIAGNOSE/TRANSLATE/EXCLUDE=(VMS="50",TI)/INCLUDE=(SEQ=10,SYS) D-6 DECevent Qualifiers and Parameters for Bit-to-Text Translation D.4 /FSTERR Qualifier The FSTERR qualifier provides a one-line-per-entry report of your event log for a variety of disk devices. Syntax Use the following syntax for the /FSTERR qualifier: DIAGNOSE/TRANSLATE/FSTERR [infile] Only disk information is presented in FSTERR reports. Example The following is an example using the /FSTERR qualifier: $ DIAGNOSE/TRANSLATE/FSTERR FOO.SYS Example Output Example D-2 shows an example of an FSTERR report. Example D-2: FSTERR Report Format ___________________________________________________________________ Drive/ MSCP Physical HSC Volume Drive Name yymmdd hhmmss Entry Evnt LED LBN Cyl Hd Sec RA RP Serial =========== ============= ===== ==== === === ==== == === === == ====== RUBY6$DUA022 921112 150138 62 01AB 92 00 D19295 PMASON$DUA006 921207 165009 63 00EB 7C 236 2 90 42 D23387 PMASON$DUA006 921207 165011 64 00EB 7C 236 2 90 42 D23387 PMASON$DUA006 921207 165050 65 00EB 1C 55 11 90 42 D23387 PMASON$DUA006 921207 165052 66 00EB 12 55 11 90 42 D23387 ___________________________________________________________________ D.5 /FULL Qualifier The /FULL qualifier specifies that all possible information for each selected event entry is reported. This format is the default report format of event translation. Syntax Use the following syntax for the /FULL qualifier: DIAGNOSE/TRANSLATE/FULL [infile] DECevent Qualifiers and Parameters for Bit-to-Text Translation D-7 Example The following is an example using the /FULL qualifier: $ DIAGNOSE/TRANSLATE/FULL FOO.SYS D-8 DECevent Qualifiers and Parameters for Bit-to-Text Translation Example Output Example D-3 shows an example of a full report. Example D-3: Full Report Format ___________________________________________________________________ ********************** ENTRY 2 ******************************** Logging OS 1. OpenVMS System Architecture 2. Alpha OS version V7.0 Event sequence number 10. Timestamp of occurrence 16-MAY-1996 09:49:33 Time since reboot 0 Day(s) 0:10:44 Host name garcia System Model Entry type 0. Unknown Entry Type ---- Device Profile ---- Unit ATRGON$DKA300 Product Name RZ26 ---- UNKNOWN DEVICE ---- ----- Not Decoded ----- x00000000 ----- Software Info ----- UCB$x_ERTCNT 0. Retries Remaining UCB$x_ERTMAX 4. Retries Allowable IRP$Q_IOSB x4108000000000002 UCB$x_STS x4F475254 Error Logging In-Progress Online Timed Out Mount In-Progress Unload At Dismount "Mount Verification" In-Progress Delete this UCB when Reference Count reaches zero Volume is Valid on the local node Suppress "Success" Mount Verification Message Write-locked Mount Verification in progress Unit is busy via Alternate STARTIO path Restart Validation is in progress Unit cannot have channels assigned to it Unit supports the Extended Function bit VMS DC$_CLASS 1. VMS DT$_TYPE 93. ___________________________________________________________________ Example D-3 (continued on next page) DECevent Qualifiers and Parameters for Bit-to-Text Translation D-9 Example D-3 (Cont.): Full Report Format ___________________________________________________________________ IRP$L_PID x00010022 Requestor "PID" IRP$x_BOFF 272. Byte Page Offset IRP$x_BCNT 32768. Transfer Size In Byte(s) UCB$x_ERRCNT 1. Errors This Unit UCB$L_OPCNT 4986. QIO's This Unit ORB$L_OWNER x08000011 Owners UIC UCB$L_DEVCHAR1 x1DCD4008 Directory Structured File Oriented Sharable Available Mounted Error Logging Allocated Foreign Capable of Input Capable of Output Random Access ___________________________________________________________________ D.6 /INCLUDE Qualifier The /INCLUDE qualifier allows you to specify selected event entries using [device_name] or [keyword] parameters. Only the event entries meeting the selection criteria are included for processing. Syntax The following shows command syntax for the /INCLUDE qualifier: DIAGNOSE/TRANSLATE/INCLUDE=keyword[val][,...] [infile] Examples Refer to Section D.6.1 for examples of commands using the /INCLUDE qualifier. D.6.1 /INCLUDE keywords You can use keywords to include information in the output re- port. A list of keywords is given in this section. The abbre- viated forms of the keywords, shown in parentheses, are also acceptable. For example, you may include Environmental_entries with the following command: $ DIAGNOSE/TRANSLATE/INCLUDE=(ENV)/OUTPUT=FILENAME.OUT D-10 DECevent Qualifiers and Parameters for Bit-to-Text Translation Selection keywords are the following: o Attentions: (ATT) Event entries that contain the device attention entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(ATT)/OUTPUT=FILENAME.OUT o Bugchecks: (BUG) Event entries that contain crash re-start, system bugcheck, or user bugcheck entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(BUG)/OUTPUT=FILENAME.OUT o Buses: (BUS) Event entries that contain all bus class en- tries. $ DIAGNOSE/TRANSLATE/INCLUDE=(BUS)/OUTPUT=FILENAME.OUT $ DIAGNOSE/TRANSLATE/INCLUDE=(buses=DEMNA)/OUTPUT=FILENAME.OUT o Cache: (CAC) Event entries that contain all cache entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(CAC)/OUTPUT=FILENAME.OUT o Configurations: (CONF) Event entries that contain the con- figuration entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(CONF)/OUTPUT=FILENAME.OUT o Control_entries: (CONT) Event entries that contain new er- rorlog created, system startup, or timestamp of occurrence entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(CONT)/OUTPUT=FILENAME.OUT o CPUs: (CPU) Event entries that contain entries of a machine check (670 entry), a 660 entry, or a 630 entry for Alpha. $ DIAGNOSE/TRANSLATE/INCLUDE=(CPU)/OUTPUT=FILENAME.OUT o Device_error: (DEVICE_ER) Event entries that contain en- tries of device error, device attention, device timeouts, logged message (MSCP), logged status (MSCP), or logged MSCP messages. $ DIAGNOSE/TRANSLATE/INCLUDE=(DEVICE_ER)/OUTPUT=FILENAME.OUT o Device_name: (DEVICE_NA) Event entries that contain the device name specified. $ DIAGNOSE/TRANSLATE/INCLUDE=(DEVICE_NA=DUA)/OUTPUT=FILENAME.OUT o Device_node: (DEVICE_NO) Event entries that contain the device node specified. $ DIAGNOSE/TRANSLATE/INCLUDE=(DEVICE_NO=GARCIA)/OUTPUT=FILENAME.OUT DECevent Qualifiers and Parameters for Bit-to-Text Translation D-11 o Device_number: (DEVICE_NU)Event entries that contain the device number specified. $ DIAGNOSE/TRANSLATE/INCLUDE=(DEVICE_NU=100)/OUTPUT=FILENAME.OUT o Disks: (DIS) Event entries that contain all disk class en- tries. $ DIAGNOSE/TRANSLATE/INCLUDE=(DIS)/OUTPUT=FILENAME.OUT $ DIAGNOSE/TRANSLATE/INCLUDE=(DISK=RZ25,DISK=RZ73)/OUTPUT=FILENAME.OUT o Environmental_entries: (ENV) Event entries that contain environmental entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(ENV)/OUTPUT=FILENAME.OUT o Host: (HOS) Event entries that contain the host specified. $ DIAGNOSE/TRANSLATE/INCLUDE=(HOS=LESH)/OUTPUT=FILENAME.OUT o Informationals: (INF) Event entries that contain only logged message entries with the MSCP flags field having bit 1 set- meaning informational. $ DIAGNOSE/TRANSLATE/INCLUDE=(INF)/OUTPUT=FILENAME.OUT o IOS or IO_subsystems: (IOS or IO_) Event entries that con- tain device errors, device timeouts, device attentions, logged status (MSCP), logged message (MSCP), or logged MSCP message entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(IOS)/OUTPUT=FILENAME.OUT o MCHKs or Machine_checks: (MCH or MAC) Event entries that contain machine check information. $ DIAGNOSE/TRANSLATE/INCLUDE=(MCH)/OUTPUT=FILENAME.OUT o Memory: (MEM) Event entries that contain soft error (CRD), extended (CRD), or memscan entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(MEM)/OUTPUT=FILENAME.OUT o Node: (NOD) Event entries that contain the node name speci- fied. $ DIAGNOSE/TRANSLATE/INCLUDE=(NOD=GARCIA)/OUTPUT=FILENAME.OUT o OS or Operating_systems: (OS or OPE) Event entries that contain operating system entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(OS)/OUTPUT=FILENAME.OUT D-12 DECevent Qualifiers and Parameters for Bit-to-Text Translation o PWR or Power: (PWR or POW) Event entries that contain DEC 7000 CPU power entries only. $ DIAGNOSE/TRANSLATE/INCLUDE=(PWR)/OUTPUT=FILENAME.OUT o Sequence_numbers: (SEQ) Event entries that contain the event sequence number specified. $ DIAGNOSE/TRANSLATE/INCLUDE=(SEQ=10)/OUTPUT=FILENAME.OUT o SWI or Software_informationals: (SWI or SOF) Event entries that contain lastfail, system startup, system configuration, volume mounts, volume dismounts, new errorlog created, or timestamp of occurrence entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(SWI)/OUTPUT=FILENAME.OUT o Sync_communications: (SYN) Event entries that contain all sync communication devices. $ DIAGNOSE/TRANSLATE/INCLUDE=(SYN)/OUTPUT=FILENAME.OUT o Tapes: (TAP) Event entries that contain all tape class en- tries. $ DIAGNOSE/TRANSLATE/INCLUDE=(TAP)/OUTPUT=FILENAME.OUT $ DIAGNOSE/TRANSLATE/INCLUDE=(TAP=TLZ06)/OUTPUT=FILENAME.OUT o Timeouts: (TIM) Event entries that contain entries of device timeout. $ DIAGNOSE/TRANSLATE/INCLUDE=(TIM)/OUTPUT=FILENAME.OUT o Unknown_entries: (UNK) Event entries that contain entries for device types that have not been classified by the cur- rent set of rules. $ DIAGNOSE/TRANSLATE/INCLUDE=(UNK)/OUTPUT=FILENAME.OUT o Unsolicited_MSCP: (UNS) Event entries that contain entries logging an MSCP message. $ DIAGNOSE/TRANSLATE/INCLUDE=(UNS)/OUTPUT=FILENAME.OUT o VMS_entry: (VMS) Event entries that contain values by entry number type. For example, the command DIAGNOSE/TRANSLATE /INCLUDE=VMS ="100" would select all entry types that equal 100, with 100 being the logged message entry. The command DIAGNOSE/TRANSLATE/EXCLUDE=VMS ="100" would not return VMS entries the item name matched. $ DIAGNOSE/TRANSLATE/INCLUDE=(VMS="50")/OUTPUT=FILENAME.OUT DECevent Qualifiers and Parameters for Bit-to-Text Translation D-13 o Volume_changes: (VOL) Event entries that contain volume mount and volume dismount entries. $ DIAGNOSE/TRANSLATE/INCLUDE=(VOL)/OUTPUT=FILENAME.OUT D.6.2 Combining /INCLUDE and /EXCLUDE Qualifiers You may combine /INCLUDE and /EXCLUDE qualifiers in the same command line to further narrow the selection scope. An INCLUDE /INCLUDE combination or an /EXCLUDE /EXCLUDE combination will result in an error message. Example The following example shows how to use /EXCLUDE and /INCLUDE qualifiers together: $ DIAGNOSE/TRANSLATE/EXCLUDE=(VM="50",TI)/INCLUDE=(SE=10,SY) D.7 /LOG Qualifier The /LOG qualifier controls the display of informational mes- sages to the terminal screen. By default, these messages are not displayed. Use the /LOG qualifier to display informational messages on the terminal screen. Use the /NOLOG qualifier to disable the display of informational messages. Informational messages consist of the number of event entries selected and rejected while a file is processed. The file must be processed with the /EXCLUDE, /INCLUDE, or /REJECTED qualifiers for the /LOG qualifier to work correctly. Syntax Use the following syntax for the /LOG qualifier. DIAGNOSE/TRANSLATE/[NO]LOG Example The following is an example of using the /LOG qualifier: $ DIAGNOSE/TRANSLATE/LOG/EXCLUDE=(DISK=RZ25) FOO.SYS D.8 /OUTPUT Qualifier The /OUTPUT qualifier redirects the output from the default system output to the specified text file. The default output is the standard output device (stdout or sys$output). Any valid file name can be specified to receive the redirected output. The /OUTPUT qualifier can be abbreviated to /OUT. D-14 DECevent Qualifiers and Parameters for Bit-to-Text Translation Syntax Use the following syntax for the /OUTPUT qualifier. DIAGNOSE/TRANSLATE/OUTPUT=output_file Output_file Parameter The output_file parameter is the name of a valid file speci- fication in which the output of the command resides. This file specification can be to the standard output device, which is the default. Example The following is an example of using the /OUTPUT qualifier: $ DIAGNOSE/INCLUDE=(DISK=RZ25)/OUTPUT=FILENAME.OUT D.9 /REVERSE Qualifier The /REVERSE qualifier specifies event entries be translated in reverse chronological order, with the most recent events displayed first. The default is to display events in forward chronological order. Syntax Use the following syntax for the /REVERSE qualifier. DIAGNOSE/TRANSLATE/REVERSE [infile] Example The following is an example of using the /REVERSE qualifier: $ DIAGNOSE/TRANSLATE/REVERSE FOO.SYS D.10 /NODE Qualifier The /NODE qualifier allows you to select event entries based on node name. Entries are specific to that node. If more than one node is specified, node names must be separated by commas and the entire string must be enclosed in parentheses. Node name length must conform to operating system conventions. Syntax Use the following syntax for the /NODE qualifier: DIAGNOSE/TRANSLATE/NODE=(node_name[,...]) [infile] The node_name parameter for the OpenVMS /NODE qualifier must be a valid node name. DECevent Qualifiers and Parameters for Bit-to-Text Translation D-15 Example The following is an example using the /NODE qualifier: $ DIAGNOSE/TRANSLATE/NODE=(GARCIA,LESH,WIER) FOO.SYS D.11 /SINCE and /BEFORE Qualifiers The /SINCE qualifier selects event entries that have occurred since the time specified. The /SINCE and /BEFORE qualifiers can be used separately or in combination. When used in combination, they select a time window from which event entries are reported. Syntax Use the following syntax for the /SINCE and /BEFORE qualifiers: DIAGNOSE/TRANSLATE/SINCE[=time]/BEFORE[=time] Time Parameter The date and time value is specified in the following time format and defined in Table D-1. DD-MMM-YYYY:HH:MM:SS.CC Table_D-1:_Date_and_Time_Code_Definitions______________________ Time Code______Meaning________________Example_______________________ DD Day of the month 01 MMM Month JAN YYYY Year 1995 HH Hours 06 MM Minutes 35 SS Seconds 08 CC________Tenths_of_a_second_____07____________________________ NOTE On OpenVMS systems, the CC field is ignored. For OpenVMS systems, the time parameter keywords supported in the DECevent utility are TODAY (TOD) and YESTERDAY (YES). TOMORROW is not a supported keyword. If the time param- eter is omitted, the operating system defaults to the keyword TODAY. D-16 DECevent Qualifiers and Parameters for Bit-to-Text Translation Example The following is an example of using the /SINCE and /BEFORE qualifiers: $ DIAGNOSE/SINCE=01-JAN-1993:06:35:08.07/BEFORE=TODAY D.12 /SUMMARY Qualifier The /SUMMARY qualifier produces a summary report. Refer to Example D-4 for a sample summary report. Syntax Use the following syntax for the /SUMMARY qualifier. DIAGNOSE/TRANSLATE/SUMMARY [infile] Example The following is an example using the /SUMMARY qualifier: $ DIAGNOSE/TRANSLATE/SUMMARY FOO.SYS Example Output Example D-4 shows a sample summary report. Example D-4: Summary Report Format ___________________________________________________________________ SUMMARY OF ALL ENTRIES LOGGED ON NODE GARCIA unknown major class MSCP 2. CRD Entry 3. 660 Entry 1. ___________________________________________________________________ DECevent Qualifiers and Parameters for Bit-to-Text Translation D-17 D.13 /TERSE Qualifier The /TERSE qualifier specifies that the registers and header of each event entry are formatted using the standard report format, but the contents of each register are not translated into readable messages. Refer to Example D-5 for an example of a terse report. Syntax Use the following syntax for the /TERSE qualifier. DIAGNOSE/TRANSLATE/TERSE [infile] Example The following is an example of using the /TERSE qualifier: $ DIAGNOSE/TRANSLATE/TERSE FOO.SYS Example Output Example D-5 shows a sample terse report. Example D-5: Terse Report Format _______________________________________________________________ ********************** ENTRY 2 ******************************** Logging OS 1. System Architecture 2. OS version V7.0 Event sequence number 10. Timestamp of occurrence 1992111609493300 Time since reboot 0 Day(s) 0:10:44 Host name garcia System Model Entry type 0. ---- Device Profile ---- Unit ATRGON$DKA300 Product Name RZ26 _______________________________________________________________ Example D-5 (continued on next page) D-18 DECevent Qualifiers and Parameters for Bit-to-Text Translation Example D-5 (Cont.): Terse Report Format _______________________________________________________________ ---- UNKNOWN DEVICE ---- ----- Not Decoded ----- x00000000 ----- Software Info ----- UCB$x_ERTCNT 0. UCB$x_ERTMAX 4. IRP$Q_IOSB x0000000000000002 UCB$x_STS x4F475254 VMS DC$_CLASS 1. VMS DT$_TYPE 93. IRP$L_PID x00010022 IRP$x_BOFF 272. IRP$x_BCNT 32768. UCB$x_ERRCNT 1. UCB$L_OPCNT 4986. ORB$L_OWNER x08000011 UCB$L_DEVCHAR1 x1DCD4008 _______________________________________________________________ DECevent Qualifiers and Parameters for Bit-to-Text Translation D-19