Specifications

9032277-04 Software Superseded by CS3/MMS3
5-11
Patches Issued After the CS1/MMS1 Release
2. The maximum number of requests that MALT can send to a server
has been increased from 1000 to 8000.
3. Requests are no longer sent all at once. They are broken up into
chunks of 100 and sent at 5 millisecond intervals. This allows
MALT to read in some responses that may back up to the point of
causing MALT to freeze.
SPECTRUM_5.0rev1.P25
Included in P34, P41, and P48.
SPECTRUM_5.0rev1.P26
Included in P45.
SPECTRUM_5.0rev1.P27
Included in P44.
SPECTRUM_5.0rev1.P28
Included in P34, P41, and P48.
SPECTRUM_5.0rev1.P29
The Event Log for a model that has recent events is showing no events
in the log. No message appears stating that there are no events for
that time frame. When trying to page up, the mouse pointer turns into
an hour glass and then hangs. The event system has a two-tiered
filtering system. In the best case all of the filtering is done by the
database layer. This is desirable because the database is organized in
a manner that makes filtering on model handles and/or time very
efficient. If database filter is used exclusively then the exact events
you have requested are pulled from the database without having to
filter on every event. The second tier uses the CsEventFilter code for
filtering. In this case each event is pulled from the database and run
through the filter. This continues until one of the following occurs:
• The end of the database is reached.
• The number of events that you requested have been found.
• The search limit is reached (Currently 10,000 events).
So, the model that the EventLog was brought up on had +10,000
events which caused the EventLog to eventually hang.