======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_PCSI-V0300 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 Integrity servers V8.4 2.4 New functionality or new hardware support provided: Yes. 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_PCSI-V0200 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 VMS84I_PCSI-V0300 KIT 5.1 New functionality addressed in this kit 5.1.1 Introducing a new keyword in PCSI. 5.1.1.1 Problem Description: This release adds a new keyword "NO INSTALL" to be specified as an option in the FILE statement while creating the Product Description File. The inclusion of this keyword avoids performing INSTALL REPLACE of the image to which it is applied. This keyword is used only to take care of discrepancies caused by dependant images within the kit and is used only for those kits which require a mandatory reboot. If this keyword is not specified, the behavior defaults to performing an INSTALL REPLACE. Images Affected: - [SYSLIB]PCSI$SHR.EXE - [SYSEXE]PCSI$MAIN.EXE 5.1.1.2 Quix and PTR cases reporting this problem: 5.1.1.2.1 Quix Cases None 5.1.1.2.2 PTR(s) 75-120-1578 5.1.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.1.1.4 Work-arounds: None. Page 3 5.2 Problems addressed in this kit 5.2.1 Add error reporting in PRODUCT REGISTER VOLUME if the logical volume does not exist in product data base. 5.2.1.1 Problem Description: PRODUCT REGISTER VOLUME was not returning an error message if the logical volume specified in the command did not exist in the product database. After installation of this patch kit, the following error message will now be displayed: %PCSI-E-LNMNOTPDB, logical name not found in product database. Images Affected: - [SYSLIB]PCSI$SHR.EXE - [SYSEXE]PCSI$MAIN.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1000866955 5.2.1.2.2 PTR(s) 75-13-2311 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Itanium after V8.4 5.2.1.4 Work-arounds: None. 5.2.2 "PRODUCT EXTRACT FILE" command does not return error message if file does not exist in the PCSI kit. Page 4 5.2.2.1 Problem Description: "PRODUCT EXTRACT FILE" command does not give an appropriate error message while trying to extract a file which does not exist in the PCSI kit. For example, OVMS5>PROD EXTRACT FILE / SELECT=NOT_EXIST.TXT DCE/OPTIONS=NOVALIDATE The following product has been selected: HP I64VMS DCE V3.2 Layered Product Do you want to continue? [YES] Portion done: 0%...100% OVMS5>DIR NOT_EXIST.TXT %DIRECT-W-NOFILES, no files found This problem has been fixed. The above command now displays the following message: %PCSI-W-FILNOTFND, NOT_EXIST.TXT file is not found in the PCSI kit. Images Affected: - [SYSLIB]PCSI$SHR.EXE - [SYSEXE]PCSI$MAIN.EXE 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases None. 5.2.2.2.2 PTR(s) 75-13-2235 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Itanium after V8.4 Page 5 5.2.2.4 Work-arounds: None. 5.2.3 PRODUCT INSTALL command fails if the directory name contains a period(".") 5.2.3.1 Problem Description: On ODS-5 disks, if the directory name contains a period ("."), the PCSI PRODUCT INSTALL command fails with the following error message: "%PCSI-F-SYN, file specification syntax error" This problem is fixed. Images Affected: - [SYSLIB]PCSI$SHR.EXE - [SYSEXE]PCSI$MAIN.EXE 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases None. 5.2.3.2.2 PTR(s) 75-118-512 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Itanium after V8.4 5.2.3.4 Work-arounds: None. 5.2.4 Add message NODISKCONTISPACE. Page 6 5.2.4.1 Problem Description: Some kits need contiguous disk allocation space in order to be installed. If contiguous space is not available, then an RMS-F-FUL error was being displayed. Example : %PCSI-E-OPENOUT, error opening DISK$I6483VMS:[SYS0.SYSCOMMON.][SYSLIB]DECC$SHR.EXE_OLD; as output -RMS-F-FUL, device full (insufficient space for allocation). This kit will now generate a RMS-F-NODISKCONTISPACE error, which more truly represents the problem encountered during installation. Images Affected: - [SYSLIB]PCSI$SHR.EXE - [SYSEXE]PCSI$MAIN.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1000866735 5.2.4.2.2 PTR(s) None. 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Itanium after V8.4 5.2.4.4 Work-arounds: None. 5.2.5 "PRODUCT EXTRACT [PDF/FILE]" command fails On ODS-5 system. Page 7 5.2.5.1 Problem Description: During product installation, if the destination directory created on the system is in EXTENDED (lower + upper case) format, but the process parsing is set to traditional at the time of PDF file extraction, the extraction will fail. The PDF file extraction works successfully when the process parsing style is changed to EXTENDED. Images Affected: - [SYSLIB]PCSI$SHR.EXE - [SYSEXE]PCSI$MAIN.EXE 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases None. 5.2.5.2.2 PTR(s) 75-13-2119 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Itanium after V8.4 5.2.5.4 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_PCSI patch kits can be found in the following files: o VMS84I_PCSI-V0200.RELEASE_NOTES o VMS84I_PCSI-V0100.RELEASE_NOTES Before kit installation, these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS84I_PCSI /VERSION=V3.0 - [/file=destination_directory] Page 8 o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_PCSI /VERSION=V3.0 - /SELECT=release_note_name[/DESTINATION=destination_directory] The names of individual RELEASE_NOTES files in the kit can be found with: PRODUCT LIST VMS84I_PCSI /VERSION=V3.0 /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYSEXE]PCSI$MAIN.EXE (new image) Image Identification Information image name: "PCSI$MAIN" image file identification: "X34.1" image file build identification: "0100000004" link date/time: 8-AUG-2011 13:07:08.90 linker identification: "Linker I02-37" Overall Image Checksum: E9EB9310 o [SYSLIB]PCSI$SHR.EXE (new image) Image Identification Information image name: "PCSI$SHR" image file identification: "X34.1" image file build identification: "0100000004" link date/time: 8-AUG-2011 13:06:51.06 linker identification: "Linker I02-37" Overall Image Checksum: 8065A46C 8 INSTALLATION INSTRUCTIONS 8.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 9 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. 8.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS84I_PCSI-V0300.ZIPEXE 8.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 VMS84I_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 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.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: Page 10 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=HP/BASE=I64VMS/VER=V3.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_PCSI-V0300 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_PCSI/PRODUCER=HP/BASE=I64VMS/VER=V3.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2011 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. Page 11 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.