DECevent Release Notes for OpenVMS Order Number: AA-QU68B-TE The DECevent Release Notes for OpenVMS provide general release information and restrictions for DECevent. DATE: January 1998 DECevent Version: V2.7 OpenVMS Alpha Version: V6.2 or higher OpenVMS VAX Version: V6.2 or higher Digital Equipment Corporation Maynard, Massachusetts ________________________ 1998 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 1998 Printed in U.S.A. All Rights Reserved. Alpha, CI, DEC, DEC 10000, DECevent, DECsystem, HSC, KDA, KDM, KRQ50, MicroVAX, RA, RQDX, RRD42, RV20, RX, RZ, TA, TK, TQK, TU, UDA, VAXserver, VAX, and the DIGITAL logo are trademarks of Digital Equipment Corporation. Contents Preface v CHAPTER 1 General Release Information 1.1 New Features or Code Repairs for this Release 1-1 1.1.1 Supported Products List Update 1-1 1.1.2 DECevent Error Log Entry Maximum Size Increased 1-1 1.1.3 FRU_TABLE Entry Causes Incorrect OpenVMS errorlog Entry 1-2 1.1.4 KNL File Internal Corruption 1-2 1.1.5 Analysis Database Locking Implemented 1-2 1.1.6 SYSLCK Privilege Now Necessary 1-2 1.1.7 DSNlink Notification Message Size Calculation Corrected 1-2 CHAPTER 2 Enhanced Features from Previous Versions 2.1 SYSLCK Privilege Necessary 2-1 2.2 Command Line Editing Available on OpenVMS in Interactive Mode 2-1 2.3 Ability to Quote Device Names to Flush Theories 2-2 2.4 Output of 'SHOW SETTINGS' Sorted 2-2 2.5 Test SICL Message Now Contains System Information 2-2 2.6 Starting Autoanalysis from GUI Is Disabled 2-2 2.7 GUI Time Selection Window Changes 2-3 2.8 Automatic Analysis Scavenges after System Crash 2-3 2.9 Privileges Needed to Execute "SAVE SYSTEM SETTINGS" Command 2-3 2.10 Obtaining DECevent Kits from the Digital Services Website 2-4 2.11 Changes to Report Output 2-4 2.12 IPMT Entries for DECevent 2-4 2.13 Starting DSNlink and Motif Processes and Images 2-4 2.14 Starting the DECevent Graphical User Interface (GUI) 2-4 2.15 Deleting Older Versions of Local Knowledge Files 2-5 2.16 Supported Devices 2-5 CHAPTER 3 Comparing DECevent and Previous Digital Fault Management Tools 3.1 Selection Criteria 3-1 3.2 Thresholding 3-1 3.2.1 Event Classes 3-2 3.2.2 Event Severity 3-2 3.2.3 Event Counting 3-2 3.2.4 Comparison of Event Counts with Thresholds 3-2 3.3 Autocopy 3-3 3.4 Cluster-Wide Support 3-3 3.5 Volume Labels 3-3 3.6 DECevent Translation of Multiple Input Files 3-3 CHAPTER 4 Known Restrictions for DECevent on OpenVMS Operating Systems 4.1 File Specification Restriction 4-1 4.2 Wildcard Restriction 4-1 4.3 DIRECTORY CANONICAL and DIRECTORY EVENT Command Restrictions 4-1 4.4 SHOW THRESHOLD Command Restriction 4-1 4.5 Analysis Restrictions 4-1 4.6 Local Settings File 4-2 4.7 Page File Quota Restriction 4-2 4.8 JTquota Restriction 4-2 4.9 /LOG Qualifier Restriction 4-2 4.10 /FSTERR Report Type Restriction 4-2 4.11 SET THRESHOLD/NAME Restriction 4-2 4.12 Evidence Support 4-2 4.13 /SINCE Parameter Restriction 4-2 4.14 /BEFORE and /SINCE Parameter Restrictions 4-3 4.15 RF74 Algorithm Incorrect 4-3 4.16 Distribution List Name Restrictions 4-3 4.17 RF31T Support 4-3 4.18 Command Restrictions with Automatic Analysis 4-3 4.19 DSNlink Message Size Exceeded 4-4 4.20 Set SICL Restriction and Command Procedure 4-4 4.21 Missing Information from the SHOW SUMMARY Command 4-4 CHAPTER 5 Known Restrictions for DECevent Specific to OpenVMS Operating Systems 5.1 Restriction When Translating Large Event Logs 5-1 CHAPTER 6 Known Restrictions for the Graphical User Interface (GUI) 6.1 Graphical User Interface User Guide For OpenVMS 6-1 6.2 GUI Startup Command 6-1 6.3 Text Entries 6-1 6.4 Multiple Input File Restriction 6-1 6.5 sys info Text Length Restriction 6-1 APPENDIX A OpenVMS Alpha Supported Devices for Bit To Text Translation A.1 Supported Devices for Bit To Text Translation A-1 A.2 Partial Device Support A-4 APPENDIX B OpenVMS Alpha Supported Devices for Analysis B.1 Supported Devices for Analysis and Notification B-1 B.2 Devices with Partial Analysis Support by DECevent B-2 APPENDIX C OpenVMS VAX Supported Devices for Bit To Text Translation C.1 Supported Devices for Bit To Text Translation C-1 C.2 Partial Device Support C-3 APPENDIX D OpenVMS VAX Supported Devices for Analysis D.1 Supported Devices for Analysis D-1 D.2 Devices with Partial Analysis Support by DECevent D-1 TABLES 4-1. Commands Requiring Prior Shutdown of Automatic Analysis 4-4 ___________________________________________________________________ Preface The DECevent Release Notes for 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 the current release of DECevent. ___________________________________________________________________ Intended Audience The DECevent Release Notes for OpenVMS are intended for use by system managers and service personnel who use DECevent software. ___________________________________________________________________ Documentation Conventions The following conventions are used in this manual: boldface Boldface type indicates the first instance of terms being type defined in text. italic Italic type indicates emphasis and complete manual titles. type Chapter 1 General Release Information This chapter provides information pertaining to the general use of the DECevent event management tool. 1.1 New Features or Code Repairs for this Release This release is primarily a knowledge release. 1.1.1 Supported Products List Update AlphaServer 8x00 5-6/625 Bit To Text and Analysis AlphaServer 8x00 version 4.0 FRU packet translation AlphaServer 800 5/[333,400,500] Bit To Text and Analysis AlphaServer 1000A 5/[300,333,400,500] Bit To Text and Analysis Qlogic 1038/1070 SCSI disk controller Bit To Text support PCI-SCSI Adapters (KZPSA/KZTSA) Bit To Text Memory Channel Adapter II Bit To Text 1.1.2 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. 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 evaluating the effort necessary to increase the DECevent maximum packet size to 64K, the current limit of DIGITAL Unix, in a future release. 1.1.3 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 to increase the following: (this requires a reboot to take effect) ERRORLOGBUFFERS = 64 (4 is default) ERLBUFFERPAGES = 32 (8 is default) Upgrade DECevent to version 2.6 or better. Rename errorlog.sys or 2) Shut down the system and set FRU_TABLE to OFF Reboot and rename errorlog.sys Upgrade DECevent to version 2.6 or better Other symptoms you may see from DECevent are as follows. Use the fix above 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. 1.1.4 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 utilized by other system applications, you should verify that installing this kit will not adversely affect those applications. Digital's Field Service engineers can obtain more information about this problem in Blitz[TD2203-a]. 1.1.5 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. 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. 1.1.6 Locking Extended to Include Mailing List and External Notification Commands After we provided 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 now 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 1.1.7 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 has been corrected in DECevent V2.7. 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 SYSLCK Privilege Now Necessary Users who utilize analysis commands now must have the SYSLCK privilege. 2.2 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 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.4 Output of 'SHOW SETTINGS' Sorted The output of the SHOW SETTINGS command 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.5 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.6 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 being displayed. The message indicates that Automatic Analysis must be started from the command line. Refer to the Analysis Guide for the details of this procedure. 2.7 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 trans- lation or analysis. The year range has been reduced to make the year scale easier to use. 2.8 Automatic Analysis Scavenges after System Crash As of DECevent V2.5, automatic analysis at startup will examine the system error log file to see if any entries are there that were missed. If it finds missed entries, they will be processed. It is no longer necessary to run manual analysis at system startup. 2.9 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 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.10 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.11 Changes to Report Output Within reports, text strings that may have previously contained non- printing control characters now will 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.12 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.13 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.14 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: $ DIAGNOSE/INTERFACE=DECW Refer to Chapter 5 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.15 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.16 Supported Devices Appendix A of these notes contains a list of all OpenVMS Alpha devices supported and recognized by DECevent's Bit To Text translation. Appendix B contains a list of all OpenVMS Alpha devices supported and recognized by the analysis and notification options of DECevent. Appendix C of these notes contains a list of all OpenVMS VAX devices supported and recognized by DECevent's Bit To Text translation. Appendix D contains a list of all OpenVMS VAX devices supported and recognized by the analysis and notification options of DECevent. When performing manual analysis and a SHOW TYPE command is issued for any operating system, unsupported tape and disk devices are displayed as UNSUP_TAP and UNSUP_DSK. Chapter 3 Comparing DECevent and Previous DIGITAL Fault Management Tools This chapter describes known differences between past fault management tools and DECevent. 3.1 Selection Criteria Selection criteria for the /INCLUDE and /EXCLUDE qualifiers differs between former fault management tools and DECevent. The following lists valid selection keywords for DECevent. /INCLUDE=(keyword=[val] [,...]) /EXCLUDE=(keyword=[val] [,...]) 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) 3.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. 3.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. 3.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 the following table: ___________________________________________________________________ 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 Time and volume mounts/dismounts. ___________________________________________________________________ 3.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. 3.2.4 Comparing Event Counts with Thresholds Once the event counts have been recalculated, DECevent compares them with the thresholds in the following manner: o 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. o If an error of any severity level exceeds the CUSTOMER threshold for that severity level, then DECevent initiates notification. 3.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. 3.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. 3.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. 3.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. Chapter 4 Known Restrictions for DECevent on OpenVMS Operating Systems This chapter describes known restrictions with this release of DECevent on Open VMS Alpha and OpenVMS VAX operating systems. Refer to Chapter 4 for DECevent restrictions specific to OpenVMS VAX operating systems. 4.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 4.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 4.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. 4.4 SHOW THRESHOLD Command Restriction The SHOW THRESHOLD command truncates the second theory number when multiple theories are called out. 4.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. 4.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. 4.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. 4.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. 4.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. 4.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. 4.11 SET THRESHOLD/NAME Restriction The SET THRESHOLD/NAME command works only for devices that have previously logged an event. 4.12 Evidence Support This release of DECevent does not currently provide evidence information in the analysis/notification reports. 4.13 /SINCE Parameter Restriction Using a colon (:) after the /SINCE parameter causes a syntax error and is not allowed. 4.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. 4.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. 4.16 Distribution List Name Restrictions When using the ADD USER command, the following words cannot be user names: CUSTOMER FSE MONITOR SICL 4.17 RF31T Support RF31T events are translated as RF31 events even though RF31 events have a different format. RF31T is unsupported for analysis. 4.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 4-1 lists the commands that require prior shutdown of automatic analysis before the command can be issued. Table 4-1. Commands Requiring Prior Shutdown Of Automatic Analysis ______________________________________________________ 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 ______________________________________________________ 4.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 4.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. 4.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 5 Known Restrictions for DECevent Specific to OpenVMS VAX Operating Systems This chapter describes known DECevent restrictions specific to OpenVMS VAX operating systems. 5.1 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 week. Chapter 6 Known Restrictions for the Graphical User Interface (GUI) This chapter describes known restrictions with this release of the DECevent GUI. 6.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. 6.2 GUI Startup Command Use the following command to start the Graphical User Interface for DECevent on OpenVMS systems: $ DIAGNOSE/INTERFACE=DECWINDOWS 6.3 Text Entries All text field entries must be terminated with a . 6.4 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. 6.5 sys info Text Length Restriction The text length fields in the sys info icon box are limited to 40 characters. Appendix A OpenVMS Alpha Supported Devices 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. A.1 Supported Devices for Bit To Text Translation DECevent Bit To Text translation supports the following systems and devices: Alpha Systems AlphaServer 800 5/xxx AlphaServer 8x00 5-6/625 AlphaServer 8x00 version 4.0 FRU packet translation AlphaServer 1000 4/200 AlphaServer 1000A 4/266 AlphaServer 1000A 5/300 AlphaServer 1000A 5/XXX AlphaServer 2000 4/200 AlphaServer 2000 5/325 AlphaServer 2000 5/375 AlphaServer 2000 5/400 AlphaServer 2000A 5/xxx AlphaServer 2100A 5/xxx AlphaServer 2100A RM 5/xxx AlphaServer 2100 5/xxx AlphaServer 2100 RM 5/375 AlphaServer 2100 4/xxx AlphaServer 4000 AlphaServer 4000A AlphaServer 4100 AlphaServer 8200 AlphaServer 8400 AlphaServer 8400 5/300 AlphaServer 8400 5/350 AlphaServer 8400 5-6/440 AlphaStation 200 4/166 AlphaStation 200 4/233 AlphaStation 400 4/233 AlphaStation 400 4/266 AlphaStation 500 AlphaStation 600 DEC 2000 400 DEC 2000 500 DEC 2000 700 DEC 2000 900 DEC 3000 400 DEC 3000 500 DEC 3000 700 DEC 3000 900 DEC 4000 DEC 7000 DEC 10000 PCI Adapters DWLPA DWLPB CCMPA PCI-SCSI Adapters (KZPSA/KZTSA) SCSI Solid State Disks EZ51R EZ54R SCSI Port Drivers AHA1740/1742A SIMPORT Qlogic 1038/1070 SCSI disk controller SCSI DISK Support DEC RZ28L-AA Atlas II 2GB DEC RZ29L-AA Atlas II 4GB DEC RZ40-AA Atlas II 9GB DEC RZ1BB-BA Atlas II 3GB DEC RZ1CB-BA Atlas II 4GB DEC RZ1DB-BA Atlas II 9GB DEC RZ1BB-CA Atlas II 2GB DEC RZ1CB-CA Atlas II 4GB DEC RZ1DB-CA Atlas II 9GB Quantum XP32275W Atlas II 2GB Quantum XP34550W Atlas II 4GB Quantum XP39100W Atlas II 9GB Quantum XP32275J Atlas II 2GB Quantum XP34550J Atlas II 4GB Quantum XP39100J Atlas II 9GB HSC Devices 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 HSC70 HSC50 HSC90 HSC60 HSC95 HSC65 HSZ70 HSG80 Other Adapters DSYT1 KFMSA KFMSB SHAC PAxxx PNxxx Memory Channel Adapter II HS Array Controllers HSJ30 HSJ40 HSD05 HSD10 HSD30 HSD40 HSZ40 HSG80 HSOF V3.1/V5.1 HSJ30/40/50 HSOF V3.1/V5.1 HSJ30/40/50 HSOF V3.1/V5.1 HSD30/50 HSOF V3.1/V5.1 HSZ20/40/50 HSOF V3.2/V5.2 HSZ40/50/70 HSOF V3.2/V5.2 HSD30/40/50 HSOF V3.2/V5.2 HSJ40/50 Internal Device Controllers CIXCD-AC Other Support DDR DSR Host Based RAID 0 and 5 I/O Adapters DEMFA DEMNA KDM70 KZMSA MSCP DSA Disks RA60 RA80 RA70 RA81 RA71 RA82 RA72 RA90 RA73 RA92 MSCP DSSI Disks RF30 RF70 RF31 RF71 RF31F RF72 RF35 RF73 RF31T MSCP DSA Tapes TA78 TA79 TA81 TA90 TA90E TA91 TA85/TA857 TA86/TA867 TA90E MSCP DSSI Tapes TF30 TF70 TF85 TF857 SCSI Tapes TZ85\857 TZ86\867 TZ87\875\877 TZ88 A.2 Partial Device Support The following systems and devices will be recognized if an event log entry is found in the event file. The device name will be displayed in the report with as much generic information as possibly translated from Bit To Text. Any remaining information will be displayed in hex. Generic Devices o Generic DU (for example, MSCP disks not yet known by OpenVMS) o Generic TU (for example, MSCP tapes not yet known by OpenVMS) o NI SCA events o OpenVMS Striping Events o OVMS Volume Shadow Events Alpha Systems/cpu DEC 2000 200 DEC 2000 300 DEC 3000 300 MSCP Controllers KCM44 KDA50-Q KDB50 KFBTA KZMSA for DSSI KRQ50 RQDX1 RQDX3 RQDX4 UDA50 UDA50-A MSCP DSA Solid State Disks ESE20 ESE52 ESE56 ESE58 MSCP DSSI Disks RF36 RFH3 RFH31 RFH35 RFH36 RFH72 RFH73 RFH74 MSCP DSSI Solid State Disks EF51 EF52 EF53 EF54 EF58 MSCP DSA Optical Disks RV20 RV60 MSCP DSA Tapes TAD34 TAD44 TAD85 TAD86 TAD87 MSCP DSSI Tapes TF86 TF867 Other TMSCP Tapes/Controllers TBK70 TK50 TK50-DEBNT TK70 TQK50 TUK50 Other Adapters DE422-SA DEFAA DEFTA DEFZA DEFEA DWTVA Appendix B OpenVMS Alpha Supported Devices for Analysis This appendix lists OpenVMS Alpha systems and devices supported by the DECevent analysis and notification feature. B.1 Supported Devices for Analysis and Notification DECevent analysis and notification supports the following systems and devices. Alpha Systems o AlphaServer 8x00 5-6/625 o AlphaServer 1000 4/200 o AlphaServer 1000A 4/266 o AlphaServer 4000 o AlphaServer 4100 o AlphaServer 8200 o AlphaServer 8400 o DEC 4000 o DEC 7000 o AlphaServer 82/8400 4Gb Memory o I/O Adapters o KDM70 o HSxxx Battery Failure Notification MSCP DSA Disks o RA72 o RA73 o RA90 o RA92 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 o RF30 o RF31 o RF31F o RF35 o RF70 o RF71 o RF72 o RF73 B.2 Devices with Partial Analysis Support by DECevent The following devices will have partial analysis support. For these devices, if a problem involves LED codes, DECevent will report "No Theory Found." MSCP DSA Disks o RA60 o RA70 o RA71 o RA80 o RA81 o RA82 Appendix C OpenVMS VAX Supported Devices 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. C.1 Supported Devices for Bit To Text Translation DECevent Bit To Text translation supports the following systems and devices: CPU's VAX 7000/10000 VAX 6000 400, 500, 600 HS Array Controllers HSD05 HSD10 HSD30 HSD40 HSJ30 HSJ40 HSC Controllers HSZ40 HSC40 HSC50 HSC60 HSC65 HSC70 HSC90 HSC95 I/O Adapters DEMFA DEMNA KDM70 KZMSA KFMSA SHAC PAxxx PNxxx DEFEA DEFZA DEFTA DEFAH MSCP DSA Disks RA60 RA80 RA70 RA81 RA71 RA82 RA72 RA90 RA73 RA92 MSCP DSSI Disks RF30 RF70 RF31 RF71 RF31F RF72 RF31T RF73 RF35 RF74 MSCP DSA Tapes TA78 TA79 TA81 TA90 TA90E TA91 MSCP DSSI Tapes TF30 TF70 TF85 TF857 HSC Devices 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 HSC70 HSC50 HSC90 HSC60 HSC95 HSC65 HSZ40 Other Adapters CIXCD (also known as CIMNA) HS Array Controllers HSD05 HSD10 HSD30 HSJ40 HSD40 HSZ40 HSJ30 HSD05 SCSI Tapes TZ85\857 TZ86\867 TZ87\875\877 TZ88 Other Support DDR-Dynamic Device Recognition DSR-Dynamic System Recognition Host Based RAID 0 and 5 C.2 Partial Device Support The following devices will be recognized if an error log entry is found in the event file. The device name will be displayed in the report with as much generic information as possibly translated from Bit To Text. Any remaining information will be displayed in hex. Generic Devices o Generic DU (for example, MSCP disks not yet known by OpenVMS) o Generic TU (for example, MSCP tapes not yet known by OpenVMS) o NI SCA events o 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 Disks RFH31 RFH35 RFH36 RFH72 RFH73 RFH74 MSCP DSSI Solid State Disks EF51 EF52 EF53 EF54 EF58 MSCP DSA Optical Disks RV20 RV60 MSCP DSA Tapes TA85/TA857 TA86/TA867 TAD34 TAD44 TAD85 TAD86 TAD87 MSCP DSSI Tapes TF86 TF867 Other TMSCP Tapes/Controllers TBK70 TK50 TK50-DEBNT TK70 TQK50 TUK50 Other Adapters DE422-SA DWTVA Appendix D OpenVMS VAX Supported Devices for Analysis This appendix lists OpenVMS VAX operating systems and devices supported by the DECevent analysis and notification feature. D.1 Supported Devices for Analysis DECevent analysis and notification supports the following devices: MSCP DSA Disks o RA72 o RA73 o RA90 o RA92 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 D.2 Devices with Partial Analysis Support by DECevent The following devices will have partial analysis support. For these devices, if a problem involves LED codes, DECevent will report "No Theory Found." MSCP DSA Disks o RA60 o RA70 o RA71 o RA80 o RA81 o RA82