DECevent Release Notes for DIGITAL UNIX and OpenVMS The DECevent Release Notes for DIGITAL UNIX and OpenVMS provide general release information and restrictions for DECevent. Date: October 1998 DECevent Version: V2.9 1998 This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicenser. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-14 Alt. III, as applicable. (c) Digital Equipment Corporation 1998. All Rights Reserved. FrameMaker is a registered trademark of Adobe Systems Incorporated. This document was prepared using FrameMaker, Version 5.5.3 Contents Preface Chapter 1 General Release Information 1.1 New Features or Code Repairs for This Version of DECevent 1.1.1 Supported Products List Update 1.1.2 DECevent Supports the New Common Event Header (CEH) 1.2 DIGITAL UNIX Information 1.2.1 UERF and the Common Event Header 1.2.2 Common Event Collection Not Supported 1.2.3 Large Error Log Entries 1.2.4 DIGITAL UNIX Example 1.2.5 Command Line Editing Available on DIGITAL UNIX in Interactive Mode 1.3 OpenVMS Information 1.3.1 KNL File Internal Corruption or Hang Problems 1.3.2 DECevent GUI Requires Updated Xwindows and Motif Libraries Chapter 2 Enhanced Features from Previous Versions 2.1 Enhanced Features for DIGITAL UNIX and OpenVMS 2.1.1 HSX80 Support 2.1.2 Output of the Command to Show the Settings Sorted 2.1.3 Test SICL Message Now Contains System Information 2.1.4 Memory Channel Update 2.1.5 Starting Autoanalysis from the GUI Is Disabled 2.1.6 GUI Time Selection Window Changes 2.1.7 Automatic Analysis Scavenges After System Crash 2.1.8 Privileges Needed to Perform "SAVE SYSTEM SETTINGS" Command 2.1.9 Obtaining DECevent Kits from the DIGITAL Services Website 2.1.10 Changes to Report Output 2.1.11 IPMT Entries for DECevent 2.1.12 Starting the DECevent Graphical User Interface (GUI) 2.1.13 DECevent Error Log Entry Maximum Size 2.1.14 Analysis Database Locking Implemented 2.1.15 Locking Extended to Include Mailing List and External Notification Commands 2.1.16 DSNlink Notification Message Size Calculation Corrected 2.1.17 DECevent GUI Fixes 2.1.18 Supported Devices 2.2 Enhanced Features for DIGITAL UNIX 2.2.1 Date Can Be Specified in Mixed Cases 2.2.2 Binary Event Trailers on DIGITAL UNIX Checked 2.2.3 Default DECevent Library Variable DIA_LIBRARY 2.2.4 Deinstalling DECevent Software 2.2.5 Reinstalling DECevent Software 2.2.6 Corrupted Event Records 2.2.7 DECevent Requires DSNlink V2.0 for Proper SICL Operation 2.2.8 Large Error Log Entries 2.2.9 DIGITAL UNIX Example 2.2.10 Command Line Editing Available on DIGITAL UNIX in Interactive Mode 2.3 Enhanced Features for OpenVMS 2.3.1 Turbolaser Power Status 2.3.2 Turbolaser Halt Frame Support 2.3.3 PKQdriver Reporting 2.3.4 DKdriver Rev 3 Packet, Fibre Channel Error Reporting 2.3.5 SYSLCK Privilege Now Necessary 2.3.6 Command Line Editing Available on OpenVMS in Interactive Mode 2.3.7 Ability to Quote Device Names to Flush Theories 2.3.8 Deleting Older Versions of Local Knowledge Files 2.3.9 Starting DSNlink and Motif Processes and Images 2.3.10 FRU_TABLE Entry Causes Incorrect OpenVMS errorlog Entry Chapter 3 Known Restrictions for the Graphical User Interface (GUI) 3.1 Known Restrictions for the GUI for DIGITAL UNIX and OpenVMS 3.1.1 Text Entries 3.1.2 Multiple Input File Restriction 3.1.3 sys info Text Length Restriction 3.2 Known Restrictions for the GUI for DIGITAL UNIX 3.2.1 GUI Enhancements 3.2.2 GUI Display Restriction with 100 D.P.I. Monitors 3.2.3 Accessing .KNL Directories 3.2.4 Brief Report Type Restriction 3.2.5 Translation Restrictions 3.2.6 Qualifier List Screen Restrictions 3.3 Known Restrictions for the GUI for OpenVMS 3.3.1 Graphical User Interface User Guide for OpenVMS 3.3.2 GUI Startup Command Chapter 4 DIGITAL UNIX - Known Restrictions for DECevent 4.1 Non-Support of DIGITAL UNIX Operating Systems Below V3.2c 4.2 Non-Support of Multiple Version Event Logs 4.3 Analysis Restriction 4.4 Translation Restriction 4.5 Local Settings File 4.6 -v Flag Restriction 4.7 "set phone" Command Restriction 4.8 "shw the" Command Restriction 4.9 "shw thr" Restriction 4.10 "ls can" and "ls evt" Command Restrictions 4.11 Wildcard Restrictions 4.12 "set thr -n" Restriction 4.13 -j Flag Restriction 4.14 Command Restrictions with Automatic Analysis 4.15 DSNlink Message Size Exceeded 4.16 Evidence Support 4.17 Distribution List Name Restrictions 4.18 Start (s:) and End (e:) Parameter Restriction 4.19 Year Restriction with Start (s:) and End (e:) Parameters 4.20 Multiple Wildcards in File Specification Produces an Error 4.21 Reverse Output Entries Incorrectly Numbered 4.22 "set sicl" Restriction and Script Files 4.23 Missing Information from Output of shw sum Command 4.24 Threshold Limit Maximum is 127 4.25 Avoiding Use of Reserved Command Verbs for Filenames 4.26 Avoiding Use of Same Filename for Input and Output Chapter 5 OpenVMS Alpha Operating Systems - Known Restrictions for DECevent 5.1 File Specification Restriction 5.2 Wildcard Restriction 5.3 DIRECTORY CANONICAL and DIRECTORY EVENT Command Restrictions 5.4 SHOW THRESHOLD Command Restriction 5.5 Analysis Restrictions 5.6 Local Settings File 5.7 Page File Quota Restriction 5.8 JTquota Restriction 5.9 /LOG Qualifier Restriction 5.10 /FSTERR Report Type Restriction 5.11 SET THRESHOLD/NAME Restriction 5.12 Evidence Support 5.13 /SINCE Parameter Restriction 5.14 /BEFORE and /SINCE Parameter Restrictions 5.15 RF74 Algorithm Incorrect 5.16 Distribution List Name Restrictions 5.17 RF31T Support 5.18 Command Restrictions with Automatic Analysis 5.19 DSNlink Message Size Exceeded 5.20 Set SICL Restriction and Command Procedure 5.21 Missing Information from the SHOW SUMMARY Command Chapter 6 OpenVMS VAX Operating Systems - Known Restrictions for DECevent Chapter 7 OpenVMS Systems - Comparing DECevent and Previous DIGITAL Fault Management Tools 7.1 Selection Criteria 7.2 Thresholding 7.2.1 Event Classes 7.2.2 Event Severity 7.2.3 Event Counting 7.2.4 Comparing Event Counts with Thresholds 7.3 Autocopy 7.4 Cluster-Wide Support 7.5 Volume Labels 7.6 DECevent Translation of Multiple Input Files Appendix A DIGITAL UNIX Systems - Devices Supported for Bit To Text Translation Appendix B DIGITAL UNIX Systems - Devices Supported for Analysis and Notification Appendix C OpenVMS Alpha Systems - Devices Supported for Bit To Text Translation Appendix D OpenVMS Alpha Systems - Devices Supported for Analysis and Notification Appendix E OpenVMS VAX Systems - Devices Supported for Bit To Text Translation Appendix F OpenVMS VAX Systems - Devices Supported for Analysis and Notification Preface The DECevent Release Notes for DIGITAL UNIX and OpenVMS provide general information about DECevent as well as differences between DECevent and past fault management tools. Also provided are restrictions for the current release of DECevent and known problems with this release of DECevent. Intended Audience The DECevent Release Notes for DIGITAL UNIX and OpenVMS are intended for use by system managers and service personnel who use DECevent software. Chapter 1 General Release Information This chapter provides information pertaining to the general use of the DECevent event management tool for DIGITAL UNIX and for OpenVMS. This release contains bug fixes and updates to knowledge libraries. 1.1 New Features or Code Repairs for This Version of DECevent The information in Section 1.1 pertains to both DIGITAL UNIX and OpenVMS. 1.1.1 Supported Products List Update - Compaq AlphaServer GS60 6/525 Bit To Text and Analysis - Compaq AlphaServer GS140 6/525 Bit To Text and Analysis - AlphaServer 8x00 6/525 Bit To Text and Analysis enhancements - AlphaServer 8x00 Double Error Halt Bit To Text - Minor Memory Channel Adapter II Bit To Text corrections 1.1.2 DECevent Supports the New Common Event Header (CEH) This release of DECevent supports the new Common Event Header. It is used by versions of OpenVMS 7.1-2 and beyond, or conditionally by DIGITAL UNIX version 4.OE or later versions of the Alpha hardware, when logging entries to the binary event log. This new header is part of an effort to remove size limitations and to improve the capability of providing automatic analysis for system problem resolution. Included with this release of DECevent is a conversion tool used to provide access to the binary event log to older programs that do not support this new header format. This utility, called DECevent_cvt_cef, can be found in the same directory from where you run the main DECevent executable. Refer to the Binary Error Log Translation Utility User's Guides for more information about this utility. 1.2 DIGITAL UNIX Information The information in Section 1.2 pertains to DECevent for DIGITAL UNIX. 1.2.1 UERF and the Common Event Header The UNIX Error Report Formatter (UERF) utility does not understand the new Common Event Header format files. If you wish to use this utility to process binary event log files, you can use a shell script that is provided with the DECevent_cvt_cef utility, called cehuerf, to assist in this process. Refer to the Binary Error Log Translation Utility User's Guides for a discussion of limitations of this script and examples on how to use it. 1.2.2 Common Event Collection Not Supported The binary error logging daemon has the ability to be configured to send events to another system, thus allowing a single system to collect events for multiple systems. While it has been documented for some time on OpenVMS systems that this configuration is not supported by DECevent, we were unaware that DIGITAL UNIX systems had this capability and had not documented this restriction. DECevent was designed to consider all event information as coming from a single system, and the analysis algorithms do not consistently take into account that different systems might be feeding it information. If device names on two systems happen to be the same, DECevent can make an error thinking that a threshold has been reached or may log a call against one device when, in fact, the other one is failing. 1.2.3 Large Error Log Entries In some cases, error log entries are larger than DECevent's current handling capability. If the following error is reported by DECevent, rename the file /var/adm/binary.errlog and disable FRU table logging at the Alpha console level. 1.2.4 DIGITAL UNIX Example DECevent V2.X Event record: 11 of file; /var/adm/binary.errlog is incorrect, recovering. *************************** ENTRY 1 ********************** Logging OS 2. Digital UNIX System Architecture 2. Alpha Event sequence number 0 1.2.5 Command Line Editing Available on DIGITAL UNIX in Interactive Mode DECevent now allows you to up-arrow through your last 20 commands While in interactive mode. The command editing style is that of Emacs. 1.3 OpenVMS Information The information in Section 1.3 pertains to DECevent for OpenVMS. 1.3.1 KNL File Internal Corruption or Hang Problems DECevent may abort execution with the error message "KNL File is internally corrupted" or may sometimes hang, with OpenVMS V6.2, V6.2-1H3, V7.0 and V7.1 if the file DECC$SHR.EXE is dated earlier than April 1997. There are patch kits that contain an updated "C" Run-Time Library that must be installed. The kit names are ALPACRT02_71 for OpenVMS Alpha V7.1, ALPACRT09_062 OpenVMS Alpha V6.2, or VAXACRT09_062 OpenVMS VAX V6.2. Note: Because this library is used by other system applications, you should verify that installing this kit will not adversely affect those applications. DIGITAL Field Service engineers can obtain more information about this problem in Blitz[TD2203-a]. 1.3.2 DECevent GUI Requires Updated Xwindows and Motif Libraries During testing we found that the DECevent GUI stimulated some problems with the Motif version 1.2.3 on OpenVMS VAX 6.2 systems and Motif version 1.2.4 on OpenVMS Alpha 6.2 systems. You must obtain the VAXMOTF07 or equivalent patch kit. After installation of the patch kit, your system should have the following versions (or later). The minimum versions for DECwindows on OpenVMS Alpha are as follows: DECwindows ident is DW V1.2-4960312 DECwindows server ident is DW T6.2-950505 DECwindows transport ident is DW T6.2-950505 DECwindows xlib ident is DW V1.2-4960312 DECwindows motif toolkit ident is DW V1.2-4960313 DECwindows apps ident is DW V1.2-4960312 DECwindows programming ident is DW V1.2-4960312 The minimum versions for DECwindows on OpenVMS VAX are as follow: DECwindows ident is DW V1.2-3960214 DECwindows server ident is DW V6.2-950419 DECwindows transport ident is DW V6.2-950419 DECwindows xlib ident is DW V1.2-3960214 DECwindows OSF/Motif Toolkit ident is DW V1.2-3960214 DECwindows apps ident is DW V1.2-3960215 DECwindows programming ident is DW V1.2-3960214 Chapter 2 Enhanced Features from Previous Versions This chapter provides information about enhanced features from previous versions of the DECevent event management tool. 2.1 Enhanced Features for DIGITAL UNIX and OpenVMS The following features pertain to both DIGITAL UNIX and OpenVMS. Enhanced features for DIGITAL UNIX can be found in Section 2.2. Enhanced features for OpenVMS can be found in Section 2.3. 2.1.1 HSX80 Support Updates to HSZ80 and HSG80 new error code is now supported. 2.1.2 Output of the Command to Show the Settings Sorted The output of the SHOW SETTINGS and shw set commands is now sorted, which should make it easier to locate the setting you want. Previously, the value most recently changed was at the end of the list. 2.1.3 Test SICL Message Now Contains System Information Previously, the test message sent to SICL mailing list did not contain the current system information for the serial number and type. Instead, it reported them as UNKNOWN. 2.1.4 Memory Channel Update Support now includes added source node identification. 2.1.5 Starting Autoanalysis from the GUI Is Disabled The DECevent GUI has been changed so that any attempt by the user to initiate Automatic Analysis will result in an informational message displaying. The message indicates that Automatic Analysis must be started from the command line. Refer to the Analysis Guide for details of this procedure. 2.1.6 GUI Time Selection Window Changes The Qualifier List's Time Selection window for using scales to set the Start Time and Stop Time has been updated to preserve the most recent values for the Start and Stop Times, and the most recent position of the date/month/year and hour/minute/second scales. The Qualifier List also preserves the most recent Start and Stop Times for the next manual translation or analysis. The year range has been reduced to make the year scale easier to use. 2.1.7 Automatic Analysis Scavenges After System Crash As of DECevent V2.5, automatic analysis at startup examines the system error log file to see if any entries are there that were missed. If it finds missed entries, they are processed. It is no longer necessary to run manual analysis at system startup. 2.1.8 Privileges Needed to Perform "SAVE SYSTEM SETTINGS" Command If a non-privileged user (one without write access to the global library file) attempts to perform a SAVE SYSTEM SETTINGS or sav sys command, one of two things can happen. The first is a message stating the following will be reported: _DIANOSE-ERR The write of the global library failed. Check if Auto-Analysis is running. The second is that DECevent could hang and you will have to use Ctrl/C to abort it. We intend to fix the hang condition in a future release of DECevent. 2.1.9 Obtaining DECevent Kits from the DIGITAL Services Website Obtain DECevent kits from the DIGITAL Services Website, located at www.service.digital.com. From the Online Services area, click on DECevent and select information on how to obtain DECevent kits. 2.1.10 Changes to Report Output Within reports, text strings that may have previously contained non-printing control characters now display those control characters as the tilde (~) character. This change was implemented to eliminate adverse effects on printing and terminal line feed. Embedded carriage returns (0x0D) are converted to spaces. This is most noticeable in reports containing configuration entries and HSC out-of-band errors. Numbers that were displayed in octal radix now have the preceding octal radix indicator, a lower case letter o (for example, o777). 2.1.11 IPMT Entries for DECevent MCS Service Engineers who need to submit IPMT problems and solutions against DECevent should use the corporate IPMT server and use the product name DECEVENT when entering DECevent IPMT issues and problems. 2.1.12 Starting the DECevent Graphical User Interface (GUI) DECevent now allows you to translate and analyze event logs with a GUI. Invoke the GUI with the following command: For DIGITAL UNIX: # xdia For OpenVMS: $ DIAGNOSE/INTERFACE=DECW Refer to Chapter 3 for known restrictions for the GUI. Refer to The DECevent Graphical User Interface User's Guide, AA-QE26A-TE, for information about how to use the GUI. 2.1.13 DECevent Error Log Entry Maximum Size The maximum size of an error log entry has been increased to 32765, to accommodate larger AlphaServer 8x00 Field Replaceable Units (FRUs) table packets. Currently, only DIGITAL UNIX is capable of writing binary events larger than 16K. The console software that creates these FRU packets is capable of creating an entry larger than the 32765 (or 16K for OpenVMS), and if allowed to, will corrupt the error log file from the point of view of DECevent and other utilities. If this happens, you must delete the error log file and refer to the console documentation for the commands necessary to disable the logging of FRU packets. We are working on eliminating the limits in a future release. Note, however, that changes also will be required in the operating systems. 2.1.14 Analysis Database Locking Implemented DECevent now locks any usage of the analysis engine. This means that if you have automatic or manual analysis running, you cannot perform any commands that refer to analysis data, such as SHOW SETTINGS or shw set. We are evaluating a design change to allow concurrent access for a future release of DECevent. Your feedback would be helpful in prioritizing the need for this change. 2.1.15 Locking Extended to Include Mailing List and External Notification Commands After providing a workaround via locking for the problem of Analysis KNL file damage caused by concurrent access, it was discovered that the mailing and external notification lists suffered from the same problem. We have extended the locking mechanism to include the mailing and external notification lists. This means that any commands that manipulate those lists must now be performed with Automatic analysis not running. The following is an example of the error you see if you attempt to modify the mailing lists while Automatic analysis is running. ERROR: Another instance of analysis is running. _DIAGNOSE-FAT: Execution failed _DIAGNOSE-FAT: No message found for status code 0 from svc_exp__f_execute_wq_entry in thread 1 ...Offending facility has no translation ...facility number: 0 ...status code: 0 _DIAGNOSE-FAT: No message found for status code 955271 from svc_exp__f_execute_wq_entry in thread 1 ...Offending facility has no translation ...facility number: 0 ...status code: 119408 2.1.16 DSNlink Notification Message Size Calculation Corrected DSNlink has a maximum message size limit of 60 blocks. DECevent V2.5A and V2.6 contained changes to observe this limit; however, the size calculations were flawed in several areas. This was corrected in the DECevent V2.7 release. 2.1.17 DECevent GUI Fixes A number of latent memory usage problems with the GUI including all known crashes have been fixed. If any problems are observed, please notify us and give the sequence of steps necessary to produce the crash, if possible. 2.1.18 Supported Devices Appendix A of these notes contains a list of all DIGITAL UNIX devices supported by the DECevent Bit To Text translation feature. Appendix B of these notes contains a list of all DIGITAL UNIX devices supported by the DECevent analysis and notification feature. Appendix C of these notes contains a list of all OpenVMS Alpha devices supported by the DECevent Bit To Text translation. Appendix D of these notes contains a list of all OpenVMS Alpha devices supported by the DECevent analysis and notification feature. Appendix E of these notes contains a list of all OpenVMS VAX devices supported by the DECevent analysis and notification feature. Appendix F of these notes contains a list of all OpenVMS VAX devices supported by the DECevent Bit To Text translation feature. 2.2 Enhanced Features for DIGITAL UNIX The following features pertain to DECevent for DIGITAL UNIX. 2.2.1 Date Can Be Specified in Mixed Cases DECevent now accepts dates entered in mixed case for selecting events. 2.2.2 Binary Event Trailers on DIGITAL UNIX Checked Binary events on DIGITAL UNIX have a specific layout that includes a four byte trailer with known required contents. Previously, DECevent did not verify the contents of a binary event's trailer before processing the event. Starting with V2.6 DECevent will check the contents of the trailer and will reject any binary event with an invalid trailer. As this change may prohibit access to potentially useful information on older versions of DIGITAL UNIX we have provided an environment variable to override this behavior. If the environment variable DIA_IGNORE_INVALID_TRAILER is defined and set to a nonzero value, DECevent will revert to the pre-V2.6 behavior of not checking the contents of the trailer. 2.2.3 Default DECevent Library Variable DIA_LIBRARY The DECevent Library environment variable, DIA_LIBRARY is now being set to /var/DIA by default during the installation process. Users that wish to use a different directory location for DIA_LIBRARY must invoke the appropriate setenv or export command to change the environment variable. 2.2.4 Deinstalling DECevent Software To permanently remove DECevent software from your system, delete each subset that you previously installed. To delete subsets: 1. Log in as superuser (login name root). 2. Make sure you are at the root directory (/) by entering the following command: # cd / 3. Enter the following form of the setld command: # setld -i | grep `DIA.* installed This produces the following display: DIABASE250 installed DECevent Base kit (Translation / Analysis) DIADOCBOOK250 installed DECevent Optional book reader documentation DIADOCPS250 installed DECevent Optional postscript documentation DIADOCTXT250 installed DECevent Optional text documentation 4. Look for the word "installed" in the listing produced, then delete the installed subsets with the following command: # setld -d subsetname [subsetname ...] 5. Looking at the previous display, you find the subset DIADOCBOOK250 with the word installed next to it. Delete this subset as follows: # setld -d DIADOCBOOK250 The system then verifies the deletion of each subset.The program reports the progress of the deletion and removal of all specified subsets. 2.2.5 Reinstalling DECevent Software When a new version of DECevent software is installed after a previous version has existed on a system, the FMG_LOCAL_PARAM_ LIBRARY.KNL file must be deleted from the home directory of each user who ran the previous version of DECevent. 2.2.6 Corrupted Event Records DECevent has been enhanced to continue processing event files even when DECevent has detected a corrupted event record. The message "Event Record XXX of file [file-name] is corrupted. Recovering..." is displayed when DECevent encounters a corrupted event entry. You can remove corrupted event entries by issuing the following command: dia -b errorlog.new -f errorlog.corrupt where errorlog.new is the new event log file and errorlog.corrupt is the corrupted file. 2.2.7 DECevent Requires DSNlink V2.0 for Proper SICL Operation DECevent requires that your operating system have V2.0 of DSNlink installed for System Initiated Call Logging (SICL) to function properly. 2.2.8 Large Error Log Entries In some cases, error log entries are larger than DECevent's current handling capability. If the following error is reported by DECevent, rename the file /var/adm/binary.errlog, and disable FRU table logging at the Alpha console level. 2.2.9 DIGITAL UNIX Example DECevent V2.X Event record: 11 of file; /var/adm/binary.errlog is incorrect, recovering. *************************** ENTRY 1 ********************** Logging OS 2. Digital UNIX System Architecture 2. Alpha Event sequence number 0 2.2.10 Command Line Editing Available on DIGITAL UNIX in Interactive Mode DECevent now allows you to up-arrow through your last 20 commands While in interactive mode. The command editing style is that of Emacs. 2.3 Enhanced Features for OpenVMS The following features pertain to DECevent for OpenVMS. 2.3.1 Turbolaser Power Status DECevent now provides power status support for the Turbolaser. 2.3.2 Turbolaser Halt Frame Support DECevent now provides halt frame support for the Turbolaser. 2.3.3 PKQdriver Reporting DECevent now supports updates for PKQdriver reporting. 2.3.4 DKdriver Rev 3 Packet, Fibre Channel Error Reporting DECevent now supports updates for DKdriver Rev 3 packet, Fibre Channel error reporting, using standardized naming conventions. 2.3.5 SYSLCK Privilege Now Necessary Users who utilize analysis commands now must have the SYSLCK privilege. 2.3.6 Command Line Editing Available on OpenVMS in Interactive Mode DECevent now allows you to up-arrow through your last 20 commands while in interactive mode. 2.3.7 Ability to Quote Device Names to Flush Theories In previous versions of DECevent for OpenVMS, the FLUSH command did not permit its device name argument to be quoted. The FLUSH command on OpenVMS also converted its device name argument to all upper case. This combination meant that the FLUSH command could not be used to delete event and analysis information that had been stored for some devices. The device name argument to the FLUSH command can now be quoted on OpenVMS. Characters within the quotation marks are not converted to upper case. An example within the DECevent interactive command shell is: DIA> flush "StorageWorks" Since the DCL command language interpreter also processes quotes, you must "quote the quotes" to use this feature from the DCL command line, as follows: $ diagnose flush """StorageWorks""" 2.3.8 Deleting Older Versions of Local Knowledge Files The file FMG_LOCAL_PARAM_LIBRARY.KNL must be deleted from the login directory SYS$LOGIN of each user who ran the previous version of DECevent. DECevent V2.1 and later will not work with .KNL files of previous versions. 2.3.9 Starting DSNlink and Motif Processes and Images You must start all prerequisite processes and images, such as Motif, before executing the DECevent startup command file: DECEVENT$STARTUP.COM in SYS$STARTUP:SYSTARTUP_VMS.COM. Failure to do so causes the DECW$TRANSPORT_COMMON logical to be undefined when DECevent starts. 2.3.10 FRU_TABLE Entry Causes Incorrect OpenVMS errorlog Entry When the console variable FRU_TABLE is set to ON, which is the default as of version 5.0 of console firmware, FRU_TABLE will place into errorlog a packet that is too large for the default setting to handle. The OpenVMS errorlog will show the first entry correctly, but the subsequent entries will appear as 11/785 entries with unusual time stamps. This occurs on 4100 and 8200/8400. There are two things that may help, as follows: 1. Modify MODPARAMS.DAT or use SYSMAN to increase the following to their maximum allowed values (this requires a reboot to take effect): ERRORLOGBUFFERS = 64 (4 is default) ERLBUFFERPAGES = 32 (8 is default) 2. Upgrade DECevent to version 2.6 or better. 3. Rename errorlog.sys and reboot the system or 1. Shut down the system and set FRU_TABLE to OFF. 2. Reboot and rename errorlog.sys. 3. Upgrade DECevent to version 2.6 or better Other symptoms you may see from DECevent are as follows. Use the previous fix to remedy the situation. $ dia DECevent V2.6 _DIAGNOSE-FAT: Unexpected error adding Error Message in thread 4 Value of errno is: 0, and vaxc$errno is: 0 Unexpected Status Exception: not enough core _DIAGNOSE-FAT: Unexpected error deleting Error Message object in thread 4 Value of errno is: 0, and vaxc$errno is: 0 Unexpected Status Exception: not enough core PRE_ERR-INF-?-pre_err__m_get_stat: Exception - %CMA-F-EXCEPTION, exception raised; address of exception object 0057A670 or $ anal/err/since=1-dec-1997/exc=vol Error Log Report Generator Version V6.1 %ERF-E-READERR, error reading SYS$SYSROOT:[SYSERR]ERRLOG.SYS;4 -RMS-W-RTB, 4674 byte record too large for user's buffer. Chapter 3 Known Restrictions for the Graphical User Interface (GUI) This chapter describes known restrictions and enhancements with this release of the DECevent Graphical User Interface (GUI). 3.1 Known Restrictions for the GUI for DIGITAL UNIX and OpenVMS The following restrictions pertain to both DIGITAL UNIX and OpenVMS. Restrictions for DIGITAL UNIX can be found in Section 3.2. Restrictions for OpenVMS can be found in Section 3.3. 3.1.1 Text Entries All text field entries must be terminated with a . 3.1.2 Multiple Input File Restriction You cannot perform translation or analysis on multiple input files. Only one input file can be translated or analysis performed upon at a time. 3.1.3 sys info Text Length Restriction The text length fields in the sys info icon box are limited to 40 characters. 3.2 Known Restrictions for the GUI for DIGITAL UNIX The following restrictions pertain to DIGITAL UNIX. 3.2.1 GUI Enhancements The DECevent GUI for DIGITAL UNIX allows you to select an output filename from the Qualifier Screen. This output, previously in upper case, is now in lower case. 3.2.2 GUI Display Restriction with 100 D.P.I. Monitors Switch 100 D.P.I. monitors to 75 D.P.I. to eliminate a window display problem. 3.2.3 Accessing .KNL Directories The default environment variable for DIA_LIBRARY is set to /var/DIA. If the user wishes to use a different location. The proper declaration command must be performed. Follow these examples for defining the new variable. setenv DIA_LIBRARY /var/NEW_FILE If you are using the Bourne Shell, use the following commands: >DIA_LIBRARY=/var/NEW_FILE >export DIA_LIBRARY 3.2.4 Brief Report Type Restriction When the brief report type is selected for manual analysis, the resulting translation shows a full report. 3.2.5 Translation Restrictions If the user is executing several singular translations or executing the dump -d) operation, the executions may consume a majority of system memory. A system message saying "unable to complete translation" may appear or the process may hang. Exit DECevent and restart to clear system memory. 3.2.6 Qualifier List Screen Restrictions Clicking on the FILE icon shows a list of main DECevent qualifiers. When selecting BINARY from this qualifier list and using a start and end entry number followed by a return, the cursor hangs. Manually click the OK box for that screen and the start and ending entry numbers will be applied. 3.3 Known Restrictions for the GUI for OpenVMS The following restrictions pertain to OpenVMS. 3.3.1 Graphical User Interface User Guide for OpenVMS The figures and examples shown in The DECevent Graphical User Interface User's Guide show Digital UNIX results. You must substitute OpenVMS commands and syntax where necessary when using the GUI on OpenVMS systems. 3.3.2 GUI Startup Command Use the following command to start the Graphical User Interface for DECevent on OpenVMS systems: $ DIAGNOSE/INTERFACE=DECWINDOWS Chapter 4 DIGITAL UNIX - Known Restrictions for DECevent This chapter describes known restrictions for DIGITAL UNIX with this release of DECevent. 4.1 Non-Support of DIGITAL UNIX Operating Systems Below V3.2c DECevent does not support the analysis of events generated on DIGITAL UNIX operating systems below version V3.2c. 4.2 Non-Support of Multiple Version Event Logs Do not run DECevent on operating systems whose event logs contain events from multiple versions of DIGITAL UNIX. 4.3 Analysis Restriction Only one instance of analysis (Automatic or Manual) can be run at a time on a given system. DECevent now locks out any other attempt to use an analysis command, including those used only to read, for example shw set. The functionality of the DECevent manual analysis mode was changed in V2.2 regarding the number of event reports that are generated when an event log is processed. The following highlight these changes. Manual Analysis Functionality V2.1 and Earlier Event logs that contain multiple events for the same CPU, that are not Corrected Read Data (CRD) errors or MSCP device events, will generate a single event report. Manual Analysis Functionality V2.2 and Later Any event log that contains multiple events from the same CPU that are not Corrected Read Data (CRD) errors, MSCP device events, or HSZ controller errors will generate a report for each event encountered. For example, if a system event log contains ten events and the events are not one of the above items, then ten reports are generated. However, if the event log contains ten events that are CRD, MSCP device, or HSZ controller errors, then a single report is generated. 4.4 Translation Restriction If the user is executing several singular translations or executing the dump (-d) operation, there exists the possibility that the executions will consume a majority of system memory. A system message saying "unable to complete translation" may appear or the process may hang. Exit DECevent and restart to clear system memory. 4.5 Local Settings File When a new version of DECevent is installed after a previous version has existed on a system, the file $HOME/FMG_LOCAL_ PARAM_LIBRARY.KNL must be deleted from the login directory of each user who ran the previous version of DECevent. 4.6 -v Flag Restriction The -v flag controls the display of informational messages telling the user how many event entries were selected and rejected. When using the -v flag, and no output is specified, the informational messages may be embedded within the report displayed on the terminal screen. 4.7 "set phone" Command Restriction Characters entered with the set phone command must be valid numeric characters. Use of alphabetical characters is not allowed. 4.8 "shw the" Command Restriction The shw the command truncates the second theory number when multiple theories are called out. 4.9 "shw thr" Restriction The shw thr command displays the event counts as 1 for devices that have logged errors. This occurs even when the devices have exceeded their thresholds and notification has been performed. DECevent is handling the events properly and performing notification at the appropriate times, but it is not displaying the correct counts. 4.10 "ls can" and "ls evt" Command Restrictions The ls can and ls evt commands do not function properly for this release of DECevent. 4.11 Wildcard Restrictions When a user attempts a translation using a wildcard in the file specification and the number or size of the filenames exceeds an internal buffer, an error message indicating that the internal file array buffer has been exceeded is displayed. _DIAGNOSE-FAT: An error occurred while executing a command ruleset _DIAGNOSE-FAT: Translate - Exceeded Internal file array buffer 4.12 "set thr -n" Restriction The set thr -n command only works for devices that have previously logged events. 4.13 -j Flag Restriction You must specify a file for rejected information to be written to when using the -j flag. 4.14 Command Restrictions with Automatic Analysis Commands that modify analysis and notification knowledge files require prior shutdown of automatic analysis. Before using any of the commands listed in this section, DECevent automatic analysis must be stopped by entering: % /sbin/init.d/dia_s_k stop After the /sbin/init.d/dia_s_k script file has been entered, and the desired command from Table 4-1 has been issued, DECevent automatic analysis may be restarted by reexecuting the script file /sbin/init.d/dia_s_k and passing start as the parameter. % /sbin/init.d/dia_s_k start Table 4-1 lists the commands that require prior shutdown of automatic analysis before the command can be issued. Table 4-1 DIGITAL UNIX Commands Requiring Prior Shutdown of Automatic Analysis Before Being Issued ad ext rem usr ad usr rep flsh set phone ign set sicl rec set sys rem rep set thres rem_sys 4.15 DSNlink Message Size Exceeded DECevent may exceed the DSNlink message size when trying to notify the Customer Support Center. If so, you will see the following message: DSN-W-MAXFILESIZE, maximum allowed file size is 60 blocks 4.16 Evidence Support This release of DECevent software does not currently provide evidence information in the analysis/notification reports. 4.17 Distribution List Name Restrictions When using the ad usr command, the following words cannot be user names: customer fse monitor sicl 4.18 Start (s:) and End (e:) Parameter Restriction For Bit To Text translations, a selection with a starting date that is greater than the ending date should result in an error message but is ignored. No error message is generated. 4.19 Year Restriction with Start (s:) and End (e:) Parameters The year 2029 is the highest year you can enter on the command line with the s: and e: parameters. 4.20 Multiple Wildcards in File Specification Produces an Error When specifying an event log for translation or analysis, only one wildcard character (*) may be used in the file specification. 4.21 Reverse Output Entries Incorrectly Numbered When reverse output is specified with the -R flag, the entries are numbered as if they were in normal, rather than reversed, order. 4.22 "set sicl" Restriction and Script Files You use the set sicl command from within the interactive command shell to set the SICL state to on, but you must then use the sav sys command to ensure the new SICL state is saved. The preferred method of setting the SICL state on is to execute the script file enable_sicl. To disable SICL, execute the script file disable_sicl. 4.23 Missing Information from Output of shw sum Command The output of the DECevent shw sum command does not specify whether a field service or a customer threshold was crossed. 4.24 Threshold Limit Maximum is 127 When changing the threshold for a device using the set thr command. A limit of 127 is the highest possible setting. 4.25 Avoiding Use of Reserved Command Verbs for Filenames Names of command verbs are not acceptable for use as filenames to be used by DECevent. 4.26 Avoiding Use of Same Filename for Input and Output When using DECevent, the filename for input and output must never be the same name. The original input file will be corrupted if the output filename has the same name. Chapter 5 OpenVMS Alpha Operating Systems - Known Restrictions for DECevent This chapter describes known restrictions with this release of DECevent on Open VMS Alpha operating systems. Refer to Chapter 6 for DECevent restrictions specific to OpenVMS VAX operating systems. 5.1 File Specification Restriction The current version of DECevent does not support file specifications that start with a node address. For example: GARCIA::disk1:[]lesh.sys 5.2 Wildcard Restriction When a user attempts a translation using a wildcard in the file specification and the number or size of the filenames exceeds an internal buffer, an error message displays indicating that the internal file array buffer has been exceeded. _DIAGNOSE-FAT: An error occurred while executing a command ruleset _DIAGNOSE-FAT: Translate - Exceeded Internal file array buffer 5.3 DIRECTORY CANONICAL and DIRECTORY EVENT Command Restrictions The DIRECTORY CANONICAL and DIRECTORY EVENT commands do not function properly in the current release of DECevent. 5.4 SHOW THRESHOLD Command Restriction The SHOW THRESHOLD command truncates the second theory number when multiple theories are called out. 5.5 Analysis Restrictions Only one instance (either manual or automatic) of analysis at a time can be run on a given system. DECevent now locks out any other attempt to activate analysis on a node. The functionality of the DECevent manual analysis mode was changed in V2.2 regarding the number of event reports that are generated when an event log is processed. The following highlight these changes. Manual Analysis Functionality V2.1 and Earlier Event logs that contain multiple events for the same CPU that are not Corrected Read Data (CRD) errors or MSCP device events will generate a single event report. Manual Analysis Functionality V2.2 and Later Any event log that contains multiple events from the same CPU that are not Corrected Read Data (CRD) errors, MSCP device events, or HSZ controller errors will generate a report for each event encountered. For example, if a system event log contains ten events and the events are not one of the previous items, then ten reports are generated. However, if the event log contains ten events that are CRD, MSCP device, or HSZ controller errors, then a single report is generated. 5.6 Local Settings File When a new version of DECevent is installed after a previous version has existed on a system, the file SYS$LOGIN:FMG_LOCAL_ PARAM_LIBRARY.KNL must be deleted from the login directory of each user who ran the previous version of DECevent. 5.7 Page File Quota Restriction DECevent may fail with an access violation if the page file quota is exceeded. The process terminates and returns you to the system prompt if this happens. You must have your system administrator increase your PGFLQUO parameter in the SYSUAF file, then logout and log in again. You may need to re-issue the last failing command. 5.8 JTquota Restriction The JTquota shown with the SHOW FIELD command when using AUTHORIZE must be increased to 8192 for DECevent software to function correctly. At the UAF> prompt following the SHOW FIELD command, change the JTquota by entering the following: MODIFY FIELD/JTQUOTA=8192. 5.9 /LOG Qualifier Restriction The /LOG qualifier controls the display of informational messages telling the user how many event entries were selected and rejected. When using the /LOG qualifier, and no output is specified, the informational messages may be embedded within the report. 5.10 /FSTERR Report Type Restriction In the current DECevent release, the /FSTERR report type produces an output for RA70, RA72, RA73 and RA9x series devices only. 5.11 SET THRESHOLD/NAME Restriction The SET THRESHOLD/NAME command works only for devices that have previously logged an event. 5.12 Evidence Support This release of DECevent does not currently provide evidence information in the analysis/notification reports. 5.13 /SINCE Parameter Restriction Using a colon (:) after the /SINCE parameter causes a syntax error and is not allowed. 5.14 /BEFORE and /SINCE Parameter Restrictions A selection with the starting date (/BEFORE) greater than the ending date (/SINCE) is ignored. No error message is generated. 5.15 RF74 Algorithm Incorrect The RF74 LBN to physical cylinder, head, and sector conversion is incorrect. The RF74 is a "banded drive" and contains a variable number of sectors per track, depending on the band. The algorithm uses this information as if it were a fixed sector disk. RF74 analysis may be affected by this. 5.16 Distribution List Name Restrictions When using the ADD USER command, the following words cannot be user names: CUSTOMER FSE MONITOR SICL 5.17 RF31T Support RF31T events are translated as RF31 events even though RF31 events have a different format. RF31T is unsupported for analysis. 5.18 Command Restrictions with Automatic Analysis Commands that modify analysis and notification knowledge files require prior shutdown of automatic analysis. Before using any of the commands listed in this section, DECevent automatic analysis must be stopped by entering the following: $ @SYS$STARTUP:DECEVENT$SHUTDOWN.COM After the @SYS$STARTUP:DECEVENT$SHUTDOWN.COM command procedure has been entered, and the desired command has been entered, DECevent automatic analysis may be restarted by executing the command procedure: SYS$STARTUP:DECEVENT$STARTUP.COM. Table 5-1 lists the commands that require prior shutdown of automatic analysis before the command can be issued. Table 5-1 OpenVMS Commands Requiring Prior Shutdown of Automatic Analysis Before Being Issued ADD EXTERNAL REMOVE USER ADD USER REPAIR FLUSH SET PHONE_NUMBER IGNORE SET SICL RECOGNIZE SET SYSTEM_INFO REMOVE REPAIRED SET THRESHOLD REMOVE_SYSTEM_INFO 5.19 DSNlink Message Size Exceeded DECevent may exceed the DSNlink message size when trying to notify the Customer Support Center. If so, the following message appears: DSN-W-MAXFILESIZE, maximum allowed file size is 60 blocks 5.20 Set SICL Restriction and Command Procedure Use the SET SICL command from within the interactive command shell to set the SICL state to on, then use the command SAVE SYSTEM SETTINGS to ensure the SICL state stays on. The preferred method of setting the SICL state on is to execute the DIA$MGR:DECEVENT$SICL_ENABLE.COM command procedure. To disable SICL, execute the DECEVENT$DISABLE_SICL.COM command procedure. 5.21 Missing Information from the SHOW SUMMARY Command The output of the DECevent SHOW SUMMARY command does not specify whether a field service or a customer threshold was crossed. Chapter 6 OpenVMS VAX Operating Systems - Known Restrictions for DECevent This chapter describes known DECevent restrictions specific to OpenVMS VAX operating systems. Restriction When Translating Large Event Logs When processing large event logs on some OpenVMS VAX systems, the performance of DECevent is noticeably slower when compared to the DCL command ANALYZE/ERROR. You can alleviate this problem by periodically creating new event logs. A reasonable practice is to rename the sys$errorlog:errorlog.sys file to errorlog.yy-mm-dd every month. Chapter 7 OpenVMS Systems - Comparing DECevent and Previous DIGITAL Fault Management Tools This chapter describes known differences between past fault management tools and DECevent. 7.1 Selection Criteria Selection criteria for the /INCLUDE and /EXCLUDE qualifiers differs between former fault management tools and DECevent. Table 7-1 is a list of valid selection keywords for DECevent. /INCLUDE=(keyword=[val] [,...]) /EXCLUDE=(keyword=[val] [,...]) Table 7-1 Valid Selection Keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES Example: /INCLUDE=(DISK=RZ56,DISK=RA) /EXCLUDE=(TAPE=TA,CPU) You also can use keywords without values, as shown in the following example: /INCLUDE=(disk, tape) 7.2 Thresholding Thresholding is the process by which DECevent automatic analysis determines whether a device has logged a sufficient number of events to warrant analysis and/or notification. DECevent performs thresholding by classifying events based on time of occurrence and relative severity, then comparing them to stored numbers called thresholds. DECevent implements thresholding in a different manner from previous fault management tools. This implementation is discussed in the following sections, which explain event classes, event severity, event counting, and the comparison process. 7.2.1 Event Classes DECevent allows the specification of thresholds within two categories called classes. These classes are DSE and CUSTOMER. The DSE class contains thresholds that are preset by DIGITAL. When a DSE threshold is crossed, analysis is initiated for the device that logged the events. If analysis generates a theory code, notification is also performed. DSE thresholds can be modified only by DIGITAL Services personnel. The CUSTOMER class contains thresholds that are not preset by DIGITAL. When a CUSTOMER threshold is crossed, notification is initiated for the device that logged the events, through the monitor mailing list and the customer external command procedures. Analysis is not initiated. CUSTOMER thresholds can be set to any value by the system manager. 7.2.2 Event Severity Within each class, thresholds are further specified according to the relative severity of the event. Severity is classified as shown in Table 7-2. Table 7-2 Event Severity Classification Severity Level Description --------------------------------- HARD Non-recoverable errors. SOFT Errors from which the device successfully recovered. MEDIA Events related to media such as disk media. INFO Events logged to record information such as Timestamps and volume mounts/dismounts. 7.2.3 Event Counting The thresholding process requires that counts be maintained for events that are logged on each device. Event counts are classified by severity. When an event is logged for a device, DECevent stores the event in the analysis state database, then recalculates the event counts for the device. If a threshold is crossed, events less than seven days old are used in automatic analysis. DECevent removes events older than seven days to prevent their use in automatic analysis. Events less than 24 hours old are counted for thresholding. 7.2.4 Comparing Event Counts with Thresholds Once the event counts have been recalculated, DECevent compares them with the thresholds in the following manner: - If an error of any severity level exceeds the DSE threshold for that severity level, then DECevent initiates analysis. If analysis generates a theory code, DECevent initiates notification. - If an error of any severity level exceeds the CUSTOMER threshold for that severity level, then DECevent initiates notification. 7.3 Autocopy Previous fault management tools provided an autocopy feature that detected failing disk drives and initiated shadow copying to preserve data. This feature is not implemented in the current version of DECevent. 7.4 Cluster-Wide Support DECevent must be installed separately on each node in a cluster. Also, DECevent must be installed in a SYS$SPECIFIC area for each node in a cluster. Do not install DECevent in your SYS$COMMON area. Installing DECevent in a SYS$COMMON area will result in file corruption as DECevent does not allow file sharing. 7.5 Volume Labels The Error Report Formatter (ERF) maintained a list of devices and their volume labels as it encountered volume mount and dismount entries. When an entry for a tape or disk device was encountered, the matching volume labels were output in the report. This feature is not implemented in the current version of DECevent. 7.6 DECevent Translation of Multiple Input Files When requested to translate entries from multiple input files, DECevent does not delineate which entries are from which input file. Entries are numbered as if they were all translated from the same input file. Appendix A DIGITAL UNIX Systems - Devices Supported for Bit To Text Translation This appendix lists DIGITAL UNIX systems and devices supported by the DECevent Bit To Text translation feature. Note: For any system or device not in this list, as much translation will be performed as possible. All remaining information in the event will be dumped in hex. Alpha Systems AlphaServer 800 5/xxx AlphaServer 1000 4/xxx AlphaServer 1000A 4/266 AlphaServer 1000A 5/xxx AlphaServer 2000 4/xxx AlphaServer 2000 5/375/400 AlphaServer 2000A 5/xxx AlphaServer 2100A 5/xxx AlphaServer 2100A RM 5/xxx AlphaServer 2100 4/xxx AlphaServer 2100 RM 5/375 AlphaServer 2100 5/xxx AlphaServer 4000/4100 5/xxx AlphaServer 8200/8400 4GB M AlphaServer 8200/8400 CRD AlphaServer 8200/8400 5/300/350/440/625 AlphaStation 200 4/xxx AlphaStation 205 4/xxx AlphaStation 255 4/xxx AlphaStation 400 4/xxx AlphaStation 500 5/xxx AlphaStation 600 5/xxx AlphaStation 533au2 AXPvme DEC 2000 200/300/400/500/700/900 DEC 3000 300/400/500/700/900 DEC 4000 DEC 7000 DEC 10000 File System/Software ADVFS Logical Storage Manager HSXXX Battery Failure Notification Memory Channel Adapter Bit To Text translation is supported by DECevent for the Memory Channel I and II Adapters, including the PCI slot identifier quadword. PCI Adapters DWLPA DWLPB CCMPA KZPCM-DA KZPDA-AA QLOGIC (1020/1040) Chip Support KZPBA-CA QLOGIC (1020/1040) Chip Support PCI-Fiber Host Bus Adapter(KGPSA) PCI-SCSI Adapters (KZPSA/KZTSA) PCI Bus HS Array Controllers All HS Array Controllers have full Bit To Text support. MSCP DSA Disks All MSCP DSA Disks have full Bit To Text support. MSCP DSSI Disks All MSCP DSSI Disks have full Bit To Text support. All SCSI Devices DECevent SCSI support for DIGITAL UNIX is implemented via CAM (Common Access Method). RZ28L-AA Atlas II 2GB RZ29L-AA Atlas II 4GB RZ40-AA Atlas II 9GB RZ1BB-AS Atlas II 3GB RZ1BB-BA Atlas II 3GB RZ1BB-BS Atlas II 3GB RZ1BB-CA Atlas II 3GB RZ1BB-CS Atlas II 3GB RZ1CB-AS Atlas II 4GB RZ1CB-BA Atlas II 4GB RZ1CB-BS Atlas II 4GB RZ1CB-CA Atlas II 4GB RZ1CB-CS Atlas II 4GB RZ1DB-AS Atlas II 9GB RZ1DB-BA Atlas II 9GB RZ1DB-BS Atlas II 9GB RZ1DB-CA Atlas II 9GB RZ1DB-CS Atlas II 9GB RZXX RDXX RW5XX RWZXX RX26 RX31 RZ1CD-BS - 4.3GB 10000RPM Ultra Wide 68 Pin RZ1CD-CS - 4.3GB 10000RPM Ultra Wide 80 Pin SCA2 RZ1EF-AA - 18.2GB 7200RPM Ultra Narrow 50 Pin RZ1EF-AB - 18.2 GB 7200RPM Ultra 50 Pin Narrow RZ1EF-AS - 18.2GB 7200RPM Ultra Narrow 50 Pin RZ1EF-BA - 18.2GB 7200RPM Ultra Wide 68 PIN RZ1EF-BB - 18.2 GB 7200RPM Ultra Wide 68 PIN RZ1EF-BS - 18.2GB 7200RPM Ultra Wide 68 PIN RZ1EF-CA - 18.2GB 7200RPM Ultra Wide 80 Pin SCA2 RZ1EF-CB - 18.2 GB 7200RPM Ultra Wide 80 Pin SCA2 RZ1EF-CS - 18.2GB 7200RPM Ultra Wide 80 Pin SCA2 TZ8X Tape Family TZ8X tape family support includes the following: TZ85/857 TZ86/867 TZ87/875/877 TZ88 Other Tapes: TK50 TKXZZ TSZXX SCSI Solid State Disks EZ31 - 100MB or 134MB Solid State Disk EZ32 - 200MB or 268.3MB Solid State Disk EZ33 - 300MB Solid State Disk EZ34 - 400MB Solid State Disk EZ35 - 500MB Solid State Disk EZ51 - 107MB Solid State Disk with Data Retention EZ52 - 214MB Solid State Disk with Data Retention EZ53 - 267MB Solid State Disk without Data Retention EZ54 - 428MB Solid State Disk with Data Retention EZ58 - 1.07GB Solid State Disk without Data Retention or 856MB Solid State Disk with Data Retention EZ64 - 475MB Solid State Disk EZ69 - 950MB Solid State Disk Appendix B DIGITAL UNIX Systems - Devices Supported for Analysis and Notification This appendix lists DIGITAL UNIX systems and devices supported by the DECevent analysis and notification features. Alpha Systems AlphaServer 800 5/xxx AlphaServer 1000 4/xxx AlphaServer 1000 4/200 AlphaServer 1000A 4/266 AlphaServer 1200 5/xxx AlphaServer 2000 5/375/400 AlphaServer 2100 RM 5/375 AlphaServer 2100 5/375/400 AlphaServer 4000/4100 5/xxx AlphaServer 8200/8400 5/300/350/440/625 AlphaServer 8200/8400 4Gb Memory AlphaServer 8200/8400 CRD Analysis AlphaStation 533au2 AXPvme DEC 4000 DEC 10000 HSxxx Battery Failure Notification HS Array Controllers HSG80 HSZ40/50/70 MSCP DSA Disks MSCP DSA disks are fully supported for analysis by DECevent. MSCP DSSI Disks MSCP DSSI disks are fully supported for analysis by DECevent. Appendix C OpenVMS Alpha Systems - Devices Supported for Bit To Text Translation This appendix lists OpenVMS Alpha systems and devices supported by the DECevent Bit To Text translation feature. Note: For any system or device not in this list, as much translation will be performed as possible. All remaining information in the event will be dumped in hex. Alpha Systems AlphaServer 800 5/xxx AlphaServer 1000 4/xxx AlphaServer 1000A 4/266 AlphaServer 1000A 5/xxx AlphaServer 1200 5/xxx AlphaServer 2000 4/xxx AlphaServer 2000 5/325/375/400 AlphaServer 2000A 5/xxx AlphaServer 2100A 5/xxx AlphaServer 2100A RM 5/xxx AlphaServer 2100 5/375/400 AlphaServer 2100 RM 5/375 AlphaServer 2100 4/xxx AlphaServer 4000/4100 5/xxx AlphaServer 8200/8400 4GB M AlphaServer 8200/8400 CRD AlphaServer 8200/8400 5/300/350/440/625 AlphaServer 8200/8400 6/440/625 AlphaStation 200 4/xxx AlphaStation 205 4/xxx AlphaStation 255 4/xxx AlphaStation 400 4/xxx AlphaStation 500 5/xxx AlphaStation 600 5/xxx AlphaStation 533au2 AXPvme DEC 2000 200/300/400/500/700/900 DEC 3000 300/400/500/700/900 DEC 4000 DEC 7000 DEC 10000 HSxxx Battery Failure Notification PCI Adapters DWLPA DWLPB CCMPA PCI-Fiber Host Bus Adapter(KGPSA) PCI-SCSI Adapters (KZPSA/KZTSA) PCI Bus ISP 1020 KZPCM-DA KZPDA-AA QLOGIC (1020/1040) Chip Support KZPBA-CA QLOGIC (1020/1040) Chip Support SCSI Solid State Disks EZ31 - 100MB or 134MB Solid State Disk EZ32 - 200MB or 268.3MB Solid State Disk EZ33 - 300MB Solid State Disk EZ34 - 400MB Solid State Disk EZ35 - 500MB Solid State Disk EZ51 - 107MB Solid State Disk with Data Retention EZ512R EZ52 - 214MB Solid State Disk with Data Retention EZ53 - 267MB Solid State Disk without Data Retention EZ54 - 428MB Solid State Disk with Data Retention EZ54R EZ58 - 1.07GB Solid State Disk without Data Retention or 856MB Solid State Disk with Data Retention EZ64 - 475MB Solid State Disk EZ69 - 950MB Solid State Disk EZXX SCSI Port Drivers AHA1740/1742A SIMPORT Qlogic 1038/1070 SCSI disk controller SCSI Disk Support RZ28L-AA Atlas II 2GB RZ29L-AA Atlas II 4GB RZ40-AA Atlas II 9GB RZ1BB-AS Atlas II 3GB RZ1BB-BA Atlas II 3GB RZ1BB-BS Atlas II 3GB RZ1BB-CA Atlas II 3GB RZ1BB-CS Atlas II 3GB RZ1CB-AS Atlas II 4GB RZ1CB-BA Atlas II 4GB RZ1CB-BS Atlas II 4GB RZ1CB-CA Atlas II 4GB RZ1CB-CS Atlas II 4GB RZ1DB-AS Atlas II 9GB RZ1DB-BA Atlas II 9GB RZ1DB-BS Atlas II 9GB RZ1DB-CA Atlas II 9GB RZ1DB-CS Atlas II 9GB RZ1CD-BS - 4.3GB 10000RPM Ultra Wide 68 Pin RZ1CD-CS - 4.3GB 10000RPM Ultra Wide 80 Pin SCA2 RZ1EF-AA - 18.2GB 7200RPM Ultra Narrow 50 Pin RZ1EF-AB - 18.2 GB 7200RPM Ultra 50 Pin Narrow RZ1EF-AS - 18.2GB 7200RPM Ultra Narrow 50 Pin RZ1EF-BA - 18.2GB 7200RPM Ultra Wide 68 PIN RZ1EF-BB - 18.2 GB 7200RPM Ultra Wide 68 PIN RZ1EF-BS - 18.2GB 7200RPM Ultra Wide 68 PIN RZ1EF-CA - 18.2GB 7200RPM Ultra Wide 80 Pin SCA2 RZ1EF-CB - 18.2 GB 7200RPM Ultra Wide 80 Pin SCA2 RZ1EF-CS - 18.2GB 7200RPM Ultra Wide 80 Pin SCA2 RZXX HSC Family The following HSC devices are supported by the DECevent Bit To Text translation feature. Their names will be displayed as controlling devices for appropriate disk and tape errors, but their own out-of-band errors are not yet supported by DECevent translation. The out-of-band events will be dumped in hex. HSC40 HSC50 HSC60 HSC65 HSC70 HSC90 HSC95 Other Adapters DSYT1 KFMSA KFMSB SHAC PAxxx PNxxx Memory Channel Adapters I and II DE422-SA DEFAA DEFTA DEFZA DEFEA DWTVA HS Array Controllers HSD05/10/30/40/50 HSG80 HSJ30/40/50 HSZ10/15/20/40/50/70 Internal Device Controllers CIXCD-AC Other Support DDR- Dynamic Device Recognition DSR - Dynamic System Recognition Host Based RAID 0 and 5 I/O Adapters DEMFA DEMNA KDM70 KZMSA MSCP DSA Disks RA60 RA70 RA71 RA72 RA73 RA80 RA81 RA82 RA90 RA92 MSCP DSA Tapes TAD34 TAD44 TA78 TA79 TA81 TAD85 TAD86 TAD87 TA90 TA90E TA91 TA85/TA857 TA86/TA867 TA90E MSCP DSSI Disks RF30 RF31 RF31F RF31T RF35 RF36 RF70 RF71 RF72 RF73 RF74 RFH3 RFH31 RFH35 RFH36 RFH72 RFH73 RFH74 MSCP DSSI Tapes TF30 TF70 TF85 TF86 TF867 TF857 SCSI Tapes TZ85\857 TZ86\867 TZ87\875\877 TZ88 Other SCSI Devices RRDXX RW5XX RWZXX RX26 RX31 Generic Devices Generic DU (for example, MSCP disks not yet known by OpenVMS) Generic TU (for example, MSCP tapes not yet known by OpenVMS) NI SCA events OpenVMS Striping Events OVMS Volume Shadow Events MSCP Controllers KCM44 KDA50-Q KDB50 KFBTA KRQ50 RQDX1 RQDX3 RQDX4 UDA50 UDA50-A MSCP DSA Solid State Disks ESE20 ESE52 ESE56 ESE58 MSCP DSA Optical Disks RV20 RV60 MSCP DSSI Solid State Disks EF51 EF52 EF53 EF54 EF58 Other TMSCP Tapes/Controllers TBK70 TK50 TK50S TK50-DEBNT TK70 TKZXX TKLXX TQK50 TSZXX TUK50 Appendix D OpenVMS Alpha Systems - Devices Supported for Analysis and Notification This appendix lists OpenVMS Alpha systems and devices supported by the DECevent analysis and notification feature. Alpha Systems AlphaServer 800 5/xxx AlphaServer 1000 4/xxx AlphaServer 1000 4/200 AlphaServer 1000A 4/266 AlphaServer 1000A 5/xxx AlphaServer 1200 5/xxx AlphaServer 2000 4/xxx AlphaServer 2000 5/375/400 AlphaServer 2100 RM 5/375 AlphaServer 2100 4/xxx AlphaServer 2100 5/375/400 AlphaServer 4000/4100 5/xxx AlphaServer 8200/8400 5/300/350/440/625 AlphaStation 533au2 AXPvme DEC 4000 DEC 7000 DEC 10000 I/O Adapters KDM70 HSxxx Battery Failure Notification MSCP DSA Disks RA60 RA70 RA71 RA72 RA73 RA80 RA81 RA82 RA90 RA92 HS Array Controllers HSD30/40/50 HSG80 HSJ30/40/50 HSZ40/50/70 There are 15 different areas of analysis that can be done on RAxx devices. Analysis and notification support for RAxx devices is implemented for the following areas: 1. RA90/92 Special Analysis 2. SDI Communication Errors Analysis 3. Non-media Drive Detected Errors Analysis 4. Media Drive Detected Errors Analysis 5. Head Matrix Analysis 6. Bad Surface Analysis 7. Servo Failures Analysis 8. Head Slap Test Analysis 9. Random Read Path Analysis 10. Bad Head Analysis 11. Radial Scratch Analysis 12. Circumferential Scratch Analysis 13. Bad Spot Analysis 14. Possible Media Errors Analysis 15. Forced Error Analysis MSCP DSSI Disks RF30 RF31 RF31F RF35 RF70 RF71 RF72 RF73 Appendix E OpenVMS VAX Systems - Devices Supported for Bit To Text Translation This appendix lists OpenVMS VAX operating systems and devices supported by the DECevent Bit To Text translation feature. Note: DECevent software's primary focus on VAX operating systems is to support Bit To Text translation for the StorageWorks products. For any device not in this list, as much translation will be performed as possible. All remaining information in the event will be dumped in hex. CPUs VAX 6000 400/500/ 600 VAX 7000 600/700/800 VAX 7000 xxx 2GB M VAX 10000 600/700/800 VAX 10000 xxx 2GB M HSXXX Battery Failure Notification HS Array Controllers HSD05/10/30/40/50 HSJ30/40/50 HSZ10/15/40/50/70 HSG80 I/O Adapters DEMFA DEMNA KDM70 KZMSA KFMSA SHAC PAxxx PNxxx DEFAA DEFEA DEFZA DEFTA DEFAH MSCP DSA Disks RA60 RA70 RA71 RA72 RA73 RA80 RA81 RA82 RA90 RA92 MSCP DSSI Disks RF30 RF31 RF31F RF31T RF35 RF36 RF70 RF71 RF72 RF73 RF74 RFH31 RFH35 RFH36 RFH72 RFH73 RFH74 MSCP DSA Tapes TA78 TA79 TA81 TA85/TA857 TA86/TA867 TA90 TA90E TA91 TAD34 TAD44 TAD85 TAD86 TAD87 MSCP DSSI Tapes TF30 TF70 TF85 TF857 TF86 TF867 HSC Family The following HSC devices are recognized by DECevent. Their names will be displayed as controlling devices for appropriate disk and tape errors, but their own out-of-band events are not yet supported by DECevent. The HSC out-of-band events are now decoded but due to a problem in OpenVMS, some text may be truncated. HSC40 HSC50 HSC60 HSC65 HSC70 HSC90 HSC95 PCI Adapters KZPCM-DA PCI-Fiber Host Bus Adapter(KGPSA) Other Adapters CIXCD (also known as CIMNA) PCI Bus DE422-SA DWTVA SCSI Tapes TZ85\857 TZ86\867 TZ87\875\877 TZ88 SCSI Solid State Disks EZ31 - 100MB or 134MB Solid State Disk EZ32 - 200MB or 268.3MB Solid State Disk EZ33 - 300MB Solid State Disk EZ34 - 400MB Solid State Disk EZ35 - 500MB Solid State Disk EZ51 - 107MB Solid State Disk with Data Retention EZ52 - 214MB Solid State Disk with Data Retention EZ53 - 267MB Solid State Disk without Data Retention EZ54 - 428MB Solid State Disk with Data Retention EZ58 - 1.07GB Solid State Disk without Data Retention or 856MB Solid State Disk with Data Retention EZ64 - 475MB Solid State Disk EZ69 - 950MB Solid State Disk EZXX SCSI Disk Support RZ28L-AA Atlas II 2GB RZ28L-AS Atlas II 2GB RZ29L-AA Atlas II 4GB RZ29L-AS Atlas II 4GB RZ40-AA Atlas II 9GB RZ40-AS Atlas II 9GB RZ1BB-AS Atlas II 3GB RZ1BB-BA Atlas II 3GB RZ1BB-BS Atlas II 3GB RZ1BB-CA Atlas II 3GB RZ1BB-CS Atlas II 3GB RZ1CB-AS Atlas II 4GB RZ1CB-BA Atlas II 4GB RZ1CB-BS Atlas II 4GB RZ1CB-CA Atlas II 4GB RZ1CB-CS Atlas II 4GB RZ1DB-AS Atlas II 9GB RZ1DB-BA Atlas II 9GB RZ1DB-BS Atlas II 9GB RZ1DB-CA Atlas II 9GB RZ1DB-CS Atlas II 9GB RZ1EF-AA - 18.2GB 7200RPM Ultra Narrow 50 Pin RZ1EF-AB - 18.2 GB 7200RPM Ultra 50 Pin Narrow RZ1EF-AS - 18.2GB 7200RPM Ultra Narrow 50 Pin RZ1EF-BA - 18.2GB 7200RPM Ultra Wide 68 PIN RZ1EF-BB - 18.2 GB 7200RPM Ultra Wide 68 PIN RZ1EF-BS - 18.2GB 7200RPM Ultra Wide 68 PIN RZ1EF-CA - 18.2GB 7200RPM Ultra Wide 80 Pin SCA2 RZ1EF-CB - 18.2 GB 7200RPM Ultra Wide 80 Pin SCA2 RZ1EF-CS - 18.2GB 7200RPM Ultra Wide 80 Pin SCA2 Other Support DDR-Dynamic Device Recognition DSR-Dynamic System Recognition Host Based RAID 0 and 5 SCSI Devices RRDXX RWSXX RWZXX RX26 RX31 Generic Devices Generic DU (for example, MSCP disks not yet known by OpenVMS) Generic TU (for example, MSCP tapes not yet known by OpenVMS) NI SCA events OpenVMS Volume Shadow events (Phase II) MSCP Controllers KCM44 KDA50-Q KDB50 KFBTA KRQ50 RQDX1 RQDX3 RQDX4 UDA50 UDA05-A MSCP DSA Solid State Disks ESE20 ESE52 ESE56 ESE58 MSCP DSSI Solid State Disks EF51 EF52 EF53 EF54 EF58 MSCP DSA Optical Disks RV20 RV60 Other TMSCP Tapes/Controllers TBK70 TK50 TK50S TK50-DEBNT TK70 TQK50 TUK50 Other Tapes TKZXX Appendix F OpenVMS VAX Systems - Devices Supported for Analysis and Notification This appendix lists OpenVMS VAX operating systems and devices supported by the DECevent analysis and notification feature. MSCP DSA Disks RA60 RA70 RA71 RA72 RA73 RA80 RA81 RA82 RA90 RA92 MSCP DSSI Storage Disks RF30 HSXXX Battery Failure Notification HS Array Controllers HSD30/40/50 HSG80 HSJ30/40/50 HSZ40/50/70 There are 15 different areas of analysis that can be done on RAxx devices. Analysis support for RAxx devices is implemented for the following areas: 1. RA90/92 Special Analysis 2. SDI Communication Errors Analysis 3. Non-media Drive Detected Errors Analysis 4. Media Drive Detected Errors Analysis 5. Head Matrix Analysis 6. Bad Surface Analysis 7. Servo Failures Analysis 8. Head Slap Test Analysis 9. Random Read Path Analysis 10. Bad Head Analysis 11. Radial Scratch Analysis 12. Circumferential Scratch Analysis 13. Bad Spot Analysis 14. Possible Media Errors Analysis 15. Forced Error Analysis