[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

2701.0. "Targetting and Notification via Iconic Map" by MERIDN::ATTERBERRY () Mon Apr 06 1992 21:15

    Hi,
    
    DECmcc T1.2.4
    TSAM V1.0
    
    Question 1:
                                                                  
    I've been playing with Targetting and the Iconic Map.  It seems that
    the Iconic map will only register a change for targets when the domain
    is explicitly enabled via the Notification window.  Regular alarms
    need no explicit enabling.  Is this by design or will this be fixed ?
    
    I have some terminal servers and stations with rules that check other
    rules.  When the secondary rule fires a targetting assignment points
    to the offending icon.  The icon will only change color if the domain
    is enabled via the Notification window and then when the notification
    does come in, it appears TWICE in the Notification Messages window.
    
    Question 2:
    
    Will the Save Current Settings in the Notification Window save more
    than just mcc_ns.maxNotifications in the MCC_NOTIFICATION_RESOURCE.DAT
    file when V1.2 is released ?
    
    Thanks.
T.RTitleUserPersonal
Name
DateLines
2701.1some answersDADA::DITMARSPeteTue Apr 07 1992 14:0371
Q1:

>    the Iconic map will only register a change for targets when the domain
>    is explicitly enabled via the Notification window.  Regular alarms
>    need no explicit enabling.  Is this by design or will this be fixed ?

Hmmm... not quite sure what you're asking here.

Targetting is done on a per-domain basis.  So is notification.  If you don't
have a notify request running for a domain (either directly or indirectly)
your targetting assignments won't do any good.

The way the IMPM should work out of the box is that the Map window's 
"Notification" customization setting should be "Enabled" (I don't think it was 
for T1.2.4, but it will be in V1.2).  What this setting does is automatically 
start up a "default" notify request for any domain that you >>OPEN<< in a 
map window.  Default notify requests listen for events in the "notification" 
event partition for the specified domain >>and all dynamic subdomains of that
domain<<.  Rules created using the MCC alarms FM post their "rule fired" events 
in the notification partition.  So, the desired effect is that if you have
alarm rules created and enabled, you should be able to get notification of those
alarm rules firing by simply opening the domain that they reside in (or a parent
domain of the domain).  Events from entities such as the Node4 entity are 
typically defined in the "configuration" event partition.  For those, you need
to create a notify request "by hand" using the Notification window.

>    I have some terminal servers and stations with rules that check other
>    rules.  When the secondary rule fires a targetting assignment points
>    to the offending icon.  The icon will only change color if the domain
>    is enabled via the Notification window 

Like the above paragraph states, you'll only get notifications of a rule firing
if you have a notify request listening for events in the domain you're 
interested in.

>and then when the notification
>    does come in, it appears TWICE in the Notification Messages window.

TWICE: once for the first rule and once for the second rule, right?  No way
around that for now.  There's no switch on an alarm rule saying "don't send
notification of this rule firing all the way to the user".  You could do 
something like this by having a rule in domain A watch for a rule in domain B 
to fire, and then only have notify requests active that apply to domain A.

If it's TWICE for just the second rule, then you probably have more than one
notify request that applies to the same domain.  This can happen for several
reasons.  Two map windows that have overlapping domain hierarchies open in
them, e.g.

                A <--- domain A open in map window 1
               / 
              B   <--- domain B open in map window 2 
             / \
            D   E

The above will result in all notifications for domains B D and E being delivered
twice to the IMPM.  

Q2:

Yes, there are a bunch of customizable things in the latest baselevel:
	size of buffer
	bell ringing
	notify request startup file
	logging controls 
		(start at startup, format, periodic new version, purge/keep)
	window geometry & bottom-row-buttons


Also, an all-new targetting interface has been added to the Notification
window.
2701.2Only from IMPM ?MERIDN::ATTERBERRYTue Apr 07 1992 15:1012
    Hi,
    
    Thanks for your answer.  I can see why I would get TWO notifications.
    If what you are saying is true, then why when I use the command
    NOTIFY DOMAIN .foo from the command line do I still not get the
    notification in domain .foo ?  I only see the icons change color when
    I do tequivalent command from the IMPM Notification Window.  I
    thought Notification was per system not per process
    
    Thanks
    
    Joe
2701.3does this still exist?TOOK::CALLANDERMCC = My Constant CompanionTue Apr 21 1992 14:3811
    the alarm event generation is per system, but the notify
    request is per user process. You must set up the notify
    command for each running MCC that you want to see the
    events for. 
    
    What has me confused is that you say you are doing a notify domain
    foo from the map and from the FCL and not seeing the same results.
    That doesn't sound right. Are you still seeing this problem?
    
    jill
    
2701.4works the same in the FCLMERIDN::ATTERBERRYTue Apr 21 1992 20:5815
    hi,
    
    Thanks for the clarification on the Notification services being per
    process.  I set up a test for the Notification via FCL and it does
    indeed show a notification event for both the parent domain and any
    sub-domains of the parent if the entity is in the sub-domain.
    
    I hope the customization of the IMPM allows for domains and sub-domains
    to be automatically enabled for notification.  I do NOT wish to tell
    MCC which domains to enable for notification every time the IMPM is
    invoked.
    
    Thanks.
    
    Joe
2701.5save notifies in t1.2.7ICS::WOODCOCKTue Apr 21 1992 21:0314
>    I hope the customization of the IMPM allows for domains and sub-domains
>    to be automatically enabled for notification.  I do NOT wish to tell
>    MCC which domains to enable for notification every time the IMPM is
>    invoked.
    
Hi Joe,

The good news is in. I just got done testing t1.2.7 to do just this. You can
save your notify requests into a .com file which will get run every time the
map is brought up. It seemed to work well without a hitch.

kind regards,
brad...