**************************** ECO SUMMARY INFORMATION **************************** Kit Name: DEC-AXPVMS-VMS731_PARTITIONING-V0300--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 8528 blocks Installation Rating: INSTALL_2 Required Feature: ES47/ES80/GS1280 Series Systems Reboot Required: Yes - rolling reboot Superseded Kits: VMS731_PARTITIONING-V0200 Mandatory Kit Dependencies: VMS731_PCSI-V0100 VMS731_UPDATE-V0200 Optional Kit Dependencies: None. VMS731_PARTITIONING-V0300.PCSI-DCX_AXPEXE Checksum: 3046403551 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS731_PARTITIONING-V0300 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 1 KIT NAME: VMS731_PARTITIONING-V0300 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2: To be installed by all customers using the following feature(s): - Customers who wish to have hard or soft partitioning on ES47, ES80 or GS1280 Series Systems. - Customers who have installed the VMS731_PARTITIONING-V0200 remedial kit. 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 Alpha V7.3-1 2.4 New functionality or new hardware support provided: Yes. 3 KITS SUPERSEDED BY THIS KIT: - VMS731_PARTITIONING-V0200 Page 2 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS731_UPDATE-V0200 - VMS731_PCSI-V0100 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 FILES PATCHED OR REPLACED: o [SYSEXE]GCM_SERVER.EXE (new image) Image Identification Information image name: "GCM_SERVER" image file identification: "GCM_SERVER V1.1" image file build identification: "X9TD-0060030000" link date/time: 25-JUN-2003 12:09:50.89 linker identification: "A11-50" Overall Image Checksum: 1052307836 o [SYSEXE]GCU.EXE (new image) Image Identification Information image name: "GCU" image file identification: "GCU V6.0" image file build identification: "X9TD-0060030002" link date/time: 25-JUN-2003 12:05:35.64 linker identification: "A11-50" Overall Image Checksum: 2598572072 o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information image name: "SDA$SHARE" image file identification: "X-2" image file build identification: "X9TD-0060030012" link date/time: 25-JUN-2003 12:05:20.63 linker identification: "A11-50" Overall Image Checksum: 832125465 Page 3 o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) Image Identification Information image name: "SYS$BASE_IMAGE" image file identification: "ALPHA X9TD-R2Y" image file build identification: "X9TD-0060030037" link date/time: 25-JUN-2003 12:02:01.33 linker identification: "A11-50" Overall Image Checksum: 686757223 o [SYS$LDR]SYS$GALAXY.EXE (new image) Image Identification Information image name: "SYS$GALAXY" image file identification: "X-3" image file build identification: "X9TD-0060030001" link date/time: 12-NOV-2003 11:37:56.53 linker identification: "A11-50" Overall Image Checksum: 3434789996 o [SYS$LDR]GALAXY.GCR (new file) o [SYS$CONFIG]GCM_RULESET.XML (new file) 6 PROBLEMS ADDRESSED IN THIS KIT 6.1 New problems addressed in the VMS731_PARTITIONING-V0300 kit 6.1.1 Fix Galaxy Shared Memory Interconnect Initialization 6.1.1.1 Problem Description: A change introduced in the VMS731_PARTITIONING-V0200 partitioning kit (Required) causes the Galaxy Node Incarnation not to be incremented. The result of this is that the shared memory cluster interconnect may fail to come online after a reboot unless the entire Galaxy is rebooted. Images Affected: - [SYS$LDR]SYS$GALAXY.EXE 6.1.1.2 CLDs, and QARs reporting this problem: Page 4 6.1.1.3 CLD(s) 75-83-1574 6.1.1.4 QAR(s) None. 6.1.1.5 Problem Analysis: This change corrects the problem by not zeroing the incarnation. 6.1.1.6 Work-arounds: None. 6.2 Problems addressed in the VMS731_PARTITIONING-V0200 kit 6.2.1 Galaxy commands produce incorrect results 6.2.1.1 Problem Description: Under SDA, certain show commands specific to Galaxy produce incorrect results. Additionally, using the DCL f$getsyi function with certain galaxy item codes produces unreadable results. Images Affected: - [SYSLIB]SDA$SHARE.EXE - [SYS$LDR]SYS$GALAXY.EXE 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.3 CLD(s) None. 6.2.1.4 QAR(s) 75-83-738 Page 5 6.2.1.5 Problem Analysis: Marvel memory is not initialized to zero, it is initialized to all 5's. The 5's in the Galaxy management data structure were causing the display problems. 6.2.1.6 Work-arounds: None. 7 INSTALLATION INSTRUCTIONS: 7.1 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 VMS731_PARTITIONING /SAVE_RECOVERY_DATA- [/SOURCE=location of Kit] 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.2 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 6 that operation. There is no need to also save files as *.*_OLD: $ DEFINE/SYS ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PRODUCER=DEC/BASE=AXPVMS/VER=V3.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS731_PARTITIONING-V0300 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/SYS ARCHIVE_OLD NO $! $ PRODUCT INSTALL VMS731_PARTITIONING /PRODUCER=DEC/BASE=AXPVMS- /VER=V1.0 /SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $ DEASSIGN/SYS ARCHIVE_OLD$! $ exit 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2004 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 Page 7 EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL COMPAQ 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.