**************************** ECO SUMMARY INFORMATION **************************** Release Date: 23-JAN-2007 Kit Name: DEC-AXPVMS-VMS82A_MANAGE-V0100--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V8.2 Approximate Kit Size: 1062 blocks Installation Rating: INSTALL_3 Reboot Required: Yes - rolling reboot Superseded Kits: None Mandatory Kit Dependencies: VMS82A_UPDATE-V0500 or later VMS82A_PCSI-V0100 or later Optional Kit Dependencies: None Checksums: VMS82A_MANAGE-V0100.ZIPEXE Checksum: 2286557983 DEC-AXPVMS-VMS82A_MANAGE-V0100--4.PCSI$COMPRESSED Checksum: 2449141243 VMS82A_MANAGE-V0100.ZIPEXE MD5 Checksum: A6FAB515F0DB6ACD28294F39CF4E5547 DEC-AXPVMS-VMS82A_MANAGE-V0100--4.PCSI$COMPRESSED MD5 Checksum: F75CAC555F3333905867A01C156E4FF3 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS82A_MANAGE-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 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 ALPHA V8.2 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: - VMS82A_PCSI-V0100 - VMS82A_UPDATE-V0500 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 VMS82A_MANAGE-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 SYSMAN IO Commands give "no more node" Warning Messages 5.2.1.1 Problem Description: After issuing the SYSMAN command SET ENVIRONMENT/CLUSTER, SYSMAN IO commands output "no more node" warning messages after successful completion. For example: SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> IO SCSI %SYSMAN-I-NODERR, error returned from node SYSTEM1 -SYSTEM-W-NOMORENODE, no more nodes Images Affected: - [SYSEXE]SYSMAN.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) QXCM1000224225 5.2.1.2.2 QAR(s) None. Page 3 5.2.1.3 Problem Analysis: Unlike other SYSMAN commands, IO commands do not suppress the NOMORENODE message when running in cluster environment context. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.1.5 Work-arounds: None. 5.2.2 Outswap of the SHADOW_SERVER Can Lead to Hung Writes With HBMM 5.2.2.1 Problem Description: Under a specific set of conditions all writes to a shadow set that contains a swap file can become deadlocked. In addition, any MOUNT or DISMOUNT of a shadow set will hang. No additional progress will be made on any active or pending shadow set copy or merge operations. Any attempt to define or alter an HBMM policy on an existing shadow set will hang. The necessary conditions that lead to this hang are: 1. The swapfile that is associated with the SHADOW_SERVER process and various other processes is located on a shadow set. 2. Host-Based Minimerge (HBMM) is enabled on that shadow set. 3. The shadow server process is outswapped due to the physical memory demands on the system. 4. Some other node in the cluster initiates an HBMM bitmap reset on the shadow set with the swapfile. As a result, new writes to that shadow set are blocked until the bitmap reset is completed. 5. There are insufficient memory or balance set slots to be able to inswap the SHADOW_SERVER without outswapping some other process. 6. Writes to the shadow set with the swapfile will remain blocked until the SHADOW_SERVER process on this node can service the HBMM bitmap reset event, and the SHADOW_SERVER process can not be inswapped until some writes complete. Page 4 Because the SHADOW_SERVER process is stuck in an outswapped state, any activity that depends on the SHADOW_SERVER process is also hung. Images Affected: - [SYS$STARTUP]VMS$CONFIG-050_SHADOW_SERVER.COM 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000229775 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: See problem description. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS V8.3 5.2.2.5 Work-arounds: None. 5.2.3 PCB and Pool Corruption 5.2.3.1 Problem Description: PCB (Process Control Block) and Pool corruption can occur when using the SYSMAN command: CLASS MODIFY class-name/[NO]WINDFALL Corruption can occur if there are any processes on the system that are using the specified class. For non-multithreaded processes, this command will often result in corruption of the PCB$Q_LOCKQFL/PCB$Q_LOCKQBL fields. For multithreaded processes, various non-paged pool corruptions can occur. Images Affected: Page 5 - [SYSLIB]SMI$OBJSHR.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) None. 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: The code to obtain a pointer to the KTB vector incorrectly obtains the address of the pointer to the KTB vector. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.3 5.2.3.5 Work-arounds: None. 5.2.4 SMI-E-BADACTRL Error on Accounts With Mixed Case Passwords 5.2.4.1 Problem Description: A SYSMAN command requiring a remote username and password will fail with a BADACTRL error when the remote user has the UAF PWDMIX flag set. SYSMAN> DO SHOW PROCESS %SYSMAN-I-OUTPUT, command execution on node NODENAME %SYSMAN-I-NODERR, error returned from node NODENAME Images Affected: - [SYSEXE]SMISERVER.EXE Page 6 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM1000297851 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: SMISERVER converts the password to uppercase. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.3 5.2.4.5 Work-arounds: None. 5.2.5 SMISERVER Process Crash With %SYSTEM-F-OBJLOCKED Error 5.2.5.1 Problem Description: A SYSMAN command can fail with an "SMI Server has aborted error": %SYSMAN-I-NODERR, error returned from node SYSTEM -SMI-E-ABORT, SMI Server has aborted A SMISERVER dump file will be created on the node at SYS$SYSTEM:SMISERVER.DMP. Analysis of the process dump shows the server aborted with an OBJLOCKED error such as: %SYSTEM-F-OBJLOCKED, security object is locked by another user break on unhandled exception preceding SHARE$SMISERVER+139568 Images Affected: - [SYSEXE]SMISERVER.EXE Page 7 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) QXCM1000299877,70-3-8549 5.2.5.2.2 QAR(s) None. 5.2.5.3 Problem Analysis: SMISERVER changes ownership on the job logical name table when servicing a request which requires a persona change. The table can be locked, and the security system service is documented as such, but SMI did not check for a locked status. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.3 5.2.5.5 Work-arounds: None. 5.2.6 REGISTER_PRIVILEGED_IMAGE.COM Procedure Updated 5.2.6.1 Problem Description: For OpenVMS V8.2, the REGISTER_PRIVILEGED_IMAGE.COM procedure was updated with information on system version numbers that changed between OpenVMS V7 and V8. There were 2 system versions that changed between V6 and V7 and these version numbers were removed. The removal of these version numbers has the impact of not allowing an image linked under OpenVMS V6 to be registered to run under OpenVMS V8.x. The additional system version number changes from OpenVMS V6 to V7 have been added back into the procedure to allow images linked under OpenVMS V6 with these versions to be registered. Images Affected: - [SYSUPD]REGISTER_PRIVILEGED_IMAGE.COM Page 8 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.3 Problem Analysis: See problem description 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.3 5.2.6.5 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYSLIB]SMI$OBJSHR.EXE (new image) Image Identification Information image name: "SMI$OBJSHR" image file identification: "X40-A9" image file build identification: "XAJT-0070050008" link date/time: 11-MAY-2006 08:36:05.46 linker identification: "A11-50" Overall Image Checksum: 3311359975 o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information image name: "SMISERVER" image file identification: "X01-15" image file build identification: "XAJT-0070050008" link date/time: 11-MAY-2006 08:36:10.95 linker identification: "A11-50" Overall Image Checksum: 758148586 o [SYSEXE]SYSMAN.EXE (new image) Image Identification Information image name: "SYSMAN" image file identification: "X01-22" image file build identification: "XAJT-0070050008" link date/time: 11-MAY-2006 08:36:06.48 linker identification: "A11-50" Overall Image Checksum: 448290712 Page 9 o [SYSUPD]REGISTER_PRIVILEGED_IMAGE.COM (new file) o [SYS$STARTUP]VMS$CONFIG-050_SHADOW_SERVER.COM (new file) 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 VMS82A_MANAGE-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 VMS82A_MANAGE[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this Page 10 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. 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 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=DEC/BASE=AXPVMS/VER=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned Page 11 For example, a sample command file to install the VMS82A_MANAGE-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS82A_MANAGE/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2007 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.