======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_SYS-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: 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-V0100 4 KIT DEPENDENCIES: Page 2 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS84I_PCSI-V0300 - VMS84I_UPDATE-V0600 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-V0200 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Floating point registers f28 through f31 may not be properly restored following execution of a $UNWIND system service. 5.2.1.1 Problem Description: When compiling programs with the /OPTIMIZE (or for COBOL,the default /MATH_INTERMEDIATE) qualifier, floating point registers f28 through f31 may not be properly restored after execution of the $UNWIND system service. When $UNWIND is issued in a condition handler, control is returned to a routine earlier in the call chain. Upon return of control, all non-scratch registers should be restored to their values at the time of the call. A problem in the $UNWIND system service caused floating point registers f28 through f31 to not be restored properly. Generally, the external symptom will be incorrect calculations. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE Page 3 - [SYS$LDR]EXCEPTION_MON.STB 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001178043 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 for Integrity Servers after V8.4 5.2.1.4 Work-arounds: Compile programs with the /NOOPTIMIZE, (or for COBOL, the /MATH_INTERMEDIATE=CIT4) qualifier. This will avoid the usage of floating point registers f28 through f31. 5.2.2 "SECREFNEG" bugcheck while executing CMS command. 5.2.2.1 Problem Description: System crash with "SECREFNEG" while executing the following CMS command: $ CMS DELETE CLASS /REMOVE_CONTENTS "" This kit fixes the issue. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.2.2 Quix and PTR cases reporting this problem: Page 4 5.2.2.2.1 Quix Cases QXCM1001148090,QXCM1001127168 5.2.2.2.2 PTR(s) None. 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.2.4 Work-arounds: None. 5.2.3 Process hangs in EXE$DEASSGN. 5.2.3.1 Problem Description: Process could hang in EXE$DASSGN code waiting for deaccess I/O to complete. This could occur during process rundown and will typically show a channel with: (1) an I/O outstanding, CCB$L_IOC is 1; (2) deaccess has been started, CCB$L_WIND has bit 0 set; (3) but no pending deaccess IRP, CCB$L_DIRP is 0. The process would hang in LEF state, unless someone tries to delete the process, at which point it would go into RWAST state. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.STB 5.2.3.2 Quix and PTR cases reporting this problem: Page 5 5.2.3.2.1 Quix Cases QXCM1001173370 5.2.3.2.2 PTR(s) 75-126-192 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.3.4 Work-arounds: None. 5.2.4 Avoid intermittent INVEXCEPTN bugcheck during image rundown. 5.2.4.1 Problem Description: This kit fixes an intermittent INVEXCEPTN bugcheck that occurs during image rundown. If we have a global section which is mapped to reserved memory and there are few processes mapping pages to the global section, the image rundown of a process can cause a system crash with INVEXCEPTN bugcheck in certain circumstances. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001158585 5.2.4.2.2 PTR(s) 75-126-176 Page 6 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.4.4 Work-arounds: None. 5.2.5 Avoid a possible INCONMMGST bugcheck. 5.2.5.1 Problem Description: This kit fixes a system crash that could occur while restarting Oracle in rare circumstances when memory resident global sections were being recreated after being deleted when Oracle was stopped. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001145141 5.2.5.2.2 PTR(s) 75-126-189 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.5.4 Work-arounds: None. Page 7 5.2.6 Per RAD PCB cache leak resulting in PCBs filling non-paged pool. 5.2.6.1 Problem Description: This kit fixes a memory leak that could fill up non-paged pool resulting in slower system performance. The issue occurred on a system with RAD enabled, but per RAD non-paged pool is disabled. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.6.2 Quix and PTR cases reporting this problem: 5.2.6.2.1 Quix Cases QXCM1001173796, QXCM1001177389 5.2.6.2.2 PTR(s) 75-126-181 5.2.6.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.6.4 Work-arounds: Increase NPAGEDYN to a large enough value to avoid pool expansion, as the PCB memory leak only occurs when nonpaged pool has expanded on a RAD system. 5.2.7 Fatal error while creating CW logical name. Page 8 5.2.7.1 Problem Description: Creating Cluster Wide logical names may result in cluster crash under certain circumstances. Images Affected: - [SYS$LDR]LOGICAL_NAMES.EXE - [SYS$LDR]LOGICAL_NAMES.STB 5.2.7.2 Quix and PTR cases reporting this problem: 5.2.7.2.1 Quix Cases QXCM1001186014, QXCM1001185701 5.2.7.2.2 PTR(s) None. 5.2.7.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.7.4 Work-arounds: None. 5.2.8 Intermittent SSRVEXCEPT system crash. 5.2.8.1 Problem Description: This kit fixes a very rare SSRVEXCEPT crash observed during internal testing. This occurred due to an instruction serialization issue that caused an unexpected Data TLB fault leading to system crash. Images Affected: - [SYSEXE]IPB.EXE - [SYSEXE]IPB_NOXDELTA.EXE - [SYSEXE]SYSBOOT.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.EXE Page 9 - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.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-128-112 5.2.8.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.8.4 Work-arounds: None. 5.2.9 Potential MTXCNTNONZ bugcheck while unloading executive images. 5.2.9.1 Problem Description: Under rare timing conditions a system could bugcheck with a MTXCNTNONZ, Mutex count nonzero at system service exit while unloading an executive image (such as an SDA extension). Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB Page 10 5.2.9.2 Quix and PTR cases reporting this problem: 5.2.9.2.1 Quix Cases QXCM1001178157 5.2.9.2.2 PTR(s) 75-13-2487 5.2.9.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.9.4 Work-arounds: None. 5.2.10 SDA command "flt show trace/summary" does not display the EPID. 5.2.10.1 Problem Description: EPID field is not populated when displaying the output of SDA command 'flt show trace/summary' This problem has been fixed. Images Affected: - [SYSLIB]FLT$SDA.EXE - [SYS$LDR]FLT$DEBUG.EXE 5.2.10.2 Quix and PTR cases reporting this problem: 5.2.10.2.1 Quix Cases QXCM1001139000 5.2.10.2.2 PTR(s) None. Page 11 5.2.10.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.10.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 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=V2.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_SYS /VERSION=V2.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=V2.0 /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYS$LDR]EXCEPTION.EXE (new image) Image Identification Information Image name: "EXCEPTION" Image file identification: "X-5" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:29.33 Overall Image Checksum: 37826890 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information Page 12 Image name: "EXCEPTION_MON" Image file identification: "X-5" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:30.63 Overall Image Checksum: 37826890 o [SYS$LDR]FLT$DEBUG.EXE (new image) Image Identification Information Image name: "FLT$DEBUG" Image file identification: "X-5" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:50.37 Overall Image Checksum: 5DD7CEA3 o [SYSLIB]FLT$SDA.EXE (new image) Image Identification Information Image name: "FLT$SDA" Image file identification: "X-8A1" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:51.09 Overall Image Checksum: 63800810 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information Image name: "IO_ROUTINES" Image file identification: "X-5" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:39.25 Overall Image Checksum: A87678EF 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: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:45.22 Overall Image Checksum: C6A67E93 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information Image name: "PROCESS_MANAGEMENT" Image file identification: "X-5" Image build identification: "0100000005" Page 13 linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:59.83 Overall Image Checksum: 1C79ACA0 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: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:32:02.89 Overall Image Checksum: 69AC58ED o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information Image name: "SYS$VM" Image file identification: "X-5" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:54.93 Overall Image Checksum: 354B6830 o [SYSEXE]SYSBOOT.EXE (new image) Image Identification Information Image name: "SYSBOOT" Image file identification: "X-154" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:53.30 Overall Image Checksum: 379E7EC5 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information Image name: "SYSTEM_PRIMITIVES" Image file identification: "X-5" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:32:08.28 Overall Image Checksum: 89E343D1 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: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:32:11.75 Page 14 Overall Image Checksum: 96E8B14A o [SYSEXE]IPB.EXE (new image) Image Identification Information Image name: "IPB" Image file identification: "X-4" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:40.84 Overall Image Checksum: A90E096E o [SYSEXE]IPB_NOXDELTA.EXE (new image) Image Identification Information Image name: "IPB_NOXDELTA" Image file identification: "X-4" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:42.13 Overall Image Checksum: 8E9E08DD o [SYS$LDR]LOGICAL_NAMES.EXE (new image) Image Identification Information Image name: "LOGICAL_NAMES" Image file identification: "X-5" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:51.05 Overall Image Checksum: 45A4DBF o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYS$LDR]LOGICAL_NAMES.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (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) Page 15 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. 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-V0200.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 Page 16 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 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=V2.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_SYS-V0200 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=V2.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! Page 17 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2012 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.