**************************** ECO SUMMARY INFORMATION **************************** Release Date: 9-JUL-2004 Kit Name: DEC-AXPVMS-VMS731_DCL-V0500--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 2816 blocks Installation Rating: INSTALL_3 Superseded Kits: VMS731_DCL-V0400 Mandatory Kit Dependencies: VMS731_SYS-V0600 VMS731_UPDATE-v0300 VMS731_PCSI-V0200 Optional Kit Dependencies: None VMS731_DCL-V0500.PCSI-DCX_AXPEXE Checksum: 1156510243 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS731_DCL-V0500 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 1 KIT NAME: VMS731_DCL-V0500 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 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_DCL-V0400 4 KIT DEPENDENCIES: Page 2 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-v0300 - VMS731_SYS-V0600 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]DCL.EXE (new image) Image Identification Information image name: "DCL" image file identification: "X-21A1" image file build identification: "XA2Q-0060030011" link date/time: 26-MAY-2004 09:58:28.94 linker identification: "A11-50" Overall Image Checksum: 2242214327 o [SYSLIB]IMGDMP.EXE (new image) Image Identification Information image name: "IMGDMP" image file identification: "X-20A2A3" image file build identification: "XA2Q-0060030004" link date/time: 19-MAY-2004 09:39:16.07 linker identification: "A11-50" Overall Image Checksum: 1590221594 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT" image file identification: "X-3" image file build identification: "XA2Q-0060030060" link date/time: 26-MAY-2004 09:58:28.09 linker identification: "A11-50" Overall Image Checksum: 623519834 Page 3 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT_MON" image file identification: "X-3" image file build identification: "XA2Q-0060030060" link date/time: 26-MAY-2004 09:58:33.08 linker identification: "A11-50" Overall Image Checksum: 1049448225 o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_DCL-V0500 KIT 6.1 New functionality addressed in this kit None 6.2 Problems addressed in this kit 6.2.1 Allow process dumps to be taken of processes installed with elevated privilege 6.2.1.1 Problem Description: This change allow process dumps to be taken of processes whose main image is installed with elevated privilege. This can only happen if the system manager has followed the steps outlined in the V7.3-1 System Manager's Manual, Volume 2, section 16.17.1. "Understanding Privileged Users and Access to Process Dumps". Images Affected: - [SYSEXE]DCL.EXE - [SYSLIB]IMGDMP.EXE - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB Page 4 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) 70.3.7872,CFS.106451 6.2.1.2.2 QAR(s) None. 6.2.1.3 Problem Analysis: Prior to V7.3, there was no safe way to take dumps of privileged images. The new process dump mechanism in V7.3 now makes this possible. 6.2.1.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.1.5 Work-arounds: None. 6.2.2 EXIT, CONTINUE and image rundown hang on ^Y interrupt 6.2.2.1 Problem Description: Interrupting an image linked with the /THREADS_ENABLE=(multi,upcalls) parameter with a control Y, and then issuing a command that causes image rundown or continued image execution, results in a hung process. The process can be unhung with a STOP/ID or a CTRL-Y STOP. SDA shows the initial kernel thread in HIB and other threads SUSPended. Images Affected: - [SYSEXE]DCL.EXE 6.2.2.2 CLDs, and QARs reporting this problem: Page 5 6.2.2.2.1 CLD(s) 70-3-8015 6.2.2.2.2 QAR(s) None. 6.2.2.3 Problem Analysis: Multithread in DCL$RUNDWN when running down an upcall enabled image was not enabled. 6.2.2.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.2.5 Work-arounds: None. 6.2.3 System may crash when deleting global sections. 6.2.3.1 Problem Description: If a system uses more global sections than specified by the system parameter GBLSECTIONS, then the system may crash when deleting global sections. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 6.2.3.2 CLDs, and QARs reporting this problem: Page 6 6.2.3.2.1 CLD(s) None. 6.2.3.2.2 QAR(s) None. 6.2.3.3 Problem Analysis: The sizing of an internal structure does not take into account that there could be more global sections than specified by the GBLSECTIONS system parameter. 6.2.3.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.3.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed in previously released VMS731_DCL kits can be found in the following files: o [SYSHLP]VMS731_DCL-V0400.RELEASE_NOTES o [SYSHLP]VMS731_DCL-V0300.RELEASE_NOTES o [SYSHLP]VMS731_DCL-V0200.RELEASE_NOTES o [SYSHLP]VMS731_DCL-V0100.RELEASE_NOTES 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_DCL-V0500.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 Page 7 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_DCL /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 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/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=V5.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS731_DCL-V0500 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS731_DCL/PRODUCER=DEC/BASE=AXPVMS- /VER=V5.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 8.4 Special Installation Instructions: The VMS731_DCL-V0500 ECO kit requires that the VMS731_SYS-V0600 kit be installed first. Installing the VMS731_DCL-V0500 ECO kit without the VMS731_SYS-V0600 kit would lead to crashes and system instability. Note that, if installed at the same time, a reboot is not required between the installation of the VMS731_SYS-V0600 and VMS731_DCL-V0500 kits. 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. Page 9 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.