Specifications

AR System Gateway
Known ARS Gateway Anomalies in SPECTRUM 6.0.3
SPECTRUM Software Release Notes Page 54
Problem 3: When arsgated is run with -tl or -tn option, the file it should
create in trace directory is missing. This is due to the arguments not being
passed to the arsgated.demon.
Solution: This is being fixed in a later release.
Problem 4: 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: Stop and restart the arsgated after changing any filters.
Problem 5: When the Show Similar Tickets button is pressed on
Windows NT from the SPECTRUM Trouble Ticket, the similar tickets are
displayed but the resolution field is not exploded.
Solution: This will be corrected in a future release of SPECTRUM AR
System Gateway.
Problem 6: 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 7: When performing a Manual Submit via the SPECTRUM Alarm
Manager, the submit fails when the probable cause text string is too long.
An example is the text string for probable cause ID 0x10c0b.
Solution: Select Show Trouble Tickets from the SPECTRUM Alarm
Manager to verify that trouble tickets are submitted. This will be corrected
in a future release of SPECTRUM AR System Gateway.