Specifications

Remedy AR System Gateway
Known ARS Gateway Anomalies in SPECTRUM 6.5
SPECTRUM Software Release Notice Page 35
Known ARS Gateway Anomalies in
SPECTRUM 6.5
Problem 1: When you run SANM-enabled AR System Gateway on the
Solaris platform with the -ts option 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
a SpectroSERVER 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.
Problem 2: When the Automatic Trouble Ticket Generator is invoked by
processd, you have no access to setting SANM parameters.
Solution: Modify the ARSGD.idb file located in the <$SPECROOT>/lib/
SDPM/partslist directory. This problem will be corrected in a future
release of SPECTRUM.
Problem 3: Base-level (no SANM) only (Windows NT)— If you modify your
filters when the Automatic Trouble Ticket Generator (arsgated) is running,
the modifications are not known by the arsgated.
Solution: This problem will be corrected in a future release of
SPECTRUM.
Problem 4: When running the arsgated, if the Remedy AR System Server
password is not entered on the command line or is not present in the
resource file, you are not prompted for your password.
Solution: The Remedy AR System Server password must be either
entered on the command line or present in the resource file. This will be
corrected in a future release of SPECTRUM AR System Gateway.
Problem 5: If an alarm is generated on a model with no name and a
trouble ticket is submitted from the Alarm Manager, when you list all the
tickets in Remedy the trouble ticket for that particular model is available
but will not be visible. This is because when displaying all trouble tickets,
Remedy lists the impacted object (model name) as the name in the list.