Specifications

Remedy AR System Gateway
Known ARS Gateway Anomalies in SPECTRUM 6.5
SPECTRUM Software Release Notice Page 36
Solution: This problem will be corrected in a future release of
SPECTRUM.
Problem 6: On the Windows NT and 2000 platforms, if you submit a
trouble ticket on an alarm to Remedy, no trouble ticket is submitted. In
addition, no error message of any kind is generated. This is occurring
because the Remedy libraries are not found by the Alarm Manager.
Solution: Manually add the location of the Remedy directory to the
environment variable PATH in the System Control Panel. For example, if
the location is “D:\Program Files\Remedy”, add this to the value for PATH
in the System Control Panel, log out, then log back in again. When you run
Alarm Manager, it should find the Remedy libraries in the specified
location and you will be able to submit trouble tickets. This problem will
be corrected in the next release of SPECTRUM.
Problem 7: When the reconfig tool script is run by any user other than
the SPECTRUM installer (with full root and ADMIN,0 privileges), the
ARSGD.idb file necessary for processd to start and maintain the Gateway
process will not be successfully placed where it needs to be. The user
receives the message:
cannot create /usr/SPEC_6.5.0/lib/SDPM/partslist/ARSGD.idb: Permission denied
reconfig: .save: cannot create reconfig: .save: cannot create reconfig: .save: cannot create
reconfig: .save: cannot create
Reconfiguration completed successfully.
The last line is misleading.
Solution: Aprisma will be providing a more instructive error message that
lets you know that you need to be root or an administrator with full read/
write privileges to run the reconfig script successfully. This message will
be available in a future release of SPECTRUM. In the meantime, if you
want the Gateway to be started and maintained by processd, the root/
admin user needs to copy the file from the $SPECROOT/ars_gateway
directory to the $SPECROOT/lib/SDPM/partslist directory after having
run the reconfig tool.