**************************** ECO SUMMARY INFORMATION **************************** Release Date: 1-APR-2004 Kit Name: DEC-AXPVMS-VMS73_PCSI-V0200--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3 Approximate Kit Size: 4640 blocks Installation Rating: INSTALL_1 Superseded Kits: VMS73_PCSI-V0100 Mandatory Kit Dependencies: None Optional Kit Dependencies: None VMS73_PCSI-V0200.PCSI-DCX_AXPEXE Checksum: 3710852473 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS73_PCSI-V0200 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 1 KIT NAME: VMS73_PCSI-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: No reboot is necessary after installation of this kit. See the section Special Installation Instructions for more information. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.3 2.4 New functionality or new hardware support provided: Yes. 3 KITS SUPERSEDED BY THIS KIT: - VMS73_PCSI-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 FILES PATCHED OR REPLACED: o [SYSEXE]PCSI$MAIN.EXE (new image) Image Identification Information image name: "PCSI$MAIN" image file identification: "X23.1" image file build identification: "X9UH-0060010027" link date/time: 26-JAN-2004 09:47:43.26 linker identification: "A11-50" Overall Image Checksum: 1410199628 o [SYSLIB]PCSI$SHR.EXE (new image) Image Identification Information image name: "PCSI$SHR" image file identification: "X23.1" image file build identification: "X9UH-0060010027" link date/time: 26-JAN-2004 09:47:38.23 linker identification: "A11-50" Overall Image Checksum: 827004523 o [SYSLIB]DCLTABLES.TEMPLATE (new file) o [SYSUPD]PCSI$CREATE_ACCOUNT.COM o [SYSUPD]PCSI$EXTRACT_TLB.COM (new file) o [SYSUPD]PCSI$REGISTER_PRODUCT.COM (new file) o [SYSUPD]PCSI.CLD (new file) o [SYSUPD]PRODUCT.HLP (new file) 6 NEW FUNCTIONALITY INTRODUCED IN THE VMS73_PCSI-V0200 KIT Page 3 6.1 New /OPTIONS=[NO]CONFIRM qualifier for most PRODUCT commands 6.1.1 Functionality Description: This patch kit implements a new /OPTIONS=[NO]CONFIRM qualifier for most PRODUCT commands. For commands such as $ PRODUCT INSTALL /OPTIONS=NOCONFIRM $ PRODUCT DELETE RECOVERY_DATA /OPTIONS=NOCONFIRM NOCONFIRM suppresses the confirmation dialog to verify the user's product or recovery data set selection before proceeding with the operation. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 6.2 /OPTIONS=SHOW_DISK_USAGE qualifier added to PRODUCT INSTALL, RECONFIGURE, and REMOVE commands. 6.2.1 Functionality Description: The /OPTIONS=SHOW_DISK_USAGE qualifier has been added to the PRODUCT INSTALL, RECONFIGURE, and REMOVE commands. Its function is to display estimated disk space usage. Previously, the only way to get this information was to use the /LOG qualifier. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 6.3 Implement Ctrl/Y and Ctrl/C handling for the PRODUCT UNDO PATCH command. 6.3.1 Functionality Description: This kit implements Ctrl/Y and Ctrl/C handling for the PRODUCT UNDO PATCH command. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE Page 4 7 NEW FUNCTIONALITY INCLUDED IN THE VMS73_PCSI-V0100 KIT 7.1 Perform installation and reconfiguration operations in recovery mode. 7.1.1 Functionality Description: 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 7.2 Uninstallation of Patch kits 7.2.1 Functionality Description: 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: Page 5 - 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. - 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 Page 6 7.3 PRODUCT SHOW OBJECT command enhanced to show the generation number The PRODUCT SHOW OBJECT command has been enhanced to show the generation number associated with each file and module installed. A generation number is an 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: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 7.4 Implementation of the /FULL qualifier of the PRODUCT LIST command. 7.4.1 Problem Description: 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 7.5 Implementation of the EXECUTE UPGRADE statement 7.5.1 Problem Description: 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 Page 7 7.6 Improved handling of files with the same generation number. 7.6.1 Problem Description: 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 7.7 Enable the use of compressed kit 7.7.1 Functionality Description: 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. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8 PROBLEMS ADDRESSED IN THIS KIT 8.1 New problems addressed in the VMS73_PCSI-V0200 kit Page 8 8.1.1 PRODUCT INSTALL operation terminates with ACCVIO 8.1.1.1 Problem Description: A PRODUCT INSTALL operation may terminate with an ACCVIO. The traceback indicates that the problem occurs while processing the 'spiu_trim_idle_products' routine. In addition, the PRODUCT INSTALL command will verify that the FID of the SYS$SPECIFIC:[000000]SYSCOMMON.DIR file and the FID of the SYS$SYSDEVICE:[000000]VMS$COMMON.DIR are identical. If they are not the same, the product installation will not proceed and the user will be alerted to the potential problem. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.1.1.2 CLDs, and QARs reporting this problem: 8.1.1.3 CLD(s) 70-3-7182 8.1.1.4 QAR(s) None. 8.1.1.5 Problem Analysis: See Problem Description 8.1.1.6 Work-arounds: None. 8.1.2 PRODUCT UNDO PATCH command may fail with %PCSI-E-RMCHKERR error 8.1.2.1 Problem Description: The PRODUCT UNDO PATCH command may fail with a %PCSI-E-RMCHKERR Images Affected: Page 9 - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.1.2.2 CLDs, and QARs reporting this problem: 8.1.2.3 CLD(s) 70-3-7310 8.1.2.4 QAR(s) None. 8.1.2.5 Problem Analysis: When two patch kits are concurrently installed using the /SAVE_RECOVERY_DATA qualifier and both patches update the same file, the PRODUCT UNDO PATCH command for either kit may fail with a %PCSI-E-RMCHKERR error. 8.1.2.6 Work-arounds: None. 8.1.3 PRODUCT LIST display improperly identified compressed kits as sequential kits. 8.1.3.1 Problem Description: The PRODUCT LIST display improperly identified compressed kits as sequential kits. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.1.3.2 CLDs, and QARs reporting this problem: Page 10 8.1.3.3 CLD(s) None. 8.1.3.4 QAR(s) None. 8.1.3.5 Problem Analysis: See Problem Description 8.1.3.6 Work-arounds: None. 8.1.4 Minor enhancements to PRODUCT UNDO PATCH and PRODUCT DELETE REOVERY_DATA commands 8.1.4.1 Problem Description: Minor enhancements and corrections were made to the display and interactive dialog of the PRODUCT UNDO PATCH and PRODUCT DELETE REOVERY_DATA commands. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.1.4.2 CLDs, and QARs reporting this problem: 8.1.4.3 CLD(s) None. 8.1.4.4 QAR(s) None. 8.1.4.5 Problem Analysis: See Problem Description Page 11 8.1.4.6 Work-arounds: None. 8.1.5 Installation or upgrade of a product may fail with %PCSI-F-BADBLOADR error 8.1.5.1 Problem Description: Installation or upgrade of a product (such as the upgrade of the VMS operating system) may fail with a %PCSI-F-BADBLOADR error. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.1.5.2 CLDs, and QARs reporting this problem: 8.1.5.3 CLD(s) 70-3-7331,70-3-7339 8.1.5.4 QAR(s) None. 8.1.5.5 Problem Analysis: this problem occurs when SYS$COMMON:[SYSLIB]DCLTABLES.EXE has an access control list associated with it. 8.1.5.6 Work-arounds: None. 8.1.6 Recovery may not be complete if installation fails 8.1.6.1 Problem Description: When using the PRODUCT INSTALL command with the /RECOVERY_MODE qualifier, if the installation fails (or is terminated with Ctrl/C or Ctrl/Y), recovery may not be complete if: o the product is installed to a non-system device, or Page 12 o the product or patch provides files in the system specific root (SYS$SPECIFIC). This problem may also cause the PRODUCT UNDO PATCH command to fail for patches that provide files in the system specific root. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.1.6.2 CLDs, and QARs reporting this problem: 8.1.6.3 CLD(s) None. 8.1.6.4 QAR(s) None. 8.1.6.5 Problem Analysis: See Problem Description 8.1.6.6 Work-arounds: None. 8.1.7 Upgrade of OpenVMS V7.3-2 from V7.3-1 fails if DCE_030_SSRT3608-0100 kit is installed at the time of the upgrade 8.1.7.1 Problem Description: The upgrade of OpenVMS V7.3-2 from V7.3-1 will fail if the remedial kit DCE_030_SSRT3608-0100 is installed at the time of the upgrade. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE Page 13 8.1.7.2 CLDs, and QARs reporting this problem: 8.1.7.3 CLD(s) 70-3-7664,70-3-7706 8.1.7.4 QAR(s) None. 8.1.7.5 Problem Analysis: The error condition reported implies that the wrong version of the KERBEROS product is installed which prevents a newer version of KERBEROS from being installed as part of the OpenVMS upgrade. The real problem, however, is a logic error in the PCSI utility triggered by a very specific set of conditions that are present in this upgrade scenario. 8.1.7.6 Work-arounds: None. 8.2 Problems addressed in the VMS73_PCSI-V0100 kit 8.2.1 "Software Reference data is not available" error message 8.2.1.1 Problem Description: 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-ABORT, 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. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE Page 14 8.2.1.2 CLDs, and QARs reporting this problem: 8.2.1.3 CLD(s) None. 8.2.1.4 QAR(s) 75-45-1560,75-66-636 8.2.1.5 Problem Analysis: See Problem Description 8.2.1.6 Work-arounds: None. 8.2.2 $SS_NOLOGNAM error on patch kit installation 8.2.2.1 Problem Description: 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 8.2.2.2 CLDs, and QARs reporting this problem: 8.2.2.3 CLD(s) None. 8.2.2.4 QAR(s) 75-66-139 8.2.2.5 Problem Analysis: See Problem Description Page 15 8.2.2.6 Work-arounds: None. 8.2.3 FILE statements enclosed in a REMOVE group do not always remove the specified files. 8.2.3.1 Problem Description: 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 8.2.3.2 CLDs, and QARs reporting this problem: 8.2.3.3 CLD(s) None. 8.2.3.4 QAR(s) 75-66-1066 8.2.3.5 Problem Analysis: See Problem Description 8.2.3.6 Work-arounds: None. 8.2.4 Files related to a particular product option are not removed 8.2.4.1 Problem Description: 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: Page 16 - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.2.4.2 CLDs, and QARs reporting this problem: 8.2.4.3 CLD(s) None. 8.2.4.4 QAR(s) None. 8.2.4.5 Problem Analysis: See Problem Description 8.2.4.6 Work-arounds: None. 8.2.5 Cannot install a product that has a software reference to another product 8.2.5.1 Problem Description: 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 8.2.5.2 CLDs, and QARs reporting this problem: 8.2.5.3 CLD(s) None. Page 17 8.2.5.4 QAR(s) 75-66-1207 8.2.5.5 Problem Analysis: See Problem Description 8.2.5.6 Work-arounds: None. 8.2.6 Build ident field not updated with an encoded generation number 8.2.6.1 Problem Description: 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 8.2.6.2 CLDs, and QARs reporting this problem: 8.2.6.3 CLD(s) None. 8.2.6.4 QAR(s) 75-66-414 8.2.6.5 Problem Analysis: See Problem Description 8.2.6.6 Work-arounds: None. Page 18 8.2.7 User can continue patch installation when wrong version of the product is installed. 8.2.7.1 Problem Description: 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 installation of the patch. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.2.7.2 CLDs, and QARs reporting this problem: 8.2.7.3 CLD(s) None. 8.2.7.4 QAR(s) 75-45-385,75-45-2554 8.2.7.5 Problem Analysis: See Problem Description 8.2.7.6 Work-arounds: None. 8.2.8 Provide better explanations when /DESTINATION qualifier is ignored. 8.2.8.1 Problem Description: 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 Page 19 - [SYSLIB]PCSI$SHR.EXE 8.2.8.2 CLDs, and QARs reporting this problem: 8.2.8.3 CLD(s) None. 8.2.8.4 QAR(s) 75-66-854 8.2.8.5 Problem Analysis: See Problem Description 8.2.8.6 Work-arounds: None. 8.2.9 Illegal PDL SOFTWARE statements that refer to another patch kit are not caught. 8.2.9.1 Problem Description: 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 statements. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.2.9.2 CLDs, and QARs reporting this problem: 8.2.9.3 CLD(s) None. Page 20 8.2.9.4 QAR(s) 75-45-321 8.2.9.5 Problem Analysis: See Problem Description 8.2.9.6 Work-arounds: None. 8.2.10 PRODUCT PACKAGE operation does not fail when USES option files are missing 8.2.10.1 Problem Description: 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. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.2.10.2 CLDs, and QARs reporting this problem: 8.2.10.3 CLD(s) None. 8.2.10.4 QAR(s) 75-45-873 8.2.10.5 Problem Analysis: See Problem Description 8.2.10.6 Work-arounds: None. Page 21 8.2.11 On reinstallation verify that the kit provides the same objects as were originally provided. 8.2.11.1 Problem Description: 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 8.2.11.2 CLDs, and QARs reporting this problem: 8.2.11.3 CLD(s) None. 8.2.11.4 QAR(s) 75-66-1065 8.2.11.5 Problem Analysis: See Problem Description 8.2.11.6 Work-arounds: None. Page 22 8.2.12 Partial product kit problems corrected 8.2.12.1 Problem Description: 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 8.2.12.2 CLDs, and QARs reporting this problem: 8.2.12.3 CLD(s) None. 8.2.12.4 QAR(s) 75-52-77,75-52-81,75-66-181 8.2.12.5 Problem Analysis: See Problem Description 8.2.12.6 Work-arounds: None. 8.2.13 PCSI database corruption Page 23 8.2.13.1 Problem Description: 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] 3. The full product is upgraded Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.2.13.2 CLDs, and QARs reporting this problem: 8.2.13.3 CLD(s) 70-3-6199 8.2.13.4 QAR(s) None. 8.2.13.5 Problem Analysis: See Problem Description 8.2.13.6 Work-arounds: None. 8.2.14 PRODUCT command aborts on deallocation of virtual memory Page 24 8.2.14.1 Problem Description: 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 8.2.14.2 CLDs, and QARs reporting this problem: 8.2.14.3 CLD(s) 70-3-6682 8.2.14.4 QAR(s) None. 8.2.14.5 Problem Analysis: See Problem Description 8.2.14.6 Work-arounds: None. 8.2.15 Insufficient error message when spawn of a subprocess fails 8.2.15.1 Problem Description: 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 reported. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE Page 25 8.2.15.2 CLDs, and QARs reporting this problem: 8.2.15.3 CLD(s) 70-3-3047 8.2.15.4 QAR(s) None. 8.2.15.5 Problem Analysis: See Problem Description 8.2.15.6 Work-arounds: None. 8.2.16 Various problems related to PRODUCT EXTRACT RELEASE_NOTES 8.2.16.1 Problem Description: 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 Page 26 8.2.16.2 CLDs, and QARs reporting this problem: 8.2.16.3 CLD(s) None. 8.2.16.4 QAR(s) 75-66-146,75-83-171 8.2.16.5 Problem Analysis: See Problem Description 8.2.16.6 Work-arounds: None. 8.2.17 Many informational, warning, and error messages have been added or revised. 8.2.17.1 Problem Description: Many informational, warning, and error messages have been added or revised. Images Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE 8.2.17.2 CLDs, and QARs reporting this problem: 8.2.17.3 CLD(s) None. 8.2.17.4 QAR(s) None. 8.2.17.5 Problem Analysis: See problem Description Page 27 8.2.17.6 Work-arounds: None. 8.2.18 ACCVIO when multiple patch kits being installed provide same file with the same generation number. 8.2.18.1 Problem Description: An ACCVIO occurs when multiple patch kits are being 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 8.2.18.2 CLDs, and QARs reporting this problem: 8.2.18.3 CLD(s) None. 8.2.18.4 QAR(s) None. 8.2.18.5 Problem Analysis: See Problem Desription 8.2.18.6 Work-arounds: None. 9 INSTALLATION INSTRUCTIONS: 9.1 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 VMS73_PCSI /SAVE_RECOVERY_DATA- [/SOURCE=location of Kit] The /SAVE_RECOVERY_DATA qualifier is optional but highly Page 28 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. 9.2 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/SYS ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PRODUCER=DEC/BASE=AXPVMS/VER=V2.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS73_PCSI kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS ARCHIVE_OLD NO $! $ PRODUCT INSTALL VMS73_PCSI /PRODUCER=DEC/BASE=AXPVMS/VER=V2.0- /SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS ARCHIVE_OLD $! Page 29 $ exit 9.3 Special Installation Instructions: No reboot is necessary after installation of this kit. However, after installation of the kit users will need to take one of the following steps to ensure that the new PCSI files are used: o Execute the command SET COMMAND SYS$UPDATE:PCSI.CLD o Log out and log back in. 10 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. 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 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.