Specifications

Problems Resolved in CS3
CS3 Software Characteristics Software Release Notice for 5.0rev1
3-4 CS3 and MMS3
case, the "No User Model" error should always be the one to be
displayed.
The resolution was to add a special case to the code to handle the
scenario when the Unknown Landscape error is received after a
previous error when the service is unusable. Now, the error with the
most useful information will always be displayed.
5. A problem occurred when the SpectroGRAPH was being displayed
on a remote X server or a machine with a completely different
operating system from the SpectroSERVER machine (e.g., HP-UX,
Linux, etc.). SPECTRUM's Install-Tools/setup.{c,k}sh script was
evaluating and modifying the fontpath settings of the remote X
server. It split the fontpath into directories and created a new
fontpath, where it omitted $SPECROOT/lib/X11/fonts/misc and all
directories that did not exist on the SPECTRUM machine. The
Install-Tools/setup.{c,k}sh script would remove any directories
from the fontpath on the remote display X server that did not
match the fontpath of the SpectroSERVER machine. Other
applications dependent on the remote would display X server
fontpath settings.
The resolution was to modify SPECTRUM's Install-Tools/setup.{c,k}sh
script to stop removing fonts from the X fontpath upon evaluation.
6. The problem was that there was no derivation point available for
Third Party developers to provide the security string inheritance
feature for new hierarchical views.
The resolution was to correct the inheritance of security strings to
allow Third Party developers to extend security string inheritance and
derive from the Security_Model model type.
7. The problem was that the SpectroSERVER process would reach
100% after only a few days of running on a Solaris workstation.
The cause was an infinite loop being executed inside the VNM's
Rollup intelligence between a Rtr_Cisco model and multiple
unmanaged DTE models that were connected to it. As an alarm
was generated on the Rtr_Cisco, it changed the unmanaged DTE
model’s rollup condition, which changed the Rtr_Cisco model's
rollup condition, and so on.
The resolution was to remove the CONNECTS_TO relation from the
Rollup_Child_Rels attribute for the unmanaged DTE model type.