Conference azur::mcc

In your MSL, you have to support a GETEVENT directive 
which describe what parameters or attributes you have to
pass to DECmcc using something call a Event sink (doing 
the mcc_event_put fonction). you have to have also a C
program that support the GETEVENT directive to be able to
generate a mcc_event_get that will wait for a specific 
event.

I think DECmcc provide some examples with the toolkit in
the mcc_examples directory.


Hope this help

regards

Francois

.1 doesn't really answer my question I'm afraid.

Let me re-state my problem.

My question is :-
After having installed V1.3 of DECmcc on node A say, how do I enable DECmcc to be able
to see/display/filter etc. events of any entity on nodes other than (and including)
node A ?

(By entities I am talking about session control, osi transport and our own entity in 
particular. By  events are mean ones which are defined with the entity's MSL which are
registered with the dictionary. )

Background :-
=============
Whilst reading the SRM section 5 it describes the mechanics behind how events are seen
in MCC which is basically what I want to get working.

It appears that I have to get hold of Software B which communicates with the event sink
and then transmits the received information on to the event manager. I have seen in the
mcc_examples directory MCC_EXAMPLE__GETEVENT.C which I assume is such a program. Is this
correct and if so how do I use it? Is there any documentation on these examples?

What else is also required to answer the above question?

How are customers instructed on how to get this working?


		Hoping someone can help.

				Thanks

					Adrian

    Adrian,  I admit that the documentation in this area is somewhat
    lacking and we're planning to spruce that up in the future.
    
    However, have you read the section in the DECnet/OSI Use Manual?
    (I think in the Event Dispatcher section; my books are packed for my
    office move).  I believe it's in the last part of that secion that
    gives examples of how to do this.  I also placed some info in the
    release notes.
    
    There are also several notes in this file explaning this in further
    detail.  Perhaps note 4301.12 would be helpful.
    
    John

I now have events working in the command line version of MCC using the
getevent directive. My DECmcc is configured to use the local MIR.

However in the mcc_iconic_map version whilst trying to setup notifications
I consistently get in the "NOTIFICATION: Create Notify Request window the following error�

No Matches found for entities or rules requested. in a window headed :-

Error attempting to create Notify Request for domain LOCAL_NS:.x500.

------------
In filling in the input to the "Create Notify Window" I have tried all possible input I
can think of but no luck. 


What is the problem with this? Anybody got any ideas?

		Adrian.

>No Matches found for entities or rules requested. in a window headed :-

Could it be that there is no entity of the specified class in this domain tree?
Just a thought....

*Robert

More information on the problem in .4 as I haven't been able to solve this one.

I have DECmcc V1.3 running on ULTRIX using the LOCAL MIR.

When I try and create notifications using the iconic map what do I add in the 
Create Notify Request window in the Entity List box? The Local MIR is named LOCAL_NS:.
but the event comes from DEC:.reo.node etc. If I enter "node DEC:.reo.node" it returns

No matches found for entities or rules requested.

I have tried wildcard ie "node *" but this doesn't match as I assume it is looking for the
Local MIR namespace LOCAL_NS.

BTW. getevent node DEC:.reo.node entity any events from mcc_fcl works fine.

	Any help greatly accepted.

			Adrian

Anyone able to help?

Question again:
===============
I have MCC V1.3 configured on ULTRIX to use the LOCAL MIR. Events which it receives from
other nodes come in as a DNS representation ie DEC:.reo.node. However I am unable to
add this DNS represenatation in the
	Create Notify Request window in the Entity List box 
as I get 
	No matches found for entities or rules requested.

How do I get this to work?

			Adrian

>I have MCC V1.3 configured on ULTRIX to use the LOCAL MIR. Events which it receives from
>other nodes come in as a DNS representation ie DEC:.reo.node. 

Hi Adrian,

I have not tried this yet (just found out about it) but try registering the
node as LOCAL_NS:.reo.node... Then apply this to the NOTIFY command:

node .reo.node

I have heard mcc will drop the NS from the event and actually display it on the
map, seems to be worth the try.

best regards,
brad...

Brad,

Thanks for your response. The node names used below are made up ones, from the original.

>>try registering the node as LOCAL_NS:.reo.node... Then apply this to the NOTIFY command:
>>
>>node .reo.node
I have already tried this ie in the Create Notify Request window

DOMAIN		LOCAL_NS:.x500
ENTITY LIST	node .reo.nodeinquestion
EVENTS		any events

Apply this gives :-
No matches found for entities or rules requested.

As already stated the command line getevent works as below :-

MCC> getevent node DEC:.reo.nodeinquestion any events, for duration 01:00:00.00

Node DEC:.reo.notinquestion
AT 1993-05-20-10:23:43.004 Any Event

Successfully received events:
Event: Renamed

                               Old Name = DEC:.reo.notinquestion
                               New Name = DEC:.reo.another
                                                               

Notice that the event comes from DEC:.reo.nodeinquestion etc. This appears to be the only 
node specification that will work ie DEC:.reo... rather than LOCAL_NS:.x500... etc.

I assume this configuration is supposed to work?

			Thanks


				Adrian

>I have already tried this ie in the Create Notify Request window

>DOMAIN		LOCAL_NS:.x500
>ENTITY LIST	node .reo.nodeinquestion
>EVENTS		any events

>Apply this gives :-
>No matches found for entities or rules requested.

bummer...

>As already stated the command line getevent works as below :-
>
>MCC> getevent node DEC:.reo.nodeinquestion any events, for duration 01:00:00.00

Adrian, I knew the above worked because I had gotten this running. My problem
was I was trying to TARGET the event. This actually worked using private dns
but broke when I went to LOCAL_NS. A couple of people have told me they have
what you (and me) want to do working unless I have misunderstood something. I
will give this a try on my own system and try to work it out and let you know.
The only other suggestion I have is to look for case sensitivity issues. Do a

DIR NODE .reo.nodeinquestion

Make sure the registered value is the same value as from the event and the
notify request. The case should be the same for ***all three*** to be safe.

best regards,
brad...

I am not sure whether this is relevant but :-

MCC> dir node LOCAL_NS:.nodeinquestion

Node LOCAL_NS:.nodeinquestion
AT 1993-05-20-14:30:52.987

Directory successful.

.......

works ok although the true domain name is LOCAL_NS:.x500.nodeinquestion. This gives :-

MCC> dir node LOCAL_NS:.x500.nodeinquestion

Node LOCAL_NS:.x500.nodeinquestion
AT 1993-05-20-14:31:53.901

The entity Node LOCAL_NS:.x500.nodeinquestion is not registered
                  Not Registered Entity = Node LOCAL_NS:.x500.nodeinquestion

>>I will give this a try on my own system and try to work it out and let you know.
Thanks Brad.

		Adrian

Hi Adrian,

Success...

> MCC> dir node LOCAL_NS:.nodeinquestion

> MCC> dir node LOCAL_NS:.x500.nodeinquestion

Your directory commands look fine. Don't confuse map hierarchies with entity 
names, they are not related.

I'm not sure where your problem is but this is what I got to work.

Node name=DEC:.lkg.node !seen by issueing a SHOW IDENTIFIERS command to entity

mcc registered name= LOCAL_NS:.lkg.node !seen by mcc DIR command on entity

notify domain x entity list=(node .lkg.node x25 prot dte *),entity list=(dte up,
                             dte down) !no severity, use targets to get colors

targets:

domain x
entity=node .lkg.node x25 prot dte *
event=dte down
severity=critical

domain x
entity=node .lkg.node x25 prot dte *
event=dte up
severity=clear

When I had the node registered as LOCAL_NS:.node I could find no combination
which worked for LOCAL_NS. When using DECdns (private) I was able to target 
from DEC:.lkg.node to LOCAL_NS:.everdy but this broke when I changed 
repositories to LOCAL. Note that the "CASE" of all the names are similar.

best regards,
brad...

    better late then never.
    
    the notify command expects the enttiy spec returned on the getevent
    to match the entity spec you get when you do the directory domain
    member all characteristics command. If they don't match you won';t
    see the events through the notify command (documented in the
    notification fm MRM).
    
    jill