Kit Name: DEC-AXPVMS-VMS82A_LAN-V0300--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V8.2 Approximate Kit Size: 2813 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VMS82A_LAN-V0200 Mandatory Kit Dependencies: VMS82A_UPDATE-V0700 or later VMS82A_PCSI-V0100 or later Optional Kit Dependencies: None Checksums: VMS82A_LAN-V0300.ZIPEXE Checksum: 1392798039 DEC-AXPVMS-VMS82A_LAN-V0300--4.PCSI$COMPRESSED Checksum: 774745110 VMS82A_LAN-V0300.ZIPEXE MD5 Checksum: AD9F138BE08D60B2E174EEB45228074F DEC-AXPVMS-VMS82A_LAN-V0300--4.PCSI$COMPRESSED MD5 Checksum: 1E85DBA7CE07B6F6B1A4A55B7FD160F7 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS82A_LAN-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 V8.2 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS82A_LAN-V0200 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS82A_PCSI-V0100 - VMS82A_UPDATE-V0700 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: - None 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS82A_LAN-V0300 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Potential Application Start-Up Problem 5.2.1.1 Problem Description: There is a potential problem in startup of an application, where the indication that the new channel is available and ready happens before the request to start the new channel finishes. This condition may result in a crash in the NET$CSMACD.EXE module when DECnet-Plus starts up, or may result in a PEDRIVER channel that cannot be stopped or started. Images Affected: - [SYS$LDR]SYS$LAN.EXE - [SYS$LDR]SYS$LAN_FDDI.EXE - [SYS$LDR]SYS$LAN_ATM.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. 5.2.1.2.2 QAR(s) None. Page 3 5.2.1.3 Problem Analysis: The LAN common routines include support for initiating fork processes. There was a change in how this is done between V8.2 and the latest V8.2 LAN kit. To avoid the potential application start-up problems with fork processing in the LAN drivers, it is necessary to have the same version of all of the LAN common routines. The previous VMS82A_LAN-V0200 patch kit did not ship the SYS$LAN.EXE, SYS$LAN_FDDI.EXE and SYS$LAN_ATM.EXE SYS$LAN modules. This kit contains those images. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.1.5 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS82A_LAN ECO kits can be found in the following files: o VMS82A_LAN-V100.RELEASE_NOTES o VMS82A_LAN-V200.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 VMS82A_LAN - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS82A_LAN - /SELECT=[SYSUPD]release_note_name[/DESTINATION=destination_directory] The names of individual RELEASE_NOTES files in the kit can be found with: PRODUCT LIST {PCSI Installation Name} /SELECT = *.RELEASE_NOTES Page 4 7 FILES PATCHED OR REPLACED: o [SYSEXE]LANACP.EXE (new image) Image Identification Information image name: "LANACP" image file identification: "X-44A1" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:38.17 linker identification: "A11-50" Overall Image Checksum: 2390169902 o [SYSEXE]LANCP.EXE (new image) Image Identification Information image name: "LANCP" image file identification: "X-74A2" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:37.93 linker identification: "A11-50" Overall Image Checksum: 2428347797 o [SYS$LDR]SYS$EI1000.EXE (new image) Image Identification Information image name: "SYS$EI1000DRIVER" image file identification: "X-17" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:39.63 linker identification: "A11-50" Overall Image Checksum: 306657818 o [SYS$LDR]SYS$EIDRIVER.EXE (new image) Image Identification Information image name: "SYS$EIDRIVER" image file identification: "X-47" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:41.19 linker identification: "A11-50" Overall Image Checksum: 1527644168 o [SYS$LDR]SYS$EW1000A.EXE (new image) Image Identification Information image name: "SYS$EW1000A" image file identification: "X-60" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:38.93 linker identification: "A11-50" Overall Image Checksum: 3037108422 Page 5 o [SYS$LDR]SYS$EW5700.EXE (new image) Image Identification Information image name: "SYS$EW5700DRIVER" image file identification: "X-56" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:39.28 linker identification: "A11-50" Overall Image Checksum: 3326801702 o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image) Image Identification Information image name: "SYS$DE500BADRIVER" image file identification: "X-5" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:31.78 linker identification: "A11-50" Overall Image Checksum: 2989399552 o [SYS$LDR]SYS$LAN.EXE (new image) Image Identification Information image name: "SYS$LAN" image file identification: "X-5" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:20.08 linker identification: "A11-50" Overall Image Checksum: 1109429658 le;[SYS$LDR]SYS$LAN_ATM.EXE (new image) Image Identification Information image name: "SYS$_LAN_ATM" image file identification: "X-5" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:25.24 linker identification: "A11-50" Overall Image Checksum: 2864478991 o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) Image Identification Information image name: "SYS$LAN_CSMACD" image file identification: "X-5" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:22.49 linker identification: "A11-50" Overall Image Checksum: 1614294034 Page 6 o [SYS$LDR]SYS$LAN_FDDI.EXE (new image) Image Identification Information image name: "SYS$LAN_FDDI" image file identification: "X-5" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:26.75 linker identification: "A11-50" Overall Image Checksum: 3301676669 le;[SYS$LDR]SYS$LAN_TR.EXE (new image) Image Identification Information image name: "SYS$LAN_TR" image file identification: "X-5" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:28.11 linker identification: "A11-50" Overall Image Checksum: 2600744368 o [SYS$LDR]SYS$LLDRIVER.EXE (new image) Image Identification Information image name: "SYS$LLDRIVER" image file identification: "X-12" image file build identification: "XAJT-0070050010" link date/time: 6-DEC-2006 10:08:40.65 linker identification: "A11-50" Overall Image Checksum: 307430601 8 INSTALLATION INSTRUCTIONS 8.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. Page 7 o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 8.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS82A_LAN-V0300.ZIPEXE 8.3 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 VMS82A_LAN[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. 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.4 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 Page 8 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 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS82A_LAN-V0300 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS82A_LAN/PRODUCER=DEC/BASE=AXPVMS/VER=V3.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2007 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. Page 9 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.