Conference azur::mcc

    If the state is ON-CONNECTED then the EVD and EVL are communicating.
    
    Try this simple test.  In FCL:  MCC> getevent node * event dispatcher
    Then in another window, MCC> test node <decnis> event dispatcher
    
    If the getevent wakes up then I suspect you have a syntax problem
    with either your getevent or notification.  You didn't mention anything
    about how you're trying to display the event in MCC.

Hi,


Thanks for that, it worked. I'm using notification services and have created 
a notification which looks for node * any event and i'm expecting something to
appear in the notification window. Notification has been enabled for that domain
and i'm turning the routing circuit on one of my hdlc links off.

Bipin.

Hi,


More info, the getevent from FCL has started to work, however it still isn't 
appearing in the notification window and everything is enabled.


Bipin

    hi Bipin,
    
    it looks like you configured your phase v node to use the local naming
    option.  by chance, is your phase V node name UPPERCASE?
    
    and are you using the LOCAL MIR in DECmcc versus DNS?
    
    if you answer yes to both these questions, then the problem you are
    seeing has to do with case sensitivity in notification.  we are aware
    of the problem, and working on it.  to work around this, use DNS as 
    your DECmcc namespace.
    
    thanks,
    -s

Hi,


>    option.  by chance, is your phase V node name UPPERCASE?

The node is registered in lower case, however the event will come in uppercase.
    
>    and are you using the LOCAL MIR in DECmcc versus DNS?

I am using the local naming option.

Could I de-register the node and enter it again using uppercase.

Bipin.
    

Hi,


Something else i've noticed is that if you set up the following getevent

MCC> getevent node * any event

Then i would this to fire on any node * event, it doesn't.

If you then do

MCC> getevent node * routing circ * any event

That works. Now i wrong in my assumption. I have checked all the filters and 
it pass all events, any ideas.

Bipin

    hello Bipin,
    
    re .5 -
    
    Because your node has been configured its name in UPPERCASE, its
    events are generated using UPPERCASE.
    
    if you have selected to use the MIR in DECmcc instead of DNS, all nodes 
    are registered in lower case.
    
    This is where the problem lies.  An event is received by a getevent
    thread in notification and compared to a list of node instances kept by
    the FM in response to the notify request.  The list of instances is 
    read from the MIR where the names are stored in lowercase; the event
    source is received in UPPERCASE.  Because of this case difference, the 
    notification FM will not see that this event is of interest.
    
    we have a fix for this problem, but i do not know how it will be
    released.
    
    i will post an answer as soon as i find out.
    
    re .6
    
    i need to know more about your setup as to why you aren't receiving
    node events.  can you please post the node event disp outb stream
    characteristics?  what event is firing that you are not able to receive
    using the GETEVENT request?
    
    -s

Hi,

outbound stream characteristics as requested:

Node uvohi2 Event Dispatcher Outbound Stream uvohi2_events
at 1993-03-18-08:22:02.310+00:00Iinf

Characteristics

    Template                          = ""
    Connect Retry Timer               = 120
    Disconnect Timer                  = 0
    Specific Filter                   = 
       {
          [
          EventCode = (Node LOCAL_NS:.UVO.UVOHI2 Event Dispatcher Outbound 
Stream uvohi2_events, Events Lost) ,
          Filter Action = Pass
          ] ,
          [
          EventCode = (Node LOCAL_NS:.UVO.UVOHI2 Event Dispatcher Outbound 
Stream uvohi2_events, Enable) ,
          Filter Action = Pass
          ] ,
          [
          EventCode = (Node LOCAL_NS:.UVO.UVOHI2 Event Dispatcher Outbound 
Stream uvohi2_events, Disable) ,
          Filter Action = Pass
          ] ,
          [
          EventCode = (Node LOCAL_NS:.UVO.UVOHI2 Event Dispatcher Outbound 
Stream uvohi2_events, Disconnect) ,
          Filter Action = Pass
          ] ,
          [
          EventCode = (Node LOCAL_NS:.UVO.UVOHI2 Event Dispatcher Outbound 
Stream uvohi2_events, Shutdown) ,
          Filter Action = Pass
          ] ,
          [
          EventCode = (Node LOCAL_NS:.UVO.UVOHI2 Event Dispatcher Outbound 
Stream uvohi2_events, Change Confidence) ,
          Filter Action = Pass
          ] ,
          [
          EventCode = (Node LOCAL_NS:.UVO.UVOHI2 Event Dispatcher Outbound 
Stream uvohi2_events, Change Filter) ,
          Filter Action = Pass
          ]
       }
    Global Filter                     = 
       {
          [
          EventCode = ((Node, Event Dispatcher, Outbound Stream), Events Lost) ,
          Filter Action = Block
          ] ,
          [
          EventCode = ((Node, Event Dispatcher, Outbound Stream), Enable) ,
          Filter Action = Block
          ] ,
          [
          EventCode = ((Node, Event Dispatcher, Outbound Stream), Disable) ,
          Filter Action = Block
          ] ,
          [
          EventCode = ((Node, Event Dispatcher, Outbound Stream), Disconnect) ,
          Filter Action = Block
          ] ,
          [
          EventCode = ((Node, Event Dispatcher, Outbound Stream), Shutdown) ,
          Filter Action = Block
          ] ,
          [
          EventCode = ((Node, Event Dispatcher, Outbound Stream), Change 
Confidence) ,
          Filter Action = Block
          ] ,
          [
          EventCode = ((Node, Event Dispatcher, Outbound Stream), Change 
Filter) ,
          Filter Action = Block
          ]
       }
    Catch All Filter                  = Pass
    Connect Timer Enabled             = True
    Sink Object                       = 0:.
    Sink Node                         = 0:.
    Sink End User                     = number = 82
    Sink Address                      = 
       {
          (
          [ DNA_CMIP-MICE ] ,
          [ DNA_SessionControlV3 , name = MCC_EVL_SINK ] ,
          [ DNA_NSP ] ,
          [ DNA_OSInetwork , 49::00-0D:AA-00-04-00-79-34:20 (LOCAL:.UVO.UVOCLU)]
          )
       }

What i am doing is disabling and enabling a routing circuit. If the getevent
has the following syntax:

getevent node * routing circuit * any events - that works, however if it is

getevent node * any event - it doesn't.

As a side issue i've also set up an occurs rule based on the same thing and i
can see the events appearing in the notification services window, however it
doesn't change the colour of the icon (i'm still working on this). But the fact 
that i'm receiving messages in the notification window, sort of implies that 
the alarms fm is doing something different.

I hope this helps.

Bipin.

    Getevent works differntly from Notify.  When you use Getevent,
    you specify *exactly* what group of events you want to receive.
    So, Getevent NODE *  will *only* trigger on NODE events, not any
    of the children of node.  Notify is a little different in that if
    the global is wildcarded it implies *the global and all children*.

Hi,

>    Getevent works differntly from Notify.  When you use Getevent,
>    you specify *exactly* what group of events you want to receive.
>    So, Getevent NODE *  will *only* trigger on NODE events, not any
>    of the children of node.  Notify is a little different in that if
>    the global is wildcarded it implies *the global and all children*.

Thats handy to know. However, i'm assuming it isn't documented anywhere and so
most people would assume that by creating a notify request all your effectively
doing is issuing a getevent.

Bipin.

In node 4673 a fix for the uppercase/lowercase problem with 
iconic map notifications was proposed.

Problem :	using local MIR
		GETEVENT is working for the NODE ... events
		Creating events with IM-PM is useless.

Where is the fix ??

rgds Richard Hainzl

    Hello,
    
    Does anyone know if the fix mentioned for the case sensitivity problem
    when useing the local nameing option mentioned earlier is available.
    
    "4673.7 
    TOOK::S_KO "Hoot mon!"
    
    we have a fix for this problem, but i do not know how it will be
        released.
    
        i will post an answer as soon as i find out."
    
    A pointer would be appreciated.
    
    
    Jon
    

    to the best of my knowledge this fix has not been released. It was
    written for inclusion in "V1.4" which we know has not been released.
    You might want to submit a CLD to get a copy of the changes.

HI,

Is the fix to this problem in the 1.4 FT kit (for VMS) recently announced?

Rgds,
Graham

Hi,

Unfortunately no. This problem is not yet solved.

Regards,
	Philippe