ECO NUMBER: VMS726C2_LAN-V0100 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-6C2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-6C2 COVER LETTER 1 KIT NAME: VMS726C2_LAN-V0100 2 KITS SUPERSEDED BY THIS KIT: None. 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: VMS726C2_COE-V0100 3.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-6C2 4.2 Files patched or replaced: o [SYSEXE]APB.EXE (new image) o [SYSEXE]DEBUG_APB.EXE (new image) o [SYS$LDR]LAN$SDA.EXE (new image) o [SYSEXE]LANACP.EXE (new image) o [SYSEXE]LANCP.EXE (new image) o [SYS$LDR]NET$CSMACD.EXE (new image) o [SYS$LDR]NET$FDDI.EXE (new image) o [SYS$LDR]SYS$EBDRIVER.EXE (new image) -- COVER LETTER -- Page 2 10 February 2003 o [SYS$LDR]SYS$EIBTDRIVER.EXE (new image) o [SYS$LDR]SYS$EIDRIVER.EXE (new image) o [SYS$LDR]SYS$ERBTDRIVER.EXE (new image) o [SYS$LDR]SYS$ERDRIVER.EXE (new image) o [SYS$LDR]SYS$EW1000A.EXE (new image) o [SYS$LDR]SYS$EWBTDRIVER.EXE (new image) o [SYS$LDR]SYS$EWDRIVER.EXE (new image) o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image) o [SYS$LDR]SYS$EZDRIVER.EXE (new image) o [SYS$LDR]SYS$FADRIVER.EXE (new image) o [SYS$LDR]SYS$FCBTDRIVER.EXE (new image) o [SYS$LDR]SYS$FCDRIVER.EXE (new image) o [SYS$LDR]SYS$FRBTDRIVER.EXE (new image) o [SYS$LDR]SYS$FRDRIVER.EXE (new image) o [SYS$LDR]SYS$FWBTDRIVER.EXE (new image) o [SYS$LDR]SYS$FWDRIVER.EXE (new image) o [SYS$LDR]SYS$ICDRIVER.EXE (new image) o [SYS$LDR]SYS$IRDRIVER.EXE (new image) o [SYS$LDR]SYS$IWDRIVER.EXE (new image) o [SYS$LDR]SYS$LAN.EXE (new image) o [SYS$LDR]SYS$LAN_ATM.EXE (new image) o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) o [SYS$LDR]SYS$LAN_FDDI.EXE (new image) o [SYS$LDR]SYS$LAN_TR.EXE (new image) o [SYSEXE]SYS$CONFIG.DAT (new file) -- COVER LETTER -- Page 3 10 February 2003 5 PROBLEMS ADDRESSED IN VMS726C2_LAN-V0100 KIT o The system can crash when another instance in the Galaxy shuts down and there is I/O outstanding to the EBA (Galaxy Shared Memory LAN) device. The driver fork routine now verifies that the other instance has not shut down before processing I/O on behalf of it. Images Affected: - [SYS$LDR]SYS$EBDRIVER.EXE o The receiving side of a transmit request to the EBA (Galaxy Shared Memory LAN) devic may crash because the PFN count is incorrect. The transmit side now updates the PFN count before updating the pointers given to the other instance in the Galaxy (that is the target of the transmit request), eliminating a race condition in the driver. Images Affected: - [SYS$LDR]SYS$EBDRIVER.EXE o If the cluster code (PEDRIVER) is using the EBA (Galaxy Shared Memory LAN) device, it may choose another slower LAN device rather than the shared memory LAN device. This change sets the device line speed to 30000 so that PEDRIVER chooses this interconnect over other slower interconnects. Images Affected: - [SYS$LDR]SYS$EBDRIVER.EXE o Occasionally, a transmit request to the EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device is not seen by the device. This causes the transmit to be delayed until the next transmit request is given to the device. Under heavy load conditions, this is not noticeable. Under light load, this is seen as a transmit that may take seconds to complete. Where the device is used as a cluster interconnect, the result is transmit retries and virtual circuit closures. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o With the EIA (82558,82559, 82559ER, DE600, DE602 PCI Ethernet) device, if the link partner redoes auto-negotiation (switch powered off, for example), the driver does not force a link transition when appropriate, resulting in the link partner selecting half-duplex mode when it should select full-duplex -- COVER LETTER -- Page 4 10 February 2003 mode. Also, the requested settings are not advertised correctly resulting in difficulty auto-negotiating to the intended speed and duplex mode. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o The EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device driver is treating the console environment variable EIx0_MODE setting of "twisted-pair" as "Full-Duplex, Twisted-pair", so it should select half-duplex 10 mbit mode, but selects full-duplex instead. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o The EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device driver is not processing the EIx0_MODE console environment variable setting of "FastFD" setting correctly. This can result in a duplex mode mismatch problem. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o The EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device occasionally reads an invalid buffer descriptor from the receive ring. When this happens a machine check occurs with resulting system crash, often with an "invalid scatter-gather map" error. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o Add support for the Intel 82559ER chip and the DE602-BB NIC. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o Add support for internal loopback mode. Some applications, for example, the UETP system test package, use internal loopback mode in the EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device driver. This now runs correctly on these NICs. -- COVER LETTER -- Page 5 10 February 2003 Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o Add support for the 82558/82559 self-test after initialization. This test ensures that the driver does not attempt to use the device before it has passed some basic functional self-testing. If self-test fails, the device is marked offline. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o Address performance problems with receive processing in the EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device driver. This change restructures receive processing to improve performance, and reduce the number of receive overflows. Receive overflows are visible in the LAN counters for the device and each overflow represents a lost packet which causes application pauses and retransmits. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o Resolve a system crash with the EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device driver and with IP traffic (generally involving a lot of telnet connections). When the number of segments comprising a transmit packet request exceeds 15, the driver copies the remaining segments into one additional segment. If this segment is not physically contiguous, therefore requiring two additional segments instead of one, the driver corrupts the stack and causes an INVEXCPTN system crash. The problem is that the check for maximum number of segments is off by one. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o Fix a few problems with auto-negotiation by DE500-BA PCI Ethernet devices to improve the ability of the driver to auto-negotiate to the correct setting. This includes adjusting the timing of various auto-negotiation events, and restarting auto-negotiation when appropriate. Images Affected: - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE -- COVER LETTER -- Page 6 10 February 2003 o On rare occasions, it is possible for the Tulip driver to reset the Tulip chip, but not wait long enough after reset before touching the device resulting in a machine check system crash. The solution is to increase the amount of time after a reset to guarantee that the device has sufficient time to reset itself after a reset. The Tulip driver includes support for the Tulip chip, DE425 EISA NIC, and the PCI Ethernet NICs DE434, DE435, DE500-XA, DE500-AA, DE500-BA, DE504-BA. Images Affected: - [SYS$LDR]SYS$ERDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE o The system can crash when configuring the DE425 on an AlphaStation 150. The driver expects to have map registers but they are not present on this system. Images Affected: - [SYS$LDR]SYS$ERDRIVER.EXE o Adjust interrupt handling changes that were done to the Tulip driver for V7.2-1H1 to address a problem with delayed interrupts. On occasion, the interrupt for a receive packet is delayed until a subsequent packet is received. Under heavy load conditions this is not noticeable, under light load, it happens occasionally. The Tulip driver includes support for the Tulip chip, DE425 EISA NIC, and the PCI Ethernet NICs DE434, DE435, DE500-XA, DE500-AA, DE500-BA, DE504-BA. Images Affected: - [SYS$LDR]SYS$ERDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE o On the Alpha Professional Workstation (XP-1000) with the embedded DE500-BA, auto-negotiation is not enabled correctly after a user request to set the mode. This results in an inability to negotiate to the desired speed and duplex mode. (DE500-BA only). Images Affected: - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE -- COVER LETTER -- Page 7 10 February 2003 o A transmit issued to the DE500-BA PCI Ethernet device driver may complete with false error status. The transmit status is correctly recognized as 'success', but in the process of setting the correct status, the driver clears the transmit length, so transmit requests completed by the driver to the user application have a length of zero bytes rather than the requested length. This may affect an application which depends on the valid length. Images Affected: - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE o Return SS$_DISCONNECT error status on transmit requests to the DE500-BA PCI Ethernet device driver which complete with a "loss of carrier" error. This error occurs if the cable is disconnected using the 10Base5 MAU on the Alpha Workstations. Images Affected: - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE o Although it is a rare occurance, it is possible for a system to hang in a continuous interrupt loop in the DE500-BA PCI Ethernet device driver. The DE500-BA generates an unusual interrupt and the interrupt service routine does not clear the interrupt condition, resulting in an apparent system hang, as interrupts are continuously generated. Images Affected: - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE o Add support for the Alpha Professional Workstation, XP-1000, for the alternative MAU options, the 10/100 UTP, 10Base2, and 10Base5, which attach to the embedded DE500-BA. Images Affected: - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE o The DEGPA firmware included in the device driver for the DEGPA PCI Gigabit Ethernet NIC cannot deal with a transmit buffer that is within 12 bytes of a 4 gigabyte boundary. This could lead to data corruption. This problem only affects the AlphaServer 4100, AlphaServer DS20, AlphaServer ES40, AlphaServer GS80 and GS160, and system upgrades such as the DS25, ES45, and only those systems with at least 4 gigabytes of memory. The fix is to avoid the problem by copying the buffer to a special buffer that is not near such a boundary. The number of times the workaround is invoked is tallied in the internal driver counters (MC LANCP SHOW -- COVER LETTER -- Page 8 10 February 2003 DEVICE/INTERNAL_COUNTERS) called "4GB workarounds", so you can see if the condition ever does occur. Images Affected: - [SYS$LDR]SYS$EW1000A.EXE o Increase the amount of time given for device reset by the DEGPA PCI Gigabit Ethernet device driver of the Tigon II chip.. The time is increased from 80 to 640 milliseconds. On some systems, insufficient reset time occasionally results in a machine check system crash when the driver touches the device after a reset. Images Affected: - [SYS$LDR]SYS$EW1000A.EXE o When a user (protocol) is stopped, the user context is not reset correctly by the DEGPA PCI Gigabit Ethernet device driver. This results in an inability to restart the user without rebooting the system. For example, if DECnet is stopped and restarted it may fail to restart. Images Affected: - [SYS$LDR]SYS$EW1000A.EXE o The multicast addresses list is not given to the DEGPA PCI Gigabit Ethernet device again after the driver resets the device to clear a transmit timeout condition. This can happen if the cable is unplugged with transmits outstanding to the device. The consequence is that multicast traffic stops for all users (protocols) until another user is started or an existing user is stopped and restarted. Images Affected: - [SYS$LDR]SYS$EW1000A.EXE o Under rare circumstances, the TGEC driver, SYS$EZDRIVER, on DEC 4000 Model 410 systems, can bugcheck with a NETDLLERR crash when the driver detects an inconsistency in its data structures. This can occur when the last user (of the EZA or EZB LAN device) stops and the number of outstanding transmits is not zero. This fix corrects the problem. Images Affected: - [SYS$LDR]SYS$EZDRIVER.EXE -- COVER LETTER -- Page 9 10 February 2003 o On DEC 7000 systems with the DEFPA PCI FDDI device, which use mailbox hardware to read and write registers, the error bits, which the driver should clear, are not being cleared properly. This may result in a machine check system crash because of stale error bits. Images Affected: - [SYS$LDR]SYS$FWDRIVER.EXE o Increase the time after a reset before touching the PDQ FDDI LAN device (FCA - DEFTA Turbochannel, FAA - DEFRA - DEFEA EISA, FWA - DEFPA PCI). This as well as the above change may contribute to an occasional machine check system crash after the driver resets the device during system boot. Images Affected: - [SYS$LDR]SYS$FCDRIVER.EXE - [SYS$LDR]SYS$FADRIVER.EXE - [SYS$LDR]SYS$FRDRIVER.EXE - [SYS$LDR]SYS$FWDRIVER.EXE o For the PDQ FDDI LAN devices (FCA - DEFTA Turbochannel, FAA - DEFRA - DEFEA EISA, FWA - DEFPA PCI), change the restart policy after a device initialization error from 'mark the device offline' to 'retry every 10 seconds indefinitely'. This change allows the driver to recover from a temporary initialization failure and to avoid the need for a system reboot to clear the condition. Images Affected: - [SYS$LDR]SYS$FCDRIVER.EXE - [SYS$LDR]SYS$FADRIVER.EXE - [SYS$LDR]SYS$FRDRIVER.EXE - [SYS$LDR]SYS$FWDRIVER.EXE o In OpenVMS Version V7.2, the device line speed was added to the LAN Device Characteristics block (LDC) that VCI applications can look at to determine device characteristics. For the token ring drivers, the speed field is incorrectly specified so it is always zero. This fix correctly adds the line speed to the LDC block. -- COVER LETTER -- Page 10 10 February 2003 Images Affected: - [SYS$LDR]SYS$ICDRIVER.EXE - [SYS$LDR]SYS$IRDRIVER.EXE - [SYS$LDR]SYS$IWDRIVER.EXE o For all LAN devices, modify the VCI transmit path (used by PEDRIVER, DECnet-Plus, TCP/IP, LAST, LAT and others) to verify the transmit request is not too long, incrementing the "Transmit too long" error counter and returning error status to the offending application. This improves the ability to diagnose application problems by identifying the failure to transmit in the device counters and making it more visible. Images Affected: - [SYS$LDR]SYS$LAN.EXE - [SYS$LDR]SYS$LAN_CSMACD.EXE - [SYS$LDR]SYS$LAN_FDDI.EXE - [SYS$LDR]SYS$LAN_TR.EXE - [SYS$LDR]SYS$LAN_ATM.EXE o For all LAN devices, modify the VCI interface to allow a VCI user to enable promiscuous mode. Images Affected: - [SYS$LDR]SYS$LAN.EXE - [SYS$LDR]SYS$LAN_CSMACD.EXE - [SYS$LDR]SYS$LAN_FDDI.EXE - [SYS$LDR]SYS$LAN_TR.EXE - [SYS$LDR]SYS$LAN_ATM.EXE o For all LAN devices, Remove the limitation of 255 multicast addresses enabled for a device. This may improve efficiency somewhat by decreasing the multicast filtering work done by the LAN driver. Only the Gigabit Ethernet devices take advantage of this capability. Images Affected: -- COVER LETTER -- Page 11 10 February 2003 - [SYS$LDR]SYS$LAN.EXE - [SYS$LDR]SYS$LAN_CSMACD.EXE - [SYS$LDR]SYS$LAN_FDDI.EXE - [SYS$LDR]SYS$LAN_TR.EXE - [SYS$LDR]SYS$LAN_ATM.EXE o Add initial hardware support for the Fore Networks HE155 (DAPBA) and HE622 (DAPCA) NICs, including the ForeThought LAN emulation code ported to OpenVMS, located in SYS$LAN_ATM4.EXE. Images Affected: - [SYS$LDR]SYS$ELDRIVER4.EXE - [SYS$LDR]SYS$LAN.EXE - [SYS$LDR]SYS$LAN_CSMACD.EXE - [SYS$LDR]SYS$LAN_FDDI.EXE - [SYS$LDR]SYS$LAN_TR.EXE - [SYS$LDR]SYS$LAN_ATM.EXE o When a DECnet-Plus NCL command, "SHOW FDDI STATION * ALL" request is processed by the LAN driver network management code, if the requested device returns counters data asynchronously, it is possible that R3 is destroyed during the LAN driver processing. This results in an INVEXCPTN crash in NCL.EXE. The problem is that R3 is not preserved cross the call to obtain counters, when it should be. This affects any DECnet-Plus network managed device that returns counters data asynchronously to a counters request, which is all XMI and all FDDI adapters. Images Affected: - [SYS$LDR]NET$CSMACD.EXE - [SYS$LDR]NET$FDDI.EXE o Fix the display of error messages displayed by LANCP and LANACP. If there were multiple errors when validating a command, not all of the error codes were saved properly, resulting in difficulty deciphering what went wrong when a command failed. -- COVER LETTER -- Page 12 10 February 2003 Images Affected: - [SYSEXE]LANACP.EXE o Increase the allowed length of the LAN$DLL logical name from 16 to 256 characters. This is used by LANACP to locate the default directory containing downline load images. Images Affected: - [SYSEXE]LANACP.EXE o If the parent device name is not specified in the definition of an ATM emulated LAN, other parameters specified in the command are lost. So, if a series of parameters are specified, in separate commands, the parameters are not saved until a command specifying the parent device name was specified. Images Affected: - [SYSEXE]LANACP.EXE o Decrease the number of receive buffers specified for use by MOP from 6 to 4 to reduce the amount of bytlm quota required by the LANACP process. Images Affected: - [SYSEXE]LANACP.EXE o If LANACP fails to enable downline load service for a particular device, at initial startup, it returns error status to the system startup code which then terminates the image. The result is that LANACP is not running after the system boots. This change modifies LANACP so it continues to run after being started, on any devices that it was able to start on, despite a startup error on a device. Images Affected: - [SYSEXE]LANACP.EXE o The message buffer for downline load service messages is too small. this could cause it to be overrun, resulting in the termination of LANACP with a stack dump. Images Affected: - [SYSEXE]LANACP.EXE -- COVER LETTER -- Page 13 10 February 2003 o Add support for automatic loading of the ATM emulated LAN drivers, for the ELAN and CLIP emulated devices. Images Affected: - [SYSEXE]LANACP.EXE o LANCP does not return the expected status to CLUSTER_CONFIG.COM resulting in unexpected errors when attempting to configure the satellite boot portion of cluster configuration. Images Affected: - [SYSEXE]LANCP.EXE o Improve the boot messages for the EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet), ERA (Tulip, DE422 EISA, DE425 EISA, DE205 ISA Ethernet), and EWA (PCI Tulip, DE434, DE435, DE500-XA, DE500-AA, DE500-BA PCI Ethernet) LAN devices, so that more details are available to diagnose boot failures. Images Affected: - [SYS$LDR]SYS$EWBTDRIVER.EXE - [SYS$LDR]SYS$ERBTDRIVER.EXE - [SYS$LDR]SYS$EIBTDRIVER.EXE - [SYSEXE]APB.EXE - [SYSEXE]DEBUG_APB.EXE o Add support for booting the Alpha Personal Workstation, XP-1000, over the embedded 21143 chip. Images Affected: - [SYS$LDR]SYS$EWBTDRIVER.EXE - [SYS$LDR]SYS$ERBTDRIVER.EXE - [SYSEXE]APB.EXE - [SYSEXE]DEBUG_APB.EXE o The boot driver for the DE500 PCI Ethernet device is not restarting auto-negotiation after resetting the device, which results in the link partner (generally an auto-negotiating 10/100 switch) selecting half-duplex mode and the boot driver selecting full-duplex mode. The duplex mode mismatch slows satellite booting considerably. -- COVER LETTER -- Page 14 10 February 2003 Images Affected: - [SYS$LDR]SYS$EWBTDRIVER.EXE - [SYSEXE]APB.EXE - [SYSEXE]DEBUG_APB.EXE o The embedded 21143 chip (10/100 Ethernet) in the Alpha Personal Workstation, is not programmed correctly resulting in an inability to auto-negotiate properly and an inability to work at all console-specified modes (the console environment variable settings). Images Affected: - [SYS$LDR]SYS$EWBTDRIVER.EXE - [SYSEXE]APB.EXE - [SYSEXE]DEBUG_APB.EXE o OpenVMS Version V7.3 LAN cluster support obsoletes the system parameter, NISCS_LAN_OVRHD, which was typically set to 18 bytes. This parameter reduces the maximum packet size used by the cluster code. When set to 0-5 bytes, the packet size exceeds the size of the receive buffers in the FDDI boot driver for the TurboChannel DEFTA, EISA DEFEA, and PCI DEFPA FDDI devices. This usually results in 1-6 bytes of zeros scattered about the images loaded by the boot driver, which in turn, results in a system crash when an affected image attempts to execute the corrupted portion of the image. The problem is significant only when the NISCA_LAN_OVRHD parameter is set to 0-5 bytes on the system which is the FDDI boot server, regardless of which OpenVMS release the server is running on. For version V7.3 and later, the parameter is obsolete and the LAN cluster driver (PEDRIVER) does not reduce the maximum packet size at all. The fix corrects the problem in the FDDI boot driver in the satellite node by increasing the receive buffer size to accomodate the maximum possible size FDDI packet. Images Affected: - [SYS$LDR]SYS$FCBTDRIVER.EXE - [SYS$LDR]SYS$FRBTDRIVER.EXE - [SYS$LDR]SYS$FWBTDRIVER.EXE -- COVER LETTER -- Page 15 10 February 2003 - [SYSEXE]APB.EXE - [SYSEXE]DEBUG_APB.EXE o Add support (device IDs) for the following new hardware: o DE602-BA i82558 100BaseTX o DE602-TA i82558 100BaseTX o IntraServer i82558 Fast Ethernet o DAPBA-FA (155m, MMF) o DAPBA-UA (155m, UTP) o DAPCA-FA (622m, MMF) Images Affected: - [SYSEXE]SYS$CONFIG.DAT 6 KIT INSTALLATION RATING: The following kit 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) INSTALLATION RATING: INSTALL_2 : To be installed by all customers using the following feature(s): OpenVMS Alpha V7.2-6C2 Operating System 7 INSTALLATION INSTRUCTIONS: 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 VMS726C2_LAN /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt -- COVER LETTER -- Page 16 10 February 2003 This kit requires a system reboot. Compaq 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. 7.1 Special Installation Instructions: 7.1.1 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 definitions and commands: - $ DEFINE/SYS NO_ASK$BACKUP TRUE - $ DEFINE/SYS NO_ASK$REBOOT TRUE - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V1.0 - De-assign the logicals assigned For example, a sample command file to install the VMS726C2_LAN-V0100 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS721H1_LAN/PROD=DEC/BASE=AXPVMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit Copyright [2003] Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. -- COVER LETTER -- Page 17 10 February 2003 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 OR ANY OF ITS SUBSIDIARIES 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.