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

Conference vaxaxp::alphanotes

Title:Alpha Support Conference
Notice:This is a new Alphanotes, please read note 2.2
Moderator:VAXAXP::BERNARDO
Created:Thu Jan 02 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:128
Total number of notes:617

124.0. "Shmnotcnct, shared memory not connected" by TAINO::RFONSECA () Tue Jun 03 1997 11:44

    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
124.1Probably a bad logical name definitionWIBBIN::NOYCEPulling weeds, pickin' stonesTue Jun 03 1997 12:0011
The "shared memory" this message refers to is the "MA780" memory
that you used to be able to use to connect several VAX-11/780 systems
together.  You definitely don't have any of it.

Most likely you have a logical name whose translation has a colon in
it.  When your application tries to use a global section, mailbox, or
common event flag cluster, the ":" indicates that you want the thing
to be in MA780 memory, to be shared among several systems.  You need
to track down where the application came up with a name containing ":".
Try looking for differences in logical names between the system that
fails and the ones that work.