**************************** ECO SUMMARY INFORMATION **************************** Release Date: 2-JUN-2005 Kit Name: DEC-AXPVMS-VMS731_DRIVER-V0300--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 3728 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VMS731_DRIVER-V0200 Mandatory Kit Dependencies: VMS731_UPDATE-V0500 VMS731_PCSI-V0200 Optional Kit Dependencies: None VMS731_DRIVER-V0300.PCSI-DCX_AXPEXE Checksum: 419440557 DEC-AXPVMS-VMS731_DRIVER-V0300--4.PCSI Checksum: 1561850712 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS731_DRIVER-V0300 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. This installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) 2.2 Reboot Requirement: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha v7.3-1 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS731_DRIVER-V0200 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS731_PCSI-V0200 - VMS731_UPDATE-V0500 Page 2 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - Version V85J-10 firmware for the HSJ80 controller. See Section 6.2.1 for additionalinformation. 5 FILES PATCHED OR REPLACED: o [SYS$LDR]SYS$DQDRIVER.EXE (new image) Image Identification Information image name: "SYS$DQDRIVER" image file identification: "X-49A1" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 01:00:09.84 linker identification: "A11-50" Overall Image Checksum: 886309383 o [SYS$LDR]SYS$DUDRIVER.EXE (new image) Image Identification Information image name: "SYS$DUDRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:56:23.19 linker identification: "A11-50" Overall Image Checksum: 371731102 o [SYS$LDR]SYS$PADRIVER.EXE (new image) Image Identification Information image name: "SYS$PADRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:59:29.93 linker identification: "A11-50" Overall Image Checksum: 1352197518 o [SYS$LDR]SYS$PBDRIVER.EXE (new image) Image Identification Information image name: "SYS$PBDRIVER" image file identification: "X-31" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:56:24.27 linker identification: "A11-50" Overall Image Checksum: 2263066164 Page 3 o [SYS$LDR]SYS$PCADRIVER.EXE (new image) Image Identification Information image name: "SYS$PCADRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:59:15.51 linker identification: "A11-50" Overall Image Checksum: 2997080665 o [SYS$LDR]SYS$PEDRIVER.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:58:27.46 linker identification: "A11-50" Overall Image Checksum: 1520939179 o [SYS$LDR]SYS$PEDRIVER_MON.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER_MON" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:58:47.68 linker identification: "A11-50" Overall Image Checksum: 2121159108 o [SYS$LDR]SYS$PIDRIVER.EXE (new image) Image Identification Information image name: "SYS$PIDRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:59:19.81 linker identification: "A11-50" Overall Image Checksum: 2435868167 o [SYS$LDR]SYS$PIPEDRIVER.EXE (new image) Image Identification Information image name: "SYS$PIPEDRIVER" image file identification: "X-6" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 01:00:08.79 linker identification: "A11-50" Overall Image Checksum: 306806743 Page 4 o [SYS$LDR]SYS$PJDRIVER.EXE (new image) Image Identification Information image name: "SYS$PJDRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:59:24.03 linker identification: "A11-50" Overall Image Checksum: 3961688863 o [SYS$LDR]SYS$PMDRIVER.EXE (new image) Image Identification Information image name: "SYS$PMDRIVER" image file identification: "X-31" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:56:31.03 linker identification: "A11-50" Overall Image Checksum: 3098755067 o [SYS$LDR]SYS$PNDRIVER.EXE (new image) Image Identification Information image name: "SYS$PNDRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:58:36.33 linker identification: "A11-50" Overall Image Checksum: 2901244974 o [SYS$LDR]SYS$TUDRIVER.EXE (new image) Image Identification Information image name: "SYS$TUDRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-MAR-2005 00:59:54.83 linker identification: "A11-50" Overall Image Checksum: 2439165483 o [SYS$LDR]SYS$PEDRIVER.STB (new file) o [SYS$LDR]SYS$PEDRIVER_MON.STB (new file) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_DRIVER-V0300 KIT Page 5 6.1 New functionality addressed in this kit None. 6.2 Problems addressed in this kit 6.2.1 Backup Jobs Fail With Datalost Errors 6.2.1.1 Problem Description: Backup jobs can fail with datalost errors. This is most often due to bad tapes. %BACKUP-E-FATALERR, fatal error on $100$MUA7:[]5MAR200200230000.; -SYSTEM-F-DATALOST, data lost If this happens, the controller will see the tapeunit in an 'exclusive access' state. Images Affected: - [SYS$LDR]SYS$TUDRIVER.EXE 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) CFS.89039, CFS.102039 6.2.1.2.2 QAR(s) None. 6.2.1.3 Problem Analysis: The cause of this problem was two-fold: o TUDRIVER mis-handled SS$_DATALOST errors. o A firmware problem causes the error to not be cleared. Because of the firmware issue, to completely fix this problem, new HSJxx firmware is needed (V85J-10 for the HSJ80). Page 6 6.2.1.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.1.5 Work-arounds: None. 6.2.2 Multiprocessor System Crash with CPUSPINWAIT or INVEXCEPTN Bugcheck 6.2.2.1 Problem Description: A multiprocessor system may crash with a CPUSPINWAIT or INVEXCEPTN bugcheck in DUTU$CANCEL. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Failing PC: FFFFFFFF.80751A54 SYS$DUDRIVER+0FA54 Failing PS: 20000000.00000800 Module: SYS$DUDRIVER (Link Date/Time: 1-OCT-2003 21:18:58.53) Offset: 0000FA54 Stack Pointers: KSP = 00000000.7FF87418 ESP = 00000000.7FF8BA70 SSP = 00000000.7FF9CD00 USP = 00000000.0010FBD0 Images Affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) None. 6.2.2.2.2 QAR(s) 75-102-14 Page 7 6.2.2.3 Problem Analysis: If during cancel scan of restart queue a cancellable CDRP was located, it was REMQUEUED and then its flink was used to continue the queue scan. It may have been updated/stale while being posted, leading to a CPUSPINWAIT bugcheck or INVEXCEPTN bugcheck. 6.2.2.4 Release Version of OpenVMS that will contain this change: V7.3-2 6.2.2.5 Work-arounds: None. 6.2.3 System can crash with a CLUEXIT bugcheck in CNX$WAIT_C+00880. 6.2.3.1 Problem Description: System can crash with a CLUEXIT bugcheck in CNX$WAIT_C+00880. A dump shows that the system is out of non-paged pool. Crashdump Summary Information: ------------------------------ Bugcheck Type: CLUEXIT, Node voluntarily exiting VMScluster Failing PC: FFFFFFFF.803042E0 CNX$WAIT_C+00880 Failing PS: 30000000.00000804 Module: SYS$CLUSTER (Link Date/Time: 10-APR-2002 15:27:49.50) Offset: 000022E0 Stack Pointers: KSP = FFFFFFFF.C37CFCF0 ESP = FFFFFFFF.C37D1000 SSP = FFFFFFFF.C37CD000 USP = FFFFFFFF.C37CD000 Images Affected: - [SYS$LDR]SYS$PIPEDRIVER.EXE Page 8 6.2.3.2 CLDs, and QARs reporting this problem: 6.2.3.2.1 CLD(s) CFS.104377,70-3-7600 6.2.3.2.2 QAR(s) None. 6.2.3.3 Problem Analysis: The pool usage is caused by a PIPE command that involves a long time period and a large amount of I/O passing through the pipe. 6.2.3.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.3.5 Work-arounds: None. 6.2.4 %DFG-F-MOVFILQIOERR error when using DFO (Disk File Optimizer) on an IDE device 6.2.4.1 Problem Description: Using DFO on an IDE device can give the following error: %DFG-F-MOVFILQIOERR, QIO error on movefile for volume DEVICE: -SYSTEM-F-BADPARAM, bad parameter value Images Affected: - [SYS$LDR]SYS$DQDRIVER.EXE 6.2.4.2 CLDs, and QARs reporting this problem: Page 9 6.2.4.2.1 CLD(s) None. 6.2.4.2.2 QAR(s) 75-100-77,75-13-1166 6.2.4.3 Problem Analysis: When accessing an IDE device using the Physical I/O calls, the code accesses the wrong IDE address. 6.2.4.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.4.5 Work-arounds: None. 6.2.5 Cluster Hang 6.2.5.1 Problem Description: Whenever a cluster member's VMS$VAXcluster SYSAP is connected via Memory Channel and/or Shared Memory CI to another node, and that partner node goes away, the member will wait the full RECNXINTERVAL before initiating a cluster state transition. This causes the cluster to look like it is hung. Images Affected: - [SYS$LDR]SYS$PADRIVER.EXE - [SYS$LDR]SYS$PBDRIVER.EXE - [SYS$LDR]SYS$PCADRIVER.EXE - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PIDRIVER.EXE - [SYS$LDR]SYS$PJDRIVER.EXE - [SYS$LDR]SYS$PMDRIVER.EXE Page 10 - [SYS$LDR]SYS$PNDRIVER.EXE 6.2.5.2 CLDs, and QARs reporting this problem: 6.2.5.2.1 CLD(s) None. 6.2.5.2.2 QAR(s) 75-13-1146 6.2.5.3 Problem Analysis: This occurs because these interconnects can not implement the SCS HOST_SHUTDOWN (a.k.a. last gasp datagram) message. The full RECNXINTERVAL delay can occur even when there is another cluster interconnect that supports the SCS HOST_SHUTDOWN message. This is because the connection manager only receives host shutdown messages that are delivered by the circuit that is currently being used by the VMS$VAXcluster SYSAP. To ensure that the connection manager is notified if any 'last gasp' message is received on any open virtual circuit to a remote node, the SCS last gasp handling has been modified to report receipt of a last gasp message on all circuits with the node that is going away. 6.2.5.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.5.5 Work-arounds: None. 6.2.6 Incorrect Virtual Circuit (VC) timeout error log entry 6.2.6.1 Problem Description: An improperly formatted error log entry produces a misleading VC timeout error log entry when the real error is an ill-formed SCS message, or other message causing a VC closure. Images Affected: Page 11 - [SYS$LDR]SYS$PADRIVER.EXE - [SYS$LDR]SYS$PBDRIVER.EXE - [SYS$LDR]SYS$PCADRIVER.EXE - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PIDRIVER.EXE - [SYS$LDR]SYS$PJDRIVER.EXE - [SYS$LDR]SYS$PMDRIVER.EXE - [SYS$LDR]SYS$PNDRIVER.EXE 6.2.6.2 CLDs, and QARs reporting this problem: 6.2.6.2.1 CLD(s) None. 6.2.6.2.2 QAR(s) 75-13-1146 6.2.6.3 Problem Analysis: None. 6.2.6.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.6.5 Work-arounds: None. 6.2.7 System Performance Issues Page 12 6.2.7.1 Problem Description: When running with one or more LAN devices that have unplugged or failed CABLES and/or switch ports, system performance can be very poor with unexplained high interrupt stack time and/or high mpsynch time. Also, with several such disconnected devices, the system may be unable to successfully boot, may not be able to join a cluster, or may experience unexplained VC closures and/or CLUEXITS. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER_MON.EXE 6.2.7.2 CLDs, and QARs reporting this problem: 6.2.7.2.1 CLD(s) 70-3-7119 6.2.7.2.2 QAR(s) None. 6.2.7.3 Problem Analysis: Upon adapter disconnected conditions, failed transmissions are reported immediately rather than waiting several seconds for a transmission failure timeout. 6.2.7.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.7.5 Work-arounds: None. 6.2.8 System Crash Page 13 6.2.8.1 Problem Description: If the SCACP command to enable checksumming on a particular VC is issued, memory can be corrupted in unpredictable ways, possibly causing crashes. Because the corruption may or may not occur in a critical memory location, there is no predicatable crash footprint for this bug. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER_MON.EXE 6.2.8.2 CLDs, and QARs reporting this problem: 6.2.8.2.1 CLD(s) None. 6.2.8.2.2 QAR(s) None. 6.2.8.3 Problem Analysis: A register that should point to the PEDRIVER Port Descriptor Table was being overwritten. 6.2.8.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.8.5 Work-arounds: None. 6.2.9 PGFIPLHI System Crash 6.2.9.1 Problem Description: The system can crash with a PGFIPLHI bugcheck Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE Page 14 - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PADRIVER.EXE - [SYS$LDR]SYS$PBDRIVER.EXE - [SYS$LDR]SYS$PCADRIVER.EXE - [SYS$LDR]SYS$PIDRIVER.EXE - [SYS$LDR]SYS$PJDRIVER.EXE - [SYS$LDR]SYS$PMDRIVER.EXE - [SYS$LDR]SYS$PNDRIVER.EXE 6.2.9.2 CLDs, and QARs reporting this problem: 6.2.9.2.1 CLD(s) None. 6.2.9.2.2 QAR(s) 75-102-1828 6.2.9.3 Problem Analysis: Some OpenVMS Alpha drivers inadvertently contain pageable image sections with code that is executed at IPL$_SCS. Because of this, there is a risk of PGFIPLHI crashes. Because the image sections are less than a page, executing on a uniprocessor is relatively safe, but SMP execution could lead to crashes on a system with a small system working set. 6.2.9.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.9.5 Work-arounds: None. Page 15 6.2.10 System may crash with an SMCIPORT bugcheck 6.2.10.1 Problem Description: An INIT operation on a soft partition of an ES47, ES80 or GS1280 system, may result in a rebuild of the Galaxy Config Tree. If a rebuild occurs, and there are two or more other soft partitions that are clustered together, and using the Shared Memory Cluster Interconnect, one or more of these systems may crash with an SMCIPORT bugcheck. Note that usage of the INIT command from within a soft partition is not a supported operation when other instances within the hard partition are booted. However, if the INIT command is inadvertently used, this fix will avoid a potential crash. Images Affected: - [SYS$LDR]SYS$PBDRIVER.EXE 6.2.10.2 CLDs, and QARs reporting this problem: 6.2.10.2.1 CLD(s) None. 6.2.10.2.2 QAR(s) 75-102-2214 6.2.10.3 Problem Analysis: ES47/ES80/GS1280 systems rebuild the Galaxy Config Tree on an INIT command. When the Config Tree is being rebuilt, various low level Galaxy routines will not function. In this case, the call to GLX$INSTANCE_BIT_NOTIFY returns an error. 6.2.10.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS V8.2 Page 16 6.2.10.5 Work-arounds: None. 6.2.11 IDE DMA Enabled on Itanium Systems. 6.2.11.1 Problem Description: IDE DMA was disabled on ES47, ES80 and GS1280 systems. This was done to fix reported Delayed Read TimeOut (DRTO) errors and crashes when starting to use a new CD drive on these systems. Images Affected: - [SYS$LDR]SYS$DQDRIVER.EXE 6.2.11.2 CLDs, and QARs reporting this problem: 6.2.11.2.1 CLD(s) None. 6.2.11.2.2 QAR(s) 75-13-1352 6.2.11.3 Problem Analysis: The IDE adapter pre-fetches DMA translation buffers for transactions it might need to do, but never actually performs. DQDRIVER was incorrectly defining a larger window than it needed to perform DMA transactions. The driver now correctly creates an optimally sized DMA window to perform the DMA transaction. A side benefit to this change is a speedup of the IDE on ES47, ES80 and GS1280 systems. 6.2.11.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS V8.2 6.2.11.5 Work-arounds: None. Page 17 6.2.12 Pro-active Change for use of DMA Direction Flags 6.2.12.1 Problem Description: Future CD record programs will be using commands that the DQDRIVER is not aware of. Since the driver looks at the command to decide DMA direction, this will lead to failures. The driver was adjusted to use the direction flags available for deciding DMA direction, thereby avoiding the issue. Images Affected: - [SYS$LDR]SYS$DQDRIVER.EXE 6.2.12.2 CLDs, and QARs reporting this problem: 6.2.12.2.1 CLD(s) None. 6.2.12.2.2 QAR(s) 75-102-690 6.2.12.3 Problem Analysis: See problem description 6.2.12.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS V8.2 6.2.12.5 Work-arounds: None. 6.2.13 Shorten "identify device" Wait Time. 6.2.13.1 Problem Description: When first started, DQDRIVER sends out an "identify device" packet to decide if an IDE device exists on the IDE bus. This command will always respond within a few seconds. DQDRIVER has been changed to wait only 10 seconds for this first command to respond. This leads to missing IDE devices being identified faster. Page 18 Images Affected: - [SYS$LDR]SYS$DQDRIVER.EXE 6.2.13.2 CLDs, and QARs reporting this problem: 6.2.13.2.1 CLD(s) None. 6.2.13.2.2 QAR(s) 75-102-690 6.2.13.3 Problem Analysis: See problem description 6.2.13.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS V8.2 6.2.13.5 Work-arounds: None. 6.2.14 Incorrect Virtual Circuit closures 6.2.14.1 Problem Description: Incorrect VC (Virtual Circuit) closures can occur rather than the proper behavior of generating 'Excessive packet losses on LAN path...' messages and continuing. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.STB Page 19 6.2.14.2 CLDs, and QARs reporting this problem: 6.2.14.2.1 CLD(s) None. 6.2.14.2.2 QAR(s) 75-112-3 6.2.14.3 Problem Analysis: When the underlying LAN is dropping packets at a fairly high rate (greater than 1 in 1000 lost), and there is only one remaining tight channel, a message will sometimes be issued saying the channel is experiencing excessive packet losses. The channel's buffer size will be prematurely reduced, often resulting in an immediate VC closure. This can result in VC closures when just the "excessive packet loss" channel messages should be generated and operation continued. 6.2.14.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS V8.2 6.2.14.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed in previous VMS731_DRIVER patch kits can be found in the following Release Notes files after the kit is installed: o VMS731_DRIVER-V0100.RELEASE_NOTES o VMS731_DRIVER-V0100.RELEASE_NOTES Before kit installation these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS731_DRIVER/VERSION=3.0- /DESTINATION=destination_directory Page 20 o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS731_DRIVER/VERSION=3.0 - /SELECT=[SYSUPD]file_name/DESTINATION=destination_directory 8 INSTALLATION INSTRUCTIONS 8.1 Compressed File This kit is provided as a DCX compressed kit. To expand this file to the installable PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS731_DRIVER-V0300.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the Decompress into "(file specification)" question, either a or an alternate directory specification 8.2 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS731_DRIVER /SAVE_RECOVERY_DATA [/SOURCE=location of Kit] The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. Page 21 The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 8.3 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V3.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS731_DRIVER kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS731_DRIVER/PRODUCER=DEC/BASE=AXPVMS- /VER=V3.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT Page 22 $! $ exit 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2005 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.