OpenVMS ALPMANA01_071 Alpha V7.1__V7.1-1 SMI$SHR ECO Summary

TITLE: OpenVMS ALPMANA01_071 Alpha V7.1__V7.1-1 SMI$SHR ECO Summary
 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       The name of the compressed file will be kit_name-dcx_vaxexe
       for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
 
       Once the file is copied to your system, it can be expanded
       by typing RUN compressed_file.  The resultant file will
       be the OpenVMS saveset or PCSI installation file which
       can be used to install the ECO.
 

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

Modification Date:  16-JUN-99
Modification Type:  New Kit

PRODUCT:    OpenVMS Alpha

COMPONENT:  SMI$SHR.EXE

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  ALPMANA01_071
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  560 Blocks
     Kit Applies To:  OpenVMS Alpha V7.1, V7.1-1H1, V7.1-1H2
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_3 - To be installed on all systems running
                                       the listed versions of OpenVMS which
                                       are experiencing the problems described.
     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 SMI$SHR on OpenVMS Alpha V7.1 through V7.1-1H2. 
This kit addresses the following problems: 

Problems Addressed in the ALPMANA01_071 Kit:

  o  Make the SYSMAN security profile consistent clusterwide.

     SYSMAN security profile is supposed to be identical on all nodes
     in a cluster that use the same security environment. SYSMAN could
     use the authorize privileges from the UAF, instead of the locally
     set privileges on some nodes. 

     For example, for a cluster named CLUSTER, node NODE1 should have
     same privilege settings as another node in the cluster, NODE2. 

          SYSMAN> set env/clus

          %SYSMAN-I-ENV, current command environment:
                  Clusterwide on local cluster
                  Username SYSTEM   (*** will be used on non-local nodes)

          SYSMAN> show profile

          %SYSMAN-I-DEFDIR, default directory on node NODE2 --
          SYS$SYSROOT:[SYSMGR]
          %SYSMAN-I-DEFPRIV, process privileges on node NODE2 --
                  TMPMBX
                  OPER
                  NETMBX
          %SYSMAN-I-DEFDIR, default directory on node NODE1 --
          SYS$SYSROOT:[SYSMGR]
          %SYSMAN-I-DEFPRIV, process privileges on node NODE1 --
                  CMKRNL
                  CMEXEC
                  CMEXEC
                  SYSNAM
                  GRPNAM
                  ALLSPOOL
                  IMPERSONATE
                  DIAGNOSE
                  LOG_IO
                  GROUP
                  ACNT
                  PRMCEB
                  PRMMBX
                  PSWAPM
                  ALTPRI
                  SETPRV
                  TMPMBX
                  WORLD
                  MOUNT
                  OPER
                  EXQUOTA
                  NETMBX
                  VOLPRO
                  PHY_IO
                  BUGCHK
                  PRMGBL
                  SYSGBL
                  PFNMAP
                  SHMEM
                  SYSPRV
                  BYPASS
                  SYSLCK
                  SHARE
                  UPGRADE
                  DOWNGRADE
                  GRPPRV
                  READALL
                  IMPORT
                  AUDIT
                  SECURITY

          Images(s) Affected:

          1.  [SYSLIB]SMI$SHR.EXE


INSTALLATION NOTES:

The images in this kit will not take effect until the system is
rebooted.  If there are other nodes in the VMScluster, 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.


All trademarks are the property of their respective owners.

alpmana01_071.README
alpmana01_071.CHKSUM
alpmana01_071.CVRLET_TXT
alpmana01_071.a-dcx_axpexe
alpmana01_071.CVRLET_TXT