[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

2877.0. "Displaying alarms and Node4 name/address" by SUBURB::SMYTHI (Ian Smyth 830-3869) Wed Apr 29 1992 10:47

	A couple of observations with T1.2.7 on VMS -

-	When using the IMPM to "Display Notifications", the notifictions 
are displayed in a different order to the "Notification Services" display
ie by using "Display Notification" from the Operations pull-down, I get the 
following -

warning        6 Node4 HHLRT3 Rule Max_Address has fired                      29-APR-1992 10:00:38.53 Domain UKHUB_NS:.EASYnet
warning        5 Node4 HHLRT2 Rule Max_Address has fired                      29-APR-1992 10:00:31.78 Domain UKHUB_NS:.EASYnet
warning        4 Node4 HHLRT1 Rule Max_Address has fired                      29-APR-1992 10:00:28.01 Domain UKHUB_NS:.EASYnet
indeterminate  3 Node4 NORA   Rule Max_Address has encountered an exception   29-APR-1992 10:00:17.45 Domain UKHUB_NS:.EASYnet
warning        2 Node4 WLORT2 Rule Max_Address has fired                      29-APR-1992 09:59:47.86 Domain UKHUB_NS:.EASYnet
warning        1 Node4 UVORT3 Rule Max_Address has fired                      29-APR-1992 09:59:39.94 Domain UKHUB_NS:.EASYnet
warning        7 Node4 BBPRT1 Rule Max_Address has fired                      29-APR-1992 10:00:53.41 Domain UKHUB_NS:.EASYnet

Using "Notification Services" from the Applications pull-down, I get

warning        1 Node4 UVORT3 Rule Max_Address has fired                      29-APR-1992 09:59:39.94 Domain UKHUB_NS:.EASYnet
warning        2 Node4 WLORT2 Rule Max_Address has fired                      29-APR-1992 09:59:47.86 Domain UKHUB_NS:.EASYnet
indeterminate  3 Node4 NORA   Rule Max_Address has encountered an exception   29-APR-1992 10:00:17.45 Domain UKHUB_NS:.EASYnet
warning        4 Node4 HHLRT1 Rule Max_Address has fired                      29-APR-1992 10:00:28.01 Domain UKHUB_NS:.EASYnet
warning        5 Node4 HHLRT2 Rule Max_Address has fired                      29-APR-1992 10:00:31.78 Domain UKHUB_NS:.EASYnet
warning        6 Node4 HHLRT3 Rule Max_Address has fired                      29-APR-1992 10:00:38.53 Domain UKHUB_NS:.EASYnet
warning        7 Node4 BBPRT1 Rule Max_Address has fired                      29-APR-1992 10:00:53.41 Domain UKHUB_NS:.EASYnet


Also, when using "Display Notifications" to display alarm details by
double-clicking on the alarm, the "Detail Notifications Window" is resized
every time the "Next" and "Previous" buttons are clicked on. This is 
really annoying when I've resized the window to display the full details
(ie no scroll bars) and I have a sequence of alarms to display. 
"Notification Services" handles this correctly.

Another "nit" which is in 1.1 and still in T1.2.7 is the display of
Node4 addresses instead of Node4 names. eg, In the above alarms, Notification
Services and Display Notifications display the node4 name in the brief 
display ie

warning        6 Node4 HHLRT3 Rule Max_Address has fired                      29-APR-1992 10:00:38.53 Domain UKHUB_NS:.EASYnet

but expand the details and the information becomes 

information   Rule fired: Node4 41.76 Maximum Address....

	If we can have the Node4 name for the brief display, why can't the
expanded display use the same?


regards,
	Ian

T.R Title User Personal
Name Date Lines

2877.1 primary vs alternate id MCC1::DITMARS Pete Wed Apr 29 1992 16:27 18

T.R	Title	User	Personal Name	Date	Lines
2877.1	primary vs alternate id	MCC1::DITMARS	Pete	`Wed Apr 29 1992 16:27`	18
	> If we can have the Node4 name for the brief display, why can't the >expanded display use the same? The place you're seeing the address is text embedded inside of an event report. The event report was produced by the alarms FM. It took the name of the entity as it was reported to it by the DNA4 AM because the DNA4 AM dictates that address is the "primary identifier" it will use, and that's what it (DNA4) always returns. The reason you're seeing name and not address in the summary is that the IMPM has a customization feature that lets users decide which "alternate identifier" to use for entity names. Where it is possible to do so, the IMPM translates an entity's primary identifier into the user's preferred alternate identifier. It's not possible for the IMPM to do this for the embedded text in the alarm report you're seeing. Both notification detail windows do include the name of the entity that the rule was reported against, at the top of the window.

>	If we can have the Node4 name for the brief display, why can't the
>expanded display use the same?

The place you're seeing the address is text embedded inside of an event
report.  The event report was produced by the alarms FM.  It took the name
of the entity as it was reported to it by the DNA4 AM because the DNA4 AM
dictates that address is the "primary identifier" it will use, and that's
what it (DNA4) always returns.

The reason you're seeing name and not address in the summary is that
the IMPM has a customization feature that lets users decide which
"alternate identifier" to use for entity names.  Where it is possible to do so,
the IMPM translates an entity's primary identifier into the user's preferred 
alternate identifier.  It's not possible for the IMPM to do this for the 
embedded text in the alarm report you're seeing.

Both notification detail windows do include the name of the
entity that the rule was reported against, at the top of the window.