ECO NUMBER: VMS72_PCSI-V0101 ----------- PRODUCT: OpenVMS VAX Operating System -------- UPDATED PRODUCT: OpenVMS VAX Operating System 7.2 ---------------- APPRX BLCK SIZE: 1824 ---------------- COVER LETTER 1 KIT NAME: DEC-VAXVMS-VMS72_PCSI-V0101--4.PCSI Note that this kit is a repackaging of the kit it supersedes and is functionally equivalent to it. 2 KITS SUPERSEDED BY THIS KIT: DEC-VAXVMS-VMS72_PCSI-V0100--4.PCSI 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) 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 should also be installed: None 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS VAX V7.2 4.2 Files patched or replaced: o [SYSEXE]PCSI$MAIN.EXE (new image) o [SYSLIB]PCSI$SHR.EXE (new image) o [SYSHLP]PRODUCT.HLP (update to HELPLIB.HLB) o [SYSUPD]PCSI.CLD (update to DCLTABLES.EXE) -- COVER LETTER -- Page 2 23 March 2001 5 PROBLEMS ADDRESSED IN VMS72_PCSI-V0101 KIT o When installing FORTRAN and FORRTL products, the system hangs if both products are selected for installation at the same time. Images Affected: - [SYSLIB]PCSI$SHR.EXE - [SYSEXE]PCSI$MAIN.EXE o If the following PCSI steps are taken: 1. Install a FULL type product kit 2. Patch the FULL product with a PATCH type kit(s) 3. Install a PARTIAL type software product on top of the FULL kit then, two versions of the same FULL product are created and patches are not transferred from the FULL product to the PARTIAL product. This would eventually lead to an un-repairable PCSI database corruption. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o The following duplicate error messages reported by the PCSI utility display during a product upgrade: %PCSI-E-INSVOLSPC, insufficient space on volume DISK$ALPCSI_SYS -PCSI-I-VOLSPC, 159261 required; 124344 available; -34917 net Terminating is strongly recommended. Do you want to terminate? [YES] no %PCSI-E-INSVOLSPC, insufficient space on volume DISK$ALPCSI_SYS -PCSI-I-VOLSPC, 159261 required; 124344 available; -34917 net Terminating is strongly recommended. Do you want to terminate? [YES] no Images Affected: - [SYSLIB]PCSI$SHR.EXE -- COVER LETTER -- Page 3 23 March 2001 o The reinstallation of a PARTIAL kit causes an ACCVIO. This occurs when certain data is passed from one instance of the PARTIAL product to another instance of the same product. After the transfer, pointers to the originating data structures are cleared. These pointers will be needed later. When the PARTIAL kits are different, re-installation of PARTIAL kit will not clear pointers. Images Affected: - [SYSLIB]PCSI$SHR.EXE o When re-installing a product that has a library module in its Product Description File (PDF), the PCSI utility terminates with an ACCVIO error. Images Affected: - [SYSLIB]PCSI$SHR.EXE - [SYSEXE]PCSI$MAIN.EXE o Changed the behavior of file conflict resolution between a file from the kit being installed and a file with the same name that has already been installed. Previously, when two files had the same generation number, the PCSI utility would retain the file already on the system disk. Now when there is a tie, the file from the kit being installed replaces the file previously installed. Images Affected: - [SYSLIB]PCSI$SHR.EXE - [SYSEXE]PCSI$MAIN.EXE o When a PRODUCT RECONFIGURE command is executed and the re-configured product has two or more patches applied to it, the PCSI utility incorrectly marks the patches as removed. This inconsistency can cause an ACCVIO on subsequent operations. Images Affected: - [SYSLIB]PCSI$SHR.EXE o When a FULL product kit replaces a file provided by another product, or a PATCH product kit replaces a file provided by its parent product or another patch, use of the IMAGE LIBRARY option of the FILE statement in the PDF (Product Description File) must be used consistently. For example, if one product -- COVER LETTER -- Page 4 23 March 2001 provides a file and places it in SYS$LIBRARY:IMAGELIB.OLB, but another product replaces the file but does not specify that it should also be placed in image library, then the installation will fail with a %PCSI-E-PARUDF error message. Images Affected: - [SYSLIB]PCSI$SHR.EXE o An attempt to upgrade a product and also apply a patch (or ECO) kit to it in the same PRODUCT INSTALL opertion may fail with the following error: %PCSI-E-FAILCONF, ... Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o Installation of two or more patch kits that provide the same file, and also update IMAGELIB.OLB with the file, may cause the PCSI product database to be inconsistent if the patch kits are installed out of order. Symptons include: o Output from a PRODUCT SHOW OBJECT /FULL command shows that all versions of the file are in conflict with one another (i.e., no file in the set has a status of "OK"). o Output from a PRODUCT SHOW OBJECT /FULL command shows that the owner of the file is one product and the owner of the module in IMAGELIB.OLB is another product (or patch). Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o When a number of patch kits are installed in a descending version sequence, and they contain files with IMAGE LIBRARY attribute set, a PRODUCT SHOW OBJECT command will display all the IMAGE LIBRARY files at conflict. This indicates incorrect entries to the PCSI database and may cause some problems. Images Affected: - [SYSLIB]PCSI$SHR.EXE -- COVER LETTER -- Page 5 23 March 2001 6 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. 7 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 VMS72_PCSI/SOURCE = [kit location] The kit location may be a tape drive, or a disk directory that contains the kit saveset. No reboot is necessary after successful installation of the kit. However, all processes will need to log out and then back in to use the new PRODUCT command qualifiers and keywords. Copyright 2001 Compaq Computer Corporation This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. 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 COMPAQ 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.