Name | Data Type | Value | Scope | Flavors |
---|---|---|---|---|
Abstract | boolean | true | TOSUBCLASS= false | None |
Description | string | The Setting class represents configuration-related and operational parameters for one or more ManagedSystemElement(s). An Element may have multiple Setting objects associated with it. The current operational values for an Element's parameters are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values present in the Setting object. For example, a modem may have a Setting baud rate of 56Kb/sec but be operating at 19.2Kb/sec. Note that the CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model. This is because many implementations have successfully used CIM_Setting. However, issues have arisen that could not be resolved without defining a new class. Therefore, until a new major release occurs, both classes will exist in the model. Refer to the Core White Paper for additional information. | None | TRANSLATABLE= true |
Version | string | 2.7.0 | TOSUBCLASS= false | TRANSLATABLE= true |
Name | Data Type | Qualifiers | ||||
---|---|---|---|---|---|---|
Name | Data Type | Value | Scope | Flavors | ||
Caption | string | |||||
Description | string | The Caption property is a short textual description (one- line string) of the object. | None | TRANSLATABLE= true | ||
MaxLen | uint32 | 64 | None | None | ||
Description | string | |||||
Description | string | The Description property provides a textual description of the object. | None | TRANSLATABLE= true | ||
ElementName | string | |||||
Description | string | A user-friendly name for the object. This property allows each instance to define a user-friendly name IN ADDITION TO its key properties/identity data, and description information. Note that ManagedSystemElement's Name property is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information MAY be present in both the Name and ElementName properties. | None | TRANSLATABLE= true | ||
SettingID | string | |||||
Description | string | The identifier by which the Setting object is known. | None | TRANSLATABLE= true | ||
MaxLen | uint32 | 256 | None | None |