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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

148.0. "Enrollment problem when linking with IPC shareable image" by BYBLOS::TAMER () Thu Jun 07 1990 20:07

I am trying to communicate with IPC between the Access module and the agent. I 
am linking with the IPC shareable image as you will see below. When I try to 
enroll the AM, I get the following problem:

MCC> enroll mcc$tp_am
%LIB-E-ACTIMAGE, error activating image $200$DUA18:[TAMER.MCC.PROTOTYPE.SRC]MCC$
TP_AM.EXE;82
-SYSTEM-F-NOTINSTALL, writable shareable images must be installed
%MCC-E-ENROLL_FAILED,  Enroll failed, table is not fully inserted.
MCC>

NOTE: IPCSHR.EXE is installed and started on the node.

Any clues?

Thanks in advance,
Phil

here is a snapshot of my *.opt file:
MCC$TP_AM_VECTOR.OBJ
MCC$TP_AM_OBJLIB.OLB/LIBRARY/INCLUDE=(mcc$tp_am_initialization , -
                                      mcc$tp_am_svc_entry      , -
                                      mcc$tp_am_utility        , -
                                      mcc$tp_am_validate       , -
                                      mcc$tp_am_translate      , -
                                      mcc$tp_am_communicate    , -
                                      mcc$tp_am_mgmt_entry)
sys$share:mcc$kernel_shr/share
sys$share:ipcshr/share
sys$share:vaxcrtl/share

T.RTitleUserPersonal
Name
DateLines
148.1See 134.4TOOK::GUERTINWherever you go, there you are.Fri Jun 08 1990 14:140
148.2Global data must be readonly...SMAUG::BELANGERQuality is not a mistake!Fri Jun 08 1990 14:529
    
    	This error results from the memory protection given to a global
    variable.  The only way to avoid this error is to define the global
    data as either readonly or globaldef.  Unfortunately, using either of
    these causes the compile to flag the data as being not portable.  In
    order to make this code portable, you have to do some conditional
    compilation.
    
    ~Jon.
148.3Making them static noshare did not solve itBYBLOS::TAMERFri Jun 08 1990 15:039
Matt,

I had with my IPC code a couple of variables defined as static.  Making them
static noshare or even taking out static all together did not solve it. I still
get the same problem and error messages at enrollment. The next reply will 
include my *.map file

Regards,
Phil 
148.4Global Variables were the Cultprits. Problem solved. Many thanks for .1 and .2BYBLOS::TAMERFri Jun 08 1990 16:010
148.5IPC allowed in a MM ?TENERE::DUNONPaul Dunon - Telecom Engineering - VBOTue Jun 12 1990 06:3611
In note 36.* I've been told that IPC should not be used in an access module, 
because of its AST operations. Has that changed since January ??
Or does the SYS$QIOW revectoring mechanism of MCC allow the use of IPC ??

I would like to know the official up-to-date position of MCC engineering about
the use of IPC.

Thanks in advance,

		-- Paul