**************************** ECO SUMMARY INFORMATION **************************** Release Date: 8-MAR-2006 Kit Name: DEC-AXPVMS-VMS82A_PCSI-V0100--4.PCSI Kit Applies To: OpenVMS ALPHA V8.2 Approximate Kit Size: 3440 blocks Installation Rating: INSTALL_1 Reboot Required: No Superseded Kits: None Mandatory Kit Dependencies: None Optional Kit Dependencies: None VMS82A_PCSI-V0100.PCSI-DCX_AXPEXE Checksum: 3447146522 DEC-AXPVMS-VMS82A_PCSI-V0100--4.PCSI Checksum: 2299326121 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS82A_PCSI-V0100 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: No reboot is necessary after installation of this kit. 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: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - None 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None Page 2 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS82A_PCSI-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Unnecessary Warning Messages May Be Displayed On Installation 5.2.1.1 Problem Description: In the PDF of a product kit, use of both an IF () test for a product, and a SOFTWARE statement to establish a software reference to the product, may cause the PCSI utility to display an inappropriate %PCSI-W-SFTREF warning message. This occurs when the IF condition is satisfied. In cases where this problem arises, there are often multiple (or nested) IF or IF-ELSE tests present. The warning message is benign, but confusing and not necessary. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.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) 75-13-1360 5.2.1.3 Problem Analysis: The IF statement processing in the PCSI utility was resolving certain conditions after the configuration phase when they could have been resolved earlier. To correct the problem, the IF processing logic was modified to evaluate certain conditions as soon as possible to avoid executing code unconditionally when only the statements in the "true" or the "false" path of the IF condition should be executed. Page 3 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 5.2.1.5 Work-arounds: None. 5.2.2 Inconsistent Use Of ACLs Can Cause Product Database Corruption 5.2.2.1 Problem Description: If a full product kit supplies a directory or file with an access control list, and a patch kit for that product updates the object but does not specify an ACL, product database corruption can occur. Specifically, if a %PCSI-E-PARUDF error is returned when installing a patch and the user chooses to continue rather than terminate the operation, the database will likely be updated incorrectly. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) None. 5.2.2.2.2 QAR(s) 75-112-47 5.2.2.3 Problem Analysis: The PCSI utility has been modified to correctly record the owner of the ACL in the product database when the product and kits patch present inconsistent information. In some circumstances, the PCSI utility will be able to automatically repair a database with this type of error by inferring ACL ownership. Page 4 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 5.2.2.5 Work-arounds: None. 5.2.3 PRODUCT UNDO PATCH Does Not Restore ACL Information 5.2.3.1 Problem Description: When a patch is uninstalled, the access control list information associated with a directory or file is not restored. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) None. 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: The operation of PRODUCT INSTALL /SAVE_RECOVERY_DATA did not save ACL information in the recovery data when a patch kit was installed. This has been corrected. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 Page 5 5.2.3.5 Work-arounds: None. 5.2.4 PRODUCT UNDO PATCH May Fail Due To Logical Volume Name 5.2.4.1 Problem Description: Attempting to uninstall a patch will fail with a %PCSIUI-E-ERRREADRMF message (Error reading recovery data file) if the patch was installed to a non-system disk that was has an associated logical volume name that does not begin with "DISK$". Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) None. 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: Normally when a volume is mounted, the MOUNT command creates an associated logical volume name of the form DISK$. However, the user can specify any logical name when the third parameter is used as in: $ MOUNT /SYSTEM The PCSI utility incorrectly assumed that an associated logical volume name begins with the string "DISK$" and failed to find the destination device logical name in the recovery data set if it did not begin with this prefix. The PCSI utility has been corrected to remove this assumption. Page 6 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 5.2.4.5 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYSEXE]PCSI$MAIN.EXE (new image) Image Identification Information image name: "PCSI$MAIN" image file identification: "X26.1" image file build identification: "XAJT-0070050007" link date/time: 9-FEB-2006 09:50:25.95 linker identification: "A11-50" Overall Image Checksum: 3168333668 o [SYSLIB]PCSI$SHR.EXE (new image) Image Identification Information image name: "PCSI$SHR" image file identification: "X26.1" image file build identification: "XAJT-0070050007" link date/time: 9-FEB-2006 09:50:23.23 linker identification: "A11-50" Overall Image Checksum: 3884064458 o [SYSUPD]PCSI.CLD (new file) 7 INSTALLATION INSTRUCTIONS 7.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: Page 7 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. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 7.2 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 VMS82A_PCSI-V0100.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 7.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_PCSI[/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 Page 8 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. 7.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 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=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS82A_PCSI-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS82A_PCSI/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! Page 9 8 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.