**************************** ECO SUMMARY INFORMATION **************************** Release Date: 11-OCT-2006 Kit Name: DEC-AXPVMS-VMS83A_ADDENDUM-V0200--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V8.3 Approximate Kit Size: 8024 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VMS83A_ADDENDUM-V0100 Mandatory Kit Dependencies: None or later Optional Kit Dependencies: None Checksums: VMS83A_ADDENDUM-V0200.ZIPEXE Checksum: 1381144010 DEC-AXPVMS-VMS83A_ADDENDUM-V0200--4.PCSI$COMPRESSED Checksum: 4067467691 VMS83A_ADDENDUM-V0200.ZIPEXE MD5 Checksum: 4059BAA70A1DACED031A8BB90A602A6A DEC-AXPVMS-VMS83A_ADDENDUM-V0200--4.PCSI$COMPRESSED MD5 Checksum: 45C69ECF7E663DF6E6EA3ADFF0288B59 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS83A_ADDENDUM-V0200 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.3 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS83A_ADDENDUM-V0100 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - None 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 VMS83A_ADDENDUM-V0200 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 System Crash When Dismounting Tape or Disk 5.2.1.1 Problem Description: After installation of the VMS83A_ADDENDUM-V0100 patch kit, the system could crash when a tape or when a disk in mount verification was dismounted. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.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: In routine IOC$DISMOUNT, the fork lock of the relevant UCB is acquired and released several times. R0 was not preserved across the macro invocation. 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_ADDENDUM ECO kits can be found in the following files: o VMS82A_ADDENDUM-V100.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_SYS/VERSION= - /DESTINATION= destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS82A_ADDENDUM/VERSION= V2.0 - /SELECT=[SYSUPD]release_note_name/DESTINATION=destination_directory 7 FILES PATCHED OR REPLACED: o [SYSEXE]AUDIT_SERVER.EXE (new image) Image Identification Information image name: "AUDIT_SERVER" image file identification: "X-12" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:49:40.79 linker identification: "A13-03" Overall Image Checksum: 3194053560 Page 4 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information image name: "IO_ROUTINES" image file identification: "X-5" image file build identification: "XBCA-0080070003" link date/time: 11-SEP-2006 14:59:29.20 linker identification: "A13-03" Overall Image Checksum: 2222556394 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information image name: "IO_ROUTINES_MON" image file identification: "X-5" image file build identification: "XBCA-0080070003" link date/time: 11-SEP-2006 14:59:31.30 linker identification: "A13-03" Overall Image Checksum: 2698973810 o [SYSLIB]LIBRTL.EXE (new image) Image Identification Information image name: "LIBRTL" image file identification: "X01-001" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:47:41.59 linker identification: "A13-03" Overall Image Checksum: 1514753709 o [SYSEXE]MONITOR.EXE (new image) Image Identification Information image name: "MONITOR" image file identification: "X-26" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:49:57.62 linker identification: "A13-03" Overall Image Checksum: 3914726037 o [SYSLIB]SECURESHRP.EXE (new image) Image Identification Information image name: "SECURESHRP" image file identification: "X-8" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:47:50.15 linker identification: "A13-03" Overall Image Checksum: 3299818619 Page 5 o [SYSLIB]SPISHR.EXE (new image) Image Identification Information image name: "SPISHR" image file identification: "ALPHA XBCA-N2O" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:49:49.78 linker identification: "A13-03" Overall Image Checksum: 3881418943 o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information image name: "SYS$CLUSTER" image file identification: "X-5" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:50:00.32 linker identification: "A13-03" Overall Image Checksum: 4197445520 o [SYS$LDR]SYS$CLUSTER_MON.EXE (new image) Image Identification Information image name: "SYS$CLUSTER_MON" image file identification: "X-5" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:50:02.12 linker identification: "A13-03" Overall Image Checksum: 3665832722 o [SYS$LDR]SYS$PEDRIVER.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER" image file identification: "X-4" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:49:54.68 linker identification: "A13-03" Overall Image Checksum: 2641392456 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information image name: "SYS$VM" image file identification: "X-5" image file build identification: "XBCA-0080070003" link date/time: 11-SEP-2006 14:59:30.87 linker identification: "A13-03" Overall Image Checksum: 4233182520 Page 6 o [SYSLIB]TRACE.EXE (new image) Image Identification Information image name: "TRACE" image file identification: "V8.3-002" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:48:41.56 linker identification: "A13-03" Overall Image Checksum: 612648440 o [SYSLIB]VMS$VMS_ACMESHR.EXE (new image) Image Identification Information image name: "VMS$VMS_ACMESHR" image file identification: "01" image file build identification: "0080070000" link date/time: 7-AUG-2006 17:50:00.81 linker identification: "A13-03" Overall Image Checksum: 2235862529 o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYSLIB]LIBRTL.STB (new file) o [SYS$LDR]SYS$CLUSTER.STB (new file) o [SYS$LDR]SYS$CLUSTER_MON.STB (new file) o [SYS$LDR]SYS$PEDRIVER.STB (new file) o [SYS$LDR]SYS$VM.STB (new file) 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. Page 7 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. 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, run the file with the following command: $ RUN VMS83A_ADDENDUM-V0200.ZIPEXE This patch kit was created using Secure Delivery and will expand into two files: 1. DEC-AXPVMS-VMS83A_ADDENDUM-V0200--4.PCSI$COMPRESSED 2. DEC-AXPVMS-VMS83A_ADDENDUM-V0200--4.PCSI$COMPRESSED_ESW The first file is the digitally signed installable kit. The second file is the kit manifest or digital signature file. Both files must be in the same directory at installation time. OpenVMS Secure Delivery automatically ensures that software installed on OpenVMS was not tampered with prior to installation. At installation time, PCSI will check for the existence of a manifest for any kits that are being installed. If no manifest is found, PCSI will issue a warning and ask if you want to proceed. If a manifest is found but does not match the kit, the installation will be aborted. The PCSI database will contain an indication as to whether a kit used Secure Delivery on installation. For additional information on Secure Delivery and PCSI, refer to sections "5.2 CDSA for OpenVMS and Secure Delivery" and "3.10.4 Support for Secure Delivery of Product Kits" in the "HP OpenVMS Version 8.3 New Features and Documentation Overview" manual. 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 VMS83A_ADDENDUM[/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. Page 8 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 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=V2.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS83A_ADDENDUM-V0200 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS83A_ADDENDUM/PRODUCER=DEC/BASE=AXPVMS/VER=V2.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! Page 9 $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2006 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.