Class CIM_SoftwareResource


  extends CIM_EnabledLogicalElement
A Software Resource (SWR) is an abstraction of the utilization of other entities in the environment (communications, memory, files, etc.) within the context of the software entity being managed. SWR have a component-like implementation that is independently manageable from the real entity outside the software. These implementations are often used for storage and transmission. Thus, a Software Resource (SWR) is: a) any entity that is used by a system (e.g. an application system) to transfer data over space and time (i.e., no data processing in terms of creation/deletion or modification of data). In contrast to normal (application) services (i.e., the abstraction of data processing in terms of its creation/deletion etc.), the SWR has limits (bounds) that are not to be exceeded. This version does not consider resources like CPU. b) the system's view of such a transfer entity. Note that the software resource is ultimately contained by or related to a limited (physical or logical) resource of the encompassing (operating) system such as memory, storage or a communication links. Anything transferred by an SWR is called an 'item'. Items may be data, code, connections, packets, etc.. Items are atomic in the model, thus there is no partial items. An instance only exists if a running system exists since it is an internal component of the system implemented by its software. Software resources are potentially external entities like files viewed internally and (at least partially) controlled by the software of the system. SoftwareResource is contained by System via SystemComponent. At least one system (e.g., one application system or a system in general) contains 0 or more software resources. If more than one system claims to contain the software resource, it is a shared resource. SoftwareResource is associated to SWRLimitSetting via ElementSettingData. One software resource can have multiple limit settings. Only one of the settings is the default and one (potentially another one) is operational (current). Settings can be shared by software resources. SoftwareResource is associated to SWRStatistics via ElementStatisticalData. In general, one software resource is expected to have three statistics. The statistics type covers each behavior characteristics at most once. I.e., the software resource has at most one allocation statistcs, one input statistics and one output statistics. Nevertheless, the implementation of the software resource may exhibit more statistics SWRStatistics instances that cover more context-specific behavior characteristics.
Details...
This class is not implemented.

Subclasses

 CIM_SWRDatabase  CIM_SWRFile  CIM_SWRPEP

Class Qualifiers

NameData TypeValueScopeFlavors
DescriptionstringA Software Resource (SWR) is an abstraction of the utilization of other entities in the environment (communications, memory, files, etc.) within the context of the software entity being managed. SWR have a component-like implementation that is independently manageable from the real entity outside the software. These implementations are often used for storage and transmission. Thus, a Software Resource (SWR) is: a) any entity that is used by a system (e.g. an application system) to transfer data over space and time (i.e., no data processing in terms of creation/deletion or modification of data). In contrast to normal (application) services (i.e., the abstraction of data processing in terms of its creation/deletion etc.), the SWR has limits (bounds) that are not to be exceeded. This version does not consider resources like CPU. b) the system's view of such a transfer entity. Note that the software resource is ultimately contained by or related to a limited (physical or logical) resource of the encompassing (operating) system such as memory, storage or a communication links. Anything transferred by an SWR is called an 'item'. Items may be data, code, connections, packets, etc.. Items are atomic in the model, thus there is no partial items. An instance only exists if a running system exists since it is an internal component of the system implemented by its software. Software resources are potentially external entities like files viewed internally and (at least partially) controlled by the software of the system. SoftwareResource is contained by System via SystemComponent. At least one system (e.g., one application system or a system in general) contains 0 or more software resources. If more than one system claims to contain the software resource, it is a shared resource. SoftwareResource is associated to SWRLimitSetting via ElementSettingData. One software resource can have multiple limit settings. Only one of the settings is the default and one (potentially another one) is operational (current). Settings can be shared by software resources. SoftwareResource is associated to SWRStatistics via ElementStatisticalData. In general, one software resource is expected to have three statistics. The statistics type covers each behavior characteristics at most once. I.e., the software resource has at most one allocation statistcs, one input statistics and one output statistics. Nevertheless, the implementation of the software resource may exhibit more statistics SWRStatistics instances that cover more context-specific behavior characteristics.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
UMLPackagePathstringCIM::Application::SWResourcesNone None
Versionstring2.19.0TOSUBCLASS= falseTRANSLATABLE= true

Local Class Properties

NameData TypeQualifiers
NameData TypeValueScopeFlavors
AspectInUseuint16
DescriptionstringThe property value is 'Aspect Is in Use' if the software resource is currently control of the software. E.g., it still has a file handle of file. Any operations on the corresponding outside entity (e.g., the file) can now result in errors. E.g., the deletion of file from the outside could be refused since it still opened by the software. Note that currently no conflict resolution is designed into software resource classes. Values: Aspect Is in Use: The software resource is in use by the software (i.e., at least a reference to the resource is held by the software). Access to the resource may result in conflicting usage of any logically identical entity external to this software. Aspect Is not in Use: In special cases it may be the case that the software resource is currently not controlled by the software (i.e., a file is currently not accessed by the software and the file handle is returned. The software resource object exists without having the file in use.None TRANSLATABLE= true
ValueMapstring0, 2, 3, 4..32767, 32768..65535None None
ValuesstringUnknown, Aspect Is in Use, Aspect Is not in Use, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
AvailableRequestedStatesuint16
DescriptionstringAvailableRequestedStates indicates the possible values for the RequestedState parameter of the method RequestStateChange, used to initiate a state change. The values listed shall be a subset of the values contained in the RequestedStatesSupported property of the associated instance of CIM_EnabledLogicalElementCapabilities where the values selected are a function of the current state of the CIM_EnabledLogicalElement. This property may be non-null if an implementation is able to advertise the set of possible values as a function of the current state. This property shall be null if an implementation is unable to determine the set of possible values as a function of the current state.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
ModelCorrespondencestringCIM_EnabledLogicalElement.RequestStateChange, CIM_EnabledLogicalElementCapabilities.RequestedStatesSupportedNone None
ValueMapstring2, 3, 4, 6, 7, 8, 9, 10, 11None None
ValuesstringEnabled, Disabled, Shut Down, Offline, Test, Defer, Quiesce, Reboot, ResetNone TRANSLATABLE= true
ByReferenceuint16
DescriptionstringByReference indicates whether the software resource handles only references to items, but not the items itself. This can be the case for buffers or pools, where the items reside in the memory that was originally allocated for them and only the reference is kept in the buffer. Other implementations or software resource types, especially distributed resources that require data transfer over space (i.e., communication) may deal with the entire item. Values: Items Are References: The software resource holds only pointers to the items (e.g., connections in a connection pool. Items Are Copies: The software resources transfers entire items, i.e., the items are copied from one place to another (e.g., packets in a communication).None TRANSLATABLE= true
ValueMapstring0, 2, 3, 4..32767, 32768..65535None None
ValuesstringUnknown, Items Are References, Items Are Copies, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
Captionstring
DescriptionstringThe Caption property is a short textual description (one- line string) of the object.None TRANSLATABLE= true
MaxLenuint3264None None
CommunicationStatusuint16
DescriptionstringCommunicationStatus indicates the ability of the instrumentation to communicate with the underlying ManagedElement. CommunicationStatus consists of one of the following values: Unknown, None, Communication OK, Lost Communication, or No Contact. A Null return indicates the implementation (provider) does not implement this property. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "Communication OK " indicates communication is established with the element, but does not convey any quality of service. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the Managed Element is known to exist and has been contacted successfully in the past, but is currently unreachable.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
ValueMapstring0, 1, 2, 3, 4, .., 0x8000..None None
ValuesstringUnknown, Not Available, Communication OK, Lost Communication, No Contact, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
Descriptionstring
DescriptionstringThe Description property provides a textual description of the object.None TRANSLATABLE= true
DetailedStatusuint16
DescriptionstringDetailedStatus compliments PrimaryStatus with additional status detail. It consists of one of the following values: Not Available, No Additional Information, Stressed, Predictive Failure, Error, Non-Recoverable Error, SupportingEntityInError. Detailed status is used to expand upon the PrimaryStatus of the element. A Null return indicates the implementation (provider) does not implement this property. "Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "No Additional Information" indicates that the element is functioning normally as indicated by PrimaryStatus = "OK". "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. "Predictive Failure" indicates that an element is functioning normally but a failure is predicted in the near future. "Non-Recoverable Error " indicates that this element is in an error condition that requires human intervention. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
ModelCorrespondencestringCIM_EnabledLogicalElement.PrimaryStatus, CIM_ManagedSystemElement.HealthStateNone None
ValueMapstring0, 1, 2, 3, 4, 5, .., 0x8000..None None
ValuesstringNot Available, No Additional Information, Stressed, Predictive Failure, Non-Recoverable Error, Supporting Entity in Error, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
ElementNamestring
DescriptionstringA 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 the Name property of ManagedSystemElement 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 can be present in both the Name and ElementName properties.None TRANSLATABLE= true
EnabledDefaultuint16
DescriptionstringAn enumerated value indicating an administrator's default or startup configuration for the Enabled State of an element. By default, the element is "Enabled" (value=2).None TRANSLATABLE= true
ValueMapstring2, 3, 5, 6, 7, 9, .., 32768..65535None None
ValuesstringEnabled, Disabled, Not Applicable, Enabled but Offline, No Default, Quiesce, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
WritebooleantrueNone None
EnabledStateuint16
DescriptionstringEnabledState is an integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, shutting down (value=4) and starting (value=10) are transient states between enabled and disabled. The following text briefly summarizes the various enabled and disabled states: Enabled (2) indicates that the element is or could be executing commands, will process any queued commands, and queues new requests. Disabled (3) indicates that the element will not execute commands and will drop any new requests. Shutting Down (4) indicates that the element is in the process of going to a Disabled state. Not Applicable (5) indicates the element does not support being enabled or disabled. Enabled but Offline (6) indicates that the element might be completing commands, and will drop any new requests. Test (7) indicates that the element is in a test state. Deferred (8) indicates that the element might be completing commands, but will queue any new requests. Quiesce (9) indicates that the element is enabled but in a restricted mode. Starting (10) indicates that the element is in the process of going to an Enabled state. New requests are queued.None TRANSLATABLE= true
ModelCorrespondencestringCIM_EnabledLogicalElement.OtherEnabledStateNone None
ValueMapstring0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11..32767, 32768..65535None None
ValuesstringUnknown, Other, Enabled, Disabled, Shutting Down, Not Applicable, Enabled but Offline, In Test, Deferred, Quiesce, Starting, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
Generationuint64
DescriptionstringGeneration is an optional, monotonically increasing property that may be used to identify a particular generation of the resource represented by this class. If Generation is supported by the implementation, its value shall not be null. Except as otherwise specified, a value (including null) of Generation specified at creation time shall be replaced by null if Generation is not supported by the implementation or shall be a, (possibly different), non-null value if the implementation does support Generation. After creation and if supported, Generation shall be updated, at least once per access, whenever the represented resource is modified, regardless of the source of the modification. Note: the Generation value only needs to be updated once between references, even if the resource is updated many times. The key point is to assure that it will be different if there have been updates, not to count each update. Note: unless otherwise specified, the value of Generation within one instance is not required to be coordinated with the value of Generation in any other instance. Note:the semantics of the instance, (as defined by its creation class), define the underlying resource. That underlying resource may be a collection or aggregation of resources. And, in that case, the semantics of the instance further define when updates to constituent resources also require updates to the Generation of the collective resource. Default behavior of composite aggregations should be to update the Generation of the composite whenever the Generation of a component is updated. Subclasses may define additional requirements for updates on some or all of related instances. For a particular instance, the value of Generation may wrap through zero, but the elapsed time between wraps shall be greater than 10's of years. This class does not require Generation to be unique across instances of other classes nor across instances of the same class that have different keys. Generation shall be different across power cycles, resets, or reboots if any of those actions results in an update. Generation may be different across power cycles, resets, or reboots if those actions do not result in an update. If the Generation property of an instance is non-null, and if any attempt to update the instance includes the Generation property, then if it doesn't match the current value, the update shall fail. The usage of this property is intended to be further specified by applicable management profiles. Typically, a client will read the value of this property and then supply that value as input to an operation that modifies the instance in some means. This may be via an explicit parameter in an extrinsic method or via an embedded value in an extrinsic method or intrinsic operation. For example: a profile may require that an intrinsic instance modification supply the Generation property and that it must match for the modification to succeed.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
HealthStateuint16
DescriptionstringIndicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The possible values are 0 to 30, where 5 means the element is entirely healthy and 30 means the element is completely non-functional. The following continuum is defined: "Non-recoverable Error" (30) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. "Critical Failure" (25) - The element is non-functional and recovery might not be possible. "Major Failure" (20) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. "Minor Failure" (15) - All functionality is available but some might be degraded. "Degraded/Warning" (10) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. "OK" (5) - The element is fully functional and is operating within normal operational parameters and without error. "Unknown" (0) - The implementation cannot report on HealthState at this time. DMTF has reserved the unused portion of the continuum for additional HealthStates in the future.None TRANSLATABLE= true
ValueMapstring0, 5, 10, 15, 20, 25, 30, ..None None
ValuesstringUnknown, OK, Degraded/Warning, Minor failure, Major failure, Critical failure, Non-recoverable error, DMTF ReservedNone TRANSLATABLE= true
InstallDatedatetime
DescriptionstringA datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.None TRANSLATABLE= true
MappingStringsstringMIF.DMTF|ComponentID|001.5None None
InstanceIDstring
DescriptionstringWithin the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order 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 creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority. (This 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 re-used to identify different underlying (real-world) elements. If the above 'preferred' algorithm is not used, the defining entity MUST assure that the resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance's NameSpace. For DMTF defined instances, the 'preferred' algorithm MUST be used with the <OrgID> set to 'CIM'.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
OverridestringInstanceIDTOSUBCLASS= falseNone
IsAspectuint16
DescriptionstringIsAspect indicates whether the instance of this software resource refers to another entity residing outside the - software that implements the resource. This knowledge should kept into account in order to solve control conflicts. The property value is 'IsAspect' if the instrumentation knows that there is a corresponding outside managed entity, e.g., a file that corresponds to this software resource. Values: Is Aspect: The instance of the software resource is an aspect. The logically identical entity external to the software (e.g., a file) is known to exist. Is not Aspect: The instance of the software resource is not an aspect. No logically identical entity external to the software (e.g., likely in the case of a buffer) is known to exist.None TRANSLATABLE= true
ValueMapstring0, 2, 3, 4..32767, 32768..65535None None
ValuesstringUnknown, Is Aspect, Is not Aspect, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
Namestring
DescriptionstringThe Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property.None TRANSLATABLE= true
MaxLenuint321024None None
OperatingStatusuint16
DescriptionstringOperatingStatus provides a current status value for the operational condition of the element and can be used for providing more detail with respect to the value of EnabledState. It can also provide the transitional states when an element is transitioning from one state to another, such as when an element is transitioning between EnabledState and RequestedState, as well as other transitional conditions. OperatingStatus consists of one of the following values: Unknown, Not Available, In Service, Starting, Stopping, Stopped, Aborted, Dormant, Completed, Migrating, Emmigrating, Immigrating, Snapshotting. Shutting Down, In Test A Null return indicates the implementation (provider) does not implement this property. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "None" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "Servicing" describes an element being configured, maintained, cleaned, or otherwise administered. "Starting" describes an element being initialized. "Stopping" describes an element being brought to an orderly stop. "Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded in the PrimaryStatus so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Migrating" element is being moved between host elements. "Immigrating" element is being moved to new host element. "Emigrating" element is being moved away from host element. "Shutting Down" describes an element being brought to an abrupt stop. "In Test" element is performing test functions. "Transitioning" describes an element that is between states, that is, it is not fully available in either its previous state or its next state. This value should be used if other values indicating a transition to a specific state are not applicable. "In Service" describes an element that is in service and operational.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
ModelCorrespondencestringCIM_EnabledLogicalElement.EnabledStateNone None
ValueMapstring0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, .., 0x8000..None None
ValuesstringUnknown, Not Available, Servicing, Starting, Stopping, Stopped, Aborted, Dormant, Completed, Migrating, Emigrating, Immigrating, Snapshotting, Shutting Down, In Test, Transitioning, In Service, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
OperationalStatusuint16
ArrayTypestringIndexedNone OVERRIDABLE= false
DescriptionstringIndicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. However, a few are not and are described here in more detail. "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. "Predictive Failure" indicates that an element is functioning nominally but predicting a failure in the near future. "In Service" describes an element being configured, maintained, cleaned, or otherwise administered. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. "Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Power Mode" indicates that the element has additional power model information contained in the Associated PowerManagementService association. OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today's environment to the future. This change was not made earlier because it required the deprecated qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly recommended that providers or instrumentation provide both the Status and OperationalStatus properties. Further, the first value of OperationalStatus should contain the primary status for the element. When instrumented, Status (because it is single-valued) should also provide the primary status of the element.None TRANSLATABLE= true
ModelCorrespondencestringCIM_ManagedSystemElement.StatusDescriptionsNone None
ValueMapstring0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..None None
ValuesstringUnknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
OtherEnabledStatestring
DescriptionstringA string that describes the enabled or disabled state of the element when the EnabledState property is set to 1 ("Other"). This property must be set to null when EnabledState is any value other than 1.None TRANSLATABLE= true
ModelCorrespondencestringCIM_EnabledLogicalElement.EnabledStateNone None
PrimaryStatusuint16
DescriptionstringPrimaryStatus provides a high level status value, intended to align with Red-Yellow-Green type representation of status. It should be used in conjunction with DetailedStatus to provide high level and detailed health status of the ManagedElement and its subcomponents. PrimaryStatus consists of one of the following values: Unknown, OK, Degraded or Error. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "OK" indicates the ManagedElement is functioning normally. "Degraded" indicates the ManagedElement is functioning below normal. "Error" indicates the ManagedElement is in an Error condition.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
ModelCorrespondencestringCIM_ManagedSystemElement.DetailedStatus, CIM_ManagedSystemElement.HealthStateNone None
ValueMapstring0, 1, 2, 3, .., 0x8000..None None
ValuesstringUnknown, OK, Degraded, Error, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
RequestedStateuint16
DescriptionstringRequestedState is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by EnabledState. This property is provided to compare the last requested and current enabled or disabled states. Note that when EnabledState is set to 5 ("Not Applicable"), then this property has no meaning. Refer to the EnabledState property description for explanations of the values in the RequestedState enumeration. "Unknown" (0) indicates the last requested state for the element is unknown. Note that the value "No Change" (5) has been deprecated in lieu of indicating the last requested state is "Unknown" (0). If the last requested or desired state is unknown, RequestedState should have the value "Unknown" (0), but may have the value "No Change" (5).Offline (6) indicates that the element has been requested to transition to the Enabled but Offline EnabledState. It should be noted that there are two new values in RequestedState that build on the statuses of EnabledState. These are "Reboot" (10) and "Reset" (11). Reboot refers to doing a "Shut Down" and then moving to an "Enabled" state. Reset indicates that the element is first "Disabled" and then "Enabled". The distinction between requesting "Shut Down" and "Disabled" should also be noted. Shut Down requests an orderly transition to the Disabled state, and might involve removing power, to completely erase any existing state. The Disabled state requests an immediate disabling of the element, such that it will not execute or accept any commands or processing requests. This property is set as the result of a method invocation (such as Start or StopService on CIM_Service), or can be overridden and defined as WRITEable in a subclass. The method approach is considered superior to a WRITEable property, because it allows an explicit invocation of the operation and the return of a result code. If knowledge of the last RequestedState is not supported for the EnabledLogicalElement, the property shall be NULL or have the value 12 "Not Applicable".None TRANSLATABLE= true
ModelCorrespondencestringCIM_EnabledLogicalElement.EnabledStateNone None
ValueMapstring0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, .., 32768..65535None None
ValuesstringUnknown, Enabled, Disabled, Shut Down, No Change, Offline, Test, Deferred, Quiesce, Reboot, Reset, Not Applicable, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
SoftwareResourceTypeuint16
DescriptionstringThe type of the software resource. Although the behavior of the different software resource types is modeled similarly, different names for resources transferring data over time or/and space have been established. SoftwareResourceType conveys their original, most common name. Values: Buffer: volatile storage (transfer over time). Queue: transfer over time (the internal FIFO) and often over space (as entry point to a communication link. Both, volatile and persistent versions exit. Protocol Endpoint: transfer over space, entry point to a communication link Remote Interface: A generalized protocol endpoint without a specific protocol. Is a proxy. Pool: A special buffer. Clearly the lower allocation limit is the important limit, i.e., depletion of the pool is a problem. Cache: Another special buffer with an aging algorithm for dropping items held in the cache. File: the simplest form of persistent storage. Database: a more sophisticated form of persistent storage that may consist of several files.None TRANSLATABLE= true
ValueMapstring0, 2, 3, 4, 5, 6, 7, 8, 9, 10..32767, 32768..65535None None
ValuesstringUnknown, Buffer, Queue, Protocol Endpoint, Remote Interface, Pool, Cache, File, Database, DMTF Reserved, Vendor ReservedNone TRANSLATABLE= true
Statusstring
DeprecatedstringCIM_ManagedSystemElement.OperationalStatusTOSUBCLASS= falseNone
DescriptionstringA string indicating the current status of the object. Various operational and non-operational statuses are defined. This property is deprecated in lieu of OperationalStatus, which includes the same semantics in its enumeration. This change is made for 3 reasons: 1) Status is more correctly defined as an array. This definition overcomes the limitation of describing status using a single value, when it is really a multi-valued property (for example, an element might be OK AND Stopped. 2) A MaxLen of 10 is too restrictive and leads to unclear enumerated values. 3) The change to a uint16 data type was discussed when CIM V2.0 was defined. However, existing V1.0 implementations used the string property and did not want to modify their code. Therefore, Status was grandfathered into the Schema. Use of the deprecated qualifier allows the maintenance of the existing property, but also permits an improved definition using OperationalStatus.None TRANSLATABLE= true
MaxLenuint3210None None
ValueMapstringOK, Error, Degraded, Unknown, Pred Fail, Starting, Stopping, Service, Stressed, NonRecover, No Contact, Lost Comm, StoppedNone None
StatusDescriptionsstring
ArrayTypestringIndexedNone OVERRIDABLE= false
DescriptionstringStrings describing the various OperationalStatus array values. For example, if "Stopping" is the value assigned to OperationalStatus, then this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in OperationalStatus.None TRANSLATABLE= true
ModelCorrespondencestringCIM_ManagedSystemElement.OperationalStatusNone None
TimeOfLastStateChangedatetime
DescriptionstringThe date or time when the EnabledState of the element last changed. If the state of the element has not changed and this property is populated, then it must be set to a 0 interval value. If a state change was requested, but rejected or not yet processed, the property must not be updated.None TRANSLATABLE= true
TransitioningToStateuint16
DescriptionstringTransitioningToState indicates the target state to which the instance is transitioning. A value of 5 "No Change" shall indicate that no transition is in progress.A value of 12 "Not Applicable" shall indicate the implementation does not support representing ongoing transitions. A value other than 5 or 12 shall identify the state to which the element is in the process of transitioning.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
ModelCorrespondencestringCIM_EnabledLogicalElement.RequestStateChange, CIM_EnabledLogicalElement.RequestedState, CIM_EnabledLogicalElement.EnabledStateNone None
ValueMapstring0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12None None
ValuesstringUnknown, Enabled, Disabled, Shut Down, No Change, Offline, Test, Defer, Quiesce, Reboot, Reset, Not ApplicableNone TRANSLATABLE= true

Local Class Methods

NameReturn TypeQualifiers
NameData TypeValueScopeFlavors
Reinitialize()uint32
DescriptionstringError situations may sometimes require drastic measures. One of them being the complete re-initialization of an software resource. Re-initialization includes that the resource is emptied entirely and the limit settings are newly applied. Reintialize Already in Progress: software resource still being reinitialized.None TRANSLATABLE= true
ValueMapstring0, 1, 2, 3, 4, 6, 7, 8, 9..32767, 32768..65535None None
ValuesstringSuccess, Not Supported, Unknown, Timeout, Failed, Access Denied, Not Found, Reinitialize already in Progress, DMTF Reserved, Vendor SpecificNone TRANSLATABLE= true

Copyright © 2008-2010 VMware, Inc. All rights reserved.