Specifications

9032277-04 Software Superseded by CS3/MMS3

5-17

Patches Issued After the CS1/MMS1 Release

This has been resolved by optimizing the code to read the template

and store it rather than repeatedly reading it for each device.

In ECM, create a new conﬁguration in the conﬁguration window by

adding attributes from the list of attributes shown. Now Undo this

insert operation by invoking Edit->Undo Insert from the Menu. The

attribute(s) inserted are not shown (refreshed) in the list of insertable

attributes window after the Undo Insert operation is performed. This

has been resolved by refreshing the list of attributes after the Undo

Insert operation is performed.

ECM does not display scheduled Jobs. The scheduled event section is

blank even though the scheduled jobs show up when displayed via

command line. This happens because of the incorrect ﬁlter string

given by ECM to CsScheduler. This has been resolved by passing the

correct ﬁlter string.

After saving a conﬁguration, the user is able to complete a load with

the safe option. When this conﬁguration is then exported and re-

imported, the user is unable to load with the safe option selected. The

user is able to load this conﬁguration when the safe load option is not

selected. The problem was occurring due to the absence of model

handle of the device when the capture operation was performed. This

has been resolved by having the model handle of the device retrieved

and packed when the conﬁguration information is stored.

The Enterprise Conﬁguration Manager core dumps when the View/

View by Flags option is selected from the menu bar. This has been

resolved by having the View by [Attribute/Flags/Sequence] for

attributes contained in a conﬁguration grayed out in the View pull

down menu when no conﬁgurations are selected.

During a capture of multiple attributes, if one or more attributes are

not captured, ECM does not treat this as a fatal error and continues.

ECM saves the captured conﬁguration, with the captured values for

successful attributes, and some default values, for unsuccessful

attributes. The result of such a capture operation is

"NON_FATAL_ERROR". This does not prevent writing the

conﬁguration to database and also shows up as successful, but sends

an event to the SS indicating capture “not successful.” This is how this

will work now:

The capture detail window indicates status, which could be either

success, partly successful, or failed