**************************** ECO SUMMARY INFORMATION **************************** Release Date: 13-APR-2004 Kit Name: DEC-AXPVMS-VMS73_LAN-V0600--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3 Approximate Kit Size: 6224 blocks Installation Rating: INSTALL_2 Required Features: LAN Superseded Kits: VMS73_LAN-V0500 Mandatory Kit Dependencies: VMS73_UPDATE-V0300 VMS73_PCSI-V0200 Optional Kit Dependencies: None. VMS73_LAN-V0600.PCSI-DCX_AXPEXE Checksum: 3164780567 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS73_LAN-V0600 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 1 KIT NAME: VMS73_LAN-V0600 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2: To be installed by all customers using the following feature(s): - LAN 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 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS73_LAN-V0500 Page 2 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS73_PCSI-V0200 - VMS73_UPDATE-V0300 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None. 5 FILES PATCHED OR REPLACED: o [SYSEXE]APB.EXE (new image) Image Identification Information image name: "APB" image file identification: "X-8" image file build identification: "X91Y-0060010002" link date/time: 25-JUL-2002 00:28:54.97 linker identification: "A11-50" Overall Image Checksum: 230135085 o [SYSEXE]DEBUG_APB.EXE (new image) Image Identification Information image name: "DEBUG_APB" image file identification: "X-8" image file build identification: "X91Y-0060010002" link date/time: 25-JUL-2002 00:33:49.61 linker identification: "A11-50" Overall Image Checksum: 2623798498 o [SYS$LIB]LAN$SDA.EXE (new image) Image Identification Information image name: "LAN$SDA" image file identification: "4" image file build identification: "0060010019" link date/time: 9-FEB-2004 15:00:59.14 linker identification: "A11-50" Overall Image Checksum: 2901176734 Page 3 o [SYSEXE]LANACP.EXE (new image) Image Identification Information image name: "LANACP" image file identification: "X-31" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:36.44 linker identification: "A11-50" Overall Image Checksum: 4016800761 o [SYS$LDR]NET$CSMACD.EXE (new image) Image Identification Information image name: "NET$CSMACD" image file identification: "X-17" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:33.46 linker identification: "A11-50" Overall Image Checksum: 498146237 o [SYS$LDR]NET$FDDI.EXE (new image) Image Identification Information image name: "NET$FDDI" image file identification: "X-17" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:34.16 linker identification: "A11-50" Overall Image Checksum: 381224813 o [SYS$LDR]SYS$EBDRIVER.EXE (new image) Image Identification Information image name: "SYS$EBDRIVER" image file identification: "X-12" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:52.96 linker identification: "A11-50" Overall Image Checksum: 3367197909 o [SYS$LDR]SYS$EIBTDRIVER.EXE (new image) Image Identification Information image name: "SYS$EIBTDRIVER" image file identification: "X-1" image file build identification: "X91Y-0060010004" link date/time: 28-JUN-2002 08:39:11.12 linker identification: "A11-50" Overall Image Checksum: 638682849 Page 4 o [SYS$LDR]SYS$EIDRIVER.EXE (new image) Image Identification Information image name: "SYS$EIDRIVER" image file identification: "X-25A3" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:54.91 linker identification: "A11-50" Overall Image Checksum: 33883901 o [SYS$LDR]SYS$ELDRIVER4.EXE (new image) Image Identification Information image name: "SYS$ELDRIVER4" image file identification: "X13A1" image file build identification: "X9UH-0060010001" link date/time: 21-AUG-2003 15:23:30.83 linker identification: "A11-50" Overall Image Checksum: 2639803918 o [SYS$LDR]SYS$ERBTDRIVER.EXE (new image) Image Identification Information image name: "SYS$ERBTDRIVER" image file identification: "X-4" image file build identification: "X91Y-0060010004" link date/time: 28-JUN-2002 08:39:35.63 linker identification: "A11-50" Overall Image Checksum: 2277817899 o [SYS$LDR]SYS$ERDRIVER.EXE (new image) Image Identification Information image name: "SYS$ERDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 14:59:58.44 linker identification: "A11-50" Overall Image Checksum: 1095835937 o [SYS$LDR]SYS$EW1000A.EXE (new image) Image Identification Information image name: "SYS$EW1000A" image file identification: "X-28C2" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:48.67 linker identification: "A11-50" Overall Image Checksum: 3725508874 Page 5 o [SYS$LDR]SYS$EW5700.EXE (new image) Image Identification Information image name: "SYS$EW5700" image file identification: "X-5A8" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:50.83 linker identification: "A11-50" Overall Image Checksum: 2452933787 o [SYS$LDR]SYS$EWBTDRIVER.EXE (new image) Image Identification Information image name: "SYS$EWBTDRIVER" image file identification: "X-4" image file build identification: "X91Y-0060010004" link date/time: 28-JUN-2002 08:39:43.47 linker identification: "A11-50" Overall Image Checksum: 3833398203 o [SYS$LDR]SYS$EWDRIVER.EXE (new image) Image Identification Information image name: "SYS$EWDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:04.37 linker identification: "A11-50" Overall Image Checksum: 936942368 o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image) Image Identification Information image name: "SYS$EWDRIVER_DE500BA" image file identification: "X-3" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:06.90 linker identification: "A11-50" Overall Image Checksum: 1469794212 o [SYS$LDR]SYS$FWDRIVER.EXE (new image) Image Identification Information image name: "SYS$FWDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:20.33 linker identification: "A11-50" Overall Image Checksum: 522156637 Page 6 o [SYS$LDR]SYS$HWDRIVER4.EXE (new image) Image Identification Information image name: "SYS$HWDRIVER4" image file identification: "X15A1" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 15:00:56.90 linker identification: "A11-50" Overall Image Checksum: 1782561927 o [SYS$LDR]SYS$LAN.EXE (new image) Image Identification Information image name: "SYS$LAN" image file identification: "X-3" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 14:59:15.77 linker identification: "A11-50" Overall Image Checksum: 50321579 o [SYS$LDR]SYS$LAN_ATM.EXE (new image) Image Identification Information image name: "SYS$LAN_ATM" image file identification: "X-28" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 14:59:25.93 linker identification: "A11-50" Overall Image Checksum: 2647142298 o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) Image Identification Information image name: "SYS$LAN_CSMACD" image file identification: "X-3" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 14:59:20.93 linker identification: "A11-50" Overall Image Checksum: 768649411 o [SYS$LDR]SYS$LAN_FDDI.EXE (new image) Image Identification Information image name: "SYS$LAN_FDDI" image file identification: "X-3" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 14:59:37.19 linker identification: "A11-50" Overall Image Checksum: 3939885673 Page 7 o [SYS$LDR]SYS$LAN_TR.EXE (new image) Image Identification Information image name: "SYS$LAN_TR" image file identification: "X-3" image file build identification: "X9UH-0060010019" link date/time: 9-FEB-2004 14:59:41.23 linker identification: "A11-50" Overall Image Checksum: 3183777688 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS73_LAN-V0600 KIT 6.1 Problems addressed in this kit 6.1.1 Writeboot not performed if VMS73_LAN-V0500 ECO kit removed 6.1.1.1 Problem Description: The VMS73_LAN-V0500 ECO kit contains the APB.EXE image. If the kit is removed via the PCSI UNDO option, the previous APB.EXE is replaced and the boot block changes. A writeboot needs to be performed in order to point to the new boot block. The kit should perform the writeboot as part of the UNDO operation but it does not. This may leave the system in an unbootable state if the VMS73_LAN-V0500 kit is removed. The VMS73_LAN-V0600 ECO kit provides this writeboot function. Images Affected: - POST_UNDO.COM 6.1.1.2 CLDs, and QARs reporting this problem: 6.1.1.2.1 CLD(s) None. 6.1.1.2.2 QAR(s) None. Page 8 6.1.1.3 Problem Analysis: See Problem Description 6.1.1.4 Release Version of OpenVMS that will contain this change: Not Applicable 6.1.1.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS 7.1 Problems addressed in the VMS73_LAN-V0500 kit 7.1.1 Link down conditions are not properly detected. 7.1.1.1 Problem Description: Link down conditions are not properly detected. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE 7.1.1.2 CLDs, and QARs reporting this problem: 7.1.1.2.1 CLD(s) CFS.87376,CFS.91975,CFS.96738 7.1.1.2.2 QAR(s) None. 7.1.1.3 Problem Analysis: When a DE60x adapter would lose a valid link, a transmit timeout had to occur before it would return a transmit request with a SS$_DISCONNECT status. This behavior was inconsistent with current gigabit ethernet drivers and would prevent some upper-layer protocols from detecting a link down condition. Page 9 7.1.1.4 Release Version of OpenVMS that will contain this change: V7.3-2 7.1.1.5 Work-arounds: None. 7.1.2 System can crash with various bugchecks. 7.1.2.1 Problem Description: The System can crash with various bugchecks. Lock manager related bugchecks seem to be the most common. Images Affected: - [SYS$LDR]SYS$FWDRIVER.EXE 7.1.2.2 CLDs, and QARs reporting this problem: 7.1.2.2.1 CLD(s) CFS.105418 7.1.2.2.2 QAR(s) None. 7.1.2.3 Problem Analysis: On transmit, the PDQ will sometimes update the consumer index before actually completing the transmit. The result can be packet corruption that leads to crashes. Large remastering operations seem to be good at aggrevating this problem. 7.1.2.4 Release Version of OpenVMS that will contain this change: V7.3-2 Page 10 7.1.2.5 Work-arounds: None. 7.1.3 INVEXCEPTN, Exception while above ASTDEL in SYS$EW1000A 7.1.3.1 Problem Description: During device initialization, if a DEGPA had a non-default setting in the LAN device database and MOP DLL enabled, it was possible for the initialization to not complete properly. This resulted in an INVEXCEPTN bugcheck when the first receive completed. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF.960F4B48 SYS$EW1000A+04B48 Failing PS: 00000000.00000804 Module: SYS$EW1000A (Link Date/Time: 4-DEC-2000 14:46:27.28) Offset: 00004B48 Images Affected: - [SYS$LDR]SYS$EW1000A.EXE 7.1.3.2 CLDs, and QARs reporting this problem: 7.1.3.2.1 CLD(s) CFS.98123 7.1.3.2.2 QAR(s) None. 7.1.3.3 Problem Analysis: The conditions described above would cause a delay in initialization. Later, when the IRP was continued from the control request queued, the LAN function was not correctly interpreted and port driver would be left in an improper state. Page 11 7.1.3.4 Release Version of OpenVMS that will contain this change: V7.3-2 7.1.3.5 Work-arounds: None. 7.1.4 Auto-negotiation never completes with DE500 network adapters 7.1.4.1 Problem Description: For DE500 network adapters with external PHYs, if the link partner advertises 100base-T4 capability, auto-negotiation will never complete. Images Affected: - [SYS$LDR]SYS$EWDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE - [SYS$LDR]SYS$ERDRIVER.EXE 7.1.4.2 CLDs, and QARs reporting this problem: 7.1.4.2.1 CLD(s) CFS.96853 7.1.4.2.2 QAR(s) None. 7.1.4.3 Problem Analysis: Since DE500 network adapters with external PHYs, are not capable of supporting 100base-T4, TU_NWAY_EXT would check to see if the link partner was advertising this capability and, if so, would restart auto-negotiation, even if there were other common capabilities. Page 12 7.1.4.4 Release Version of OpenVMS that will contain this change: V7.3-2 7.1.4.5 Work-arounds: None. 7.1.5 LAN device initialization fails leaving device unusable 7.1.5.1 Problem Description: If a soft error occurs while a LAN protocol is starting, it is possible for the initialization to fail and leave the device in an unusable state until the next reboot. Images Affected: - [SYS$LDR]SYS$EWDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE - [SYS$LDR]SYS$ERDRIVER.EXE 7.1.5.2 CLDs, and QARs reporting this problem: 7.1.5.2.1 CLD(s) None. 7.1.5.2.2 QAR(s) None. 7.1.5.3 Problem Analysis: During soft error processing, pending control requests were being returned without any processing. 7.1.5.4 Release Version of OpenVMS that will contain this change: V7.3-2 Page 13 7.1.5.5 Work-arounds: None. 7.1.6 DMA Write Engine loss of synchronization 7.1.6.1 Problem Description: Some Gigabit Ethernet LAN-on-Motherboard (LOM) and Network-Interface-Card (NIC) implementations may, in response to a rare trigger event, experience a DMA Write Engine loss of synchronization when transferring data from adapter/chip memory to host CPU memory. This loss of synchronization can manifest itself in one or a combination of several ways: o Data integrity problem o System hang o Transmit time-out o System Crash, depending how the network connection is used. This problem can occur on the following Gigabit Ethernet LAN-on-Motherboard (LOM) and Network-Interface-Card (NIC) implementations: o DS25 GbE LOM Implementation, UTP copper o 3X-DEGXA-SA PCI GbE NIC, MMF o 3X-DEGXA-TA PCI GbE NIC, UTP copper In those situations where a non-data CRC checking protocol is being used, applications are at risk to produce indeterminate results stemming from the DMA Write Engine loss of synchronization. Non-data CRC checking protocols include but are not limited to: o OpenVMS Cluster - data CRC checking can be turned on, but is off by default o OpenVMS Pathworks o DECnet o LAT o DLI In these situations there are no user-discernable symptoms. Other causes of the problem can cause the following symptoms: Page 14 - Transmit Time-outs - System Crash - Unexplained Link Drops - Apparent Loss Of Network Connection - in situations where a data CRC checking protocol is being used, IP for example, the network connection is effectively disconnected from the network. In this case, all packets received subsequent to the trigger event are discarded by the IP protocol stack. HP has observed this problem only in internal laboratory environments. There are no known field/customer reports of this problem, or manifestations of this problem occurring. While the likelihood of the trigger event occurring in a customer application environment is perceived to be low in most cases, the actual probability is not known. However, it is not zero. Because of th is HP is advising customers of the anomaly so that they may take precautions to prevent it. Images Affected: - [SYS$LDR]SYS$EW5700.EXE - [SYSLIB]LAN$SDA.EXE 7.1.6.2 CLDs, and QARs reporting this problem: 7.1.6.2.1 CLD(s) None. 7.1.6.2.2 QAR(s) None. 7.1.6.3 Problem Analysis: This condition is triggered by the rare occurrence of the back-to-back receipt of 13 or more, 81 to 84 Byte long packets coincident with a medium-to-high aggregate (transmit & receive) load of jumbo frame traffic, and/or an instance of high CPU utilization that causes the CPU to be near 100% busy. Once triggered, all subsequently received packets, regardless of size, will, unless preempted by a system hang or transmit time-out, be impacted by the DMA Write Engine loss of synchronization. A device reset, accompanied by a link drop of approximately 0.5 second, is required to clear the Page 15 condition. 7.1.6.4 Release Version of OpenVMS that will contain this change: V7.3-2 7.1.6.5 Work-arounds: None. 7.1.7 DE600 driver would restart the device incorrectly 7.1.7.1 Problem Description: Occasionally, after supplying it with more receive buffers, the DE600 driver would restart the device incorrectly. This resulted in a machine check. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE - [SYSLIB]LAN$SDA.EXE 7.1.7.2 CLDs, and QARs reporting this problem: 7.1.7.2.1 CLD(s) None. 7.1.7.2.2 QAR(s) None. 7.1.7.3 Problem Analysis: A recent change was made to EIDRIVER to synthesize transit error status when the link was down. This allowed applications to recognize link down conditions properly, most notably, to allow TCP/IP to recognize that the link was down for failover purposes. This change resulted in link status not being recognized properly for the DE602-FA. This driver change corrects the problem, and the link state is now recognized properly. Page 16 7.1.7.4 Release Version of OpenVMS that will contain this change: V7.3-2 7.1.7.5 Work-arounds: None. 7.1.8 ATM link continuously cycles up and down 7.1.8.1 Problem Description: An event such as the network cable being pulled and reconnected would cause the ATM link to continuously cycle up and down. Images Affected: - [SYS$LDR]SYS$HWDRIVER4.EXE 7.1.8.2 CLDs, and QARs reporting this problem: 7.1.8.2.1 CLD(s) CFS.90390 7.1.8.2.2 QAR(s) None. 7.1.8.3 Problem Analysis: When an ATM station opens a ILMI connection to its adjacent station and it remains open, if an event causes the port driver to do a reset, a second ILMI port is opened which causes the link to constantly cycle up and down. 7.1.8.4 Release Version of OpenVMS that will contain this change: V7.3-2 Page 17 7.1.8.5 Work-arounds: None. 7.1.9 When specifying media type using LANCP, other port settings did not work correctly. 7.1.9.1 Problem Description: When specifying the media type with LANCP using a SET or DEFINE DEVICE /MEDIA command, if other qualifiers such as /SPEED or /FULL_DUPLEX were specified, and the previous media type did not support the specified speed or duplex, the /SPEED and /FULL_DUPLEX qualifiers would be ignored. For example, if a DE435 was set for a media type of BNC and the LANCP command SET DEVICE /MEDIA=TWISTED /SPEED=100 was used, the /SPEED qualifier would be ignored because the BNC media type does not support it. Images Affected: - [SYSEXE]LANACP.EXE 7.1.9.2 CLDs, and QARs reporting this problem: 7.1.9.2.1 CLD(s) CFS.10001 7.1.9.2.2 QAR(s) None. 7.1.9.3 Problem Analysis: In applying a port's mode changes to the adaptor, media setting changes were done last which caused a problem if there was another mode change specified that was dependent on the media setting. For example, if the media setting was changed from BNC to UTP and at the same time a full duplex setting was specified, the duplex setting would be ignored by the port driver since full duplex is not valid for BNC media. Page 18 7.1.9.4 Release Version of OpenVMS that will contain this change: V7.3-2 7.1.9.5 Work-arounds: None. 7.1.10 Modifies the default to driver link handling from firmware link handling. 7.1.10.1 Problem Description: The driver or the firmware can do link handling. The driver defaults to relying on firmware link handling. However, the firmware in the DEGXA-SB version of the DEGXA fiber NIC has some issues which may affect functionality. This change modifies the default to driver link handling to avoid the firmware issues. Images Affected: - [SYS$LDR]SYS$EW5700.EXE 7.1.10.2 CLDs, and QARs reporting this problem: 7.1.10.2.1 CLD(s) None. 7.1.10.2.2 QAR(s) None. 7.1.10.3 Problem Analysis: See problem Description 7.1.10.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS after V7.3-2 Page 19 7.1.10.5 Work-arounds: None. 7.2 Problems addressed in the VMS73_LAN-V0100 to VMS73_LAN-V0400 kits Problem information for problems addressed in VMS73_LAN-V0100 to VMS73_LAN-V0400 V7.3 LAN kits can be found in the file [SYSHLP]VMS73_LAN-V0100_to_V0400.README. These kits have been incorporated in the VMS73_UPDATE-V0300 ECO kit. 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 VMS73_LAN-V0600.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 Page 20 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 VMS73_LAN /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. 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/SYS 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=V6.0/SAVE_RECOVERY_DATA Page 21 o De-assign the logical names assigned For example, a sample command file to install the VMS73_LAN kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/SYS ARCHIVE_OLD NO $! $ PROD INSTALL VMS73_LAN/PRODUCER=DEC/BASE=AXPVMS- /VER=V6.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2004 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.