Conference azur::mcc

    
    Okay, we will start with the basics; this should allow you to verify
    your set up.
    
    
    1) you must create rules from the "Rule View" in the iconic map, or by
    using the "Create domain <name> rule <name>" command.
    
    	If these are created using the "create mcc 0 alarm rule <name>" 
    	command, then you MUST have an "in domain <name>" qualifier on the
    	end of the command.
    
    	Rules that are created outside the context of a domain will not
    	cause the entity on the map to turn a color.
    
    2) When creating rules, the occurs function allows wildcards, these
    wildcards are NOT filtered based on the content of the domain. In 
    other words, if you create an occurs function on "node4 *" then it
    will fire the event every time any node4 event (that matches the event
    in the occurs function) is sinked to the node you are running on.
    
    3) When a rule fires, the notification services pull the entity name
    from the rule fired data, and attempt to turn that entity a color. If
    that entity is not register or not a part of the domain for which the
    rule was created then the rule will turn a color and not the entity.
    
    4) "Notify all" menu item turns on notification for a domain if it is
    not already. This can be turned on by default. 
    
    5) The enable and disable salience items are used to say if
    notifications should only be displayed in the notification window (pull
    up the notification application from the "Applications" menu).
    
    6) The notification windows allow you to view the current status of the
    notify requests, always check that they are in the "running" state.
    
    7) The ft kit provides the Iconic map use with the ability to use any
    of the NOTIFY command functions (V1.1 iconic map only allowed access to
    rule firing information from the map). This means that you can enter 
    the equivalent of "Notify domain <name> events="any configuration
    events" to obtain all raw event information for the entities in the
    domain specified. You can also make use of the targetting commands to
    cause the appropriate (from the users view; not the entity models)
    entity a color. Select nothing on the map and from the "Operations"
    menu choose the Assign Target command. Then "Assign target domain
    <name> event source=Node4 * remote node *, eve name="any configuration
    event", managed object="node4 * remote node #1", target entity ="Node4
    #1", target severity=warning". This command will cause all remote node
    events for that domain to be returned to the map for the remote node
    specified in the event, and with a severity of warning.
    
    -----------------
    If you still have a problem let me know.
    jill
    

    Hi Jill,
    
    Boy did DECmcc get weird the second day of the show. I followed your
    checklist and found everything to be in order. Map icons still would
    not turn colors.
    
    Late in the afternoon during yet another demo, an icon turned green,
    This icon was in the displayed map. Seizing the moment I explained to
    the customer the notion of upwards propagation of alarms to the top
    level domain. From the popup menu I selected look up and went up one
    level of domain. The icon for the domain that I just left did not turn
    color. I then double clicked on it to go back down. The icon that
    represented the node that had the alarm fire was now back to the clear
    color. Never did I clear that alarm. This was the only time during both
    days that an alarm did show up on the map.
    
    Another annoying problem is that the odd time when graphing parameters
    the work in progress window will not go away. It would become
    transparent and resist all attempt to hide it. At the end of yesterday
    I had about 8 of these guys hidden under the main map.
    
    Once yesterday afternoon I got a notification of a thread disappearing
    and the cause being an illegal instruction. 
    
    The system has been returned back to Toronto so I really can't give you
    anymore info. Just a thought. Is ft1.2-4 tested against Motif? I was
    running Ultrix 4.2a with Motif.
    
    Thanks for your help.
    
    Richard

    I didn't even think to ask you that, 
    
    NO!!! we run under decwindows. Most things run okay under Motif but
    we know that there are some gotchas, just no one around here uses it
    enough of the time to really bang on it like you would at a show. At
    DECUS we explicitly used DECwindows to avoid any potential gotchas. The
    color change stuff may well be a highly sensitive area when it comes to
    which window manager you are using.
    
    Any one else using Motif and DECmcc extensively?
    
    jill
    

>    DECUS we explicitly used DECwindows to avoid any potential gotchas. The
>    color change stuff may well be a highly sensitive area when it comes to
>    which window manager you are using.
>    
>    Any one else using Motif and DECmcc extensively?
>    

Not a problem here.  I'm using Motif and DECmcc (extensively) on my
workstation.    (VMS V5.4-3)    I got icons-a-poppin' colors everywhere w/no
problems.  

/doug

P.S. I am using DECmcc T1.2.4 

    
    as you know Doug, T1.2.4 wasn't availble when we went to DECUS.
    

...but I've slept since then.

;^)