OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: system PRIVILEGED account (rootstage1.cxo.cpqcorp.net)
Date: Wed Nov 07 2001 - 17:05:08 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    TITLE: OpenVMS VMS73_LMF-V0100 ALPHA 7.3 LMF ECO Summary

    New Kit Date : 04-OCT-2001
    Modification Date: Not Applicable
    Modification Type: New Kit

    NOTE: An OpenVMS saveset or PCSI installation file is stored
           on the Internet in a self-expanding compressed file.
     
           For OpenVMS savesets, the name of the compressed saveset
           file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
           kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
           saveset is copied to your system, expand the compressed
           saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
     
           For PCSI files, once the PCSI file is copied to your system,
           rename the PCSI file to kitname-dcx_axpexe.pcsi, then it can
           be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
           file will be the PCSI installation file which can be used to install
           the ECO.
     

     
    Copyright (c) Compaq Computer Corporation 2001. All rights reserved.

    OP/SYS: OpenVMS Alpha

    COMPONENT: LMF

    SOURCE: Compaq Computer Corporation

    ECO INFORMATION:

         ECO Kit Name: VMS73_LMF-V0100
                        DEC-AXPVMS-VMS73_LMF-V0100--4.PCSI
         ECO Kits Superseded by This ECO Kit: None
         ECO Kit Approximate Size: 1136 Blocks
         Kit Applies To: OpenVMS Alpha 7.3
         System/Cluster Reboot Necessary: Yes
         Rolling Re-boot Supported: No
         Installation Rating: INSTALL_3
                               
                                3 - To be installed by customers
                                    experiencing the problems corrected.

         Kit Dependencies:

           The following remedial kit(s) must be installed BEFORE
           installation of this kit:

             None
             
           In order to receive all the corrections listed in this
           kit, the following remedial kits should also be installed:

             None

    ECO KIT SUMMARY:

    An ECO kit exists for LMF on Alpha V7.3. This kit addresses the following
    problems:

    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.

         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= -
                  _$ "-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 -
                      _$ /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.
                          ___________________________________________________

                      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

    INSTALLATION NOTES:

    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.

    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

                       ******* 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.

                       ********************

    All trademarks are the property of their respective owners.

    ---