ECO NUMBER: VMS73_LMF-V0100 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 COVER LETTER 1 KIT NAME: VMS73_LMF-V0100 2 KITS SUPERSEDED BY THIS KIT: None. 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: None. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.3 4.2 Files patched or replaced: o [SYS$STARTUP]LICENSE_CHECK.EXE (new image) o [SYSEXE]LMF.EXE (new image) o [SYSEXE]SHOW.EXE (new image) o [SYS$LDR]SYSLICENSE.EXE (new image) 5 PROBLEMS ADDRESSED IN VMS73_LMF-V0100 KIT o Some OpenVMS Alpha Version 7.3 GS80/160/320 AlphaServer systems with hard or soft partitions and a common license database (LDB) have difficulty booting up all partitions if you had modified nonsharable license PAKs to share license units among OpenVMS instances. This problem has been corrected. -- COVER LETTER -- Page 2 30 August 2001 Before you install this kit, you must perform the following steps: 1. If you installed workarounds, remove them. OpenVMS systems that have a problem using a common license database on hard and soft partitions display the following symptoms: o Booting OpenVMS produces OPCOM messages which state that licenses cannot be loaded. o Logging in to OpenVMS produces an error message which states that the OPENVMS-ALPHA license cannot be loaded. To get around the inability to use nonsharable license PAKs in a common license database to share license units among OpenVMS instances on hard and soft partitions, Compaq recommended that you use one of the following two workarounds: o Use of a separate license database for each operating system instance running OpenVMS on AlphaServer GS80/160/320 systems o Use of temporary (120-day) license PAKs provided by Compaq Services If you used either of these workarounds, you must remove it before installing this kit. To remove the workaround: o If you had set up separate license databases You should create a common license database before installing this kit. See the OpenVMS License Management Utility Manual for guidelines on setting up a common license database. o If you installed temporary PAKs If you installed temporary PAKs in the common license database, you must disable the temporary PAKs for the following licenses: - OPENVMS-ALPHA - OPENVMS-ALPHA-USER - OPENVMS-ALPHA-USER-ADL To see a list of temporary PAKs installed on your system, enter the following command: $ LICENSE LIST /FULL /BEFORE /TERMINATION_DATE= - -- COVER LETTER -- Page 3 30 August 2001 _$ "-120-" OPENVMS-ALPHA, OPENVMS-ALPHA-USER, - _$OPENVMS-ALPHA-USER-ADL This command displays (for the three license we specify) the licenses that satisfy one of the following conditions: - Have already terminated - Will terminate within the next 120 days. Disable each of the temporary PAKs listed above with the LICENSE DISABLE command. For example: $ LICENSE DISABLE OPENVMS-ALPHA - _$ /AUTHORIZATION=authorization-value where authorization-value helps to identify the license, and is displayed by the LICENSE LIST command you used to find the temporary PAKs. 2. Install Licenses Before you install this kit, you should perform the following steps to ensure that the common license database can share license units among hard and soft partitions: i. Calculate required units. o Load the base OpenVMS license. o Load the SMP licenses. o Use the following command to verify that you have the correct number of license units: $ SHOW LICENSE /UNIT_REQUIREMENTS /CLUSTER ________________________ Note ____________________ The base OpenVMS license allows you to have only one interactive user login per physical system (not per partition). (However, you can always login from OPA0: in each partition.) For additional interactive users, you will require additional license units. See your Compaq representative to determine your needs. __________________________________________________ ii. Add your licenses to the common license database. For example: $ LICENSE REGISTER license-name /ISSUER=DEC - _$ /AUTHORIZATION=USA123456 - -- COVER LETTER -- Page 4 30 August 2001 _$ /PRODUCER=DEC - _$ /UNITS=1050 - _$ /AVAILABLITY=H - _$ /OPTIONS=(NO_SHARE) - _$ /CHECKSUM=2-BGON-IAMA-GNOL-AIKO Note that you cannot use the /INCLUDE qualifier with the LICENSE REGISTER command to override the NO_SHARE attribute of the license. iii. Modify the license to override the NO_SHARE attribute of the PAKs with the command LICENSE REGISTER/INCLUDE=(node-name-list). For example: $ LICENSE MODIFY OPENVMS-ALPHA - _$ /INCLUDE=(NODEA, NODEB, NODEC) iv. To make OpenVMS Alpha license units available to the instance of OpenVMS running in each partition, you must ensure that SRM environment variable SYS_SERIAL_NUM is the same in each partition. To do so, perform the following steps: a. From the master console of each partition (usually on console line 0), use the SHOW SYS_SERIAL_NUM command to display the system serial number. For example: $ ^P halted CPU 0 halt code=1 operator initiated halt PC = ffffffff9c0a0aa8 P00>>>SHOW SYS_SERIAL_NUM sys_serial_num G2A105 If the value of SYS_SERIAL_NUM is blank, use the SHOW SYS_SERIAL_NUM command from the master console in each of the other partitions to check for a non-blank system serial number. ________________________ Note ____________________ If all partition consoles show a blank value for SYS_ SERIAL_NUM, you must create a non-zero value of up to 16 characters. Ensure that the system serial number that you create is not used on any other AlphaServer GS80/160/320 on this OpenVMS Cluster. ___________________________________________________ -- COVER LETTER -- Page 5 30 August 2001 b. Once you have determined the system serial number, use the SET SYS_SERIAL_NUM command from the master console of each partition to change SYS_SERIAL_NUM to the correct value. For example: $ ^P halted CPU 0 halt code=1 operator initiated halt PC = ffffffff9c0a0aa8 P00>>>SET SYS_SERIAL_NUM G2A105 You must do this in every hard partition and in every soft partition. v. In order for the OpenVMS Cluster license database to be updated correctly, Compaq recommends that you completely shutdown and reboot all OpenVMS Cluster common nodes. A rolling upgrade type of boot does not correctly update the common license database. ________________________ Note ________________________ Any time you reconfigure the number of hard or soft partitions on your AlphaServer GS80/160/320 you must make sure that all partitions have the same SYS_SERIAL_NUM if your system is part of an OpenVMS Cluster that shares a common license database. See AlphaServer GS80/160/320 Getting Started with Partitions for more information about hard and soft partitions. ______________________________________________________ Images Affected: - [SYS$LDR]SYSLICENSE.EXE - [SYS$STARTUP]LICENSE_CHECK.EXE - [SYSEXE]LMF.EXE - [SYSEXE]SHOW.EXE -- COVER LETTER -- Page 6 30 August 2001 6 KIT INSTALLATION RATING: The following kit 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) INSTALLATION RATING: INSTALL_3 : To be installed by customers experiencing the problems corrected. 7 INSTALLATION INSTRUCTIONS: 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 VMS73_LMF /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt This kit requires a system reboot. Compaq strongly recommends that a reboot is performed immediately after kit installation. If a reboot is not performed, your system may be left in an inconsistant state. The entire cluster must be rebooted at the same time. Rolling reboots are not allowed and, if done, may lead to system instability. ******* NOTE ******* There are several steps that must be performed before this kit is installed. Refer to section 5.0 for information on these actions that must be performed before kit installation. ******************** Copyright (c) Compaq Computer Corporation, 2001 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. COMPAQ, the Compaq logo, VAX, Alpha, VMS, and OpenVMS are registered in the U.S. Patent and Trademark Office. All other product names mentioned herein may be trademarks of their respective companies. -- COVER LETTER -- Page 7 30 August 2001 Confidential computer software. Valid license from Compaq 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. Compaq shall not 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 Compaq 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 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.