Australia - Updated: 24-SEP-2003
hp.com home products and services support and drivers solutions how to buy
» contact hp
hp.com home hp OpenVMS ECOs

IMPORTANT NOTICE

The online distribution of OpenVMS and related product patches is being migrated to the HP ITRC (Information Technology Resource Center) patch distribution site. The new ITRC patch server will allow OpenVMS customers to take advantage of many enhanced features for patch searching and distribution.

Beginning August 1, 2003, OpenVMS and related Layered Product, publicly available patches will be available from the HP ITRC web site at

http://itrc.hp.com/service/patch/mainPage.do

The same patches will still be available from the existing patch server in Colorado Springs (http://www.support.compaq.com/patches/) through the end of October 2003, to give customers sufficient time to update their bookmarks and make the transition to the HP ITRC web site.

ECO kits will also be available by raw FTP from (ftp://ftp.itrc.hp.com/).

PLEASE UPDATE YOUR BOOKMARKS AND REGISTER ON THE NEW SITE NOW

Note: if you're having trouble connecting to the ITRC site, please delete any cookies for "itrc.hp.com" from your browser and try again. Report any difficulties with or suggestions to MrVMS

» Sydney CSC home page

Navigation
» ECOinfo main index
» Search ECOs
» Search FTP site
» Browse FTP site

ECO Indexes
» Chronological Index
» Indexed by Version
» Indexed by Rating
» Alpha Indexed by Name
» VAX Indexed by Name
» On Hold List

Associated Links
» OpenVMS Home Page
» OpenVMS News
» DIA/WIS Web Service

Feedback
» mail to CSC
.
Sydney Customer Support Centre OpenVMS ECO information
    Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)

ALPMANA03_062 (Alpha V6.2 SYSMAN/SMISERVER) ECO Summary

To obtain this kit please call the Customer Support Centre or use the FTP site

Search for this ECO kit and dependencies
Search the Compaq FTP web site this kit (exact match)
Search the Compaq FTP web site this or related ECOs

    
      
    
      
    Copyright (c) Compaq Computer Corporation 2001.  All rights reserved.
    
    New Kit Date     :  07-FEB-2001
    Modification Date:  Not Applicable
    Modification Type:  Updated Kit  Supersedes ALPMANA02_062
    
    
    PRODUCT:     OpenVMS Alpha
    
    COMPONENTS:  SMISERVER.EXE
                 SMI$OBJSHR.EXE
                 SMI$SHR.EXE
                 STARTUP.COM
                 SYSMAN.EXE
    
    SOURCE:      Compaq Computer Corporation
    
    ECO INFORMATION:
    
         ECO Kit Name:  ALPMANA03_062
         ECO Kits Superseded by This ECO Kit:  ALPMANA02_062
         ECO Kit Approximate Size:  1710
         Kit Applies To:  OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3
         System/Cluster Reboot Necessary:  No
         Rolling Re-boot Supported:  Information not available
         Installation Rating:  INSTALL_2
                               To  be  installed  by   all  customers  using  the
                               following feature(s):
    
                               SYSMAN.
    
         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 SYSMAN and STARTUP on OpenVMS Alpha V6.2.  This kit
    addresses the following problems:
    
    PROBLEMS ADDRESSED IN ALPMANA03_062 KIT:
    
      o  The SYSMAN security profile is supposed to be identical on all
         nodes  in  a  cluster that uses the same security environment.
         In  some  instances,  however,  SYSMAN  uses  the   authorized
         privileges  from the UAF instead of the locally set privileges
         on some nodes.
    
         This problem was not completely fixed by kit ALPMANA02_062.
    
            Images Affected:  [SYSLIB]SMI$SHR.EXE
    
    
    Problems Addressed in the ALPMANA02_062 Kit:
    
      o  Make SYSMAN security profile consistent clusterwide.
    
         The SYSMAN security profile is supposed to be identical on all nodes
         in a cluster that use the same security environment. However, 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 the
         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:
    
           -  [SYSLIB]SMI$SHR.EXE
    
    
    Problems Addressed in the ALPMANA02_070 Kit for OpenVMS Alpha V6.2,
    V6.2-1H1, V6.2-1H2, and V6.2-1H3:
    
      o  A crash in STARTUP.COM may occur on standalone OpenVMS Alpha
         V6.2 nodes during the IOGEN section of the SYSMAN startup or
         during STARTNET.COM.  One of the symptoms of this crash is
         corruption in the System Page Table Entry (SPTE) free list.
    
         This problem is corrected in OpenVMS Alpha V7.0.
    
      o  SYSMAN 'DO' commands that result in very long output records
         result in errors similar to the following:
    
           -RMS-F-SYS, QIO system service request failed
           -SYSTEM-F-MBTOOSML, mailbox is too small for request
    
         There may be some SYSMAN truncation errors also.
    
      o  The SYSMAN 'PARAM SET' command, when executed on a cluster,
         would return with an extraneous NOMORENODE error message.
    
      o  With the SYSMAN 'DO' command, certain DCL commands that do not
         have output (e.g., SYSMAN> DO DEFINE XXX YYY) would take at
         least 10 seconds/node to complete.
    
    
    Problems Addressed in the ALPMANA01_070 Kit for OpenVMS Alpha V6.2,
    V6.2-1H1, V6.2-1H2, V6.2-1H3:
    
      o  SYSMAN 'DO' commands that result in very long output records
         result in errors similar to the following:
    
           -RMS-F-SYS, QIO system service request failed
           -SYSTEM-F-MBTOOSML, mailbox is too small for request
    
         There may be some SYSMAN truncation errors also.
    
      o  The SYSMAN 'PARAM SET' command, when executed on a cluster,
         would return with an extraneous NOMORENODE error message.
    
      o  With the SYSMAN 'DO' command, certain DCL commands that do not
         have output (e.g., SYSMAN> DO DEFINE XXX YYY) would take at
         least 10 seconds/node to complete.
    
    
    Problems Addressed in the ALPMANA01_062 Kit:
    
      o  SYSMAN accommodates the use of a ! character at the beginning
         of its command line.  All characters subsequent to the ! are
         ignored and processing is passed to the next SYSMAN> prompt.
    
         In OpenVMS V6.2, a regression in behavior occurred causing a !
         character at the beginning of a SYSMAN command line to return
         the following warning:
    
           %CLI-W-NOCOMD, no command on line -  reenter with alphabetic
                          first character
    
      o  OpenVMS Alpha V6.2 systems can crash due to corrupt system
         page table entries (SPTE).
    
         This problem is corrected in OpenVMS Alpha V7.0
    
    
    RELATED ARTICLES:
    
    Detailed articles describing the problems listed above may exist in the
    OPENVMS database.  To view these articles, open the appropriate product
    database and perform a query using either of the following search strings:
    'ALPMANA03_062' or 'ALPMANA'.
    
    
    ECO KIT ORDERING INSTRUCTIONS:
    
    If after an evaluation you wish to obtain this kit, request it
    electronically using the appropriate Advanced Electronic Services
    (AES) Service Tool.  If you are not familiar with how to request
    kits electronically, open the DIA, WIS or DSNLINK database and
    review the article entitled:
    
         [AES] How To Electronically Request ECO Kits Using Service Tools
    
    
    INSTALLATION NOTES:
    
    No reboot is necessary after successful installation of the kit.
    
    Install this kit with the VMSINSTAL utility  by  logging  into  the
    SYSTEM account, and typing the following at the DCL prompt:
    
    @SYS$UPDATE:VMSINSTAL ALPMANA03_062 [location of the saveset]
    
    The saveset location may be a tape drive, CD, or a  disk  directory
    that contains the kit saveset.
    
      
      ==========================================================================
      |                     Table of Kit Image Information                     |
      +----------------------------+----------+-----------------+--------------+
      |                            | Overall  | Image File      | Image Link   |
      | Image Name                 | Checksum | Identification  | Date/Time    |
      +----------------------------+----------+-----------------+--------------+
      | SMI$OBJSHR.EXE             | 15580A2E | X-40A1A2A2      | 23-OCT-2000  |
      |                                       |                 | 22:45:55.62  |
      +----------------------------+----------+-----------------+--------------+
      | SMI$SHR.EXE                | B8092E3C | X-3             | 23-OCT-2000  |
      |                                       |                 | 22:43:24.10  |
      +----------------------------+----------+-----------------+--------------+
      | SMISERVER.EXE              | 1953B5A2 | X-13            | 23-OCT-2000  |
      |                                       |                 | 22:50:14.46  |
      +----------------------------+----------+-----------------+--------------+
      | SYSMAN.EXE                 | DE789773 | X-19            | 23-OCT-2000  |
      |                                       |                 | 22:48:46.45  |
      +----------------------------+----------+-----------------+--------------+
    
privacy statement using this site means you accept its terms feedback to the webmaster
VMS rules VMS rocks OpenVMS rules OpenVMS rocks