Installing DECamds This document describes how to install DECamds software on OpenVMS Alpha and VAX systems. 1 Preparing to Install DECamds This section describes the preparations and requirements necessary for installing DECamds. DECamds provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. You can print the release notes from the following location: SYS$HELP:AMDS070.RELEASE_NOTES For information about how to access the online release notes, see Section 5. 2 Kit Location and Installation Information The DECamds kit has two components: o The Data Analyzer is installed on any system where you want to analyze, detect and display events, and initiate corrective action. o The Data Provider is installed on any node from which you want to gather system data and permit fixes. For OpenVMS Alpha systems, use the POLYCENTER Software Installation Utility to install the DEC-AXPVMS-AMDS-V0700- 1.PCSI kit (see Section 4) on the software distribution compact disk.<> For OpenVMS VAX systems, install the AMDS070.A and AMDS070.B save sets using the VMSINSTAL procedure. The kits are located in the [AMDS070] directory on the compact disk. For information on how to install and use DECamds on OpenVMS VAX systems, see Section 5. You can find the DECamds kits, named AMDS070.A and AMDS070.B, on the following media: Magnetic tape Third volume 1 TK50 tape Second volume Compact disk [AMDS070] directory<> 3 Installation Requirements This section provides a checklist of hardware and software requirements for DECamds. A typical installation takes approximately 5 to 10 minutes per node, depending on the type of media and your system configuration. o Hardware Requirements - A workstation monitor. For any hardware configuration without a DECwindows Motif display device, use the DECwindows server to direct the display to a workstation or an X terminal. - 16 MB of memory for VAX systems and 32 MB for Alpha systems, for the Data Analyzer portion of DECamds. You should use a more powerful system as the number of nodes and the amount of collected data rises. Table 1 shows general guidelines for the default Data Analyzer node. Note that the following table does not preclude DECamds from running on a less powerful system than listed for the number of nodes being monitored. Table_1_Recommended_System_Requirements____________________ Number of Monitored Recommended Alpha Recommended VAX Nodes__________Hardware________________Hardware____________ 1-30 DEC 3000 Model 400, 32 VAXstation 3100, 16 MB MB 20-50 DEC 3000 Model 400, 64 VAXstation 4000 MB Model 60 40-90 DEC 3000 Model 500 VAXstation 4000 Model 90 91 or more DEC 4000 Model 620 VAX 6000-420 o Operating System Version 2 At least one of the following: OpenVMS Version 5.5 or higher OpenVMS VAX Version 6.0 or higher OpenVMS AXP Version 6.1 OpenVMS Alpha Version 6.2 or higher o Display Software DECwindows Motif for OpenVMS Version 1.1 or higher installed on the Data Analyzer node system. o Privileges ________________________________________________________ Operation__________________Privileges_Needed____________ Monitor only (read-only OPER access) Implement fixes (write OPER, CMKRNL access) Stop, start, reload, or OPER, CMKRNL, LOG_IO, SYSNAM, restart the Data Provider SYSPRV node. Includes changing security_or_group_name._________________________________ ________________________ Note ________________________ For OpenVMS VAX Version 6.0 and later or OpenVMS AXP Version 6.1 and later, if the Data Provider is running on the same node as the Data Analyzer node, you must also have either SYSPRV privilege or ACL access to the RMA0: device. ______________________________________________________ o License Registration VAXcluster, VMScluster, or VMScluster-Client license. For information on registering a license, see the OpenVMS License Management Utility Manual. o Disk Space - 3500 blocks on VAX. Note that VMSINSTAL turns off BYPASS privilege at the start of the installation.<> - 4000 blocks on Alpha.<> 3 To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE o System Parameter Settings Same as needed for operating system installation. The Installation Verification Procedure (IVP) requires additional space as follows: - GLBPAGFIL 1200 - WSMAX 16384 You can modify WSMAX and GLBPAGFIL using the System Management utility (SYSMAN). See the OpenVMS System Manager's Manual for more information. o Process Account Quotas (minimum) - ASTLM[1] 150 - BIOLM[1] 51 - BYTLM[1] 75000 - FILLM 20 - PRCLM 3 - PGFLQUO 25600 - TQELM[1] 100 - WSEXTENT 16384 [1]The AMDS$COMM_READS logical determines the default value. If you are reinstalling DECamds, or have changed AMDS$COMM_READS, then the following formulas are used to determine the default value: ASTLM >= (AMDS$COMM_READS*3) BIOLM >= (AMDS$COMM_READS+1) BYTLM >= (AMDS$COMM_READS*1500) TQELM >= (AMDS$COMM_READS*2) User account quotas are stored in the file SYSUAF.DAT. Use the OpenVMS Authorize utility (AUTHORIZE) to verify and change user account quotas. For more information on modifying account quotas, see the description of the Authorize utility in the OpenVMS system management documentation. 4 o VMSINSTAL Requirements (VAX only) - Log in to a privileged account. - Ensure that the default device and directory is set to the SYS$UPDATE logical name. - Ensure adequate quotas for installation. - Ensure that users are not logged in to the system. If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO and press the Return key; then correct the problem and restart the installation.<> ________________________ Note ________________________ Digital recommends that you perform a system disk backup before installing any software. Use the backup procedures that are established at your site. For details about performing a system disk backup, see the OpenVMS Backup utility documentation. ______________________________________________________ 4 OpenVMS Alpha System Installation This section describes the installation procedure on an OpenVMS Alpha system. o Starting the Installation Depending on the interface to your system, use one of these procedures to start the installation: ________________________________________________________ Interface Command_______________________________________ Motif From a DECterm, enter the PRODUCT command at the DCL prompt ($): $ PRODUCT 5 ________________________________________________________ Interface Command_______________________________________ DCL Enter the PRODUCT command, the name of the task to be performed, and the name of one or more products. For example, to install DECamds Version 7.0, enter the following command: $ PRODUCT INSTALL AMDS/SOURCE=distribution- media/HELP For a description of the features you can request with the PRODUCT INSTALL command when starting an installation such as running the IVP, purging files, and configuring the installation, see the POLYCENTER Software Installation Utility User's Guide or Motif help. As an installation procedure progresses, the system displays a percentage message to indicate how much of the installation is done. For example: Percent Done: 15% ...30% ...46% ...62% ...76% ...92% %PCSI-I-SUCCESS, operation completed successfully If you started the installation using the /LOG qualifier, the system displays details of the installation. o Stopping and Restarting the Installation Depending on the interface to your system, use one of these procedures to stop and restart the installation: 6 ________________________________________________________ Interface___Action______________________________________ DCL To stop the procedure at any time: press Ctrl/Y and then enter the PRODUCT REMOVE command to reverse any changes to the system that occurred during the partial installation. This deletes all files created up to that point and causes the installation procedure to exit. Motif To close the POLYCENTER Software Installation utility window, choose Exit from the File menu. o Recovering from Errors If the installation procedure fails for any reason, the following message is displayed: %POLYCENTER Software Installation utility %INSTAL-E-INSFAIL, The installation of DECamds 7.0 has failed. An error during the installation can occur if one or more of the following conditions exist: o The operating system version is incorrect. o The prerequisite software version is incorrect. o Quotas necessary for successful installation are inadequate. o Process quotas required by the POLYCENTER Software Installation utility are inadequate. o The OpenVMS Help library is currently in use. If you receive any error message beginning with %PCSI- E-INSTAL, refer to the DCL HELP/MESSAGE utility for POLYCENTER Software Installation information and a possible solution to the problem. If the installation fails, you must restart the installation procedure. If the installation fails due to an IVP failure, contact a Digital field service representative. 7 Sample Installation on an OpenVMS Alpha System Example 1 shows a sample installation on an OpenVMS Alpha system. This sample was run on a system that had no previous version of DECamds installed. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. Example 1 Sample OpenVMS Alpha Installation $ PRODUCT INSTALL AMDS/SOURCE=DAD15:[AMDS070.KIT] The following product has been selected: DEC AXPVMS AMDS V7.0 [Available] Do you want to continue? [YES] *** DEC AXPVMS AMDS V7.0: DECamds (Availability Manager for Distributed Systems) V7.0 COPYRIGHT © (c) 1994, 1995 -- All rights reserved Digital Equipment Corporation License and Product Authorization Key (PAK) Information Do you want all the default values for this product? [YES] DECamds Startup File DECamds Message Help DECamds Logicals Customization File DECamds Data Provider Security Access File DECamds Data Provider Installation Verification Procedure DECamds Data Analyzer Security Access File DECamds Data Analyzer Installation Verification Procedure (IVP) IVP may fail due to the following PQL values being too low: PQL_MASTLM, PQL_MBIOLM, PQL_MTQELM, or PQL_MBYTLM See the file AMDS$SYSTEM:AMDS$PCSI_IVP_OUTPUT.LOG for help on failure. Do you want to view the values? [NO] (continued on next page) 8 Example 1 (Cont.) Sample OpenVMS Alpha Installation %PCSIUI-I-DONEASK, execution phase starting The following product will be installed: DEC AXPVMS AMDS V7.0 %PCSI-I-VOLINFO, estimated space information for volume DISK$ALPHAVMS070 -PCSI-I-VOLSPC, 0 required; 89505 available; 89505 net Portion Done: 0%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS AMDS V7.0 %PCSI-I-EXETSTSTART, start of test procedure %PCSI-I-EXETSTOK, end of test procedure; completed with no errors *** DEC AXPVMS AMDS V7.0: DECamds (Availability Manager for Distributed Systems) V7.0 This product requires the following SYSGEN parameters: GBLPAGES add 1172<> 5 OpenVMS VAX System Installation The DECamds installation procedure consists of a series of questions and informational messages. See Example 2 for a sample installation. The actual installation should take only a few minutes, but depending on your installation media, this time could be longer. To abort the installation procedure at any time, press Ctrl/Y. When you press Ctrl/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. To install DECamds: 1. Invoke VMSINSTAL from a privileged account. @SYS$UPDATE:VMSINSTAL AMDS070 Device-name OPTIONS N Device-name is the name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. OPTIONS N is an optional parameter that indicates you want to see the question on release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation 9 because they might contain additional information about the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. For more information about software installation options, see the OpenVMS System Manager's Manual. 2. Confirm DECnet status. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. . . . * Do you want to continue anyway [NO]? Type yes and continue the installation. 3. Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? You should always back up your system disk before performing any installation. If you are satisfied with the backup of your system disk, press Return. 4. Mount the media. Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, AMDS MOUNTED ON _MTA0: (NODE 1) The following products will be processed: DECamds V7.0 Beginning installation of DECamds V7.0 at 10:43 %VMSINSTAL-I-RESTORE, Restoring product saveset A... You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To abort the installation for other reasons, press Ctrl/Y. 10 If your installation kit contains more than one volume, VMSINSTAL prompts you to mount the additional volumes and then asks you to indicate that you are ready for the installation to proceed. 5. Select a release notes option. If you select Options N, the following is displayed: Release notes included with this kit are copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you choose to display the release notes, you can terminate the display at any time by pressing Ctrl/C. Release notes are copied to the system help directory (SYS$HELP:AMDS070.RELEASE_NOTES), even if you select option 4. After the installation, enter the following command to review the release notes through the Help facility: $ HELP DECamds RELEASE_NOTES ________________________ Note ________________________ The name of the release notes file installed by VMSINSTAL consists of the current product name and version number. Do not delete release notes for previous versions of DECamds. ______________________________________________________ 6. Choose which components to install. You now have the choice to install either the DECamds Data Analyzer, or the DECamds Data Provider, or both on this system. * Would you like to install the DECamds Data Analyzer on this system [Y]? * Would you like to install the DECamds Data Provider on this system [Y]? 7. Respond to license registration queries. 11 You will be asked if you have loaded the appropriate license. The right to use the DECamds Data Provider is granted with the VAXCLUSTER license. This installation will only ask for the presence of the license. If you answer yes to the following question and do not have a license, then the IVP will fail. * Do you have the VAXCLUSTER license loaded [Y]? If you have not registered and loaded your PAK, you must answer NO to this question. You must register and load your PAK, then restart the installation. For information on registering a license, see the OpenVMS License Management Utility Manual. 8. Choose the Help Message installation option. The Help Message utility (MSGHLP) provides online explanations and user actions for OpenVMS messages. The MSGHLP database, DECAMDS.MSGHLP$DATA, consumes approximately 200 blocks and will be placed by default on your system disk in SYS$COMMON:[SYSHLP]. Refer to the OpenVMS System Messages: Companion Guide for Help Message Users and the OpenVMS System Manager manual for instruction on how to add the DECamds Help Message database to your system. * Would you like to install the MSGHLP database for DECamds [Y]? If you answer YES (or use the default), the DECamds help message database, DECAMDS.MSGHLP$DATA, will be copied to SYS$COMMON:[SYSHLP]. Refer to the OpenVMS System Messages: Companion Guide for Help Message Users for complete information on setting up and using the Help Message utility. 9. Choose the Installation Verification Procedure (IVP) option. * Do you want to run the IVP after the installation [YES]? It is recommended that you run the IVP because it ensures that the installation is successful. If the IVP finds the Data Provider on the system, it will ensure the driver is left in the state in which the IVP found it. 12 You can run the IVP independently to verify that the software is available on your system. See Section 9 for information about running the IVP separately. 10.Choose the purge files option. * Do you want to purge files replaced by this installation [YES]? Purging is recommended; however, if you want to keep files from the previous version, enter NO and press Return. 11.Read informational messages. See the sample installation procedure in Example 2. 12.Observe the Installation Verification Procedure (IVP). See the sample installation procedure in Example 2. Sample Installation on an OpenVMS VAX System Example 2 shows a sample installation on an OpenVMS VAX system and assumes that DECnet has been shut down, that no users are logged on to your system, and that OPTIONS N is specified to print the release notes. The Installation Verification Procedure (IVP) runs at the end of the installation. This sample was run on a system that had no previous version of DECamds installed. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. Example 2 Sample OpenVMS VAX Installation $ @VMSINSTAL AMDS070 SYS$UPDATE VAX/VMS Software Product Installation Procedure V7.0 It is 27-JAN-1995 at 15:13. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: (continued on next page) 13 Example 2 (Cont.) Sample OpenVMS VAX Installation AMDS V7.0 Beginning installation of AMDS V7.0 at 15:14 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright (c) 1995 Digital Equipment Corporation. All rights reserved. Beginning the installation of DECamds V7.0. %AMDS-I-VERINSTAL, Installing DECamds on an OpenVMS VAX V7 system You now may choose to install the DECamds Data Analyzer. The Data Analyzer must be installed on a system in which at least DECwindows Motif V1.1 has been installed. * Would you like to install the DECamds Data Analyzer on this system [Y]? The right to use the DECamds Data Provider is granted with the VAXCLUSTER license. This installation will only ask for the presence of the license. If you answer yes to the following question and do not have a license, then the IVP will fail. * Do you have an appropriate license loaded [Y]? * Do you want to run the IVP after the installation [YES]? * Do you want to purge files replaced by this installation [YES]? No further questions will be asked during the installation. This installation will take approximately 5-10 minutes to complete. %VMSINSTAL-I-RESTORE, Restoring product save set B ... The DECamds startup file (AMDS$STARTUP.COM) is being copied to the SYS$STARTUP directory. Digital recommends you include this file in your site specific startup procedures as follows: @SYS$STARTUP:AMDS$STARTUP START The command procedure AMDS$LOGICALS.COM was already found in the SYS$COMMON:[AMDS] directory. This installation will provide an AMDS$LOGICALS.TEMPLATE file instead of the AMDS$LOGICALS.COM file. Please check the new .TEMPLATE file and add any changes to your current AMDS$LOGICALS.COM file. (continued on next page) 14 Example 2 (Cont.) Sample OpenVMS VAX Installation The file SYS$COMMON:[AMDS]AMDS$CONSOLE_ACCESS.DAT already exists. This installation will provide a AMDS$CONSOLE_ACCESS.TEMPLATE file instead of the AMDS$CONSOLE_ACCESS.DAT file to avoid superceding a version of the file you may currently be using. The installation will now provide the DECamds customization files. If this installation finds one of the customization files already residing in the installation directory, then the installation will provide a .TEMPLATE file instead of the .DAT file. It will be left up to the installer to check the AMDS$SYSTEM directory for any differences between the .DAT and .TEMPLATE files. The installation procedure will provide a .TEMPLATE file for the following customization files found in the AMDS$SYSTEM directory: AMDS$APPLIC_CUSTOMIZE.DAT AMDS$SEVERITY_DEFS.DAT AMDS$OCCURRENCE_DEFS.DAT AMDS$THRESHOLD_DEFS.DAT AMDS$INTERVAL_DEFS.DAT AMDS$FILTER_DEFS.DAT AMDS$SORT_DEFS.DAT AMDS$GEOMETRY_DEFS.DAT The file SYS$COMMON:[AMDS]AMDS$DRIVER_ACCESS.DAT already exists. This installation will provide a AMDS$DRIVER_ACCESS.TEMPLATE file instead of the AMDS$DRIVER_ACCESS.DAT file to avoid superceding a version of the file you may currently be using. DECamds installation V7.0 is complete. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %AMDS-I-NODRIVER, data collection not started, only define AMDS$SYSTEM DECamds V7.0 Installation Verification Procedure (IVP) Beginning. Copyright © Digital Equipment Corporation 1995. All Rights Reserved. This IVP will check following pieces of DECamds: DATA PROVIDER - RMDRIVER (continued on next page) 15 Example 2 (Cont.) Sample OpenVMS VAX Installation DATA ANALYZER - AMDS$CONSOLE and AMDS$COMM Before running this IVP, any process currently running the DECamds Data Analyzer on this machine must be stopped. The IVP will now check for the existence of the AMDS$COMM process which indicates that someone is currently running the Data Analyzer. AMDSIVP-I-RMRELOAD, reloading with new data provider for IVP to use Copyright (c) 1995 Digital Equipment Corporation. All rights reserved. %AMDS-I-RMSHUT, stopping RMDRIVER processing for this node %AMDS-S-RMSUCCESS, RMDRIVER shutdown successful Copyright (c) 1995 Digital Equipment Corporation. All rights reserved. %AMDS-I-RMSTART, starting RMDRIVER processing for this node %AMDS-I-LOADSECDB, loading security database %AMDS-S-RMSUCCESS, RMDRIVER startup successful You currently do not have a DECwindows display to direct the Data Analyzer output towards. You are now given the option to continue and allow the IVP to create a display for you or exit and either create your own display or run the IVP from a workstation. Would you like to continue? [Y/N]Y You have chosen to let the IVP create a DECwindows display. You will be prompted for a node to direct the display towards. Specify a valid node on which you are allowed to create a display from your current node. This procedure does not check the validity of the remote node you specify. Nodename to direct the display towards: AMDS %DCL-S-SPAWNED, process AMDS$IVP_CONS spawned Waiting 5 minutes to allow the DECamds Data Analyzer to run. You should see the Event Log and System Overview windows appear on your DECwindows display device. AMDSIVP-S-ALLPASS, DECamds has passed the IVP DECamds V7.0 Installation Verification Procedure Complete (continued on next page) 16 Example 2 (Cont.) Sample OpenVMS VAX Installation Installation of AMDS V7.0 completed at 15:23 VMSINSTAL procedure done at 15:23 $ LOG SYSTEM logged out at 27-JAN-1995 15:23:53.60<> Recovering from Errors Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o A prerequisite software version is incorrect. o Privileges necessary for successful IVP are insufficient. o Quotas necessary for successful IVP are insufficient. o System parameter values for successful IVP are insufficient. o The OpenVMS help library is currently in use. o The product license has not been registered and loaded. o The node on which the DECamds Data Analyzer was being displayed does not allow connections from your process and node. For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. For information on installation requirements, see Section 3. If the IVP fails, check the AMDS$SYSTEM:AMDS$CONS_LOG.LOG for any errors that might have occurred while the IVP was executing the console verification portion. 17 6 Postinstallation Tasks on Data Provider Nodes Perform the following tasks after installing DECamds on Data Provider nodes: 1. If you have not read the release notes, please read them. 2. Modify user accounts. Users who maintain the security or group name files or load new versions of the driver need privileges associated with the driver startup procedure. 3. Add AMDS$STARTUP.COM to the node's startup and shutdown procedures to provide for automatic startup and shutdown of the Data Provider driver when a node is booted or shut down. o On an OpenVMS Version 5.5 system, add the following command line to SYS$MANAGER:SYSTARTUP_V5.COM $ @SYS$STARTUP:AMDS$STARTUP.COM START o On any OpenVMS system, add the following command line to SYS$MANAGER:SYSTARTUP_VMS.COM $ @SYS$STARTUP:AMDS$STARTUP.COM START Also, edit SYSHUTDWN.COM to add the following line: $ @SYS$SHUTDOWN:AMDS$STARTUP.COM STOP 4. Modify default security files. To implement fixes, which require write access, the security files must be modified. The Data Provider security file contains a list of three-part codes representing Data Analyzer nodes that have read or write access to that node. Refer to the section "Security Features" in Chapter 1 of the DECamds User's Guide for complete instructions about designing security files. 5. Assign a node to a group. See the section "Setting Up Node Groups" in Chapter 1 of the DECamds User's Guide. 6. Start DECamds (the Data Provider). 18 Even though the IVP starts and stops the driver, you must start the Data Provider drivers by entering the following command on each node: $ @SYS$STARTUP:AMDS$STARTUP.COM START ________________________ Note ________________________ Starting, stopping, or reloading DECamds (the AMDS$STARTUP.COM procedure) requires at least TMPMBX, NETMBX, SYSNAM, LOG_IO, and CMKRNL privileges. Use the OpenVMS Authorize utility (AUTHORIZE) to determine whether users have the required privileges and then make adjustments as needed. ______________________________________________________ 6.1 Starting, Stopping, and Reloading DECamds To start and stop the Data Provider driver, enter the following command: (Use this command if a node will be used to both provide and collect system data.) $ @SYS$STARTUP:AMDS$STARTUP.COM [parameter] where the optional parameter is one of the following: NODRIVER Defines the default input and output logicals on the Data Analyzer node driver. Use this parameter on the Data Analyzer node where the Data Provider driver is not running. It is the default. START Starts the Data Provider driver. STOP Stops the Data Provider driver. RELOAD Loads a new Data Provider driver. Use this parameter when installing a new version of DECamds. ________________________ Note ________________________ On systems running OpenVMS VAX Version 6.0 or higher, if you use the OpenVMS Snapshot Facility, stop the DECamds Data Analyzer and Data Provider node drivers before taking a system snapshot. ______________________________________________________ 19 7 Postinstallation Tasks on the Data Analyzer Node Perform the following tasks after installing the DECamds Data Analyzer: 1. If you were previously running an earlier version of DECamds, check the differences between the .DAT or .COM files on your system and the associated .TEMPLATE files provided with the new kit. Change your existing files as necessary. ________________________ Note ________________________ The new .TEMPLATE files may contain important changes. However, to avoid altering your customizations, the upgrade procedure does not modify your existing customized versions of these files. Check the new .TEMPLATE versions of these files provided with the kit, and make the appropriate change to your files. ______________________________________________________ 2. Modify default DECamds security files on each Data Analyzer node. To implement fixes, which require write access, the security files must be modified. Refer to the section "Security Features" in Chapter 1 of the DECamds User's Guide for complete instructions about designing security files. 3. Define the system directory logical name AMDS$SYSTEM. To define the logical name AMDS$SYSTEM on systems running the Data Analyzer but not the Data Provider, enter the following command: $ @SYS$STARTUP:AMDS$STARTUP.COM NODRIVER This command requires SYSNAM privilege. The NODRIVER parameter specifies that the procedure is to define the input and output logical names in AMDS$LOGICALS.COM. 4. Modify user accounts as needed. 20 To use DECamds, user accounts require certain privileges and quotas: o Using the Data Analyzer node for data collection (read access) requires TMPMBX, NETMBX, and OPER privileges. o Performing fixes (write access) requires the CMKRNL privilege in addition to TMPMBX, NETMBX, and OPER. o Using the AMDS$STARTUP.COM to start, stop, or reload the Data Provider requires at least TMPMBX, NETMBX, SYSNAM, LOG_IO, and CMKRNL privileges. 5. Start the application. For example, the following command starts DECamds with all input files read from AMDS$SYSTEM and all output files written to the current default directory. Only data from group A nodes and group B nodes are displayed. $ AVAIL /CONFIGURE=AMDS$SYSTEM /LOG_DIRECTORY=SYS$LOGIN- _$/GROUP=(GROUP_A, GROUP_B) See Chapter 2, "Getting Started," in the DECamds User's Guide for startup options. 8 Determining and Reporting Problems If you encounter a problem while using DECamds, report the problem to Digital. Depending on the nature of the problem and the type of support you have, take one of these actions: o If your software contract or warranty agreement entitles you to telephone support, call your Digital support center. o If the problem has to do with the DECamds documentation, submit a Reader's Comments form. See the Preface for instructions. Review the Software Product Description (SPD) and Warranty Addendum for an explanation of the warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. 21 9 Running the Installation Verification Procedure Separately Usually the Installation Verification Procedure (IVP) runs during installation. Should system problems occur after you install DECamds, check the integrity of installed files by executing the following command procedure: $ @SYS$TEST:AMDS$IVP.COM The IVP leaves the Data Provider in the same state in which it was found. For example, if the Data Provider is running, the IVP stops and starts it. 22