Specifications

Patches Issued Since the CS2/MMS2 Release

Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1

5-52 CS3 and MMS3

were selected. Also, ﬁlter changes are not alway saved although the

"Make Permanent" button is selected.

The resolution was to change the condition and state preferences so

that they are *NOW* manually written out instead of relying on the

preference binders.

SPECTRUM_5.0rev1.P85

The problem was when SPECTRUM lost SNMP contact (i.e. via

incorrect community name) with a 3Com FMS the model turned RED

instead of ORANGE.

The resolution was to change the support_ICMP attribute so that if an

illegal community is entered for a model it will turn ORANGE instead

of RED.

SPECTRUM_5.0rev1.P86

Included in SPECTRUM_5.0rev1.P101

SPECTRUM_5.0rev1.P87

The various SPECTRUM Data Export import scripts (e.g.,

SDEOraImport) use awk internally to read values for several

attributes from the input schema ﬁle. The awk commands fail when

the schema ﬁle gets too large (around 100 records).

The resolution was to replace the faulty awk code with perl code in

each of the scripts. Additionally, the dtxscript.tpl (template ﬁle) was

modiﬁed to obtain the perl directory location during SPECTRUM

install and export it during run time. Finally, code was added to avoid

a macro expansion error in datex.cus.

The problem was that SPECTRUM Data Export SDEOraImport script

drops and recreates indices during every table load (including

appends). The table name is obtained from the .SDE ﬁle where it's

speciﬁed as simplySTAT_ROUT. So when the script attempts to drop

and then recreate indices (which are created based on the table name)