Specifications

Alarm Notification Manager (SANM)
Corrected SANM Anomalies in SPECTRUM 6.0.2
SPECTRUM Software Release Notes Page 41
with the value f would correctly display in the Event View and Alarm
View, but not in AlarmNotifier. This problem has been corrected.
sanm566
5 Previously, when using SANM to filter alarm information from
AlarmNotifier, multiple SETs and CLEARs for the same device(s) and
alarm ID(s) could be seen in log files following communications
interruptions, such as can occur during online backups, for example.
This problem has been corrected. sanm585
6 Following communications interruptions such as those described
above, multiple SETs and CLEARs for the same device(s) and alarm
ID(s) no longer appear in log files.
7 Previously, when using SANM to filter alarm information from
AlarmNotifier, if GET_EXISTING_ALARMS was set to “false” in the
<$SPECROOT>/Notifier/.alarmrc resource file, then AlarmNotifier
was re-started, new alarms with creation dates previous to when
AlarmNotifier was re-started could be seen. This was because updates
to those “prior” alarms (which were cleared when AlarmNotifier was
re-started) were interpreted as new alarms. This problem has been
corrected. sanm580
8 A new filtering mechanism has been included in AlarmNotifier that
correctly interprets such updates, and they are no longer sent to
AlarmNotifier, nor ultimately, to SANM.
9 Previously, when using trace files to determine SANM policy
functionality with AlarmNotifier, intermittent segmentation faults
would occur from AlarmNotifier. This problem has been corrected.
sanm602
10 A change in the way filter values are truncated in the trace files has
eliminated the segmentation faults in these instances.
11 When you use the Policy Administrator on NT, text no longer fails to
appear in the title bars of message windows and dialog boxes. On
Windows NT, users who are selected to receive e-mail notification data
now receive the e-mail.