# Class CIM_SettingData
extends CIM_ManagedElement

CIM_SettingData is used to represent configuration and and operational parameters for CIM_ManagedElement instances. There are a number of different uses of CIM_SettingData supported in the model today. Additional uses may be defined in the future. Instances of CIM_SettingData may represent Aspects of a CIM_ManagedElement instance. This is modeled using the CIM_SettingsDefineState association. CIM_SettingData may be used to define capabilities when associated to an instance of CIM_Capabilities through the CIM_SettingsDefineCapabilities association. Instances of CIM_SettingData may represent different types of configurations for a CIM_ManagedElement, including persistent configurations, in progress configuration changes, or requested configurations. The CIM_ElementSettingData association is used to model the relationship between a CIM_SettingData instance and the CIM_ManagedElement for which it is a configuration. When an instance of CIM_SettingData represents a configuration, the current operational values for the parameters of the element are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values that are present in the SettingData object. For example, a modem might have a SettingData baud rate of 56Kb/sec but be operating at 19.2Kb/sec. Note: The CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model 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. SettingData instances can be aggregated together into higher- level SettingData objects using ConcreteComponent associations.

### Table of Contents
Hierarchy
Direct Known Subclasses
Class Qualifiers
Class Properties
Class Methods

## Class Hierarchy

CIM_ManagedElement
|
+--CIM_SettingData

## Direct Known Subclasses

CIM_AccessControlServiceSettingData
CIM_AccountSettingData
CIM_BootConfigSetting
CIM_BootSettingData
CIM_BootSourceSetting
CIM_CLPSettingData
CIM_CommonDatabaseSettingData
CIM_ConfigurationData
CIM_ConnectivityMembershipSettingData
CIM_DiagnosticSettingData
CIM_EnabledLogicalElementSettingData
CIM_ExportedFileShareSetting
CIM_FCIPSettings
CIM_FCSwitchSettings
CIM_FileSystemSetting
CIM_IEEE8021xSettings
CIM_ImportedFileShareSetting
CIM_IndicationServiceSettingData
CIM_IPAssignmentSettingData
CIM_IPSettings
CIM_IPVersionSettingData
CIM_iSCSIConnectionSettings
CIM_iSCSISessionSettings
CIM_JobSettingData
CIM_LAGPortPartnerSettings
CIM_LogicalPortSettings
CIM_MPLSQosPRTrfcProf
CIM_NetworkPolicyActionSettingData
CIM_NetworkPolicyRuleSettingData
CIM_PrintServiceSettings
CIM_RedundancySetSettingData
CIM_ReplicationSettingData
CIM_ResourceAllocationSettingData
CIM_SAEndpointRefreshSettings
CIM_ScopedSettingData
CIM_SCSIMultipathSettings
CIM_SSHSettingData
CIM_StatisticalSetting
CIM_StorageClientSettingData
CIM_StorageNameBinding
CIM_StorageSetting
CIM_SWRLimitSetting
CIM_SynchronizationAspect
CIM_TCPSettings
CIM_TelnetSettingData
CIM_TierSettingData
CIM_TimeZoneSettingData
CIM_VideoHeadResolution
CIM_VirtualSystemMigrationSettingData
CIM_VirtualSystemSettingData
CIM_VLANEndpointSettingData
CIM_VLANSystemSettingData
CIM_WiFiEndpointSettings
CIM_WiFiNetworkDetectionSettings

## Class Qualifiers

Name | Data Type | Value
--- | --- | ---
Abstract | boolean | true
Description | string | CIM_SettingData is used to represent configuration and and operational parameters for CIM_ManagedElement instances. There are a number of different uses of CIM_SettingData supported in the model today. Additional uses may be defined in the future. Instances of CIM_SettingData may represent Aspects of a CIM_ManagedElement instance. This is modeled using the CIM_SettingsDefineState association. CIM_SettingData may be used to define capabilities when associated to an instance of CIM_Capabilities through the CIM_SettingsDefineCapabilities association. Instances of CIM_SettingData may represent different types of configurations for a CIM_ManagedElement, including persistent configurations, in progress configuration changes, or requested configurations. The CIM_ElementSettingData association is used to model the relationship between a CIM_SettingData instance and the CIM_ManagedElement for which it is a configuration. When an instance of CIM_SettingData represents a configuration, the current operational values for the parameters of the element are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values that are present in the SettingData object. For example, a modem might have a SettingData baud rate of 56Kb/sec but be operating at 19.2Kb/sec. Note: The CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model 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. SettingData instances can be aggregated together into higher- level SettingData objects using ConcreteComponent associations.
UMLPackagePath | string | CIM::Core::Settings
Version | string | 2.33.0

## Class Properties

### Local Class Properties

Name | Data Type | Default Value | Qualifiers
--- | --- | --- | ---
Name | Data Type | Value
ChangeableType | uint16 |
Description | string | Enumeration indicating the type of setting. 0 "Not Changeable - Persistent" indicates the instance of SettingData represents primordial settings and shall not be modifiable. 1 "Changeable - Transient" indicates the SettingData represents modifiable settings that are not persisted. Establishing persistent settings from transient settings may be supported. 2 "Changeable - Persistent" indicates the SettingData represents a persistent configuration that may be modified. 3 "Not Changeable - Transient" indicates the SettingData represents a snapshot of the settings of the associated ManagedElement and is not persistent.
ValueMap | string | 0, 1, 2, 3
Values | string | Not Changeable - Persistent, Changeable - Transient, Changeable - Persistent, Not Changeable - Transient
ConfigurationName | string |
Description | string | An instance of CIM_SettingData may correspond to a well-known configuration that exists for an associated CIM_ManagedElement. If the ConfigurationName property is non-NULL, the instance of CIM_SettingData shall correspond to a well-known configuration for a Managed Element, the value of the ConfigurationName property shall be the name of the configuration, and the ChangeableType property shall have the value 0 or 2. A value of NULL for the ConfigurationName property shall mean that the instance of CIM_SettingData does not correspond to a well-known configuration for a Managed Element or that this information is unknown.
ElementName | string |
Description | string | The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query. (Note: The name does not have to be unique within a namespace.)
Override | string | ElementName
Required | boolean | true
InstanceID | string |
Description | string | Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: <OrgID>:<LocalID> Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>. <LocalID> is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. For DMTF-defined instances, the "preferred" algorithm must be used with the <OrgID> set to CIM.
Key | boolean | true
Override | string | InstanceID

### Inherited Properties

Name | Data Type | Class Origin
--- | --- | ---
Caption | string | CIM_ManagedElement
Description | string | CIM_ManagedElement
Generation | uint64 | CIM_ManagedElement

## Class Methods