Conference azur::mcc

    
    Yes, it is a bizarre symptom.  However, I suppose it's possible that 
    the event pool got corrupted.
    
    Questions:
    
    	Is it reproducible?  
    	Have you been running dna4_evl sink without problem until now?  
    	What type of systems are bylu08 and bylu21 (I can't see it)?
    	How busy are those events generated?
    	What is your process quota?
    
    In the meantime, I am trying to find a V11 MCC system so I can try to
    reproduce this problem.   
    
    Thanks for the input.
    
    	Jean
    
    
    
    	

Hello Jean,

	Thanks for the quick answer. The two machines are both VMS machines.
The BYLU08 is standalone 3100. The BYLV21 is a 3800 with one sattelite, a
3100, as cluster member. The BYLV21 is runnin VMS 5.4-3. BYLU08 VMS version
is minimum 5.4, but I'm not sure exactly which version as I am writing this
from Digital and the machine is at a customer site.

	I only started using the mcc event logger on Monday, the 9th of
December and the problem is very reproducable, in that I have never
succeeded in having a GETEVENT directive work with out MCC giving me an
access violation. As to the number of events, it is 1. I create the event
myself by zeroing the line counters on BYLU08 and see with Reply/enable exactly
one event. There are however the general events occuring on BYLV21 such
as adjaceny down, or Downline Load failures, but they occur about
2 per minute, not very frequently.

	The process quota on the BYLV21 is, I believe, 20.

Julie Ann 

    Hello, 
    
    	Has my problem been forgotten? I realize with the field test and
    the volume of notes that you people are pretty busy, but I need to
    resolve my problem also.
    
    Thanks
    Julie Ann

Julie Ann,

	No, your problem is not forgotten.  Like you said, the tight schedule 
to release V1.2 and holidays really distracted our attention somewhat.

	I finally found a V1.1 to sink events (not easy, we all use V1.2 now ;-)
).  I tried and couldn't reproduce the acc-violation problem at all.  

	Your log showed acc-viols occurred on both event getter (in getevent)
and event putter (in sink) ends.  I have consulted this behavior with Kernel 
team regarding the possibility of such acc-violations.  The answer is that 
the event pool may have been corrupted.  For V1.1, this is possible and 
unpredicatable.  The advice I got is that you should exit and kill ALL MCC 
processes on the entire system.  Restart MCC again.

	Do you have access to V1.2 kit?  V1.2 MCC Event Manager is much
improved and more reliable.  It may be a good idea to upgrade your mcc to
V1.2.  If you decide to do so, let me know.  You will need to have some
new images to run event sink.

	Jean

    Hi Jean,
    
    	Well, it works under V1.2. 
    
    Thanks, Julie Ann