[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

678.0. "Shmnotcnct, shared memory not connected" by TAINO::RFONSECA () Tue Jun 03 1997 10:28

    Customer running OpenVMS 6.2-1h3 on a AlphaServer 2100.  They are 
    currently converting their VAX applications to Alpha.  Yesterday the
    Alpha was rebooted because some power problems and today they are
    receiving the following message while accessing the online screens:
    
    	system-f-SHMNOTCNCT
    
    Whith the help/message I was able to obtain additional information but
    it doesn;t make much sense to me.  Can somebody provide a clear
    explanation on this situation ?  Below is the info from the
    help/message:
    
    SHMNOTCNCT,  shared memory not connected
    
      Facility:     SYSTEM, System Services
    
      Explanation:  The shared memory specified (that is, that part of the
                    name to the left of the colon [:]) is not connected to 
                    this processor. This error also occurs when colons are
                    inadvertently placed in common event flag cluster, 
                    mailbox, or global section names.
    
      User Action:  Connect the shared memory.
    
    P.S. - This behavior is presented by most of the code.  The same code
           is running on other AXP boxes witht problems.
    
T.RTitleUserPersonal
Name
DateLines
678.1Probably bogus...GIDDAY::GILLINGSa crucible of informative mistakesTue Jun 03 1997 21:026
  The message is specific to an ancient form of shared memory used on
  VAX 780s. The most likely reason you're seeing it on any modern system is
  a bogus status code. The status value is 829 (hex 33D). Most likely some
  program or function is leaving that value in R0 and it's being interpreted
  as a status code.
						John Gillings, Sydney CSC
678.2ACISS2::LENNIGDave (N8JCX), MIG, @CYOTue Jun 03 1997 22:014
    I wonder how much of this 'ancient form of shared memory' logic is 
    going to get a revival with Galaxies. The 782's sharing of memory
    between two processors running seperate copies of the OS was the
    first thing that came to mind when I started reading about it...
678.3we took a lookEVMS::GRANTWed Jun 04 1997 09:446
    Not on the topic of the base note, but.....
    
    We looked at the VAX shared memory code and documentation during our
    Galaxy investigation. The code may not reappear but it gave us food
    for thought.