Specifications

Alarm Notification Manager (SANM)
Corrected SANM Anomalies in SPECTRUM 6.5
SPECTRUM Software Release Notice Page 25
specify the System Account — it cannot access the network.) Then
make sure the user or user group assigned to the Task Scheduler is
also defined as a SPECTRUM user in SpectroGRAPH.
If you find that the Task Scheduler is not performing SANM tasks as
scheduled, check the Windows NT Task Scheduler Service Startup
parameters. Even when these Task Scheduler parameters are incorrect,
you can schedule associations. The Task Scheduler, however, will not be
able to perform the association.
Corrected SANM Anomalies in SPECTRUM
6.5
1 If you change a SANM policy association while AlarmNotifier is
running, and the value for GET_EXISTING_ALARMS in the .alarmrc
resource file is set to TRUE, the states of all previously existing alarms
are now correctly displayed as EXISTING.
Known SANM Anomalies in SPECTRUM 6.5
Problem 1: When you run SANM-enabled AlarmNotifier on the Solaris
platform with the option -ts set less than the number of models you are
filtering (e.g.: if you have 1000 models, you should not set the option -ts
to be 500), the swap space will eventually be used up causing
SpectroSERVER to shutdown.
Solution: When setting up the trace file, be careful about its size in
relation to the number of models specified in the policy filter. To be safe,
accept the default size of 10000.
Tip:
Tip:
When Microsoft Internet Explorer 5.0 is installed on your PC, the
Windows NT 4.0 Schedule Service (Atsvc.exe) is upgraded to
the Task Scheduler Service (mstask.exe), which enables you to
assign different user accounts to run scheduled tasks.