Specifications

Alarm Notification Manager (SANM)
Known SANM Anomalies in SPECTRUM 6.0.3
SPECTRUM Software Release Notes Page 41
not specify the System Account — it cannot access the network.) Then
make sure the user or user group assigned to the Schedule Service is
also defined as a SPECTRUM user in SpectroGRAPH.
If you find that the Scheduler is not performing SANM tasks as
scheduled, check the NT Schedule Service Startup parameters. Even
when these Schedule Service parameters are incorrect, you can schedule
associations. The Scheduler, however, will not be able to perform the
association.
Known SANM Anomalies in SPECTRUM 6.0.3
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 segmentation fault.
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.
Problem 2: If, in a distributed SpectroSERVER environment, policies are
created and stored on different SpectroSERVERs by running Policy
Administrator against different initial SpectroSERVERs and schedules are
created to associate these policies with a particular application, the
scheduled associations will fail. sanm391
Solution: Ensure that all policies are stored on one SpectroSERVER by
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. See
About the SPECTRUM Control Panel for more information
about configuring the Task Scheduler Service for scheduled
SPECTRUM tasks.