Specifications
Alarm Notification Manager (SANM)
Corrected SANM Anomalies in SPECTRUM 6.0.2
SPECTRUM Software Release Notes Page 40
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.
Corrected SANM Anomalies in SPECTRUM
6.0.2
1 Previously, if the SpectroSERVERs in your SPECTRUM landscape
map used different naming services such as Network Information
Service (NIS) and Domain Name Service (DNS), you had to use
Landscape parameters instead of SpectroSERVER Host parameters
when creating or modifying the filters in a policy. This problem has
been corrected. sanm321
2 You now can use SpectroSERVER host parameters when creating or
modifying filters in a policy.
3 Policy Administrator now correctly displays text for probable cause
codes beginning with the value f (for example, fxxxxxxx, where x=any
value). It also correctly saves them into filters as fxxxxxxx. sanm400
4 Previously, when using SANM to filter alarm information from
AlarmNotifier, created events and probable cause codes beginning
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.