======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_UPDATE-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: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. 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: 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 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 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS84I_UPDATE-V0100 KIT 5.1 New functionality addressed in this kit 5.1.1 VMSINSTAL Support for Kits Signed Using HP Code Signing Service VMSINSTAL has been enhanced to verify the software kits that are shipped as savesets and signed by HP Code Signing Service (HPCSS). While installing the software kits that are not signed by HPCSS, VMSINSTAL displays the following informational message and prompt: %VMSINSTAL-I-VALSIGN, Performing product kit validation of signed kits... %VMSINSTAL-I-NOVALDONE, Product is not signed by HP Do you want to install this product [NO]? If you answer YES, the installation continues. If you answer NO, it aborts. Note that this feature is supported on the OpenVMS Version 8.4 release kit. For more information, see Section 2.2 in the HP OpenVMS Version 8.4 New Features and Documentation Overview. The kit validation status is updated in VMSINSTAL.HISTORY file with 'U' when validation fails or is not validated. NOTE: - If you enter Ctrl+Z, kit installation proceeds. This is a known issue. - Currently there is no option to override the above prompt during installation. Page 3 5.2 Problems addressed in this kit 5.2.1 CLUSTER_CONFIG[_LAN] Deletes SYS0 Root 5.2.1.1 Problem Description: In a specific scenario, during the execution of CLUSTER_CONFIG[_LAN] for cluster configurations, pressing Ctrl+Y results in the deletion of SYS0 root and the system becomes unusable. This happens due to improper handling of exit handlers. This problem has been fixed by setting proper exit handlers. Images Affected: - [SYSMGR]CLUSTER_CONFIG.COM - [SYSMGR]CLUSTER_CONFIG_LAN.COM 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases None. 5.2.1.2.2 PTR(s) 75-120-1243 5.2.1.3 Work-arounds: None. 5.2.2 I64VMS$PCSI_INSTALL_MIN.COM Fails With an Error Message 5.2.2.1 Problem Description: When executing the I64VMS$PCSI_INSTALL_MIN.COM command procedure to build a minimal PCSI-Bootable system, it fails with the following error message: %SYSTEM-W-NOSUCHDEV, no such device available \VMI$ROOT\ %SYSTEM-W-NOSUCHDEV, no such device available This problem has been fixed. Images Affected: Page 4 - [SYSEXE]I64VMS$PCSI_INSTALL_MIN.COM 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-120-1260 5.2.2.3 Work-arounds: None. 5.2.3 Alignment Faults in RMS When BACKUP is Running 5.2.3.1 Problem Description: On OpenVMS Version 8.4, when backup is running, a large number of alignment faults occur in RMS. The alignment faults were reported at offset RMS+180A1. This problem has been fixed. Images Affected: - [SYS$LDR]RMS.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-123-127 5.2.3.3 Work-arounds: None. Page 5 5.2.4 Non-paged Pool Corruption Results in System Crash 5.2.4.1 Problem Description: Under certain conditions, system crashes due to non-paged pool corruption. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases None. 5.2.4.2.2 PTR(s) 75-120-1252, 75-120-1253 5.2.4.3 Work-arounds: None. 5.2.5 Byte-ranging Locking Feature in C RTL fcntl() API Fails With EACCES 5.2.5.1 Problem Description: C RTL fcntl() API, when invoked to perform byte-range locking fails with EACCES error, even if there is no lock currently held on the associated file. fcntl() API uses the fields of the FileID of a file to identify the byte-range locks currently held on that file. In some cases, the fields of the FileID interpreted by C RTL is wrong and may result in a failure with EACCES error. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE - [SYSLIB]DECC$SHRP.EXE Page 6 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-120-1302 5.2.5.3 Work-arounds: None. 5.2.6 Semaphore-Permission or Privileges Issues When Called From a Process That has Minimum Privileges (NETBMX,TMPMBX) 5.2.6.1 Problem Description: Semget fails when called from a process having minimum privileges (NETMBX,TMPMBX). This is because of the prot field being passed to the $CRMPSC call. Now, the prot field based on the semflag argument has been modified, so that $CRMPSC creates global section with sufficient permissions. Semctl with flag set to IPC_RMID must delete the semaphore set and also the global section associated with the semaphore set. But, the deletion of global section fails because it requires the SYSGBL and PRMGBL privileges to delete the systemwide global section permanently. Now, the privileges are enabled to delete the global section on a call to semctl with IPC_RMID. These problems have been fixed. Images Affected: - [SYSLIB]DECC$SHRP.EXE 5.2.6.2 Quix and PTR cases reporting this problem: Page 7 5.2.6.2.1 Quix Cases None. 5.2.6.2.2 PTR(s) 75-120-1286 5.2.6.3 Work-arounds: None. 5.2.7 lstat() Does not Return the Correct Bits in the st_mode Field for Files That are Symbolic Links 5.2.7.1 Problem Description: lstat() does not return the correct bits in the st_mode field for files that are symbolic links. lstat() when invoked with a symbolic link, must return information on the symbolic link itself. Instead, it returns information on the target file. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE 5.2.7.2 Quix and PTR cases reporting this problem: 5.2.7.2.1 Quix Cases None. 5.2.7.2.2 PTR(s) 75-123-131 5.2.7.3 Work-arounds: None. Page 8 5.2.8 Alignment Faults in Integrity VM 5.2.8.1 Problem Description: On OpenVMS Version 8.4, when copying a file from one disk to another disk, alignment faults occur in the Integrity VM AVIO storage driver. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$GSPDRIVER.EXE - [SYS$LDR]SYS$GSPBTDRIVER.EXE - [SYS$LDR]SYS$GSPDRIVER.STB 5.2.8.2 Quix and PTR cases reporting this problem: 5.2.8.2.1 Quix Cases None. 5.2.8.2.2 PTR(s) 75-123-129 5.2.8.3 Work-arounds: None. 5.2.9 Error Formatter (ERRFMT) Process Exits Reporting an Error Through VMS Mail 5.2.9.1 Problem Description: In some specific Integrity server systems, the first reboot after OpenVMS installation may see a VMS Mail as below: From: SYSTEM "ERRFMT - I bring you bad news..." To: SYSTEM Subj: ERRFMT encountered fatal errors and is deleting itself. Page 9 If you see this message, you must restart the ERRFMT process by entering the following command from the SYSTEM account: $ @SYS$SYSTEM:STARTUP ERRFMT Images Affected: - None 5.2.9.2 Quix and PTR cases reporting this problem: 5.2.9.2.1 Quix Cases None. 5.2.9.2.2 PTR(s) 75-123-102, 75-120-1327 5.2.9.3 Work-arounds: Restart the ERRFMT process by entering the following command from the SYSTEM account: $ @SYS$SYSTEM:STARTUP ERRFMT 5.2.10 Problem Accessing Large Files on Integrity server Systems Having Greater Than 4 GB of Physical Memory 5.2.10.1 Problem Description: If you are accessing large files on Integrity servers such as BL860 i2, BL870 i2, or BL890 i2, having greater than 4 GB of physical memory results in a system crash. While performing large I/O operations such as copy, search, and so on, on a large file present on SMART Array served disks, the system may crash with INVEXCEPTN. Also, installation of oracle may fail while creating large database files. Images Affected: Page 10 - [SYS$LDR]SYS$PKRDRIVER.EXE 5.2.10.2 Quix and PTR cases reporting this problem: 5.2.10.2.1 Quix Cases None. 5.2.10.2.2 PTR(s) 75-120-1309 5.2.10.3 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYS$LDR]SYS$GSPDRIVER.EXE (new image) Image Identification Information Image name: "SYS$GSPDRIVER" image file identification: "X-5" image file build identification: "XC9U-BL1-000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:11:58.96 Overall Image Checksum: 178D3280 o [SYS$LDR]SYS$GSPBTDRIVER.EXE (new image) Image Identification Information Image name: "SYS$GSPBTDRIVER" image file identification: "X-5" image file build identification: "XC9U-BL1-000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:11:52.36 Overall Image Checksum: 85D507F2 o [SYSLIB]DECC$SHR.EXE (new image) Image Identification Information image name: "DECC$SHR" image file identification: "V8.4-00" image file build identification: "XC9Y-BL1-000000" link date/time: 8-JUN-2010 13:30:42.06 linker identification: "Linker I02-37" Overall Image Checksum: 7FE1FD33 Page 11 o [SYSLIB]DECC$SHRP.EXE (new image) Image Identification Information image name: "DECC$SHRP" image file identification: "V8.4-00" image file build identification: "XC9Y-BL1-000000" link date/time: 8-JUN-2010 13:30:37.08 linker identification: "Linker I02-37" Overall Image Checksum: 4D117F3A o [SYS$LDR]RMS.EXE (new image) Image Identification Information Image name: "RMS" image file identification: "X-5" image file build identification: "XC9U-BL1-000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:11:02.26 Overall Image Checksum: 4720D9D0 o [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE (new image) Image Identification Information Image name: "SYS$TRANSACTION_SERVICES" image file identification: "V2.1-X035-XC9U" image file build identification: "XC9U-BL1-000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:09:45.51 Overall Image Checksum: 277B1C09 o [SYS$LDR]SYS$PKRDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKRDRIVER" image file identification: "X-5" image file build identification: "XCA2-BL1-000000" link date/time: 16-JUN-2010 17:13:41.21 linker identification: "Linker I02-37" Overall Image Checksum: AA3C0964 o [SYSMGR]CLUSTER_CONFIG.COM (new file) o [SYS$LDR]CLUSTER_CONFIG_LAN.COM (new file) o [SYS$LDR]SYS$GSPDRIVER.STB (new file) o [SYSEXE]I64VMS$PCSI_INSTALL_MIN.COM (new file) Page 12 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: 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 Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS84I_UPDATE-V0100.ZIPEXE 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 VMS84I_UPDATE[/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. Page 13 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=HP/BASE=I64VMS/VER=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_UPDATE-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_UPDATE/PRODUCER=HP/BASE=I64VMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! Page 14 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2010 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.