Conference azur::mcc

    PS: the process this was executed from had ALL privs enabled.
    <

    Well, it's been a long time since I've had to deal with the event sink.
    One thing to try. Place "set priv/all" command into your login.com. I can't
    remember if the detached process (which then runs the .com file to start
    the event sink - or that's what it did 2 years ago) gets passed the 
    parent's process privileges. If it doesn't, then the child process will
    get the privileges that are set up in your login.com. That may be
    insufficient for the MCC process.
    		Cindy
    
    
    

    
    
    Hi Cindy,
    
    Nope, still does not start up correctly:
    
    @sys$startup:MCC_STARTUP_DNA4_EVL.COM
    %PURGE-W-SEARCHFAIL, error searching for
    SYS$COMMON:[MCC]MCC_DNA4_EVL.LOG;*
    -RMS-E-FNF, file not found
    DECmcc (T1.2.4)
    
    
    Node4 30.207 Object task
    AT 14-JAN-1992 11:03:20
    
    No such entity: Node4 nyws07 Object task
                             Unknown Entity = Node4 nyws07 Object task
                                                                                    
    Node4 30.207 Object task
    AT 14-JAN-1992 11:03:23
    
    No privilege to perform directive at Node.
    
    Node4 30.207 Local Sink Monitor
    AT 14-JAN-1992 11:03:26
    
    No privilege to perform directive at Node.
    
    Node4 30.207 Local Sink Monitor
    AT 14-JAN-1992 11:03:26
    
    Specified entity in unacceptable state for directive.
    
    
    Node4 30.207 Local Sink Monitor
    AT 14-JAN-1992 11:03:29
    
    Attempt to create duplicate entity rejected.
    
    Node4 30.207 Local Sink Monitor
    AT 14-JAN-1992 11:03:30 Characteristics
    Specified entity in unacceptable state for directive.
    
    
    Node4 30.207 Outbound Stream 30.207 Remote Sink Monitor
    AT 14-JAN-1992 11:03:31
    
    Deletion completed successfully.
    
    Node4 30.207 Outbound Stream NYWS07 Remote Sink Monitor
    AT 14-JAN-1992 11:03:32
    
    Creation completed successfully.
    
    Node4 30.207 Outbound Stream NYWS07 Remote Sink Monitor
    AT 14-JAN-1992 11:03:32
    
    Pass completed successfully.
    
    Node4 30.207 Outbound Stream NYWS07 Remote Sink Monitor
    AT 14-JAN-1992 11:03:33
    
    Pass completed successfully.
    
    Node4 30.207 Outbound Stream NYWS07 Remote Sink Monitor
    AT 14-JAN-1992 11:03:33
    
    Pass completed successfully.
    
    Node4 30.207 Outbound Stream NYWS07 Remote Sink Monitor
    AT 14-JAN-1992 11:03:34
    
    Pass completed successfully.
    
    Node4 30.207 Outbound Stream NYWS07 Remote Sink Monitor
    AT 14-JAN-1992 11:03:34
    
    Pass completed successfully.
    
    Node4 30.207 Outbound Stream NYWS07 Remote Sink Monitor
    AT 14-JAN-1992 11:03:35
    
    Pass completed successfully.
    
    Node4 30.207 Local Sink Monitor
    AT 14-JAN-1992 11:03:35
    
    Internal error in DECnet Phase IV AM
    
    $

Hi Nick -
	One by one I'll attempt to explain what happened and see if we can't get
you up and running...
( 1 ) First
    $  @MCC_STARTUP_DNA4_EVL.COM
    %PURGE-W-SEARCHFAIL, error searching for
    SYS$COMMON:[SYSMGR]MCC_DNA4_EVL.LOG;*
    -RMS-E-FNF, file not found
>> the dcl command issued was:
   $PURGE MCC_DNA4_EVL.LOG/keep=10
>> So the error you received is o.k. because there are no mcc_dna4_evl.log files
   in the sys$common:[sysmgr] directory...
( 2 ) Next under MCC the following command was issued:
      DELETE node4 <os_node> object task
>>    So the following message:
    No such entity: Node4 nyws07 Object task
                             Unknown Entity = Node4 nyws07 Object task
>>    is also exceptable because the object Task does not exist on node nyws07...
( 3 ) The next commands under MCC which could not be executed would require you
      to have oper and sysprv on the node4 in this case nyws07 thst is specified
      in the <os_node> portion of the MCC_STARTUP_DNA4_EVL.COM procedure...

- hope this helped
  darryl

    I get the same problem like you and try with the set proc/priv=all
    	and does not work.
    	for the error :
    	NO PRIVILEGE TO PERFORM DIRECTIVE AT NODE.
    
    	I solved this problem in adding my account in the proxy database.
    	like:
    	UAF> add/procy mynode::MCC MCC/default
    
    	But i get always the message at the end for the command:
    	
    	ENABLE node4 0 local sink monitor
    
    	Internal error in DECnet Phase IV AM.
    
    	I am investigating this problem to find a solution.
    
    			Regards Serge

    I am experiencing exactly  the same  "Internal error in DECnet Phase IV
    AM." problem.

    Additionally, I am receiving warning messages during the create and pass 
    event directives.

    CREATE node4 peney outbound stream peney remote sink monitor class=0, -
    	event type = {0,1,2,3,4,5,6,7,8,9}
    %MCC-W-QUALUNKNOWN, qualifier is unknown: EVENT

    My system is running BMS T1.2.4, VMS 5.4-2 and DECnet Phase IV Extensions.

    Georges.

    I try to investigate more the problem and try in starting from the 
    	MCC> prompt with the command:
    
    		MCC> ENABLE NODE4 XX.XXXX LOCAL SINK MONITOR
    
    	and i get the same message :
    	Internal error in DECnet phase IV AM.
    
    	After i try in using the mode forms of MCC
    	with this command.
    		
    		MCC> Use mode Forms 
    		and after do the command ENABLE NODE4 XX.XXXX local sink monitor
	
    	and IT WORKS !!!!!!
    
    
    	I don't understand why , but it create the MCC_DNA4_EVL process.
    
    	Next step is to try if event logger works fine with the process.
    
    
    						regards Serge

Hi all,

	Sorry that I wasn't available for an immediate response.  Hope you 
don't mind that I answer all questions in one note.

	1) Internal error when you ENABLEd the local sink.

	   This is a bug, already fixed.  

	2) Privilege violation for some commands.

	   Currently, users have two options for privileged directives.  
	   For all cases, the account used must have appropriate privileges.
	   
	   The first option is to specify explicit access, in MCC terms, 
	   you need to pass <by user, by pass> qualifiers.  The second 
	   option is to set a proxy to an account (if the proxy is not a 
	   default proxy, you have to specify the <by user> qualifier).

	   Specifically for enabling the local sink monitor, additional 
	   DEFAULT privileges (DETACH,SYSNAM,TMPMX,NETMBX) are required.

	3) Unacceptable state message

	   You will get this message when enabling the local sink monitor if
	   the local sink monitor STATE is non-existent or ON.  This
	   command will only work when the local sink monitor state iS OFF.

	Thank you for your input.

	Jean

    for 1) Internal error when you ENABLEd the local sink.
    
    
    		Can we have the fix ??
    
    					thanks Serge

We are considering when to make an internal update to the field test
kit available.  It will contain the fix for this problem, in addition
to others.

Unfortunately, "already fixed" just means that the code has been
changed to correct the bug, not that there is a newer kit with the
change included.  We do not have the resources available to support
distributing each bugfix to a management module during field test.

-- Erik

    Thank you Erik for the answer 
    
    				Serge