Conference azur::mcc

6185.0. "Problem with notification window behaviour." by KETJE::PACCO (Horum omnium fortissimi sunt Belgae) Wed Nov 30 1994 06:18

I fear I have not understood correctly what the documentation tries to explain
about the behaviour on the POLYCENTER Notification window of the iconic map.

I refer to the ALARMS and NOTIFICATION SERVICES USE manual and the
description of a 'notification used by the iconic map' as described on
page 3-12:
quote
A notification is considered to be not in use by the iconic map
when it is not contributing to an icon's color.
unquote
and for OldestNotUsedByMap:
quote
Try to delete oldest notification NOT IN USE BY MAP
unquote

Lets take the following (very simplified) example.
==================================================
I use the ICONIC MAP and the notification services with the following
mcc_notification resources:
	maxNotifications	4
	overflowMultiplier	1.5
	bufferFullPolicy	OldestNotUsedByMap

I use the following domains:
	domain  A,	containing	circuits
			containing	nodes
	 		containing one	dispatcher (data collector)
	domain  B,	containing (the same) nodes

I open the ICONIC MAP on domain A, and enable the following notification
requests:
	domain A	collector *	any event
	domain B	node *		any event

Node events are being sent.
Data collector are being sent to the dispatcher (with retargetting to
circuits and nodes).
==================================================
I reduced the window to 6 entries (4*1.5) to be able to better observe the
behaviour of the notification window.

What I expect to have (by this example) is
1). The data collector (qualified) events being 'kept' as long as possible
on the iconic map.  This means that I expect to have at least 4 collector
events at any time (as those contribute to the icons colors), eventually 5 or
6, (assumed I have received at least several collector events).
2). The DECnet phase V (Indeterminate) events are allowed to 'scroll' in
the 'overflow' region. In other words any event, including those which 
'do not contribute to the icons colors' are allowed to reside in the overflow
region.  Anyhow I should not see more than 2 node events on the
notification window.


What I see on the notifications window is the following:
1). When only 'indeterminate node events' arrive, I see maximum 6 events.   O.K.

2). When I generate a collector event, that event is seen on the window, and
highlights the iconic map. Then it is being shifted upwards any time a new
(indeterminate) node event comes in.  After a while that event is removed
from the notifications window and the iconic map looses its highlighted color.


Based on this experience, i do not understand any more how notification is
meant to function.  Is the an inconsistency here or what ?