Conference azur::mcc

I believe there is a recent QAR on this problem.
See note 7 on how to check the QAR database.  

You can also enter a problem description if you do not find it
there already.

-- Erik

    Re .1                       
    I'm having similar problems:  Here's a copy of a recent
    MCC_DNA4_EVL.LOG.   Is this the same error, as I've not traced this
    problem yet?
    
$ manage/enter/presen=mcc_dna4_evl
Declared network object MCC_DNA4_EVL,28-OCT-1992 12:16:55.53
Wait for EVL link,28-OCT-1992 12:16:55.54
Connected to EVL,28-OCT-1992 12:18:16.77
Terminated mcc_dna4_evl_main,29-OCT-1992 09:54:21.43
%ERF-W-NOMSG, Message number 00089E68
  SYSTEM       job terminated at 29-OCT-1992 09:54:22.02
  Accounting information:
  Buffered I/O count:            3154         Peak working set size:    2250
  Direct I/O count:                41         Peak page file size:      7413
  Page faults:                   2966         Mounted volumes:             0
  Charged CPU time:           0 00:01:27.27   Elapsed time:     0 21:37:29.63
    
    Re.2 
    I guess the QARs are 430 or 486, but I can't access the Database at the
    moment to check theri status.

    UTLRIX V1.2.3 has a similiar problem.
    /Claudia
    

    Hi , 
    	
    	I have also the same problems . See logfile .
    	Is there a way to restart it automatically with success becaause
    	sometimes it does not reconnect to EVL and you have to stop the EVL
    	process and restart it to able the DNA4 to reconnect to the EVL .
    
    	Declared network object MCC_DNA4_EVL, 6-NOV-1992 13:17:37.40
    Wait for EVL link, 6-NOV-1992 13:17:37.41
    Connected to EVL, 6-NOV-1992 13:17:39.34
    Terminated mcc_dna4_evl_main, 8-NOV-1992 00:13:06.41
    %ERF-W-NOMSG, Message number 00089C68
      SYSTEM       job terminated at  8-NOV-1992 00:13:10.34
    
    Thanks Best regards Serge GUILBERT
    

	Sorry for the delay but I'm every time at the customer site.
    	The log is here.          
    
    	The same for EVL problems.
$
$ manage/enter/presen=mcc_dna4_evl
Declared network object MCC_DNA4_EVL, 2-NOV-1992 15:51:20.22
Wait for EVL link, 2-NOV-1992 15:51:20.23
Connected to EVL, 2-NOV-1992 15:52:11.93
Terminated mcc_dna4_evl_main, 3-NOV-1992 12:15:56.24
%ERF-W-NOMSG, Message number 00089E68
  SYSTEM       job terminated at  3-NOV-1992 12:15:57.38

  Accounting information:
  Buffered I/O count:             605         Peak working set size:    1794
  Direct I/O count:                48         Peak page file size:      7552
  Page faults:                   2358         Mounted volumes:             0
  Charged CPU time:           0 00:02:38.36   Elapsed time:     0 20:24:42.72


$!
$
$ manage/enter/presen=mcc_dna4_evl
Declared network object MCC_DNA4_EVL, 3-NOV-1992 12:20:27.87
Wait for EVL link, 3-NOV-1992 12:20:27.88
Connected to EVL, 3-NOV-1992 12:20:29.44
Terminated mcc_dna4_evl_main, 5-NOV-1992 17:29:26.48
%ERF-W-NOMSG, Message number 00089E68
  SYSTEM       job terminated at  5-NOV-1992 17:29:28.21

  Accounting information:
  Buffered I/O count:            1821         Peak working set size:    1772
  Direct I/O count:                44         Peak page file size:      7552
  Page faults:                   5426         Mounted volumes:             0
  Charged CPU time:           0 00:07:49.83   Elapsed time:     2 05:09:07.71

    
    Yes, this problem and its reply were entered in QAR 486. 
    
    mcc_dna4_evl only serves as an event monitor (sink) of the system's EVL.
    It is system EVL that initiates and maintains the network connection to 
    the sink.  EVL drops its link to event monitor for various reasons
    (unpredictably).  
     
    	If this occurs frequently, set up EVL$LOG bitset (refer to 
    DECNETVAX notes 21.5) and examine the reason in sys$manager:evl.log.    
    
    	We have tried to implement mcc_dna4_evl such a way so it stays up
    for re-connection.  It obviously did not work.  We are investigating
    other options to see if the monitor can be re-connected by EVL.
    In the meantime, please examine why the link is periodically dropped
    in your environment.  It can be environmental.
    
    	Yes, once after the sink process terminates itself, you will
    have to DISABLE and ENABLE the sink so that it makes itself known to 
    EVL again.
    
    	Please let me know what EVL.log reveals about your environment.
    
    	Thanks.
    
    	Jean
    	
    p.s.  sorry about delayed response.  I have been assigned to other
    projects.  
    

    
    add to .6.
    
    One more thing, the mcc_dna4_evl.log that you attached shows me that
    you haven't turn mcc_dna4_evl_log logical bit on.  Without setting up
    logical, the log will not collect any useful information (other than
    what you saw).  This is how:
    
    	disable the local sink monitor (mcc disable command)
    	edit mcc_common:mcc_dna4_evl.com file
    	add $define mcc_dna4_evl_log 30 (or 10 or 20) before $manage
    		command
    	enable the monitor (mcc enable command) again
    
    After awhile, you should see sys$login:mcc_dna4_evl.log start
    collecting more information (about event, about sink status..)
    
    Try this way in addition to setting up EVL$log.  We may find out what
    has happened to your environment.
    
    	Jean