Conference azur::mcc

    Greetings,
    
    I have a VAXstation running VMS V5.5-1 and DECnet/OSI with DECmcc
    V1.3.0.  I need to be able to send events from a PhaseIV node into
    DECmcc, but am having trouble doing so.
    
    I can get a link from the PhaseIV node to the EVL process on the DECmcc
    node, and also see the events coming up in the OPCOM process as
    formatted NICE data, but cannot get a connection through to the
    MCC_DNA5_EVL pocess.
    
    VCan anyone give any ideas ?
    
    Thanks in advance.
    
    
    Reece Boucher

Reece,
    
    You aren't receiving the PhaseIV Relayed events because you haven't
created a local outbound stream to deliver them to the MCC sink.

The way phaseIV relay works is the DECnet PhaseIV node sends an event
to your phaseV node.  It doesn't have a concept of how to deliver the
event to a specific *task* on the node like PhaseV does, it simply 
delivers the event to the EVD task on that node.  The system EVD there
looks at it and sees that it's a phaseIV event and "encapsulates" it
with phaseV event information, and sends the event down all outbound streams
which don't have it explicitly filtered out.

Here is where you need to do some work.  You now need to tell the EVD
that your MCC EVL process is interested in these events by creating
a local outbound stream to your MCC EVL sink process.  The DNA5 EVL will
then receive the event, see that it's a phaseIV relayed event, strip off
the encapsulation, feed it through the phaseIV event decode routines,
and post the result to MCC as a phaseIV event.

In the following example I'm using LAKE as the local nodename and MCC_LAKE
as the name of the outbound stream.  You can use whatever is appropriate
for your setup.

MCC> create node LAKE event dispatcher outbound stream MCC_LAKE

MCC> set node LAKE event dispatcher outbound stream MCC_LAKE -
_MCC> sink node DEC:.tay.lake

MCC> set node LAKE event dispatcher outbound stream MCC_LAKE -
_MCC> sink end user name = MCC_EVL_SINK

MCC> enable node LAKE event dispatcher outbound stream MCC_LAKE


	-- John

Hi Folks,

I have the same problem as Reece. But if I do
mcc>crea node emd:.grd.bern.grdnet eve disp out strea mcc_grdnet

I got the following error message
You are not authorized to perform this Directive
I am full privileged and have full access to the namespace.

But it is possible to do the same with ncl.
ncl>crea eve disp out strea mcc_grdnet 

Can someone provide me with a solution?

Regards Fred

    Is this on a VMS node?  Have you granted the account you're running
    from  the NET$xxx identifiers as required for net management?
    Read the VMS DECnet/OSI manuals for more details.  You'll probably
    need NET$EXAMINE and NET$MANAGE.  As I rememeber there are
    
    NET$EXAMINE, NET$MANAGE, NET$SECURITY, NET$REGISTERDNSOBJECT
    
    identifiers added in VMS for this purpose.
    
    The reason NCL works and MCC doesn't is that NCL is very tied to
    the internal API's of VMS DECnet so it doesn't have to make a request
    through the net for its requests.  It uses the "back door" if it's
    a local request and only system priv's come into play.
    
    MCC on the other hand always uses the net so the request is given
    to the CML server process which checks for these privs.
    That's my guess what's going on.
    
    John

    Hi John,
    
    It is a VMS system with V. 5.5-2, DECnet/OSI V 5.6A and DECmcc V.1.3.0
    I have all Privs an i had the following Identifiers NET$EXAMINE,
    NET$MANAGE, NET$SECURITY. After your reply i added
    NET$REGISTERDNSOBJECT as well. Still i get the same error message.
    mcc>crea node .grd.bern.grdnet eve disp out str mcc_grdnet
    
    Node EMD:.grd.bern.grdnet Event Dispatcher Outbound Stream mcc_grdnet
    AT  8-OCT-1993 11:33:33
    
    You are not authorized to perform this Directive
    
    
    Regards Fred

    I give.  Try adding a decnet proxy for that account in authorize.
    Check the file protection on CML.EXE, make sure it's W:RE
    also make sure the CML$SERVER account has NET$EXAMINE in the
    authorization file.