**************************** ECO SUMMARY INFORMATION **************************** Release Date: 6-JUN-2006 Kit Name: DEC-AXPVMS-VMS82A_CLUSTER-V0100--4.PCSI Kit Applies To: OpenVMS ALPHA V8.2 Approximate Kit Size: 816 blocks Installation Rating: INSTALL_3 Reboot Required: Yes - rolling reboot Superseded Kits: None Mandatory Kit Dependencies: VMS82A_UPDATE-V0200 or later VMS82A_PCSI-V0100 or later Optional Kit Dependencies: None VMS82A_CLUSTER-V0100.PCSI-DCX_AXPEXE Checksum: 3787428473 DEC-AXPVMS-VMS82A_CLUSTER-V0100--4.PCSI Checksum: 2035543039 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS82A_CLUSTER-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-V0200 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_CLUSTER-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 SYSMAN Command DO SHOW PROCESS Fails With SMI-E-BADACTRL error 5.2.1.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 -SMI-E-BADACTRL, remote access control info invalid Images Affected: - [SYSEXE]SMISERVER.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) QXCM1000297851 5.2.1.2.2 QAR(s) None. Page 3 5.2.1.3 Problem Analysis: SMISERVER uppercases the password. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2. 5.2.1.5 Work-arounds: None. 5.2.2 SYSMAN Command Failure 5.2.2.1 Problem Description: A SYSMAN command fails with an "SMI Server has aborted" error: %SYSMAN-I-NODERR, error returned from node MYNODE -SMI-E-ABORT, SMI Server has aborted Analysis of a process dump shows that the server aborted with an OBJLOCKED error: %SYSTEM-F-OBJLOCKED, security object is locked by another user break on unhandled exception preceding SHARE$SMISERVER+139568 Images Affected: - [SYSEXE]SMISERVER.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000299877 5.2.2.2.2 QAR(s) None. Page 4 5.2.2.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 does not check for a locked status. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.2.5 Work-arounds: None. 5.2.3 SCACP Startup Takes Too Long 5.2.3.1 Problem Description: When SCACP is started on a system with thousands of devices, startup can take extremely long (30 sec to over a minute) and consume 100% of a CPU. Images Affected: - [SYSEXE]SCACP.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) QXCM1000242636,WFM3211094919=321 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: Inefficient scan of the IO database looking for SCA ports. Page 5 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.3.5 Work-arounds: None. 5.2.4 Processes Terminate With %SYSTEM-S-NORMAL 5.2.4.1 Problem Description: FASTPATH_SERVER, CONFIGURE, SMISERVER, and SMHANDLER can exit with with process terminations of %SYSTEM-S-NORMAL. At the same time, OPCOM and the Console can show -SYSTEM-F-BADPARAM error messages with no reference to which process or image reported the message. Images Affected: - [SYSEXE]FASTPATH_SERVER.EXE - [SYSEXE]CONFIGURE.EXE - [SYSEXE]SMISERVER.EXE - [SYSEXE]SYS$SMHANDLER.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM1000326946 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: Most of the standard system server processes idle in the hibernate (HIB) state and do their work at AST level in response to messages and other asynchronous events. In almost all cases, these processes do not exit, even during system shutdown. So, typically, if such a server is taken out of HIB state via an unexpected SYS$WAKE, the server process just loops back and re-executes the SYS$HIBER system service. However, the FASTPATH_SERVER, CONFIGURE, SMISERVER, and SMHANDLER servers do not make any provision against such an unexpected SYS$WAKE, and Page 6 terminate if unexpectedly woken up. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.4.5 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYSEXE]CONFIGURE.EXE (new image) Image Identification Information image name: "CONFIGURE" image file identification: "X-8" image file build identification: "XAJT-0070050001" link date/time: 11-MAY-2006 08:36:12.46 linker identification: "A11-50" Overall Image Checksum: 4258456377 o [SYSEXE]FASTPATH_SERVER.EXE (new image) Image Identification Information image name: "FASTPATH_SERVER" image file identification: "X-5A2" image file build identification: "0070050033" link date/time: 11-MAY-2006 08:36:12.19 linker identification: "A11-50" Overall Image Checksum: 618696175 o [SYSEXE]SCACP.EXE (new image) Image Identification Information image name: "SCACP" image file identification: "X-28A1" image file build identification: "XAJT-0070050001" link date/time: 11-MAY-2006 08:36:13.04 linker identification: "A11-50" Overall Image Checksum: 1655457672 o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information image name: "SMISERVER" image file identification: "X01-15" image file build identification: "XAJT-0070050008" Page 7 link date/time: 11-MAY-2006 08:36:10.95 linker identification: "A11-50" Overall Image Checksum: 758148586 o [SYSEXE]SYS$SMHANDLER.EXE (new image) Image Identification Information image name: "SYS$SMHANDLER" image file identification: "X-7" image file build identification: "0070050000" link date/time: 11-MAY-2006 08:36:33.66 linker identification: "A11-50" Overall Image Checksum: 294448031 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 DCX compressed kit. To expand this file to the installable .PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS82A_CLUSTER-V0100.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Page 8 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the"Decompress into (file specification)" question, either a or an alternate directory specification 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_CLUSTER[/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. 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 Page 9 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 For example, a sample command file to install the VMS82A_CLUSTER-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS82A_CLUSTER/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2006 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 Page 10 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.