Conference azur::mcc

    I think this is same kind of problem, with EVL startup procedure too.
    Somethink to do with VMS 5.5.  
    
    Either use the user, password       or
    set a proxy account on the MCC system           or
    just use NCP command and define the object and number and set it
    
    I use the last 2, password do appear anywhere.
    Hope it helps.
    
    Raj
    Just another MCC user
    Singapore

Hi there,

I tried creating the object in NCP as suggested, but when I now try to enable
the sink I get the following error:

MCC> enable mcc 0 collection_am sink decnet

MCC 0 COLLECTION_AM SINK DECnet
AT  4-AUG-1992 16:07:45

The requested operation cannot be completed
                  Entity Existence Info = Entity Existence Cannot Be Determined,
                      MCC Routine Error = %MCC-I-NOEVENTREQ, event not
                                          forwarded; no requests outstanding

Has anyone seen this before ??

Cheers,

Gary.

    Hi -
    	The command sequence for starting up the collector sink
    	is:
    	MCC> enable mcc 0 coll sink decnet
    	Sorry create will not work in this instance...
    
    
    
    
    
    	Thanks...
    - darryl

    Hi (.2) -
     	I haven't seen this one yet.
        You don't need to create the object ahead of time.
        So you can delete it if you have created it.
        Now execute the following:
    	MCC> enroll mcc_collection_am
    	MCC> disable mcc 0 coll sink decnet
     	MCC> enable mcc 0 coll sink decnet
     	MCC> show show mcc 0 coll all attr
        MCC> test mcc 0 coll
    
    	This should be it...
    
    	Any problems contact me at:
        took::d_ball or kitfox::ball
        226-5345...
    
    
    
    
    
    Thanks...
    - darryl
    

You need to make sure that the DEFAULT privs for the
account that's starting up the EVC sink are sufficient.
(I forget the priv list...)  

Most folk simply have SETPRV turned on and think that'll
be sufficient; It's not.

/doug

What privileges is required for enabling the collector_am sink?

You certainly don't get it started with only TMPMBX and NETMBX.

Bj�rn Olav Haugom

A quick code inspection reveals that you need NETMBX, TMPMX, SYSNAM and
DETACH to start the sink.  This makes sense, since you have to actually
create a detached process (the sink process) and create a named DECnet
object as part of the sink creation process.

/doug

>                        -< NETMBX,TMPMBX,SYSNAM,DETACH >-
>
>A quick code inspection reveals that you need NETMBX, TMPMX, SYSNAM and
>DETACH to start the sink.  This makes sense, since you have to actually
>create a detached process (the sink process) and create a named DECnet
>object as part of the sink creation process.

I found the answer in the Alarms and Notification guide on page 8-8 in the Data
Collector AM chapter. You also need the SYSPRV privilege in addition to 
NETMBX,TMPMBX,SYSNAM,DETACH.

Bj�rn olav

I don't mean to sound argumentative, but the Collector AM code *only*
checks for the 4 privs I listed...   Just to be sure I also tested this by
enabling/disabling & sending events to the sink (UDPIP and DECNET) from an
account *only* those privs enabled (default and authorized) and it worked
fine.  This was for SSB V1.3.0.

There's no sense enabling more privs than necessary...

/doug

> There's no sense enabling more privs than necessary...

I totally agree. With SYSPRV your able to damage a whole lot more than without.

Bj�rn Olav