ECO NUMBER: VMS722_PCSI-V0100 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 COVER LETTER 1 KIT NAME: VMS722_PCSI-V0100 2 KITS SUPERSEDED BY THIS KIT: None. 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: None. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-2 4.2 Files patched or replaced: o [SYSEXE]PCSI$MAIN.EXE (new image) o [SYSLIB]PCSI$SHR.EXE (new image) o [SYSLIB]DCLTABLES.TEMPLATE (new file) o [SYSUPD]PCSI.CLD (new file) o [SYSUPD]PRODUCT.HLP (new file) o [SYSUPD]PCSI$CREATE_ACCOUNT.COM (new file) o [SYSUPD]PCSI$EXTRACT_TLB.COM (new file) o [SYSUPD]PCSI$REGISTER_PRODUCT.COM (new file) -- COVER LETTER -- Page 2 26 June 2003 5 NEW FUNCTIONALITY INCLUDED IN THE VMS722_PCSI-V0100 KIT o This patch kit implements a new /RECOVERY_MODE qualifier. When installing a patch or full type kit in recovery mode, if the operation is terminated (either due to an error condition or by the user entering CTRL-C or CTRL-Y), any files that were added, modified, or deleted by the kit installation are restored to their state prior to the operation. The /RECOVERY_MODE qualifier enables recovery mode for the PRODUCT INSTALL and PRODUCT RECONFIGURE commands. The /RECOVERY_MODE qualifier allows you to recover from a failed installation of any type of kit. Once the operation completes, the recovery data is automatically deleted. *** Note *** All current OpenVMS operating system patch kits support this new /RECOVERY_MODE capability. However, operating system patch kits that are no longer current and/or some current layered product patch kits may not support /RECOVERY_MODE. If such a kit is installed using the /RECOVERY_MODE qualifier PCSI may not be able to correctly perform a recovery, leaving your system in an inconsistent state. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o This patch kit gives the user the capability to uninstall (UNDO) patch kits for which recovery data has been saved. This capability is supported by the following new commands: o PRODUCT INSTALL /SAVE_RECOVERY_DATA o PRODUCT UNDO PATCH o PRODUCT SHOW RECOVERY_DATA o PRODUCT DELETE RECOVERY_DATA There are several constraints to using this functionality that the user should be aware of: - A patch must be installed using the /SAVE_RECOVERY_DATA qualifier in order to create a recovery data set for use at the time the kit is uninstalled. Each PRODUCT INSTALL /SAVE_RECOVERY_DATA command creates a separate recovery data set that will contain information about one or more patches. -- COVER LETTER -- Page 3 26 June 2003 - Patches can only be uninstalled in the reverse order in which they were installed. You can "UNDO" the last patch installed, then the previous one, etc. - Once there is recovery data on the system, if a patch kit is installed without the /SAVE_RECOVERY_DATA qualifier, recovery data for all patch kits that had been installed using the /SAVE_RECOVERY_DATA qualifier will be lost. However, the user will be notified by any patch installation that will delete recovery data and will be given the opportunity to cancel the installation before any data is deleted. - Any installation of a non-patch kit, for example a layered product kit, will delete all recovery data sets that may have been created during previous patch installations. However, the user will be notified by any installation that will delete recovery data and will be given the opportunity to cancel the installation before any data is deleted. - The PRODUCT UNDO PATCH command is not related to the PRODUCT REMOVE command that is used to uninstall full products. - All current OpenVMS operating system patch kits support this new UNDO mode capability. However, operating system patch kits that are no longer current and/or some current layered product patch kits may not support UNDO mode. If such a kit is installed using the PRODUCT INSTALL /SAVE_RECOVERY_DATA command and then uninstalled using PRODUCT UNDO PATCH, your system may be left in an inconsistent state. Consult the on-line help text for more information about the patch removal capability. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o The PRODUCT SHOW OBJECT command has been enhanced to show the generation number associated with each file and module installed. A generation number is a attribute of certain objects that is used by the POLYCENTER Software Installation utility to resolve conflicts when two or more products provide the same file or library module. See the on-line help text for the PRODUCT SHOW OBJECT command to learn more about generation numbers. Images Affected: -- COVER LETTER -- Page 4 26 June 2003 - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o The /FULL qualifier has been added to the PRODUCT LIST command. This qualifier provides file size and other useful information about files in a product kit. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o The EXECUTE UPGRADE statement has been added to the product description language for creating product description files. This statement allows product kit developers to specify that a command procedure be executed only when the product is being upgraded. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o If a file or library module from a product kit being installed has the same generation number attribute as an object with the same name already installed by another product (or another patch for the same product), the file or module from the kit will be installed. Previously, the file or module already installed was retained. This change ensures that the re-installation of a full product or patch will cause objects from the kit to be re-copied to the system. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o The PRODUCT INSTALL command can operate on PCSI kits with a file type of .PCSI$COMPRESSED in a transparent manner. Compressed kits are encoded using a data compression technique that significantly reduces their file size. When a compressed kit is installed, records are decompressed (expanded) on-the-fly so no additional disk space is required to store a decompressed version of the kit. Full support for creating and manipulating compressed kits is expected to be available in the next release for OpenVMS Alpha. This remedial kit enables the use of compressed kits when they become available in the future. -- COVER LETTER -- Page 5 26 June 2003 Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 6 PROBLEMS ADDRESSED IN VMS722_PCSI-V0100 KIT o Fix problem with intra-product file and module conflict detection so that the correct object is provided when multiple patch kits for the same product are installed that provide the same object but have different generation numbers associated with them. This correction, for example, allows OpenVMS remedial kits to be installed in any order even through some may provide different versions of the same file or library module. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o When a patch kit uses an if-else construct to update either file A or file B, depending on the setting of a logical name that is tested in the patch kit's product description file, an ACCVIO can occur. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o The following commands do not correctly process files that are specified in a USES clause of an EXECUTE PRECONFIGURE statement in a kit's product description file: o PRODUCT PACKAGE /FORMAT=REFERENCE does not include such files o PRODUCT COPY /FORMAT=REFERENCE does not copy such files o PRODUCT LIST does not show such files as being packaged in the kit o PRODUCT EXTRACT FILE does not find such files In addition, the PRODUCT COPY and PRODUCT EXTRACT FILE commands may terminate with the following error message when processing -- COVER LETTER -- Page 6 26 June 2003 kits created with OpenVMS Alpha V7.1-2 or V7.2 that use the EXECUTE PRECONFIGURE statement in their product description file: %PCSI-E-READERR, error reading .PCSI-PCSI-E-INVDOCMTL, internal error - product document has invalid product material ordering %PCSI-E-OPFAILED, operation failed Terminating is strongly recommended. Do you want to terminate? [YES] All of these problems have been corrected. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o The IF () product description language statement does not process version selection criteria. The function returns a true value if any version of the specified product were installed. With this fix the IF () statement will process version selection criteria correctly. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o The EXECUTE POSTINSTALL statement in a product description file did not execute during a PRODUCT RECONFIGURE operation as documented. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o An attempt to remove a software product terminates with the following error message: %PCSI-E-NOSOFREF, Software Reference data is not available %PCSI-E-S_OPFAIL, operation failed %PCSI-E-ABOARD, operation terminated due to an unrecoverable error condition This error can occur when a software product is removed that has an optional reference to another product, but that option was not selected when the product was installed. -- COVER LETTER -- Page 7 26 June 2003 Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o Several obscure problems related to partial product kits have been resolved. In general, these problems were related to operations performed after a partial kit had been successfully installed. These problems included failures in: 1. Installing a full product kit with a lower version than that of a partial kit for the same product 2. Downgrading a platform product that included a partial kit. This also fixes a product database corruption problem. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o Use of the PDL statement EXECUTE START...STOP INTERACTIVE in a patch kit causes the installation of the patch kit to fail with an $SS_NOLOGNAM error. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o In a product description language file for a patch kit, FILE statements enclosed in a REMOVE group nested in an IF-ELSE group do not always remove the specified files. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o When a product is installed with an option selected and then subsequently reinstalled with the option deselected, the files for that option are not removed. Images Affected: -- COVER LETTER -- Page 8 26 June 2003 - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o A product that has a software reference to another product can not be installed if that other product does not allow an upgrade to itself. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o At installation, when the SOURCE option on a FILE statement in a PDF refers to a file that is not a .EXE file, the build ident field of an Alpha image is not updated with an encoded generation number. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o PCSI allows the user to continue the installation of a patch kit when the wrong version of the product to which the patch applies is installed. This fix prevents the installation of the patch. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o Provide better explanations to the user when the /DESTINATION qualifier of the PRODUCT INSTALL command is purposely ignored. This occurs when the same version of a product is re-installed or a patch is applied to an installed product. In these cases the destination cannot be changed. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o Installation of a patch kit that contains a PDL SOFTWARE statement that refers to another patch kit fails with an ACCVIO. This fix enforces a restriction against such -- COVER LETTER -- Page 9 26 June 2003 statements. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o The PRODUCT PACKAGE operation does not abort when a file specified in the USES option of an EXECUTE statement is not found. With this fix the PACKAGE operation will abort. All missing files will be identified before the operation terminates. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o On reinstallation of a product, verify that the kit provides the same objects as were originally provided when the product was first installed. During the kit development process, product developers may add or delete objects from their kit but fail to change the version of the kit. This can result in unintended behavior when installing the new kit and in certain cases may lead to product database corruption. This happens because reinstallation of the same version of a product is assumed to be a replacement operation and certain optimizations are utilized in the processing of the kit. With this change, the POLYCENTER Software Installation utility compares the list of objects previously installed with the objects listed in the new kit to verify that there is a one-to-one correspondence. If not, the developer is notified of the discrepancy. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o In the following scenario, product database corruption will occur. The corruption is caused by improper processing of a DIRECTORY statement in the product description file: 1. A full product is installed that explicitly creates directories [A] and [A.B.C] 2. A patch kit is then installed that explicitly creates directory [A.B] -- COVER LETTER -- Page 10 26 June 2003 3. The full product is upgraded Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o Under certain conditions, the PRODUCT command aborts on deallocation of virtual memory. This is most likely to occur when the destination device for an installation contains many access control lists. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o If during the execution of a PRODUCT INSTALL command, an attempt to spawn a subprocess fails or an attempt to create a detached subprocess fails, the primary error message is not reported - just a generic PCSI abort message is displayed. With this change, the primary error message is now reported. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o Fix Various problems related to PRODUCT EXTRACT RELEASE_NOTES: o Preserve the file name of a release notes file on extraction instead of giving it the name of DEFAULT.PCSI$RELEASE_NOTES. o If there is more than one release notes file in a product kit, because they may be in different formats such as .TXT, .HTML, and PS, extract them as separate files instead of concatenating them. o Support sequential files in VFC format as release notes. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE -- COVER LETTER -- Page 11 26 June 2003 o Many informational, warning, and error messages have been added or revised. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o An ACCVIO occurs when multiple patch kits are installed and two or more of these kits provide the same file with the same generation number. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 7 KIT INSTALLATION RATING: The following kit 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) INSTALLATION RATING: INSTALL_1 : To be installed by all customers. 8 INSTALLATION INSTRUCTIONS: 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 VMS722_PCSI /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt No reboot is necessary after successful installation of the kit. However, users will need to log out and log back in in order to use the new PCSI features. -- COVER LETTER -- Page 12 26 June 2003 8.1 Special Installation Instructions: 8.1.1 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 definitions and commands: - $ DEFINE/SYS NO_ASK$BACKUP TRUE - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=1.0 - De-assign the logicals assigned For example, a sample command file to install the VMS722_PCSI-V0100 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $! $ PROD INSTALL VMS722_PCSI/PROD=DEC/BASE=AXPVMS/VER=1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit © Copyright [2003] 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 -- COVER LETTER -- Page 13 26 June 2003 EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP OR ANY OF ITS SUBSIDIARIES 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.