Specifications

9032277-04 CS3 Software Characteristics
3-3
Problems Resolved in CS3
The resolution was to add a default value for Model_Name so that the
application name could be displayed properly. GIB enumerations were
added to the Model Information view GIB file so that the correct
values would be displayed for Model State, Condition, and Contact
Status. And, finally, the read modes for the appropriate attributes
were changed from Read-Only to Read-Instance and Read-Write to
Read-Write-Instance so that the ??? symbols would no longer appear
in the DS3/E3 Configuration view.
2. The problem was with SpectroWATCH threshold watches that
were set to generate alarms. If you cleared the alarm for an
exceeded threshold, the watch was not reinitialized. This caused a
problem if the threshold was exceeded again. In order to receive a
second alarm, you had to deactivate and reactivate the watch
through the Alarm Manager.
The resolution was to add a check button to the Watch Editor, called
Reset watch upon user clearing of alarm. This button and its
functionality will be enabled if the options "Generate an alarm if
violated" and "Alarm is user clearable" are both checked.
3. The problem was in displaying a TAB report using the Report
Display GUI. The xterm would come up but all you would see in
the report was the error ld.so.1: more: fatal: relocation
error: file more: symbol cur_term: referenced
symbol not found Killed. This was found to be a problem
particularly on workstations running the Solaris 2.7 operating
system, where the "more" command is no longer statistically
linked with the curses library. The view cannot be properly viewed
if you cannot use the "more" command.
The resolution was to add /usr/lib to the LD_LIBRARY_PATH in
$SPECROOT/Install-Tools/setup.{k,c}sh. This allows the curses
library to be loaded dynamically and the Report Display GUI to be
viewed without errors.
4. The problem was that an "Unknown Landscape" error and "No
User Model" error were competing for display when the Event
view was started from the command line with -showSplash set to
False by a user who had no user model in the VNM database. If
this occurred, only the last error in the error stack would be
displayed in the window. The "Unknown Landscape" error does
not give a real description of the problem and only appeared
because the service failed after the user model was queried. In this