Transcript
DECevent Event Management Utility for DIGITAL UNIX Installation Guide DATE:
April 1997
DECevent Version:
V2.4
DIGITAL UNIX Version:
3.0 or higher. Future maintenance releases may require higher versions.
This guide contains instructions for installing DECevent on a DIGITAL UNIX operating system. It also explains how to read the online release notes after installing the product. This document applies to DECevent V2.4 and all maintenance updates throughout that version.
1997 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Copyright © Digital Equipment Corporation 1997 All Rights Reserved. Printed in the United States of America. Alpha, DEC, DECevent, DIGITAL, DIGITAL UNIX, OpenVMS, VAX, VMS, and the DIGITAL logo are trademarks of Digital Equipment Corporation. All other trademarks and registered trademarks are the property of their respective holders. 1
Contents PREFACE
CHAPTER 1 PREPARING FOR DECEVENT INSTALLATION
v 1–1
1.1
RELEASE NOTES
1–1
1.2
LICENSE REGISTRATION
1–1
1.3
CHECKING THE MEDIA SOFTWARE DISTRIBUTION KIT
1–1
1.4
PREINSTALLATION REQUIREMENTS 1.4.1 Checking Login Privileges 1.4.2 Hardware Requirements 1.4.3 Software Requirements 1.4.4 Determining Which Subsets to Load 1.4.5 Subset Space Requirements 1.4.6 Determining if Sufficient Space Exists for Installation
1–2 1–2 1–2 1–2 1–2 1–3 1–3
1.5
BACKING UP YOUR SYSTEM DISK
1–4
1.6
STOPPING THE INSTALLATION
1–4
1.7
ERROR RECOVERY
1–4
CHAPTER 2 INSTALLING DECEVENT SOFTWARE 2.1
INSTALLING DECEVENT FROM THE DISTRIBUTION MEDIA 2.1.1 Log In as Superuser 2.1.2 Mount the Media on the Appropriate Drive 2.1.3 Enter the setld Command 2.1.4 Select Subsets
2.2
POSTINSTALLATION PROCEDURES 2.2.1 Automatic Analysis 2.2.2 Enabling SICL 2.2.3 Disabling SICL
CHAPTER 3 DEINSTALLING DECEVENT 3.1
DELETING DECEVENT FROM YOUR SYSTEM
CHAPTER 4 UPDATING KNOWLEDGE LIBRARIES FOR DEVICE SUPPORT
2–1 2–1 2–2 2–2 2–2 2–2 2–8 2–8 2–9 2–10 3–1 3–1 4–1
4.1
INTRODUCTION
4–1
4.2
KNL UPDATE EXAMPLE
4–1
iii
Contents APPENDIX A FILES INSTALLED ON YOUR SYSTEM
A–1
APPENDIX B FILE HIERARCHY
B–1
APPENDIX C EXAMPLE DECEVENT INSTALLATION AND DEINSTALLATION LOGFILES
C–1
C.1
EXAMPLE DECEVENT INSTALLATION
C–1
C.2
EXAMPLE DECEVENT DEINSTALLATION
C–5
TABLES
iv
1
Conventions
1–1
DECevent Subsets
vi
1–2
Disk Space Requirements for Optional DECevent Subsets
1–3
A–1
Installed DECevent Files
A–1
1–3
Preface
This guide describes how to install the DECevent software on Alpha processors that are running the DIGITAL UNIX operating system software. The installation procedure creates DECevent directories subordinate to the /opt, /usr/opt, and /var/opt directories and loads DECevent software subsets.
Intended Audience This guide is intended for system managers who install DECevent.
Manual Structure This manual is organized as follows: • • • • • • •
Chapter 1—Describes how to prepare for the installation of the DECevent event management utility. Chapter 2 —Describes how to install the DECevent event management utility from the distribution media as well as post-installation procedures you must follow. Chapter 3—Describes how to deinstall the DECevent event management utility. Chapter 4—Describes how to update DECevent knowledge libraries for device support. Appendix A—Lists and describes the DECevent related files installed on your system after DECevent has been installed. Appendix B—Contains artwork that depicts the DECevent event management utility file hierarchy as well as a description of the file hierarchy. Appendix C—Contains examples of the DECevent event management utility installation and deinstallation logfiles.
Associated Manuals In addition to this guide, the DECevent documentation set includes the following manuals: •
•
•
DECevent Translation and Reporting Utility for DIGITAL UNIX User and Reference Guide—AA-QAA3C-TE This user guide details commands for the bit-to-text translation of events. DECevent Analysis and Notification Utility for DIGITAL UNIX User and Reference Guide—AA-QAA4C-TE This user guide details commands for the analysis and notification features of DECevent. DECevent Release Notes for DIGITAL UNIX Users—AA-QAA6C-TE These release notes are also available in ASCII format.
v
Preface •
The DECevent Graphical User Interface User’s Guide—AA-QE26C-TE This user guide is intended for those users that prefer a graphical user interface (GUI) when using DECevent.
Conventions The following conventions are used in this guide:
Table 1: Conventions
vi
Convention
Meaning
UPPERCASE and lowercase
The DIGITAL UNIX system differentiates between lowercase and uppercase characters. Literal strings that appear in text, examples, syntax descriptions, and function descriptions must be entered exactly as shown.
user input
This bold typeface is used in interactive examples to indicate input entered by the user. In the online Bookreader version, user input also appears in a bold font.
system output
This typeface is used to indicate system output or the exact name of a command, option, partition, pathname, directory, or file.
%
The percent sign (%) is the default user prompt.
#
A number sign is the default superuser prompt.
(Ctrl/X)
In procedures, a sequence such as (Ctrl/X) indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
Chapter 1 Preparing for DECevent Installation
Before starting the installation procedures in Chapter 2, complete the preparation requirements outlined in this chapter.
1.1 Release Notes Your documentation includes the DECevent Release Notes for DIGITAL UNIX Users. Read these release notes before using this product. DECevent provides both hardcopy and online release notes. The release notes may contain critical information about changes to the application. The online DECevent Release Notes are located in the following directory: /usr/share/doclib/DIA240 To gain access to the online release notes, install any of the DIADOC230 subsets, provided in PostScript, ASCII text, and Bookreader formats. Refer to Section 2.1.4 for instructions on installing these subsets.
1.2 License Registration The License Product Authorization Key (License PAK) must be registered in the License Database (LDB) in order to use the analysis and notification features of DECevent on a newly licensed node. The PAK is not needed to run the translation feature of DECevent. Registration is performed as a post-installation procedure.
1.3 Checking the Media Software Distribution Kit Use the Bill of Materials (BOM) to check the contents of your DECevent software distribution kit. Contact your DIGITAL representative if the kit is damaged or incomplete.
Preparing for DECevent Installation 1–1
1.4 Preinstallation Requirements This section discusses various requirements that must be met before installing DECevent. Installing DECevent on your DIGITAL UNIX operating system takes 5 to 10 minutes. NOTE You must deinstall previous versions of DECevent on your system before installing a new version. Follow the instructions contained in Chapter 3.
1.4.1 Checking Login Privileges You must be able to log on as a superuser (root) on the system where you are installing DECevent. Only when you are logged on as a superuser do you have sufficient privileges to install the DECevent software.
1.4.2 Hardware Requirements DECevent installs on any Alpha system running the DIGITAL UNIX operating software.
1.4.3 Software Requirements DECevent V2.4 requires the DIGITAL UNIX operating system Version 3.0 or higher. Future DECevent releases may require higher versions of the operating system, as described in the online release notes, the README file, or the cover letter. DECevent also requires the DIGITAL UNIX Base System subset (OSFBASE) to be loaded on the system where you will install it. To check whether the subset is loaded, do the following: 1. Log in to the system where you will install DECevent. 2. Enter the following command: # /usr/sbin/setld -i | grep OSFBASE
Check the displayed rows for the name of the relevant subset and any patches. When a subset is loaded, the word installed appears in a row after the subset identifier. If the word installed does not appear (the second column in a row is blank), the subset or patch is not loaded. In this case, you must load the missing DIGITAL UNIX software before installing DECevent.
1.4.4 Determining Which Subsets to Load DECevent consists of one required subset, DIABASE230, and three optional subsets which contain the DECevent documentation kit. These subsets are described in Table 1–1.
1–2 Preparing for DECevent Installation
Table 1–1: DECevent Subsets Subset
Description
Status
DIABASE230
DECevent Base Kit Translation and Analysis
Mandatory
DIADOCTXT230
DECevent text documentation files
Optional
DIADOCPS230
DECevent postscript documentation files
Optional
DIADOCBOOK230
DECevent Bookreader documentation files
Optional
Refer to Section 2.1.4 for information on installing these software subsets.
1.4.5 Subset Space Requirements The installation procedure creates DECevent directories subordinate to the /opt, /usr/opt, and /var/opt directories and loads DECevent software subsets. The disk space requirements, in bytes, for the /opt directory is 1.3K bytes. The /usr/opt directory requires 18,517K bytes of disk space and the /var/opt directory requires 44K bytes of disk space. Table 1–2 identifies in bytes the disk space required to load each optional DECevent software subset. Table 1–2: Disk Space Requirements for Optional DECevent Subsets Subset
Location
Byte Size
DIADOCTXT240
/usr/opt/DIA240/share/doclib/DIA240/txt
507159
DIADOCPS240
/usr/opt/DIA240/share/doclib/DIA240/ps
3040224
DIADOCBOOK240
/usr/opt/DIA240/share/doclib/DIA240/book
3600031
1.4.6 Determining if Sufficient Space Exists for Installation Use the following procedure to determine if enough free space exits to install the DECevent subsets: 1. Determine the available space on your drive. For each directory listed in Section 1.4.5, issue the following command: # df directory
Preparing for DECevent Installation 1–3
For each specified directory, the program will display size and location data. For example: # df /var/opt Filesystem 512-blocks Used Avail Capacity Mounted on /dev/rz0h 810952 132978 596878 18% /var # df /usr/opt Filesystem 512-blocks Used Avail Capacity Mounted on /dev/rz3c 1983846 968620 816840 54% /usr # df /opt Filesystem 512-blocks Used Avail Capacity Mounted on /dev/rz3c 1983846 945730 839730 53% /
2. Compare the space available with the space required. The free space identified under the "Available" column must accommodate the size requirements identified in Section 1.4.5. For example, MOUNT POINT ----------/opt /usr/opt /var/opt
AVAILABLE --------32386 839730 596878
REQUIRED -------1.3K bytes 18,517K bytes 44K bytes
NOTE If not enough space exists, see DIGITAL UNIX System Administration (AA-PS2RDTE) for further instructions.
1.5 Backing Up Your System Disk DIGITAL recommends that you back up your system disk before installing any software. For details on performing a system disk backup, see your DIGITAL UNIX documentation.
1.6 Stopping the Installation You can stop the installation procedure any time by using Ctrl/C. Files created up to this point are not deleted automatically. You must delete these files interactively. Appendix A lists the files and directories created during the installation procedure.
1.7 Error Recovery If errors occur during the installation, the system displays failure messages. If the installation fails due to insufficient disk space, the following message appears for the appropriate subset: There is not enough file system space for subset DIABASE240. DIABASE240 will not be loaded.
Errors can occur during the installation if any of the following conditions exist: •
The operating system version is incorrect.
1–4 Preparing for DECevent Installation
•
The system parameter values for successful installation are insufficient, meaning not enough disk space on a partition.
For descriptions of error messages generated by these conditions, see the DIGITAL UNIX documentation on system messages, recovery procedures, and DIGITAL UNIX software installation. For information on system software requirements, see Section 1.4.3.
Preparing for DECevent Installation 1–5
Chapter 2 Installing DECevent Software
This chapter describes the DECevent installation procedure. Before starting the installation, read Chapter 1, which describes general information and requirements for installing the product.
2.1 Installing DECevent from the Distribution Media The following sections describe the procedure for installing DECevent from the distribution media and provides examples of prompts and displays. NOTE A product authorization key (PAK) license is required in order to utilize the DECevent analysis and notification added-value options. The license is obtained by a DIGITAL Customer Services engineer through the technical information management architecture (TIMA) and must be installed on your system prior to kit installation. To find the DECevent service PAK in TIMA, select the TIMA tools database and search for "DECEVENT PAK". The title of the tool you need is "Service Tools Product Authorization Key (PAK) Distribution Tool". Refer to TIMA documentation for specifics. In addition, customers may acquire the PAK information by requesting the PAK from DSNlink hardware support. Licenses are verified at run time by the License Management Facility (LMF). For more information on LMF concepts and operation, enter the HELP LICENSE command at the DCL ($) prompt. NOTE If a version of DECevent software prior to V2.1 was installed on the system, all users must delete the local knowledge library, $HOME/FMG_LOCAL_PARAM_LIBRARY.KNL, from their home directory after installing a new version of DECevent. Failure to delete the older, incompatible knowledge library causes the new version of DECevent to fail during initilization.
Installing DECevent Software
2–1
2.1.1 Log In as Superuser Log in as superuser and set default directory to root (/): % su Password:
# cd / # pwd / #
2.1.2 Mount the Media on the Appropriate Drive Make sure your installation tape is mounted and on-line. If you are installing DECevent from a CD ROM, make sure the CD is inserted into the CD ROM drive.
2.1.3 Enter the setld Command For local (node-specific) installations from a tape, enter the following command: # setld -l device_name
For example, for the device /dev/rmt0h: # setld -l /dev/rmt0h
For installations from a CD ROM drive, perform the following steps: # /sbin/mount -r /dev/rz4c /mnt #cd mnt # ls DIA_UNXAXP_SSB240 lost+found # cd DIA* ls # DIA.image DIADOCBOOK240 DIADOCTXT240 SPACE DIABASE240 DIADOCPS240 INSTCTRL instctrl # /usr/sbin/setld -l .
2.1.4 Select Subsets # setld -l /dev/rmt0h
or for CD ROM installations: # /usr/sbin/setld -l . *** Enter subset selections *** The following subsets are mandatory and will be installed automatically unless you choose to exit without installing any subsets: * DECevent Base kit (Translation / Analysis) The subsets listed below are optional:
2–2 Installing DECevent Software
There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) DECevent Optional book reader documentation files 2) DECevent Optional postscript documentation files 3) DECevent Optional text documentation files Or you may choose one of the following options: 4) 5) 6) 7)
ALL mandatory and all optional subsets MANDATORY subsets only CANCEL selections and redisplay menus EXIT without installing any subsets
Enter your choices or press RETURN to display menus.
If you specify more than one number at the following Choices prompt, separate each number with a space, not a comma. Choices (for example, 1 2 4-6): 5
Next, the installation script lets you verify your choice. For example, if you enter 5 in response to the Choices prompt, you see the following display: You are installing the following mandatory subsets: DECevent Base kit (Translation / Analysis) Is this correct? (y/n): y DECevent Base kit (Translation / Analysis) Copying from . (disk) Working...Wed Oct 23 04:20MDT 1996 Verifying DECevent subset DIABASE240 has been successfully loaded. Event log translation is set up for this node. If you have a Product Authorization Key for analysis issue the following command after the installation is complete: /usr/sbin/diasetup Configuring "DECevent Base kit (Translation / Analysis)" (DIABASE240) Converting the /var/opt/DIA240/DIA/FMG_ANA__PRM_STATE_DB.KNL to new KNL format... File ’var/opt/DIA240/DIA/FMG_ANA__PRM_STATEDB.OLD_KNL’ is already a Version 3.x KNL Restoring the previous Permanent State Database. Found a local settings KNL. Renaming it to //FMG_LOCAL_PARAM_LIBRARY.OLD_KNL
If you do not have DSNlink installed on your system, the following message appears: You currently do not have DSNlink installed on this system. Without DSNlink, you cannot take full advantage of DECevent’s Notification capabilities. DECevent functions properly without DSNlink. However, DECevent cannot notify the Customer Support Center when problems are found (notifications are sent locally). Notifying the Customer Support Center greatly enhances DECevent’s diagnosis capability and enables DIGITAL to service your hardware problems automatically without onsite intervention when problems are found.
Installing DECevent Software
2–3
Contact your local DIGITAL service engineer about installing DSNlink.
If DSNlink is installed on your system, the previous message is not displayed and the verification process starts. The verification process (IVP) starts whether or not DSNlink is installed. If you have a Product Authorization Key (PAK) installed on your system enabling automatic analysis, the IVP performs four steps. The first step is a bit-to-text verification and is shown next. Performing DECevent Installation Verification Procedure Output of DECevent bit to text IVP: DECevent V2.4 ************************* ENTRY 1 *********************** Logging OS System Architecture Event sequence number Timestamp of occurrence Host name
2. Digital UNIX 2. Alpha 3. 13-JAN-1995 12:08:06 fluid
System type register x00000002 Number of CPUs (mpnum) x00000001 CPU logging event (mperr) x00000000 Event validity Event severity Entry type
DEC 4000
1. O/S claims event is valid 1. Severe Priority 100. CPU Machine Check Errors
CPU Minor class
1. Machine check (670 entry)
Frame Revision SCB Vector FRU 1 FRU 2 Severity CPU ID Error Count Threshold For Fail Code Fail Code Error Flag 1 Error Flag 2
x0001 x0670 Processor Machine Check Abort x00 Field Not Valid x00 Field Not Valid x0000 Field Not Valid x0001 x0000 x0000 x0000 x0000000000200000 CPU_1 Cache TAG Parity Error x0000000000000000
frame id byte count
x00000000 x00000000
End of Frame
The second step of the verification procedure, shown below, only appears if a Product Authorization Key (PAK) is installed on your system, allowing you to perform analysis on supported devices. Output of DECevent Analysis
IVP:
DECevent V2.4 The optional, licensed software to perform analysis and/or notification is enabled. Copyright
(c)
Digital Equipment Corporation, All Rights Reserved.
2–4 Installing DECevent Software
This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation ("DIGITAL"). This software has been installed and enabled to enhance the maintenance services provided by DIGITAL. Use of this software by anyone other than DIGITAL maintenance personnel is not permitted without a license. Customers who have signed a DIGITAL Service Agreement ("Agreement") have been granted such a license for their own use on equipment covered by the Agreement. Any other use, copying or license to any other party whatsoever is not permitted. DIGITAL reserves the right to remove or disable this software at its discretion. U.S. Pat. 5,469,463.
Installing DECevent Software
2–5
DECevent Notification Report DECevent has detected that the following device needs attention: DEVICE: NODE: SYSTEM SERIAL NUMBER: SYSTEM TYPE:
fluid
DEC_4000 N/A N/A N/A
DECevent Diagnosis Information Digital Services Device: Error: Count:
fluid N/A 0
Theory:
30F2C.14-1:2;1
Evidence:
TBD
Time Of Error:
DEC_4000
95-01-13 12:08:06
The above analysis IVP notification report is produced through an event log, supplied with the installation, for testing purposes only. The event log is deleted upon completion of a successful installation. The third part of the IVP, shown below, tests the Show Settings command. Output of DECevent show settings IVP: DECevent V2.4 Current Settings Information: Name Value ==================================================================== CMD_TRACE 0 CTR_TRACE 0 DEBUG_STATE 0 ETC_TRACE 0 FMG__DEBUG_STATE 0 FMG__TRACE_STATE 0 RPT_TRACE 0 TRACE_STATE 0 CTR__DMP_RUL ROOT.DUMP_EVENT_CA CTR__RUL_LIB CTR__DEF_RUL_LIB CTR__SUM_LIB CTR__DEF_SUM_LIB DEF_CTR_RULE ROOT.HEADER_CA DEF_ETC_RULE ROOT.HEADER_EV.OSF_HEADER_EV ETC__DMP_RUL ROOT.DUMP_EVENT_EV ETC__RUL_LIB ETC__DEF_RUL_LIB ETC__SEL_LIB ETC__DEF_SEL_LIB RPT__RUL_LIB RPT__DEF_RUL_LIB HELP_FILE FMG_HELP_FILE CURRENT_CLI UNIX VMS_DEFAULT /TRANSLATE UNIX_DEFAULT -a CHEROKEE_VMS_DEFAULT /TRANSLATE DEF_EVT_LOG /usr/amd/binary.errlog LOCALE AMERICAN_ENGLISH PRINT_MESSAGES 7 STREAM_SIZE 20 SYS_ACT_LOG_NAME DIA_ACTIVITY.LOG KNL__DEF_ENTRIES 32 KNL__LIB_DIRECTORY DIA_LIBRARY KNL__LIB_PREFIX FMG_ KNL__LIB_SUFFIX .KNL
2–6 Installing DECevent Software
VAX_VMS_STACK_SIZE VAX_VMS_GUARD_SIZE ALPHA_VMS_STACK_SIZE ALPHA_VMS_GUARD_SIZE RULE_MAX_BYTECNT DEFAULT_REPORT ANA_TRACE NOT_TRACE ANA__FAC_DB ANA__PRM_DB ANA__RUL_LIB ANA__TMP_DB NOT__RUL_LIB NOT__MAIL_LIB NOT__EXTERNAL_LIB FMG__CUST_PROFILE FMG_VERSION SICL_STATE SICL_PROTOCOL_VERS AUTO_COPY ANALYSIS_TRIGGER_AUTOMATIC ANALYSIS_TRIGGER_MANUAL NOT__DEF_CSC_PHONE NOT__MAX_DSNLNK_MSG MAIL_DEBUG
10 3 50 30 100000 FULL_RE 0 0 ANA__FAC_STATE_DB ANA__PRM_STATE_DB ANA__DEF_RUL_LIB ANA__TMP_STATE_DB NOT__DEF_RUL_LIB NOT__DEF_MAIL_LIB NOT__DEF_EXTERNAL_LIB /usr/sbin/DIA120/FMGPROFILE 2.2 OFF 1 OFF AUTOMATIC MANUAL 1-800-354-9000 59 0
The fourth part of the IVP tests the Show Parameters command. This step in the verification process only appears if a PAK is installed on your system. Output of DECevent show parameters IVP: DECevent V2.4 The optional, licensed, software to perform analysis and/or notification is enabled. Copyright
(c)
Digital Equipment Corporation,
All Rights Reserved.
This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation ("DIGITAL"). This software has been installed and enabled to enhance the maintenance services provided by DIGITAL. Use of this software by anyone other than DIGITAL maintenance personnel is not permitted without a license. Customers who have signed a DIGITAL Service Agreement ("Agreement") have been granted such a license for their own use on equipment covered by the Agreement. Any other use, copying or license to any other party whatsoever is not permitted. DIGITAL reserves the right to remove or disable this software at its discretion. U.S. Pat. 5,469,463. Analysis Notification Parameters: PHONE NUMBER SICL
Customer Service Phone Number is System Initiated Call Logging is
1-800-354-9000 OFF
SYSTEM INFO
System Info for garcia.cxo.dec.com Serial Number 1234567 System Type DEC2000_300
DECevent IVP completed successfully
Installing DECevent Software
2–7
The verification procedure is complete at this point and the installation script continues. You must define the following environmental variable in order to use this product: csh> setenv DIA_LIBRARY /var/DIA or sh> DIA_LIBRARY=/var/DIA sh> export DIA_LIBRARY #
NOTE Upon completion of this installation script, as shown after the IVP verification procedure above, you must define an environmental variable in order for the GUI to find and access the DECevent knowledge library (KNL) files. Use one of the the following commands as shown previously: setenv DIA_LIBRARY /var/DIA
If you are using the Bourne Shell, use the following commands to define the environmental variable: >DIA_LIBRARY=/var/DIA >export DIA_LIBRARY
The DECevent installation procedure is now complete. Remember to define the proper environmental variable for GUI access and to issue the diasetup command to enable analysis. These steps are detailed again in the following post-installation section. If, during the course of the installation, you encounter errors from the setld utility, see the Diagnostics section of the setld(8) reference page for an explanation of the error and the appropriate action to take.
2.2 PostInstallation Procedures You must perform the following post-installation procedures to start automatic analysis, enable SICL, or disable SICL. These steps are not required for translation support.
2.2.1 Automatic Analysis Type the following command at the system prompt: # diasetup
The post-installation procedure responds with the following: Could not find file DECevent_OSF.PAK Name of the file containing the DECevent PAK: decevent.pak Checking for previous DECevent PAK... No entry in license database for this product New License Date:
1-JAN-1997
Unloading and deleting DECEVENT No entry in license database for this product
2–8 Installing DECevent Software
Registering DECEVENT Loading DECEVENT
Enter system serial number for this host (garcia): AB2400A19H
NOTE You must enter the system specific serial number of the host on which DECevent is being installed. Check your DIGITAL service contract for the host name under contract or contact your Field Service engineer. DECevent V2.4 DECevent’s automatic analysis can now be started. If you do not want to start automatic analysis now the following command can be issued later: dia stup garcia.cxo.dec.com > /var/DIA/garcia.cxo.dec.com.log& For more information on the use of DECevent, see the user guide and/or issue "man dia".
NOTE The preferred method for startup is to use the above startup file, not the command line command, as noted in the DECevent Analysis and Notification Utility for DIGITAL UNIX User and Reference Guide. Do you wish to startup automatic analysis now? (y/n): y PLEASE NOTE: DECevent is set up to do analysis on this machine. For more information on the use of DECevent, see the user guide and/or issue "man dia". The installation of DECevent analysis is now complete.
Automatic analysis is enabled at this point in the post-installation procedure.
2.2.2 Enabling SICL The post-installation procedure continues, allowing you to enable SICL, which requires DSNlink be installed on your system. Type the following command at the system prompt: # enable_sicl
The post-installation procedure responds with the following: This procedure is used to ENABLE the DECevent SICL capabilities. SICL (System Initiated Call Logging) causes the DECevent software to log service calls with a DIGITAL Customer Support Center when repair actions are required for a particular device.
Do you wish to continue? (y/n or ? for help): y Is SICL to be ENABLED at this site? (y/n/or ? for help): y
Installing DECevent Software
2–9
In order to properly handle SICL data at the DIGITAL CSC, system serial numbers must be accurately entered in the DECevent database. The following information was found in the DECevent database: Your current DECevent System Information Settings are: DECevent V2.4 Analysis Notification Parameters: PHONE NUMBER SICL
Customer Service Phone Number is System Initiated Call Logging is
1-800-354-9000 OFF
SYSTEM INFO
System Info for garcia.cxo.dec.com Serial Number 1234dbwd System Type DEC3000_500
Is the DECevent information complete and correct? (y/n/or ? for help):y SICL requires that DSNlink software be installed and that this site is registered for SICL with the appropriate Customer Support Center (CSC). Is DSNlink installed at this site? (y/n/or ? for help): y Enter customer profile filename (? for help): myprofile dia> _DIAGNOSE-INF: This modification is only saved for the current session dia> dia> Current Settings Information: Name Value ============================================ SICL_STATE ON dia> DECevent SICL enable program terminated successfully.
SICL has been enabled at this point in the post-installation procedure.
2.2.3 Disabling SICL If you want to disable SICL at any time, enter the following command at the system prompt: # disable_sicl
The post-installation procedure responds with the following, allowing you to disable SICL: This procedure is used to DISABLE the DECevent SICL capabilities. SICL (System Initiated Call Logging) causes the DECevent software to log service calls with a DIGITAL Customer Support Center when repair actions are required for a particular device. If automatic analysis is currently running it will be temporarily shutdown for the duration of this command procedure. Is SICL to be DISABLED at this site? (y/n/or ? for help): y
2–10 Installing DECevent Software
Will now prevent DECevent from logging SICL calls to the CSC DECevent V2.4 dia> _DIAGNOSE-INF: This modification is only saved for the current session dia> dia> Current Settings Information: Name Value ============================================== SICL_STATE OFF dia> DECevent SICL disable program terminated successfully.
NOTE For more information on using the translation features of DECevent, see the DECevent Translation and Reporting Utility for DIGITAL UNIX User and Reference Guide. For more information on using the analysis and notification features of DECevent, see the DECevent Analysis and Notification Utility for DIGITAL UNIX User and Reference Guide. Enter the man dia command at the system prompt for DECevent online help.
Installing DECevent Software 2–11
Chapter 3 Deinstalling DECevent
This chapter describes the DECevent deinstallation procedure.
3.1 Deleting DECevent from Your System If you must remove a version of DECevent 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: # setld -i | grep ’DIA.* DIABASE240 installed DIADOCBOOK240 installed DIADOCPS240 installed DIADOCTXT240 installed
installed’ DECevent Base kit DECevent Optional DECevent Optional DECevent Optional
(Translation/Analysis) book reader documentation postscript documentation text documentation
4. Look for the word installed in the listing produced, then delete the installed subsets with the following command: # setld -d DIABASE240 DIADOCBOOK240 DIADOCPS240 DIADOCTXT240 Deleting "DECevent Optional book reader documentation files" (DIADOCBOOK240). Deleting "DECevent Optional postscript documentation files" (DIADOCPS240). Deleting "DECevent Optional text documentation files" (DIADOCTXT240). Deleting "DECevent Base kit (Translation / Analysis)" (DIABASE240).
Deinstalling DECevent 3–1
The system will then verify the deletion of each subset. Refer to Appendix C for an example of the procedure for deleting the DECevent subsets. The program will report the progress of the deletion and removal of all specified subsets.
3–2 Deinstalling DECevent
Chapter 4 Updating Knowledge Libraries for Device Support
4.1 Introduction DECevent knowledge libraries contain the necessary information about devices supported by DECevent thus enabling translation, reporting and analysis on those devices. DECevent allows you to update knowledge libraries by installing a .KNL (knowledge library) update kit. This chapter shows an example of a .KNL update kit installation.
4.2 KNL Update Example Start the .KNL update installation procedure by entering, at the system prompt, the setld -l command followed by the name of the .KNL update kit as shown below. The system responds with information relevant to the .KNL update procedure. # setld -l DIAKNL_UNXAXP_231
The KNL update continues by displaying the subsets available to you in the KNL update kit. Note the DECevent KNL update kit is listed as a mandatory subset and will be installed if you choose option 3 in the menu, allowing all mandatory and optional subsets to be installed. *** Enter subset selections *** The following subsets are mandatory and will be installed automatically unless you choose to exit without installing any subsets: * DECevent KNL update kit The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) DECevent rel notes, postscript 2) DECevent rel notes, text 3) 4) 5) 6)
ALL mandatory and all optional subsets MANDATORY subsets only CANCEL selections and redisplay menus EXIT without installing any subsets
Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 3
Updating Knowledge Libraries for Device Support 4–1
You are installing the following mandatory subsets: DECevent KNL update kit You are installing the following optional subsets: DECevent rel notes, postscript DECevent rel notes, text Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. DECevent KNL update kit Copying from DIAKNL_UNXAXP_231 (disk) Verifying DECevent rel notes, postscript Copying from DIAKNL_UNXAXP_231 (disk) Verifying DECevent rel notes, text Copying from DIAKNL_UNXAXP_231 (disk) DECevent subset DIAKNL231 has been successfully loaded. Event log translation is set up for this node. Configuring "DECevent KNL update kit" (DIAKNL231) Performing DECevent Installation Verification Procedure Output of DECevent bit to text IVP:
At this point in the KNL update, the DECevent Installation Verification Procedure (IVP) is run to ensure successful bit-to-text translation, to ensure a Product Authorization Key (PAK) is installed to support analysis, to ensure proper settings for DECevent, and to ensure proper parameters are set, if a PAK is installed, for DECevent to function correctly. The IVP is shown in Chapter 2 and will not be shown here. Performing DECevent Installation Verification Procedure . . . DECevent IVP completed successfully You must define the following environmental variable in order to use this product: csh> setenv DIA_LIBRARY /var/DIA or sh> DIA_LIBRARY=/var/DIA sh> export DIA_LIBRARY If you have a Product Authorization Key for analysis, issue the following command to start automatic analysis: /usr/sbin/diasetup Configuring "DECevent rel notes, postscript" (DIADOCPS231) Configuring "DECevent rel notes, text" (DIADOCTXT231) #
The KNL update kit installation is now complete.
4–2 Updating Knowledge Libraries for Device Support
Appendix A Files Installed on Your System
Table A–1 shows where DECevent files actually reside. The files are softlinked back to corresponding positions in the operating system. Table A–1 describes the contents of DECevent directories. Table A–1: Installed DECevent Files Subset
Directory
DIABASE240 DIADOCTXT240
/usr/opt/DIA240/share/man/man8 dia.8 /usr/opt/DIA240/share/doclib/DIA240 README
DIABASE240
/opt/DIA240/sbin/init.ddia_s_k
Startup/Shutdown script
DIABASE240
Disable sicl
DIABASE240
/usr/opt/DIA240/sbin disable_sicl /usr/sbin enable_sicl /usr/sbin dia /usr/opt/DIA240/lib/DIA DEC_4000.BIN
DIABASE240
/usr/opt/DIA240/lib/DIA DEC_7000.BIN
Analysis knowledge file
DIABASE240
/usr/opt/DIA240/lib/DIA AXP_SYS9_EV4.BIN
Analysis knowledge file
DIABASE240
/usr/opt/DIA240/lib/DIA AXP_SYS9_EV5.BIN
Analysis knowledge file
DIABASE240
/usr/opt/DIA240/lib/DIA AXP_SYS12_EV5.BIN
Analysis Knowledge file
DIABASE240 DIABASE240
File
Description Help files Informational README file.
Enable sicl Image file Analysis knowledge file
Files Installed on Your System A–1
Table A–1 (Cont.): Installed DECevent Files Subset
Directory
File
DIABASE240
/usr/opt/DIA240/lib/DIA AXP_SYS17_EV4.BIN
Analysis Knowledge file
DIABASE240
/usr/opt/DIA240/lib/DIA AXP_SYS27_EV45.BIN
Analysis Knowledge file
DIABASE240
/usr/opt/DIA240/lib/DIA HSAC.BIN
Analysis Knowledge file
DIABASE240
/usr/opt/DIA240/lib/DIA DSA.BIN
Analysis knowledge file
DIABASE240
/usr/opt/DIA240/lib/DIA KDM70.BIN
Analysis knowledge file
DIABASE240
/usr/opt/DIA240/lib/DIA RFXX.BIN
Analysis knowledge file
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_AMERICAN_ENGLISH_HELP_
Knowledge library
STRINGS.KNL DIABASE240
Description
/usr/opt/DIA240/lib/DIA FMG_AMERICAN_ENGLISH_MESSAGES.KNL Knowledge library
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_ANA_ _DEF_RUL_LIB.KNL
Knowledge library
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_ANA_ _FAC_STATE_DB.KNL
Knowledge library
DIABASE240
/usr/var/opt/DIA240/DIA FMG_ANA_ _PRM_STATE_DB.KNL
Knowledge library
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_CTR_ _DEF_RUL_LIB.KNL
Knowledge library
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_ETC_ _DEF_RUL_LIB.KNL
Knowledge library
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_ETC_ _DEF_SEL_LIB.KNL
Knowledge library
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_FACTORY_GLOBAL_PARAM_
Knowledge library
LIBRARY.KNL DIABASE240
/var/opt/DIA240/DIA FMG_GLOBAL_PARAM_LIBRARY.KNL
Knowledge library
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_HELP_FILE_AMERICAN_
On-line help
ENGLISH.HLP_OSF
A–2 Files Installed on Your System
Table A–1 (Cont.): Installed DECevent Files Subset
Directory
File
Description
DIABASE240
/usr/var/opt/DIA240/DIA FMG_NOT_ _DEF_EXTERNAL_LIB.KNL
Knowledge library
DIABASE240
/usr/var/opt/DIA240/DIA FMG_NOT_ _DEF_MAIL_LIB.KNL
Knowledge library
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_NOT_ _DEF_RUL_LIB.KNL
Knowledge library
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_RPT_ _DEF_RUL_LIB.KNL
Knowledge library
DIABASE240
/usr/opt/DIA240/lib/DIA FMG_UNIX_COMMAND.KNL
Knowledge library
DIADOCPS240
/usr/opt/DIA240/share/doclib/DIA240/ps dia240v_unix_analysis_user_guide.ps
Analysis User’s Guide postscript
DIADOCTXT240
/usr/opt/DIA240/share/doclib/DIA240/txt dia240v_unix_analysis_user_guide.txt
Analysis User’s Guide text
DIADOCBOOK240
/usr/opt/DIA240/share/doclib/DIA240/book dia240v_unix_analysis_user_guide.decw_
Analysis User’s Guide bookreader
book DIADOCBOOK240
/usr/opt/DIA240/share/doclib/DIA240/book dia240v_unix_analysis_user_guide.decw_ bookshelf
Analysis User’s Guide bookshelf file
DIADOCPS240
/usr/opt/DIA240/share/doclib/DIA240/ps dia240v_unix_installation_guide.ps
Installation Guide postscript
DIADOCTXT240
/usr/opt/DIA240/share/doclib/DIA240/txt dia240v_unix_installation_guide.txt
Installation Guide text
DIADOCPS240
/usr/opt/DIA240/share/doclib/DIA240/ps dia240v_unix_release_notes.ps
Release Notes postscript
DIADOCTXT240
/usr/opt/DIA240/share/doclib/DIA240/txt dia240v_unix_release_notes.txt
Release Notes text
DIADOCPS240
/usr/opt/DIA240/share/doclib/DIA240/ps dia240v_unix_xlation_user_guide.ps
Translation User’s Guide postscript
DIADOCTXT240
/usr/opt/DIA240/share/doclib/ dia240v_unix_xlation_user_guide.txt DIA240/txt
Translation User’s Guide text
DIADOCBOOK240
/usr/opt/DIA240/share/doclib/DIA240/book dia240v_unix_xlation_user_guide.decw_
Translation User’s Guide bookreader
book
Files Installed on Your System A–3
Table A–1 (Cont.): Installed DECevent Files Subset
Directory
File
DIADOCBOOK240
/usr/opt/DIA240/share/doclib/DIA240/book dia240v_unix_xlation_user_guide.decw_ bookshelf
Description Translation User’s Guide bookshelf
DIABASE240
/usr/opt/DIA240/lib/X11/uid dia_gui_unix.uid
GUI UID File
DIADOCPS240
/usr/opt/DIA240/share/doclib/DIA240/ps dia240v_gui_user_guide.ps
GUI User Guide postscript
A–4 Files Installed on Your System
Appendix B File Hierarchy
This appendix defines the DECevent file hierarchy.
File Hierarchy B–1
/ --+ | +----- sbin/ | \_____ init.d/ | \_____ rc2.d/ | \_____ rc3.d/ | +----- opt/DIAxxx | \_____ sbin/ | \_____ init.d/ | \_____ rc2.d/ | \_____ rc3.d/ | +----- usr/sbin/ | +----- usr/man/ | \_____ man8/ | +----- usr/share/ | \_____ doclib/ | \_____ DIAxxx/ | \_____ txt/ | \_____ ps/ | \_____ book/ +----- usr/lib/ | \_____ DIA/ | \_____ X11/ | \_____ uid/ | +----- usr/opt/DIAxxx/ | \_______ sbin/ | \_______ man/ | | \_____ man8/ | \_______ share/ | | \_____ doclib/ | | \_____ DIAxxx/ | | \_____ txt/ | | \_____ ps/ | | \_____ book/ | \_______ lib/ | \_____ DIA/ | \_____ X11/ | \_____ uid/ | +----- var/ | \_______ DIA/ | +----- var/opt/DIAxxx/ \_______ DIA/
Files located in the /opt/DIA240/... directory are softlinked back to the / directory. Files located in the /usr/opt/DIA240/... directory are softlinked back to the /usr directory. Files located in the /var/opt/DIA240... directory are softlinked back to the /var directory. The startup/shutdown file dia_s_k physically resides in the /sbin/init.d directory. Two softlinks are established by diasetup: one is set at run level 2 for shutdown (/sbin/rc2.d/K97dia ->/sbin/init.d/dia_s_k) and the other is set at run level 3 for startup (/sbin/rc3.d/S15dia ->/sbin/init.d/dia_s_k). The dia or xdia executable lives under the /usr/sbin directory. Currently, dia is a hard link to the xdia image.
B–2 File Hierarchy
Man pages for DECevent reside in dia.8. They are located under the /usr/man/man8 directory. The documentation for DECevent is placed under /usr/share/doclib/DIAxxx, where xxx is the kit version. A README file is placed in this directory along with the man pages. Three other subdirectories may also exist, depending on what type of documentation subset is installed. For example, if the PostScript version of the documentation is installed, then a .ps subdirectory is created. The DECevent Release Notes for DIGITAL UNIX Users, the DECevent Event Management Utility for DIGITAL UNIX Installation Guide, the DECevent Analysis and Notification Utility for DIGITAL UNIX User and Reference Guide, and the DECevent Translation and Reporting Utility for DIGITAL UNIX User and Reference Guide are found under these directories. A uid file, diagui_unix.uid which is used with the GUI interface is placed under the /usr/lib/X11/uid/ directory. Finally, all KNL and BIN files reside under the /var/opt/DIA240 directory. Softlinks are created to make all KNL and BIN files appear under the /var/DIA directory.
File Hierarchy B–3
Appendix C Example DECevent Installation and Deinstallation Logfiles
C.1 Example DECevent Installation The following is an example of the DECevent installation procedure: # setld -l . *** Enter subset selections *** The following subsets are mandatory and will be installed automatically unless you choose to exit without installing any subsets: * DECevent Base kit (Translation / Analysis) The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) DECevent Optional book reader documentation files 2) DECevent Optional postscript documentation files 3) DECevent Optional text documentation files Or you may choose one of the following options: 4) 5) 6) 7)
ALL mandatory and all optional subsets MANDATORY subsets only CANCEL selections and redisplay menus EXIT without installing any subsets
Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 5 You are installing the following mandatory subsets: DECevent Base kit (Translation / Analysis) Is this correct? (y/n): y DECevent Base kit (Translation / Analysis) 21-OCT-1996 15:26:07.34 Copying from DIA_UNXAXP_SSB_240 (disk) Working....Mon Oct 21 15:16:03 MDT 1996 Verifying
Example DECevent Installation and Deinstallation Logfiles
C–1
DECevent subset DIABASE240 has been sucessfully loaded. Event log translation is set up for this node. If you have a Product Authorization Key for analysis issue the following command after the installation is complete: diasetup Configuring "DECevent Base kit (Translation / Analysis)" (DIABASE240) Converting the /var/opt/DIA240/DIA/FMG_ANA__PRM_STATE_DB.KNL to new KNL format.. File ’/var/opt/DIA240/DIA/FMG_ANA__PRM_STATE_DB.OLD_KNL’ is already a Version 3.x KNL Restoring the previous Permanent State Database. Found a local Settings KNL. Renaming it to //FMG_LOCAL_PARAM_LIBRARY.OLD_KNL You currently do not have DSNlink installed on this system. Without DSNlink, you cannot take full advantage DECevent’s Notification capabilities. DECevent functions properly without DSNlink. However, DECevent cannot notify the Customer Support Center when problems are found (notifications are sent locally). Notifying the Customer Support Center greatly enhances DECevent’s diagnosis capability and enables DIGITAL to service your hardware problems automatically without onsite intervention when problems are found. Contact your local DIGITAL service engineer about installing DSNlink. Performing DECevent Installation Verification Procedure Output of DECevent bit to text IVP: 21-OCT-1996 15:26:07.34 DECevent V2.4 ******************************** ENTRY Logging OS System Architecture Event sequence number Timestamp of occurrence Host name
2. Digital UNIX 2. Alpha 3. 13-JAN-1995 12:08:06 fluid
System type register x00000002 Number of CPUs (mpnum) x00000001 CPU logging event (mperr) x00000000 Event validity Event severity Entry type CPU Minor class Frame Revision SCB Vector FRU 1 FRU 2 Severity CPU ID Error Count Threshold For Fail Code Fail Code Error Flag 1 Error Flag 2
1 ********************************
DEC 4000
1. O/S claims event is valid 1. Severe Priority 100. CPU Machine Check Errors 1. Machine check (670 entry) x0001 x0670 Processor Machine Check Abort x00 Field Not Valid x00 Field Not Valid x0000 Field Not Valid x0001 x0000 x0000 x0000 x0000000000200000 CPU_1 Cache TAG Parity Error x0000000000000000
C–2 Example DECevent Installation and Deinstallation Logfiles
frame id byte count
x00000000 x00000000
End of Frame
Output of DECevent Analysis IVP: DECevent V2.4 The optional, licensed, software to perform analysis and/or notification is enabled. Copyright
(c)
Digital Equipment Corporation,
All Rights Reserved.
This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation ("DIGITAL"). This software has been installed and enabled to enhance the maintenance services provided by DIGITAL. Use of this software by anyone other than DIGITAL maintenance personnel is not permitted without a license. Customers who have signed a DIGITAL Service Agreement ("Agreement") have been granted such a license for their own use on equipment covered by the Agreement. Any other use, copying or license to any other party whatsoever is not permitted. DIGITAL reserves the right to remove or disable this software at its discretion. U.S. Pat. 5,469,463. DECevent Notification Report DECevent has detected that the following device needs attention: DEVICE: NODE: SYSTEM SERIAL NUMBER: SYSTEM TYPE:
fluid
DEC_4000 N/A N/A N/A
DECevent Diagnosis Information Digital Services Device: Error: Count:
fluid N/A 0
Theory:
30F2C.14-1:2;1
Evidence:
TBD
Time Of Error:
DEC_4000
95-01-13 12:08:06
Output of DECevent show settings IVP: DECevent V2.4 Current Settings Information:
Example DECevent Installation and Deinstallation Logfiles
C–3
Name Value ============================================================================== CMD_TRACE 0 CTR_TRACE 0 DEBUG_STATE 0 ETC_TRACE 0 FMG__DEBUG_STATE 0 FMG__TRACE_STATE 0 RPT_TRACE 0 TRACE_STATE 0 CTR__DMP_RUL ROOT.DUMP_EVENT_CA CTR__RUL_LIB CTR__DEF_RUL_LIB CTR__SUM_LIB CTR__DEF_SUM_LIB DEF_CTR_RULE ROOT.HEADER_CA DEF_ETC_RULE ROOT.HEADER_EV.OSF_HEADER_EV ETC__DMP_RUL ROOT.DUMP_EVENT_EV ETC__RUL_LIB ETC__DEF_RUL_LIB ETC__SEL_LIB ETC__DEF_SEL_LIB RPT__RUL_LIB RPT__DEF_RUL_LIB HELP_FILE FMG_HELP_FILE CURRENT_CLI UNIX VMS_DEFAULT /TRANSLATE UNIX_DEFAULT -a CHEROKEE_VMS_DEFAULT /TRANSLATE DEF_EVT_LOG /usr/adm/binary.errlog LOCALE AMERICAN_ENGLISH PRINT_MESSAGES 7 STREAM_SIZE 20 SYS_ACT_LOG_NAME DIA_ACTIVITY.LOG KNL__DEF_ENTRIES 32 KNL__LIB_DIRECTORY DIA_LIBRARY KNL__LIB_PREFIX FMG_ KNL__LIB_SUFFIX .KNL VAX_VMS_STACK_SIZE 10 VAX_VMS_GUARD_SIZE 3 ALPHA_VMS_STACK_SIZE 50 ALPHA_VMS_GUARD_SIZE 30 RULE_MAX_BYTECNT 100000 DEFAULT_REPORT FULL_RE ANA_TRACE 0 NOT_TRACE 0 ANA__FAC_DB ANA__FAC_STATE_DB ANA__PRM_DB ANA__PRM_STATE_DB ANA__RUL_LIB ANA__DEF_RUL_LIB ANA__TMP_DB ANA__TMP_STATE_DB NOT__RUL_LIB NOT__DEF_RUL_LIB NOT__MAIL_LIB NOT__DEF_MAIL_LIB NOT__EXTERNAL_LIB NOT__DEF_EXTERNAL_LIB FMG__CUST_PROFILE /usr/sbin/DIA120/FMGPROFILE FMG_VERSION 2.2 SICL_STATE OFF SICL_PROTOCOL_VERS 1 AUTO_COPY OFF ANALYSIS_TRIGGER_AUTOMATIC AUTOMATIC ANALYSIS_TRIGGER_MANUAL MANUAL NOT__DEF_CSC_PHONE 1-800-354-9000 NOT__MAX_DSNLNK_MSG 59 MAIL_DEBUG 0 Output of DECevent show parameters IVP: DECevent V2.4 The optional, licensed, software to perform analysis and/or notification is enabled.
C–4 Example DECevent Installation and Deinstallation Logfiles
Copyright
(c)
Digital Equipment Corporation,
All Rights Reserved.
This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation ("DIGITAL"). This software has been installed and enabled to enhance the maintenance services provided by DIGITAL. Use of this software by anyone other than DIGITAL maintenance personnel is not permitted without a license. Customers who have signed a DIGITAL Service Agreement ("Agreement") have been granted such a license for their own use on equipment covered by the Agreement. Any other use, copying or license to any other party whatsoever is not permitted. DIGITAL reserves the right to remove or disable this software at its discretion. U.S. Pat. 5,469,463.
Analysis Notification Parameters: PHONE NUMBER SICL
Customer Service Phone Number is System Initiated Call Logging is
1-800-354-9000 OFF
SYSTEM INFO
System Info for garcia.cxo.dec.com Serial Number 1234567 System Type DEC2000_300
DECevent IVP completed successfully You must define the following environmental variable in order to use this product: csh> setenv DIA_LIBRARY /var/DIA or sh> DIA_LIBRARY=/var/DIA sh> export DIA_LIBRARY
C.2 Example DECevent Deinstallation The following is an example of the DECevent deinstallation procedure: DECevent V2.4 # setld -i | grep ’DIA.* installed’ DIABASE240 installed DECevent Base kit (Translation/Analysis) DIADOCBOOK240 installed DECevent Optional book reader documentation DIADOCPS240 installed DECevent Optional postscript documentation DIADOCTXT240 installed DECevent Optional text documentation # setld -d DIABASE240 DIADOCBOOK240 DIADOCPS240 DIADOCTXT240 Deleting "DECevent Optional book reader documentation files" (DIADOCBOOK240). Deleting "DECevent Optional postscript documentation files" (DIADOCPS240). Deleting "DECevent Optional text documentation files" (DIADOCTXT240). Deleting "DECevent Base kit (Translation / Analysis)" (DIABASE240).
Example DECevent Installation and Deinstallation Logfiles
C–5
