======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_SYS-V0500 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 for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_SYS-V0400 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS84I_PCSI-V0400 - VMS84I_UPDATE-V0900 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_SYS-V0500 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Loss of S0/S1 space while allocating large values of NPAGEDYN. 5.2.1.1 Problem Description: When NPAGEDYN is set to very large values memory holes in S0/S1 space may develop as the system may skip over some available space as it attempts to allocate large memory chunks on naturally aligned granularity hint boundaries. On one customer's system, increasing the NPAGEDYN from 255 MB to 256 MB lead to a loss of 134 MB of allocatable S0/S1 space. This problem has been corrected with this change. To enable this fix, bit 8 of the SYSGEN parameter MMG_CTLFLAGS needs to be set. Under the default conditions, you can set the value to 259 to set bit 8 while preserving the other default bits. Images Affected: - [SYS$LDR]SYS$BASE_IMAGE.EXE - [SYSLIB]SDA$SHARE.EXE - [SYSEXE]SYSGEN.EXE - [SYSEXE]SYSBOOT.EXE - [SYSEXE]SYSMAN.EXE - [SYSEXE]SMISERVER.EXE Page 3 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001296093 5.2.1.2.2 PTR(S) None 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.1.4 Work-arounds: None 5.2.2 Process Control Region Corruption. 5.2.2.1 Problem Description: System crashes or hangs due to corruption of the Process Control Region (CTL$GQ_ALLOCREG) and/or the RDE region (CTL$A_REGION_TABLE) for a process that had (or has) multiple kernel threads. The point of corruption is often a deallocated RDE (Region Descriptor Entry). Additional synchronization around the allocation and deallocation of the RDE was added to avoid this issue. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001296054 QXCM1001311525 QXCM1001334102 Page 4 5.2.2.2.2 PTR(S) 75-126-384 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.2.4 Work-arounds: None 5.2.3 Improve performance handling alignment faults. 5.2.3.1 Problem Description: Systems with a large number of alignment faults can see process slowdowns, heavy use of the MMG spinlock, and high MP Synchronization time. The alignment fault handler now reduces its use of the spinlock reducing contention and improving performance in environments having a large number of alignment faults. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases N/A 5.2.3.2.2 PTR(S) 75-74-335 Page 5 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.3.4 Work-arounds: None 5.2.4 RAD.COM showing up incorrect RAD memory distribution. 5.2.4.1 Problem Description: For a particular RAD memory configuration, RAD.COM can show incorrect memory distribution where the memory belonging to multiple RADs is added up to one specific RAD and the other RADs are showing no memory. This problem has been fixed. Images Affected: - [SYSEXE]SYSBOOT.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001325538 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 Integrity after V8.4 5.2.4.4 Work-arounds: None Page 6 5.2.5 Avoid intermittent DELCONPFN bugcheck during process rundown. 5.2.5.1 Problem Description: Some customers may experience an intermittent DELCONPFN bugcheck in MMG$DEL_CONTENTS_PFN_C. The root cause is still under investigation, but a workaround has been made that can be enabled by setting bit 9 in the SYSGEN parameter MMG_CTLFLAGS. This bit should not enabled unless recommended by OpenVMS engineering. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB - [SYSLIB]LIB.MLB - [SYSLIB]LIB.L32 - [SYSLIB]LIB.L64 - [SYSLIB]LIB.R64 - [SYSLIB]LIB.REQ - [SYSLIB]SYS$LIB_C.TLB 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001318159 5.2.5.2.2 PTR(S) None 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 7 5.2.5.4 Work-arounds: None 5.2.6 Add diagnostic info for FILCNTNONZ issue. 5.2.6.1 Problem Description: Some OpenVMS I64 nodes have experienced an intermittent FILCNTNONZ bugcheck during process rundown. A workaround for this particular FILCNTNONZ bugcheck was introduced in VMS84I_SYS-V0300 and VMS84I_UPDATE-V0900 to prevent the bugcheck by freezing the process. With this new update additional diagnostic information is being collected to assist OpenVMS Engineering in troubleshooting the issue. Images Affected: - [SYS$LDR]SWIS$DEBUG.EXE - [SYS$LDR]SWIS$DEBUG.STB - [SYSLIB]SWIS$SDA.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB - [SYSLIB]LIB.MLB 5.2.6.2 Quix and PTR cases reporting this problem: 5.2.6.2.1 Quix Cases QXCM1001340612 Page 8 5.2.6.2.2 PTR(S) None 5.2.6.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.6.4 Work-arounds: None 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_SYS patch kits can be found in the following files: o VMS84I_SYS-V0100.RELEASE_NOTES o VMS84I_SYS-V0200.RELEASE_NOTES o VMS84I_SYS-V0300.RELEASE_NOTES o VMS84I_SYS-V0400.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_SYS /VERSION=V5.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_SYS /VERSION=V5.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_SYS /VERSION=V5.0 /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYS$LDR]EXCEPTION.EXE (new image) Image Identification Information Page 9 Image name: "EXCEPTION" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:10.26 Overall Image Checksum: 73DA03CA o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information Image name: "EXCEPTION_MON" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:14.43 Overall Image Checksum: 73DA03CA o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information Image name: "IO_ROUTINES" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:44.91 Overall Image Checksum: 4014A1B9 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information Image name: "IO_ROUTINES_MON" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:54.53 Overall Image Checksum: 64A9BC9D o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) Image Identification Information Image name: "MESSAGE_ROUTINES" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:47:00.72 Overall Image Checksum: 2E2247D9 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information Image name: "PROCESS_MANAGEMENT" Image file identification: "X-5" Page 10 Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:55:23.31 Overall Image Checksum: 7D7750D3 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information Image name: "PROCESS_MANAGEMENT_MON" Image file identification: "X-5" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:55:32.78 Overall Image Checksum: A9AC37A o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information Image name: "SDA$SHARE" Image file identification: "X-2" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:53:48.72 Overall Image Checksum: 2389685D o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information Image name: "SECURITY" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:08.39 Overall Image Checksum: 6A1C5EFE o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information Image name: "SECURITY_MON" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:13.48 Overall Image Checksum: F257F663 o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information Image name: "SMISERVER" Image file identification: "X01-15" Image build identification: "0100000141" linker identification: "Linker I02-37" Page 11 Link Date/Time: 17-SEP-2014 16:53:55.06 Overall Image Checksum: B3A64ED o [SYS$LDR]SWIS$DEBUG.EXE (new image) Image Identification Information Image name: "SWIS$DEBUG" Image file identification: "X-5" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:55:31.00 Overall Image Checksum: 6B25B3D6 o [SYSLIB]SWIS$SDA.EXE (new image) Image Identification Information Image name: "SWIS$SDA" Image file identification: "X-2A1" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:55:33.15 Overall Image Checksum: 81C15147 o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) Image Identification Information Image name: "SYS$BASE_IMAGE" Image file identification: "IA64 XCFR-J2I" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:29:41.12 Overall Image Checksum: 8358BD5D o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information Image name: "SYS$VM" Image file identification: "X-5" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:54:45.90 Overall Image Checksum: 3E175CF2 o [SYSEXE]SYSBOOT.EXE (new image) Image Identification Information Image name: "SYSBOOT" Image file identification: "X-154" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:53:50.20 Overall Image Checksum: 22B8B7B1 Page 12 o [SYSEXE]SYSGEN.EXE (new image) Image Identification Information Image name: "SYSGEN" Image file identification: "X-5" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:53:48.59 Overall Image Checksum: 4F07F1F9 o [SYSEXE]SYSMAN.EXE (new image) Image Identification Information Image name: "SYSMAN" Image file identification: "X01-22" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:53:48.93 Overall Image Checksum: AA73A266 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information Image name: "SYSTEM_PRIMITIVES" Image file identification: "X-5" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:55:20.11 Overall Image Checksum: 341149A3 o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) Image Identification Information Image name: "SYSTEM_PRIMITIVES_MIN" Image file identification: "X-5" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:55:32.88 Overall Image Checksum: A2038794 o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYSEXE]I64VMS$PCSI_INSTALL_MIN.COM (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYSLIB]LIB.L32 (new file) Page 13 o [SYSLIB]LIB.L64 (new file) o [SYSLIB]LIB.MLB (new file) o [SYSLIB]LIB.R64 (new file) o [SYSLIB]LIB.REQ (new file) o [SYS$LDR]MESSAGE_ROUTINES.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]SECURITY.STB (new file) o [SYS$LDR]SECURITY_MON.STB (new file) o [SYS$LDR]SWIS$DEBUG.STB (new file) o [SYSLIB]SYS$LIB_C.TLB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) 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: 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. Page 14 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_SYS-V0500.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_SYS[/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: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT 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 Page 15 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=V5.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_SYS-V0500 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_SYS/PRODUCER=HP/BASE=I64VMS/VER=V5.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2014 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 Page 16 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.