pcsvDevice.dll.mui PCSV Proxy Provider for devices 6422a55cf89253e4e19ac90a4da364ee

File info

File name: pcsvDevice.dll.mui
Size: 137216 byte
MD5: 6422a55cf89253e4e19ac90a4da364ee
SHA1: c0abbb733e1f7ed90e9fcd7d10fee25c12aff732
SHA256: 0a9e67df8424e37fa5362e664481dbb57e559c580d8afece9d7a28dd4eafa4a3
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in Czech language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id Czech English
1InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below.
To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm:
:
Where and are separated by a colon (:), and where 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 _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and .
is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and 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.
If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.
InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below.
To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm:
:
Where and are separated by a colon (:), and where 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 _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and .
is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and 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.
If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.
2The Caption property is a short textual description (one- line string) of the object. The Caption property is a short textual description (one- line string) of the object.
3The Description property provides a textual description of the object. The Description property provides a textual description of the object.
4A 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. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class.
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 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. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class.
52.19.0 2.19.0
6ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema. ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema.
7View is an abstract class that provides a common superclass for classes providing de-normalized, aggregate representations of managed resources. The definition of each sub-class will include properties propagated from the the graph of classes that are used to model the resource in the normalized view. The classes may be resource classes or associations. The definition of how a value is propagated (i.e. source class and value transformations) is required to be specified.
Sub-classes may be explicitly constrained to be read only. If a sub-class is not constrained as read only, the designers are strongly encouraged to carefully consider the data synchronization and consistencies issues that may result. The ElementView association may be used to find the instances that form the normalized view of the managed resource.
View is an abstract class that provides a common superclass for classes providing de-normalized, aggregate representations of managed resources. The definition of each sub-class will include properties propagated from the the graph of classes that are used to model the resource in the normalized view. The classes may be resource classes or associations. The definition of how a value is propagated (i.e. source class and value transformations) is required to be specified.
Sub-classes may be explicitly constrained to be read only. If a sub-class is not constrained as read only, the designers are strongly encouraged to carefully consider the data synchronization and consistencies issues that may result. The ElementView association may be used to find the instances that form the normalized view of the managed resource.
82.26.0 2.26.0
9A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed. A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.
10The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property. The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property.
11Indicates 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.
Indicates 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.
12Unknown Unknown
13Other Other
14OK OK
15Degraded Degraded
16Stressed Stressed
17Predictive Failure Predictive Failure
18Error Error
19Non-Recoverable Error Non-Recoverable Error
20Starting Starting
21Stopping Stopping
22Stopped Stopped
23In Service In Service
24No Contact No Contact
25Lost Communication Lost Communication
26Aborted Aborted
27Dormant Dormant
28Supporting Entity in Error Supporting Entity in Error
29Completed Completed
30Power Mode Power Mode
31DMTF Reserved DMTF Reserved
32Vendor Reserved Vendor Reserved
33Strings 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. Strings 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.
34A 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.
A 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.
35Indicates 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.
Indicates 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.
36Degraded/Warning Degraded/Warning
37Minor failure Minor failure
38Major failure Major failure
39Critical failure Critical failure
40Non-recoverable error Non-recoverable error
41CommunicationStatus 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.
CommunicationStatus 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.
42Not Available Not Available
43Communication OK Communication OK
44DetailedStatus 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.
DetailedStatus 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.
45No Additional Information No Additional Information
46OperatingStatus 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.
OperatingStatus 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.
47Servicing Servicing
48Migrating Migrating
49Emigrating Emigrating
50Immigrating Immigrating
51Snapshotting Snapshotting
52Shutting Down Shutting Down
53In Test In Test
54Transitioning Transitioning
55PrimaryStatus 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.
PrimaryStatus 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.
56CIM_ManagedSystemElement is the base class for the System Element hierarchy. Any distinguishable component of a System is a candidate for inclusion in this class. Examples of system components include:
- software components such as application servers, databases, and applications
- operating system components such as files, processes, and threads
- device components such as disk drives, controllers, processors, and printers
- physical components such as chips and cards.
CIM_ManagedSystemElement is the base class for the System Element hierarchy. Any distinguishable component of a System is a candidate for inclusion in this class. Examples of system components include:
- software components such as application servers, databases, and applications
- operating system components such as files, processes, and threads
- device components such as disk drives, controllers, processors, and printers
- physical components such as chips and cards.
572.22.0 2.22.0
58CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices. CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices.
592.6.0 2.6.0
60A free-form string that represents the status of the job. The primary status is reflected in the inherited OperationalStatus property. JobStatus provides additional, implementation-specific details. A free-form string that represents the status of the job. The primary status is reflected in the inherited OperationalStatus property. JobStatus provides additional, implementation-specific details.
61The time that the Job was submitted to execute. A value of all zeroes indicates that the owning element is not capable of reporting a date and time. Therefore, the ScheduledStartTime and StartTime are reported as intervals relative to the time their values are requested. The time that the Job was submitted to execute. A value of all zeroes indicates that the owning element is not capable of reporting a date and time. Therefore, the ScheduledStartTime and StartTime are reported as intervals relative to the time their values are requested.
62The time that the current Job is scheduled to start. This time can be represented by the actual date and time, or an interval relative to the time that this property is requested. A value of all zeroes indicates that the Job is already executing. The property is deprecated in lieu of the more expressive scheduling properties, RunMonth, RunDay, RunDayOfWeek, and RunStartInterval. The time that the current Job is scheduled to start. This time can be represented by the actual date and time, or an interval relative to the time that this property is requested. A value of all zeroes indicates that the Job is already executing. The property is deprecated in lieu of the more expressive scheduling properties, RunMonth, RunDay, RunDayOfWeek, and RunStartInterval.
63The time that the Job was actually started. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property. The time that the Job was actually started. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.
64The time interval that the Job has been executing or the total execution time if the Job is complete. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property. The time interval that the Job has been executing or the total execution time if the Job is complete. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.
65The number of times that the Job should be run. A value of 1 indicates that the Job is not recurring, while any non-zero value indicates a limit to the number of times that the Job will recur. Zero indicates that there is no limit to the number of times that the Job can be processed, but that it is terminated either after the UntilTime or by manual intervention. By default, a Job is processed once. The number of times that the Job should be run. A value of 1 indicates that the Job is not recurring, while any non-zero value indicates a limit to the number of times that the Job will recur. Zero indicates that there is no limit to the number of times that the Job can be processed, but that it is terminated either after the UntilTime or by manual intervention. By default, a Job is processed once.
66The month during which the Job should be processed. Specify 0 for January, 1 for February, and so on. The month during which the Job should be processed. Specify 0 for January, 1 for February, and so on.
67January January
68February February
69March March
70April April
71May May
72June June
73July July
74August August
75September September
76October October
77November November
78December December
79The day in the month on which the Job should be processed. There are two different interpretations for this property, depending on the value of DayOfWeek. In one case, RunDay defines the day-in-month on which the Job is processed. This interpretation is used when the DayOfWeek is 0. A positive or negative integer indicates whether the RunDay should be calculated from the beginning or end of the month. For example, 5 indicates the fifth day in the RunMonth and -1 indicates the last day in the RunMonth.

When RunDayOfWeek is not 0, RunDay is the day-in-month on which the Job is processed, defined in conjunction with RunDayOfWeek. For example, if RunDay is 15 and RunDayOfWeek is Saturday, then the Job is processed on the first Saturday on or after the 15th day in the RunMonth (for example, the third Saturday in the month). If RunDay is 20 and RunDayOfWeek is -Saturday, then this indicates the first Saturday on or before the 20th day in the RunMonth. If RunDay is -1 and RunDayOfWeek is -Sunday, then this indicates the last Sunday in the RunMonth.
The day in the month on which the Job should be processed. There are two different interpretations for this property, depending on the value of DayOfWeek. In one case, RunDay defines the day-in-month on which the Job is processed. This interpretation is used when the DayOfWeek is 0. A positive or negative integer indicates whether the RunDay should be calculated from the beginning or end of the month. For example, 5 indicates the fifth day in the RunMonth and -1 indicates the last day in the RunMonth.

When RunDayOfWeek is not 0, RunDay is the day-in-month on which the Job is processed, defined in conjunction with RunDayOfWeek. For example, if RunDay is 15 and RunDayOfWeek is Saturday, then the Job is processed on the first Saturday on or after the 15th day in the RunMonth (for example, the third Saturday in the month). If RunDay is 20 and RunDayOfWeek is -Saturday, then this indicates the first Saturday on or before the 20th day in the RunMonth. If RunDay is -1 and RunDayOfWeek is -Sunday, then this indicates the last Sunday in the RunMonth.
80A positive or negative integer used in conjunction with RunDay to indicate the day of the week on which the Job is processed. RunDayOfWeek is set to 0 to indicate an exact day of the month, such as March 1. A positive integer (representing Sunday, Monday, ..., Saturday) means that the day of week is found on or after the specified RunDay. A negative integer (representing -Sunday, -Monday, ..., -Saturday) means that the day of week is found on or BEFORE the RunDay. A positive or negative integer used in conjunction with RunDay to indicate the day of the week on which the Job is processed. RunDayOfWeek is set to 0 to indicate an exact day of the month, such as March 1. A positive integer (representing Sunday, Monday, ..., Saturday) means that the day of week is found on or after the specified RunDay. A negative integer (representing -Sunday, -Monday, ..., -Saturday) means that the day of week is found on or BEFORE the RunDay.
81-Saturday -Saturday
82-Friday -Friday
83-Thursday -Thursday
84-Wednesday -Wednesday
85-Tuesday -Tuesday
86-Monday -Monday
87-Sunday -Sunday
88ExactDayOfMonth ExactDayOfMonth
89Sunday Sunday
90Monday Monday
91Tuesday Tuesday
92Wednesday Wednesday
93Thursday Thursday
94Friday Friday
95Saturday Saturday
96The time interval after midnight when the Job should be processed. For example,
00000000020000.000000:000
indicates that the Job should be run on or after two o\'clock, local time or UTC time (distinguished using the LocalOrUtcTime property.
The time interval after midnight when the Job should be processed. For example,
00000000020000.000000:000
indicates that the Job should be run on or after two o\'clock, local time or UTC time (distinguished using the LocalOrUtcTime property.
97This property indicates whether the times represented in the RunStartInterval and UntilTime properties represent local times or UTC times. Time values are synchronized worldwide by using the enumeration value 2, "UTC Time". This property indicates whether the times represented in the RunStartInterval and UntilTime properties represent local times or UTC times. Time values are synchronized worldwide by using the enumeration value 2, "UTC Time".
98Local Time Local Time
99UTC Time UTC Time
100The time after which the Job is invalid or should be stopped. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. A value of all nines indicates that the Job can run indefinitely. The time after which the Job is invalid or should be stopped. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. A value of all nines indicates that the Job can run indefinitely.
101The User who is to be notified upon the Job completion or failure. The User who is to be notified upon the Job completion or failure.
102The User that submitted the Job, or the Service or method name that caused the job to be created. The User that submitted the Job, or the Service or method name that caused the job to be created.
103Indicates the urgency or importance of execution of the Job. The lower the number, the higher the priority. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the setting information that would influence the results of a job. Indicates the urgency or importance of execution of the Job. The lower the number, the higher the priority. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the setting information that would influence the results of a job.
104The percentage of the job that has completed at the time that this value is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run data can be stored in this single-valued property.
Note that the value 101 is undefined and will be not be allowed in the next major revision of the specification.
The percentage of the job that has completed at the time that this value is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run data can be stored in this single-valued property.
Note that the value 101 is undefined and will be not be allowed in the next major revision of the specification.
105Percent Percent
106Indicates whether or not the job should be automatically deleted upon completion. Note that the \'completion\' of a recurring job is defined by its JobRunTimes or UntilTime properties, or when the Job is terminated by manual intervention. If this property is set to false and the job completes, then the extrinsic method DeleteInstance must be used to delete the job instead of updating this property. Indicates whether or not the job should be automatically deleted upon completion. Note that the \'completion\' of a recurring job is defined by its JobRunTimes or UntilTime properties, or when the Job is terminated by manual intervention. If this property is set to false and the job completes, then the extrinsic method DeleteInstance must be used to delete the job instead of updating this property.
107A vendor-specific error code. The value must be set to zero if the Job completed without error. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property. A vendor-specific error code. The value must be set to zero if the Job completed without error. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.
108A free-form string that contains the vendor error description. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property. A free-form string that contains the vendor error description. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.
109Describes the recovery action to be taken for an unsuccessfully run Job. The possible values are:
0 = "Unknown", meaning it is unknown as to what recovery action to take
1 = "Other", indicating that the recovery action will be specified in the OtherRecoveryAction property
2 = "Do Not Continue", meaning stop the execution of the job and appropriately update its status
3 = "Continue With Next Job", meaning continue with the next job in the queue
4 = "Re-run Job", indicating that the job should be re-run
5 = "Run Recovery Job", meaning run the Job associated using the RecoveryJob relationship. Note that the recovery Job must already be in the queue from which it will run.
Describes the recovery action to be taken for an unsuccessfully run Job. The possible values are:
0 = "Unknown", meaning it is unknown as to what recovery action to take
1 = "Other", indicating that the recovery action will be specified in the OtherRecoveryAction property
2 = "Do Not Continue", meaning stop the execution of the job and appropriately update its status
3 = "Continue With Next Job", meaning continue with the next job in the queue
4 = "Re-run Job", indicating that the job should be re-run
5 = "Run Recovery Job", meaning run the Job associated using the RecoveryJob relationship. Note that the recovery Job must already be in the queue from which it will run.
110Do Not Continue Do Not Continue
111Continue With Next Job Continue With Next Job
112Re-run Job Re-run Job
113Run Recovery Job Run Recovery Job
114A string describing the recovery action when the RecoveryAction property of the instance is 1 ("Other"). A string describing the recovery action when the RecoveryAction property of the instance is 1 ("Other").
115KillJob is being deprecated because there is no distinction made between an orderly shutdown and an immediate kill. CIM_ConcreteJob.RequestStateChange() provides \'Terminate\' and \'Kill\' options to allow this distinction.
A method to kill this job and any underlying processes, and to remove any \'dangling\' associations.
KillJob is being deprecated because there is no distinction made between an orderly shutdown and an immediate kill. CIM_ConcreteJob.RequestStateChange() provides \'Terminate\' and \'Kill\' options to allow this distinction.
A method to kill this job and any underlying processes, and to remove any \'dangling\' associations.
116Success Success
117Not Supported Not Supported
118Timeout Timeout
119Failed Failed
120Access Denied Access Denied
121Not Found Not Found
122Vendor Specific Vendor Specific
123Indicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion. Indicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion.
124A Job is a LogicalElement that represents an executing unit of work, such as a script or a print job. A Job is distinct from a Process in that a Job can be scheduled or queued, and its execution is not limited to a single system. A Job is a LogicalElement that represents an executing unit of work, such as a script or a print job. A Job is distinct from a Process in that a Job can be scheduled or queued, and its execution is not limited to a single system.
1252.10.0 2.10.0
126Primary classification of the error. The following values are defined:
2 - Communications Error. Errors of this type are principally associated with the procedures and/or processes required to convey information from one point to another.
3 - Quality of Service Error. Errors of this type are principally associated with failures that result in reduced functionality or performance.
4 - Software Error. Error of this type are principally associated with a software or processing fault.
5 - Hardware Error. Errors of this type are principally associated with an equipment or hardware failure.
6 - Environmental Error. Errors of this type are principally associated with a failure condition relating the to facility, or other environmental considerations.
7 - Security Error. Errors of this type are associated with security violations, detection of viruses, and similar issues.
8 - Oversubscription Error. Errors of this type are principally associated with the failure to allocate sufficient resources to complete the operation.
9 - Unavailable Resource Error. Errors of this type are principally associated with the failure to access a required resource.
10 -Unsupported Operation Error. Errors of this type are principally associated with requests that are not supported.
Primary classification of the error. The following values are defined:
2 - Communications Error. Errors of this type are principally associated with the procedures and/or processes required to convey information from one point to another.
3 - Quality of Service Error. Errors of this type are principally associated with failures that result in reduced functionality or performance.
4 - Software Error. Error of this type are principally associated with a software or processing fault.
5 - Hardware Error. Errors of this type are principally associated with an equipment or hardware failure.
6 - Environmental Error. Errors of this type are principally associated with a failure condition relating the to facility, or other environmental considerations.
7 - Security Error. Errors of this type are associated with security violations, detection of viruses, and similar issues.
8 - Oversubscription Error. Errors of this type are principally associated with the failure to allocate sufficient resources to complete the operation.
9 - Unavailable Resource Error. Errors of this type are principally associated with the failure to access a required resource.
10 -Unsupported Operation Error. Errors of this type are principally associated with requests that are not supported.
127Communications Error Communications Error
128Quality of Service Error Quality of Service Error
129Software Error Software Error
130Hardware Error Hardware Error
131Environmental Error Environmental Error
132Security Error Security Error
133Oversubscription Error Oversubscription Error
134Unavailable Resource Error Unavailable Resource Error
135Unsupported Operation Error Unsupported Operation Error
136A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType. A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.
137A string that uniquely identifies the entity that owns the definition of the format of the Message described in this instance. OwningEntity MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or standards body defining the format. A string that uniquely identifies the entity that owns the definition of the format of the Message described in this instance. OwningEntity MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or standards body defining the format.
138An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message. An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.
139The formatted message. This message is constructed by combining some or all of the dynamic elements specified in the MessageArguments property with the static elements uniquely identified by the MessageID in a message registry or other catalog associated with the OwningEntity. The formatted message. This message is constructed by combining some or all of the dynamic elements specified in the MessageArguments property with the static elements uniquely identified by the MessageID in a message registry or other catalog associated with the OwningEntity.
140An array containing the dynamic content of the message. An array containing the dynamic content of the message.
141An enumerated value that describes the severity of the Indication from the notifier\'s point of view:
0 - the Perceived Severity of the indication is unknown or indeterminate.
1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property.
2 - Information should be used when providing an informative response.
3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed.
4 - Minor should be used to indicate action is needed, but the situation is not serious at this time.
5 - Major should be used to indicate action is needed NOW.
6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result).
7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it\'s too late to take remedial action.
2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the Error is purely informational or its severity is simply unknown.
An enumerated value that describes the severity of the Indication from the notifier\'s point of view:
0 - the Perceived Severity of the indication is unknown or indeterminate.
1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property.
2 - Information should be used when providing an informative response.
3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed.
4 - Minor should be used to indicate action is needed, but the situation is not serious at this time.
5 - Major should be used to indicate action is needed NOW.
6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result).
7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it\'s too late to take remedial action.
2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the Error is purely informational or its severity is simply unknown.
142Information Information
143Minor Minor
144Major Major
145Critical Critical
146Fatal/NonRecoverable Fatal/NonRecoverable
147An enumerated value that describes the probable cause of the error. An enumerated value that describes the probable cause of the error.
148Adapter/Card Error Adapter/Card Error
149Application Subsystem Failure Application Subsystem Failure
150Bandwidth Reduced Bandwidth Reduced
151Connection Establishment Error Connection Establishment Error
152Communications Protocol Error Communications Protocol Error
153Communications Subsystem Failure Communications Subsystem Failure
154Configuration/Customization Error Configuration/Customization Error
155Congestion Congestion
156Corrupt Data Corrupt Data
157CPU Cycles Limit Exceeded CPU Cycles Limit Exceeded
158Dataset/Modem Error Dataset/Modem Error
159Degraded Signal Degraded Signal
160DTE-DCE Interface Error DTE-DCE Interface Error
161Enclosure Door Open Enclosure Door Open
162Equipment Malfunction Equipment Malfunction
163Excessive Vibration Excessive Vibration
164File Format Error File Format Error
165Fire Detected Fire Detected
166Flood Detected Flood Detected
167Framing Error Framing Error
168HVAC Problem HVAC Problem
169Humidity Unacceptable Humidity Unacceptable
170I/O Device Error I/O Device Error
171Input Device Error Input Device Error
172LAN Error LAN Error
173Non-Toxic Leak Detected Non-Toxic Leak Detected
174Local Node Transmission Error Local Node Transmission Error
175Loss of Frame Loss of Frame
176Loss of Signal Loss of Signal
177Material Supply Exhausted Material Supply Exhausted
178Multiplexer Problem Multiplexer Problem
179Out of Memory Out of Memory
180Output Device Error Output Device Error
181Performance Degraded Performance Degraded
182Power Problem Power Problem
183Pressure Unacceptable Pressure Unacceptable
184Processor Problem (Internal Machine Error) Processor Problem (Internal Machine Error)
185Pump Failure Pump Failure
186Queue Size Exceeded Queue Size Exceeded
187Receive Failure Receive Failure
188Receiver Failure Receiver Failure
189Remote Node Transmission Error Remote Node Transmission Error
190Resource at or Nearing Capacity Resource at or Nearing Capacity
191Response Time Excessive Response Time Excessive
192Retransmission Rate Excessive Retransmission Rate Excessive
193Software Program Abnormally Terminated Software Program Abnormally Terminated
194Software Program Error (Incorrect Results) Software Program Error (Incorrect Results)
195Storage Capacity Problem Storage Capacity Problem
196Temperature Unacceptable Temperature Unacceptable
197Threshold Crossed Threshold Crossed
198Timing Problem Timing Problem
199Toxic Leak Detected Toxic Leak Detected
200Transmit Failure Transmit Failure
201Transmitter Failure Transmitter Failure
202Underlying Resource Unavailable Underlying Resource Unavailable
203Version Mismatch Version Mismatch
204Previous Alert Cleared Previous Alert Cleared
205Login Attempts Failed Login Attempts Failed
206Software Virus Detected Software Virus Detected
207Hardware Security Breached Hardware Security Breached
208Denial of Service Detected Denial of Service Detected
209Security Credential Mismatch Security Credential Mismatch
210Unauthorized Access Unauthorized Access
211Alarm Received Alarm Received
212Loss of Pointer Loss of Pointer
213Payload Mismatch Payload Mismatch
214Transmission Error Transmission Error
215Excessive Error Rate Excessive Error Rate
216Trace Problem Trace Problem
217Element Unavailable Element Unavailable
218Element Missing Element Missing
219Loss of Multi Frame Loss of Multi Frame
220Broadcast Channel Failure Broadcast Channel Failure
221Invalid Message Received Invalid Message Received
222Routing Failure Routing Failure
223Backplane Failure Backplane Failure
224Identifier Duplication Identifier Duplication
225Protection Path Failure Protection Path Failure
226Sync Loss or Mismatch Sync Loss or Mismatch
227Terminal Problem Terminal Problem
228Real Time Clock Failure Real Time Clock Failure
229Antenna Failure Antenna Failure
230Battery Charging Failure Battery Charging Failure
231Disk Failure Disk Failure
232Frequency Hopping Failure Frequency Hopping Failure
233Loss of Redundancy Loss of Redundancy
234Power Supply Failure Power Supply Failure
235Signal Quality Problem Signal Quality Problem
236Battery Discharging Battery Discharging
237Battery Failure Battery Failure
238Commercial Power Problem Commercial Power Problem
239Fan Failure Fan Failure
240Engine Failure Engine Failure
241Sensor Failure Sensor Failure
242Fuse Failure Fuse Failure
243Generator Failure Generator Failure
244Low Battery Low Battery
245Low Fuel Low Fuel
246Low Water Low Water
247Explosive Gas Explosive Gas
248High Winds High Winds
249Ice Buildup Ice Buildup
250Smoke Smoke
251Memory Mismatch Memory Mismatch
252Out of CPU Cycles Out of CPU Cycles
253Software Environment Problem Software Environment Problem
254Software Download Failure Software Download Failure
255Element Reinitialized Element Reinitialized
256Logging Problems Logging Problems
257Leak Detected Leak Detected
258Protection Mechanism Failure Protection Mechanism Failure
259Protecting Resource Failure Protecting Resource Failure
260Database Inconsistency Database Inconsistency
261Authentication Failure Authentication Failure
262Breach of Confidentiality Breach of Confidentiality
263Cable Tamper Cable Tamper
264Delayed Information Delayed Information
265Duplicate Information Duplicate Information
266Information Missing Information Missing
267Information Modification Information Modification
268Information Out of Sequence Information Out of Sequence
269Key Expired Key Expired
270Non-Repudiation Failure Non-Repudiation Failure
271Out of Hours Activity Out of Hours Activity
272Out of Service Out of Service
273Procedural Error Procedural Error
274Unexpected Information Unexpected Information
275A free-form string describing the probable cause of the error. A free-form string describing the probable cause of the error.
276A free-form string describing recommended actions to take to resolve the error. A free-form string describing recommended actions to take to resolve the error.
277The identifying information of the entity (i.e., the instance) generating the error. If this entity is modeled in the CIM Schema, this property contains the path of the instance encoded as a string parameter. If not modeled, the property contains some identifying string that names the entity that generated the error. The path or identifying string is formatted per the ErrorSourceFormat property. The identifying information of the entity (i.e., the instance) generating the error. If this entity is modeled in the CIM Schema, this property contains the path of the instance encoded as a string parameter. If not modeled, the property contains some identifying string that names the entity that generated the error. The path or identifying string is formatted per the ErrorSourceFormat property.
278The format of the ErrorSource property is interpretable based on the value of this property. Values are defined as:
0 - Unknown. The format is unknown or not meaningfully interpretable by a CIM client application.
1 - Other. The format is defined by the value of the OtherErrorSourceFormat property.2 - CIMObjectPath. A CIM Object Path as defined in the CIM Infrastructure specification. Note: CIM 2.5 and earlier used the term object names.
The format of the ErrorSource property is interpretable based on the value of this property. Values are defined as:
0 - Unknown. The format is unknown or not meaningfully interpretable by a CIM client application.
1 - Other. The format is defined by the value of the OtherErrorSourceFormat property.2 - CIMObjectPath. A CIM Object Path as defined in the CIM Infrastructure specification. Note: CIM 2.5 and earlier used the term object names.
279CIMObjectPath CIMObjectPath
280A string defining "Other" values for ErrorSourceFormat. This value MUST be set to a non NULL value when ErrorSourceFormat is set to a value of 1 ("Other"). For all other values of ErrorSourceFormat, the value of this string must be set to NULL. A string defining "Other" values for ErrorSourceFormat. This value MUST be set to a non NULL value when ErrorSourceFormat is set to a value of 1 ("Other"). For all other values of ErrorSourceFormat, the value of this string must be set to NULL.
281The CIM status code that characterizes this instance.
This property defines the status codes that MAY be return by a conforming CIM Server or Listener. Note that not all status codes are valid for each operation. The specification for each operation SHOULD define the status codes that may be returned by that operation.
The following values for CIM status code are defined:
1 - CIM_ERR_FAILED. A general error occurred that is not covered by a more specific error code.
2 - CIM_ERR_ACCESS_DENIED. Access to a CIM resource was not available to the client.
3 - CIM_ERR_INVALID_NAMESPACE. The target namespace does not exist.
4 - CIM_ERR_INVALID_PARAMETER. One or more parameter values passed to the method were invalid.
5 - CIM_ERR_INVALID_CLASS. The specified Class does not exist.
6 - CIM_ERR_NOT_FOUND. The requested object could not be found.
7 - CIM_ERR_NOT_SUPPORTED. The requested operation is not supported.
8 - CIM_ERR_CLASS_HAS_CHILDREN. Operation cannot be carried out on this class since it has instances.
9 - CIM_ERR_CLASS_HAS_INSTANCES. Operation cannot be carried out on this class since it has instances.
10 - CIM_ERR_INVALID_SUPERCLASS. Operation cannot be carried out since the specified superclass does not exist.
11 - CIM_ERR_ALREADY_EXISTS. Operation cannot be carried out because an object already exists.
12 - CIM_ERR_NO_SUCH_PROPERTY. The specified Property does not exist.
13 - CIM_ERR_TYPE_MISMATCH. The value supplied is incompatible with the type.
14 - CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED. The query language is not recognized or supported.
15 - CIM_ERR_INVALID_QUERY. The query is not valid for the specified query language.
16 - CIM_ERR_METHOD_NOT_AVAILABLE. The extrinsic Method could not be executed.
17 - CIM_ERR_METHOD_NOT_FOUND. The specified extrinsic Method does not exist.
18 - CIM_ERR_UNEXPECTED_RESPONSE. The returned response to the asynchronous operation was not expected.
19 - CIM_ERR_INVALID_RESPONSE_DESTINATION. The specified destination for the asynchronous response is not valid.
20 - CIM_ERR_NAMESPACE_NOT_EMPTY. The specified Namespace is not empty.
21 - CIM_ERR_INVALID_ENUMERATION_CONTEXT. The enumeration context supplied is not valid.
22 - CIM_ERR_INVALID_OPERATION_TIMEOUT. The specified Namespace is not empty.
23 - CIM_ERR_PULL_HAS_BEEN_ABANDONED. The specified Namespace is not empty.
24 - CIM_ERR_PULL_CANNOT_BE_ABANDONED. The attempt to abandon a pull operation has failed.
25 - CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED. Filtered Enumeratrions are not supported.
26 - CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED. Continue on error is not supported.
27 - CIM_ERR_SERVER_LIMITS_EXCEEDED. The WBEM Server limits have been exceeded (e.g. memory, connections, ...).
28 - CIM_ERR_SERVER_IS_SHUTTING_DOWN. The WBEM Server is shutting down.
29 - CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED. The specified Query Feature is not supported.
The CIM status code that characterizes this instance.
This property defines the status codes that MAY be return by a conforming CIM Server or Listener. Note that not all status codes are valid for each operation. The specification for each operation SHOULD define the status codes that may be returned by that operation.
The following values for CIM status code are defined:
1 - CIM_ERR_FAILED. A general error occurred that is not covered by a more specific error code.
2 - CIM_ERR_ACCESS_DENIED. Access to a CIM resource was not available to the client.
3 - CIM_ERR_INVALID_NAMESPACE. The target namespace does not exist.
4 - CIM_ERR_INVALID_PARAMETER. One or more parameter values passed to the method were invalid.
5 - CIM_ERR_INVALID_CLASS. The specified Class does not exist.
6 - CIM_ERR_NOT_FOUND. The requested object could not be found.
7 - CIM_ERR_NOT_SUPPORTED. The requested operation is not supported.
8 - CIM_ERR_CLASS_HAS_CHILDREN. Operation cannot be carried out on this class since it has instances.
9 - CIM_ERR_CLASS_HAS_INSTANCES. Operation cannot be carried out on this class since it has instances.
10 - CIM_ERR_INVALID_SUPERCLASS. Operation cannot be carried out since the specified superclass does not exist.
11 - CIM_ERR_ALREADY_EXISTS. Operation cannot be carried out because an object already exists.
12 - CIM_ERR_NO_SUCH_PROPERTY. The specified Property does not exist.
13 - CIM_ERR_TYPE_MISMATCH. The value supplied is incompatible with the type.
14 - CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED. The query language is not recognized or supported.
15 - CIM_ERR_INVALID_QUERY. The query is not valid for the specified query language.
16 - CIM_ERR_METHOD_NOT_AVAILABLE. The extrinsic Method could not be executed.
17 - CIM_ERR_METHOD_NOT_FOUND. The specified extrinsic Method does not exist.
18 - CIM_ERR_UNEXPECTED_RESPONSE. The returned response to the asynchronous operation was not expected.
19 - CIM_ERR_INVALID_RESPONSE_DESTINATION. The specified destination for the asynchronous response is not valid.
20 - CIM_ERR_NAMESPACE_NOT_EMPTY. The specified Namespace is not empty.
21 - CIM_ERR_INVALID_ENUMERATION_CONTEXT. The enumeration context supplied is not valid.
22 - CIM_ERR_INVALID_OPERATION_TIMEOUT. The specified Namespace is not empty.
23 - CIM_ERR_PULL_HAS_BEEN_ABANDONED. The specified Namespace is not empty.
24 - CIM_ERR_PULL_CANNOT_BE_ABANDONED. The attempt to abandon a pull operation has failed.
25 - CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED. Filtered Enumeratrions are not supported.
26 - CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED. Continue on error is not supported.
27 - CIM_ERR_SERVER_LIMITS_EXCEEDED. The WBEM Server limits have been exceeded (e.g. memory, connections, ...).
28 - CIM_ERR_SERVER_IS_SHUTTING_DOWN. The WBEM Server is shutting down.
29 - CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED. The specified Query Feature is not supported.
282CIM_ERR_FAILED CIM_ERR_FAILED
283CIM_ERR_ACCESS_DENIED CIM_ERR_ACCESS_DENIED
284CIM_ERR_INVALID_NAMESPACE CIM_ERR_INVALID_NAMESPACE
285CIM_ERR_INVALID_PARAMETER CIM_ERR_INVALID_PARAMETER
286CIM_ERR_INVALID_CLASS CIM_ERR_INVALID_CLASS
287CIM_ERR_NOT_FOUND CIM_ERR_NOT_FOUND
288CIM_ERR_NOT_SUPPORTED CIM_ERR_NOT_SUPPORTED
289CIM_ERR_CLASS_HAS_CHILDREN CIM_ERR_CLASS_HAS_CHILDREN
290CIM_ERR_CLASS_HAS_INSTANCES CIM_ERR_CLASS_HAS_INSTANCES
291CIM_ERR_INVALID_SUPERCLASS CIM_ERR_INVALID_SUPERCLASS
292CIM_ERR_ALREADY_EXISTS CIM_ERR_ALREADY_EXISTS
293CIM_ERR_NO_SUCH_PROPERTY CIM_ERR_NO_SUCH_PROPERTY
294CIM_ERR_TYPE_MISMATCH CIM_ERR_TYPE_MISMATCH
295CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED
296CIM_ERR_INVALID_QUERY CIM_ERR_INVALID_QUERY
297CIM_ERR_METHOD_NOT_AVAILABLE CIM_ERR_METHOD_NOT_AVAILABLE
298CIM_ERR_METHOD_NOT_FOUND CIM_ERR_METHOD_NOT_FOUND
299CIM_ERR_UNEXPECTED_RESPONSE CIM_ERR_UNEXPECTED_RESPONSE
300CIM_ERR_INVALID_RESPONSE_DESTINATION CIM_ERR_INVALID_RESPONSE_DESTINATION
301CIM_ERR_NAMESPACE_NOT_EMPTY CIM_ERR_NAMESPACE_NOT_EMPTY
302CIM_ERR_INVALID_ENUMERATION_CONTEXT CIM_ERR_INVALID_ENUMERATION_CONTEXT
303CIM_ERR_INVALID_OPERATION_TIMEOUT CIM_ERR_INVALID_OPERATION_TIMEOUT
304CIM_ERR_PULL_HAS_BEEN_ABANDONED CIM_ERR_PULL_HAS_BEEN_ABANDONED
305CIM_ERR_PULL_CANNOT_BE_ABANDONED CIM_ERR_PULL_CANNOT_BE_ABANDONED
306CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED
307CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED
308CIM_ERR_SERVER_LIMITS_EXCEEDED CIM_ERR_SERVER_LIMITS_EXCEEDED
309CIM_ERR_SERVER_IS_SHUTTING_DOWN CIM_ERR_SERVER_IS_SHUTTING_DOWN
310CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED
311A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode. A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode.
3122.22.1 2.22.1
313CIM_Error is a specialized class that contains information about the severity, cause, recommended actions and other data related to the failure of a CIM Operation. Instances of this type MAY be included as part of the response to a CIM Operation. CIM_Error is a specialized class that contains information about the severity, cause, recommended actions and other data related to the failure of a CIM Operation. Instances of this type MAY be included as part of the response to a CIM Operation.
314Within 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:
:
Where and are separated by a colon \':\', and where 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 that is assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness must not contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID must appear between and .
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 resulting InstanceID is not re-used 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 set to \'CIM\'.
Within 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:
:
Where and are separated by a colon \':\', and where 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 that is assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness must not contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID must appear between and .
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 resulting InstanceID is not re-used 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 set to \'CIM\'.
315The user-friendly name for this instance of a Job. In addition, the user-friendly name can be used as a property for a search or query. (Note: Name does not have to be unique within a namespace.) The user-friendly name for this instance of a Job. In addition, the user-friendly name can be used as a property for a search or query. (Note: Name does not have to be unique within a namespace.)
316JobState is an integer enumeration that indicates the operational state of a Job. It can also indicate transitions between these states, for example, \'Shutting Down\' and \'Starting\'. Following is a brief description of the states:
New (2) indicates that the job has never been started.
Starting (3) indicates that the job is moving from the \'New\', \'Suspended\', or \'Service\' states into the \'Running\' state.
Running (4) indicates that the Job is running.
Suspended (5) indicates that the Job is stopped, but can be restarted in a seamless manner.
Shutting Down (6) indicates that the job is moving to a \'Completed\', \'Terminated\', or \'Killed\' state.
Completed (7) indicates that the job has completed normally.
Terminated (8) indicates that the job has been stopped by a \'Terminate\' state change request. The job and all its underlying processes are ended and can be restarted (this is job-specific) only as a new job.
Killed (9) indicates that the job has been stopped by a \'Kill\' state change request. Underlying processes might have been left running, and cleanup might be required to free up resources.
Exception (10) indicates that the Job is in an abnormal state that might be indicative of an error condition. Actual status might be displayed though job-specific objects.
Service (11) indicates that the Job is in a vendor-specific state that supports problem discovery, or resolution, or both.
Query pending (12) waiting for a client to resolve a query
JobState is an integer enumeration that indicates the operational state of a Job. It can also indicate transitions between these states, for example, \'Shutting Down\' and \'Starting\'. Following is a brief description of the states:
New (2) indicates that the job has never been started.
Starting (3) indicates that the job is moving from the \'New\', \'Suspended\', or \'Service\' states into the \'Running\' state.
Running (4) indicates that the Job is running.
Suspended (5) indicates that the Job is stopped, but can be restarted in a seamless manner.
Shutting Down (6) indicates that the job is moving to a \'Completed\', \'Terminated\', or \'Killed\' state.
Completed (7) indicates that the job has completed normally.
Terminated (8) indicates that the job has been stopped by a \'Terminate\' state change request. The job and all its underlying processes are ended and can be restarted (this is job-specific) only as a new job.
Killed (9) indicates that the job has been stopped by a \'Kill\' state change request. Underlying processes might have been left running, and cleanup might be required to free up resources.
Exception (10) indicates that the Job is in an abnormal state that might be indicative of an error condition. Actual status might be displayed though job-specific objects.
Service (11) indicates that the Job is in a vendor-specific state that supports problem discovery, or resolution, or both.
Query pending (12) waiting for a client to resolve a query
317New New
318Running Running
319Suspended Suspended
320Terminated Terminated
321Killed Killed
322Exception Exception
323Service Service
324Query Pending Query Pending
325The date or time when the state of the Job last changed. If the state of the Job 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. The date or time when the state of the Job last changed. If the state of the Job 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.
326The amount of time that the Job is retained after it has finished executing, either succeeding or failing in that execution. The job must remain in existence for some period of time regardless of the value of the DeleteOnCompletion property.
The default is five minutes.
The amount of time that the Job is retained after it has finished executing, either succeeding or failing in that execution. The job must remain in existence for some period of time regardless of the value of the DeleteOnCompletion property.
The default is five minutes.
327Requests that the state of the job be changed to the value specified in the RequestedState parameter. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost.
If 0 is returned, then the task completed successfully. Any other return code indicates an error condition.
Requests that the state of the job be changed to the value specified in the RequestedState parameter. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost.
If 0 is returned, then the task completed successfully. Any other return code indicates an error condition.
328Completed with No Error Completed with No Error
329Unknown/Unspecified Error Unknown/Unspecified Error
330Can NOT complete within Timeout Period Can NOT complete within Timeout Period
331Invalid Parameter Invalid Parameter
332In Use In Use
333Method Parameters Checked - Transition Started Method Parameters Checked - Transition Started
334Invalid State Transition Invalid State Transition
335Use of Timeout Parameter Not Supported Use of Timeout Parameter Not Supported
336Busy Busy
337Method Reserved Method Reserved
338RequestStateChange changes the state of a job. The possible values are as follows:
Start (2) changes the state to \'Running\'.
Suspend (3) stops the job temporarily. The intention is to subsequently restart the job with \'Start\'. It might be possible to enter the \'Service\' state while suspended. (This is job-specific.)
Terminate (4) stops the job cleanly, saving data, preserving the state, and shutting down all underlying processes in an orderly manner.
Kill (5) terminates the job immediately with no requirement to save data or preserve the state.
Service (6) puts the job into a vendor-specific service state. It might be possible to restart the job.
RequestStateChange changes the state of a job. The possible values are as follows:
Start (2) changes the state to \'Running\'.
Suspend (3) stops the job temporarily. The intention is to subsequently restart the job with \'Start\'. It might be possible to enter the \'Service\' state while suspended. (This is job-specific.)
Terminate (4) stops the job cleanly, saving data, preserving the state, and shutting down all underlying processes in an orderly manner.
Kill (5) terminates the job immediately with no requirement to save data or preserve the state.
Service (6) puts the job into a vendor-specific service state. It might be possible to restart the job.
339Start Start
340Suspend Suspend
341Terminate Terminate
342Kill Kill
343A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition.
If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' must be returned.
A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition.
If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' must be returned.
344When the job is executing or has terminated without error, then this method returns no CIM_Error instance. However, if the job has failed because of some internal problem or because the job has been terminated by a client, then a CIM_Error instance is returned. When the job is executing or has terminated without error, then this method returns no CIM_Error instance. However, if the job has failed because of some internal problem or because the job has been terminated by a client, then a CIM_Error instance is returned.
345Unspecified Error Unspecified Error
346If the OperationalStatus on the Job is not "OK", then this method will return a CIM Error instance. Otherwise, when the Job is "OK", null is returned. If the OperationalStatus on the Job is not "OK", then this method will return a CIM Error instance. Otherwise, when the Job is "OK", null is returned.
347A concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job. A concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job.
348InstanceID is the property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. InstanceID is the property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace.
349This property corresponds to the EnabledState property of the logical computer system represented by CIM_ComputerSystem. See CIM_EnabledLogicalElement.EnabledState for details on EnabledState. This property corresponds to the EnabledState property of the logical computer system represented by CIM_ComputerSystem. See CIM_EnabledLogicalElement.EnabledState for details on EnabledState.
350Enabled Enabled
351Disabled Disabled
352Not Applicable Not Applicable
353Enabled but Offline Enabled but Offline
354Deferred Deferred
355Quiesce Quiesce
356This property corresponds to the RequestedState property of the logical computer system represented by CIM_ComputerSystem. See CIM_EnabledLogicalElement.RequestedState for details on RequestedState. This property corresponds to the RequestedState property of the logical computer system represented by CIM_ComputerSystem. See CIM_EnabledLogicalElement.RequestedState for details on RequestedState.
357Shut Down Shut Down
358No Change No Change
359Offline Offline
360Test Test
361Reboot Reboot
362Reset Reset
363This property corresponds to the OperationalStatus property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.OperationalStatus Description for details. This property corresponds to the OperationalStatus property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.OperationalStatus Description for details.
364Relocating Relocating
365This property corresponds to the HealthState property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.HealthState for details. This property corresponds to the HealthState property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.HealthState for details.
366This property indicates the availability of the FRU Information on this physical computer system. See CIM_PhysicalAssetCapabilities.FRUInfoSupported for details. This property indicates the availability of the FRU Information on this physical computer system. See CIM_PhysicalAssetCapabilities.FRUInfoSupported for details.
367This property corresponds to CIM_PhysicalFrame.Tag. See CIM_PhysicalFrame.Tag for details. This property corresponds to CIM_PhysicalFrame.Tag. See CIM_PhysicalFrame.Tag for details.
368This property corresponds to CIM_PhysicalFrame.Manufacturer. See CIM_PhysicalFrame.Manufacturer for details. This property corresponds to CIM_PhysicalFrame.Manufacturer. See CIM_PhysicalFrame.Manufacturer for details.
369This property corresponds to CIM_PhysicalFrame.Model. See CIM_PhysicalFrame.Model for details. This property corresponds to CIM_PhysicalFrame.Model. See CIM_PhysicalFrame.Model for details.
370This property corresponds to CIM_PhysicalFrame.SKU. See CIM_PhysicalFrame.SKU for details. This property corresponds to CIM_PhysicalFrame.SKU. See CIM_PhysicalFrame.SKU for details.
371This property corresponds to CIM_PhysicalFrame.SerialNumber. See CIM_PhysicalFrame.SerialNumber for details. This property corresponds to CIM_PhysicalFrame.SerialNumber. See CIM_PhysicalFrame.SerialNumber for details.
372This property corresponds to CIM_PhysicalFrame.Version. See CIM_PhysicalFrame.Version for details. This property corresponds to CIM_PhysicalFrame.Version. See CIM_PhysicalFrame.Version for details.
373This property corresponds to CIM_PhysicalFrame.PartNumber. See CIM_PhysicalFrame.PartNumber for details. This property corresponds to CIM_PhysicalFrame.PartNumber. See CIM_PhysicalFrame.PartNumber for details.
374This property corresponds to PowerUtilizationModesSupported property of CIM_PowerUtilizationManagementCapabilities. See CIM_PowerUtilizationManagementCapabilities.PowerUtilizationModesSupported for details. This property corresponds to PowerUtilizationModesSupported property of CIM_PowerUtilizationManagementCapabilities. See CIM_PowerUtilizationManagementCapabilities.PowerUtilizationModesSupported for details.
375Dynamic Dynamic
376Static Static
377This property corresponds to the PowerUtilizationMode of the CIM_PowerUtilizationManagementService. See CIM_PowerUtilizationManagementService.PowerUtilizationMode for details. This property corresponds to the PowerUtilizationMode of the CIM_PowerUtilizationManagementService. See CIM_PowerUtilizationManagementService.PowerUtilizationMode for details.
378None None
379This property corresponds to CIM_PowerAllocationSettingData.Limit. See CIM_PowerAllocationSettingData.Limit for details. This property corresponds to CIM_PowerAllocationSettingData.Limit. See CIM_PowerAllocationSettingData.Limit for details.
380User-friendly names of the numeric sensors on the computer system. See CIM_NumericSensor.ElementName for details. User-friendly names of the numeric sensors on the computer system. See CIM_NumericSensor.ElementName for details.
381States of numeric sensors. See CIM_NumericSensor.EnabledState for details. States of numeric sensors. See CIM_NumericSensor.EnabledState for details.
382Health states of numeric sensors. See CIM_NumericSensor.HealthState for details. Health states of numeric sensors. See CIM_NumericSensor.HealthState for details.
383Current states of numeric sensors. See CIM_NumericSensor.CurrentState for details. Current states of numeric sensors. See CIM_NumericSensor.CurrentState for details.
384Primary statuses of numeric sensors. See CIM_NumericSensor.PrimaryStatus for details. Primary statuses of numeric sensors. See CIM_NumericSensor.PrimaryStatus for details.
385Base units of the values returned by the numeric sensors. See CIM_NumericSensor.BaseUnits for details. Base units of the values returned by the numeric sensors. See CIM_NumericSensor.BaseUnits for details.
386Degrees C Degrees C
387Degrees F Degrees F
388Degrees K Degrees K
389Volts Volts
390Amps Amps
391Watts Watts
392Joules Joules
393Coulombs Coulombs
394VA VA
395Nits Nits
396Lumens Lumens
397Lux Lux
398Candelas Candelas
399kPa kPa
400PSI PSI
401Newtons Newtons
402CFM CFM
403RPM RPM
404Hertz Hertz
405Seconds Seconds
406Minutes Minutes
407Hours Hours
408Days Days
409Weeks Weeks
410Mils Mils
411Inches Inches
412Feet Feet
413Cubic Inches Cubic Inches
414Cubic Feet Cubic Feet
415Meters Meters
416Cubic Centimeters Cubic Centimeters
417Cubic Meters Cubic Meters
418Liters Liters
419Fluid Ounces Fluid Ounces
420Radians Radians
421Steradians Steradians
422Revolutions Revolutions
423Cycles Cycles
424Gravities Gravities
425Ounces Ounces
426Pounds Pounds
427Foot-Pounds Foot-Pounds
428Ounce-Inches Ounce-Inches
429Gauss Gauss
430Gilberts Gilberts
431Henries Henries
432Farads Farads
433Ohms Ohms
434Siemens Siemens
435Moles Moles
436Becquerels Becquerels
437PPM (parts/million) PPM (parts/million)
438Decibels Decibels
439DbA DbA
440DbC DbC
441Grays Grays
442Sieverts Sieverts
443Color Temperature Degrees K Color Temperature Degrees K
444Bits Bits
445Bytes Bytes
446Words (data) Words (data)
447DoubleWords DoubleWords
448QuadWords QuadWords
449Percentage Percentage
450Pascals Pascals
451Unit modifiers for the values returned by the numeric sensors. See CIM_NumericSensor.UnitModifier description for details. Unit modifiers for the values returned by the numeric sensors. See CIM_NumericSensor.UnitModifier description for details.
452See CIM_NumericSensor.RateUnits for details. See CIM_NumericSensor.RateUnits for details.
453Per MicroSecond Per MicroSecond
454Per MilliSecond Per MilliSecond
455Per Second Per Second
456Per Minute Per Minute
457Per Hour Per Hour
458Per Day Per Day
459Per Week Per Week
460Per Month Per Month
461Per Year Per Year
462See CIM_NumericSensor.CurrentReading for details. See CIM_NumericSensor.CurrentReading for details.
463See CIM_NumericSensor.SensorType for details. See CIM_NumericSensor.SensorType for details.
464Temperature Temperature
465Voltage Voltage
466Current Current
467Tachometer Tachometer
468Counter Counter
469Switch Switch
470Lock Lock
471Humidity Humidity
472Smoke Detection Smoke Detection
473Presence Presence
474Air Flow Air Flow
475Power Consumption Power Consumption
476Power Production Power Production
477Pressure Pressure
478See CIM_NumericSensor.OtherSensorTypeDescription for details. See CIM_NumericSensor.OtherSensorTypeDescription for details.
479See CIM_NumericSensor.UpperThresholdNonCritical for details. See CIM_NumericSensor.UpperThresholdNonCritical for details.
480See CIM_NumericSensor.UpperThresholdCritical description for details. See CIM_NumericSensor.UpperThresholdCritical description for details.
481See CIM_NumericSensor.UpperThresholdFatal for details. See CIM_NumericSensor.UpperThresholdFatal for details.
482This property represents the identifiers for the underlying logs on this physical computer system. See CIM_RecordLog.InstanceID for details. This property represents the identifiers for the underlying logs on this physical computer system. See CIM_RecordLog.InstanceID for details.
483See CIM_RecordLog.MaxNumberOfRecords for details. See CIM_RecordLog.MaxNumberOfRecords for details.
484See CIM_RecordLog.CurrentNumberOfRecords for details. See CIM_RecordLog.CurrentNumberOfRecords for details.
485See CIM_RecordLog.OverWritePolicy for details. See CIM_RecordLog.OverWritePolicy for details.
486Wraps When Full Wraps When Full
487Never Overwrites Never Overwrites
488See CIM_RecordLog.LogState for details. See CIM_RecordLog.LogState for details.
489Normal Normal
490Erasing Erasing
491Strings identifying the boot sources on this physical computer system. See CIM_BootSourceSetting.StructuredBootString description for details. Strings identifying the boot sources on this physical computer system. See CIM_BootSourceSetting.StructuredBootString description for details.
492An array of elements identifying the boot order of the persistent boot configuration that shall be used during the next boot of the computer system, unless the OneTimeBootSource for the next boot is specified. The value of each element in this array is an index referencing an element in the array of StructuredBootString. An array of elements identifying the boot order of the persistent boot configuration that shall be used during the next boot of the computer system, unless the OneTimeBootSource for the next boot is specified. The value of each element in this array is an index referencing an element in the array of StructuredBootString.
493This property identifies the boot source that is used for the next one-time boot. The value of this property is an index referencing an element in the array of StructuredBootString. This property identifies the boot source that is used for the next one-time boot. The value of this property is an index referencing an element in the array of StructuredBootString.
494This property identifies the number of processors on this physical computer system. This property identifies the number of processors on this physical computer system.
495See CIM_ProcessorCapabilities.NumberOfProcessorCores for details. See CIM_ProcessorCapabilities.NumberOfProcessorCores for details.
496See CIM_ProcessorCapabilities.NumberOfProcessorThreads for details. See CIM_ProcessorCapabilities.NumberOfProcessorThreads for details.
497See CIM_Processor.Family for details. See CIM_Processor.Family for details.
498See CIM_Processor.MaxClockSpeed for details. See CIM_Processor.MaxClockSpeed for details.
499See CIM_Memory.BlockSize for details. See CIM_Memory.BlockSize for details.
500See CIM_Memory.NumberOfBlocks for details. See CIM_Memory.NumberOfBlocks for details.
501See CIM_Memory.ConsumableBlocks for details. See CIM_Memory.ConsumableBlocks for details.
502The major number component of the current BIOS version information. The major number component of the current BIOS version information.
503The minor number component of the current BIOS version information. The minor number component of the current BIOS version information.
504The revision number component of the current BIOS version information. The revision number component of the current BIOS version information.
505The build number component of the current BIOS version information. The build number component of the current BIOS version information.
506The major number component of the version information for the current management firmware on this physical computer system. The major number component of the version information for the current management firmware on this physical computer system.
507The minor number component of the version information for the current management firmware on this physical computer system. The minor number component of the version information for the current management firmware on this physical computer system.
508The revision number component of the version information for the current management firmware on this physical computer system. The revision number component of the version information for the current management firmware on this physical computer system.
509The build number component of the version information for the current management firmware on this physical computer system. The build number component of the version information for the current management firmware on this physical computer system.
510The user-friendly name for the current management firmware on this physical computer system. The user-friendly name for the current management firmware on this physical computer system.
511The version string for the current management firmware on this physical computer system. The version string for the current management firmware on this physical computer system.
512Type information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.OSType for details. Type information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.OSType for details.
513Version information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.Version for details. Version information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.Version for details.
514EnabledState of the current or last running operating system on this physcial computer system. EnabledState of the current or last running operating system on this physcial computer system.
515The BIOS version information in string format. The BIOS version information in string format.
516See CIM_ComputerSystem.Dedicated for details. See CIM_ComputerSystem.Dedicated for details.
517Not Dedicated Not Dedicated
518Storage Storage
519Router Router
520Layer 3 Switch Layer 3 Switch
521Central Office Switch Central Office Switch
522Hub Hub
523Access Server Access Server
524Firewall Firewall
525Print Print
526I/O I/O
527Web Caching Web Caching
528Management Management
529Block Server Block Server
530File Server File Server
531Mobile User Device Mobile User Device
532Repeater Repeater
533Bridge/Extender Bridge/Extender
534Gateway Gateway
535Storage Virtualizer Storage Virtualizer
536Media Library Media Library
537ExtenderNode ExtenderNode
538NAS Head NAS Head
539Self-contained NAS Self-contained NAS
540UPS UPS
541IP Phone IP Phone
542Management Controller Management Controller
543Chassis Manager Chassis Manager
544Host-based RAID controller Host-based RAID controller
545Storage Device Enclosure Storage Device Enclosure
546Desktop Desktop
547Laptop Laptop
548Virtual Tape Library Virtual Tape Library
549Virtual Library System Virtual Library System
550Network PC/Thin Client Network PC/Thin Client
551FC Switch FC Switch
552Ethernet Switch Ethernet Switch
553See CIM_System.IdentifyingDescriptions for details. See CIM_System.IdentifyingDescriptions for details.
554See CIM_ComputerSystem.OtherDedicatedDescriptions for details. See CIM_ComputerSystem.OtherDedicatedDescriptions for details.
555See CIM_System.OtherIdentifyingInfo for details. See CIM_System.OtherIdentifyingInfo for details.
556See CIM_Processor.CurrentClockSpeed for details. See CIM_Processor.CurrentClockSpeed for details.
557See CIM_Sensor.SensorContext for details. See CIM_Sensor.SensorContext for details.
558See CIM_NumericSensor.LowerThresholdNonCritical for details. See CIM_NumericSensor.LowerThresholdNonCritical for details.
559See CIM_NumericSensor.LowerThresholdCritical description for details. See CIM_NumericSensor.LowerThresholdCritical description for details.
560See CIM_NumericSensor.LowerThresholdFatal description for details. See CIM_NumericSensor.LowerThresholdFatal description for details.
561An extrinsic method for changing the state of this physical computer system. Requests that the state of the element be changed to the value specified in the RequestedState parameter. When the requested state change takes place, the EnabledState and RequestedState will be the same. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost.
A return code of 0 shall indicate the state change was successfully initiated.
A return code of 1 shall indicate that the method is not supported. A return code of 2 shall indicate that the method failed.
A return code of 4096 shall indicate the state change was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job.
An extrinsic method for changing the state of this physical computer system. Requests that the state of the element be changed to the value specified in the RequestedState parameter. When the requested state change takes place, the EnabledState and RequestedState will be the same. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost.
A return code of 0 shall indicate the state change was successfully initiated.
A return code of 1 shall indicate that the method is not supported. A return code of 2 shall indicate that the method failed.
A return code of 4096 shall indicate the state change was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job.
562Job Started Job Started
563See CIM_ComputerSystem.RequestedStateChange.RequestedState for details. See CIM_ComputerSystem.RequestedStateChange.RequestedState for details.
564Defer Defer
565May contain a reference to the ConcreteJob created to track the state transition initiated by the method invocation. May contain a reference to the ConcreteJob created to track the state transition initiated by the method invocation.
566See CIM_ComputerSystem.TimeoutPeriod for details. See CIM_ComputerSystem.TimeoutPeriod for details.
567An extrinsic method for clearing a log on this physical computer system.
Requests that the Log be cleared of all entries.
The return value shall be 0 if the request was successfully executed, 1 if the request is not supported, and 2 if an error occurred. A return code of 4096 shall indicate the request to clear log was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job.
An extrinsic method for clearing a log on this physical computer system.
Requests that the Log be cleared of all entries.
The return value shall be 0 if the request was successfully executed, 1 if the request is not supported, and 2 if an error occurred. A return code of 4096 shall indicate the request to clear log was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job.
568Idenfier for the log that is requested to be cleared. Idenfier for the log that is requested to be cleared.
569An extrinsic method for installing software on this physical computer system. If 0 is returned, the function completed successfully and no ConcreteJob instance was required. The return value shall be 1 if the request is not supported, and 2 if an error occurred. If 4096 is returned, a ConcreteJob will be started to to perform the install. The Job\'s reference will be returned in the output parameter Job. An extrinsic method for installing software on this physical computer system. If 0 is returned, the function completed successfully and no ConcreteJob instance was required. The return value shall be 1 if the request is not supported, and 2 if an error occurred. If 4096 is returned, a ConcreteJob will be started to to perform the install. The Job\'s reference will be returned in the output parameter Job.
570Reference to the job (may be null if job completed). Reference to the job (may be null if job completed).
571See CIM_SoftwareIdentity.Classifications for details. See CIM_SoftwareIdentity.Classifications for details.
572Firmware Firmware
573BIOS/FCode BIOS/FCode
574Software Bundle Software Bundle
575Management Firmware Management Firmware
576See CIM_SoftwareInstallationService.InstallFromURI.URI for details. See CIM_SoftwareInstallationService.InstallFromURI.URI for details.
577See CIM_SoftwareInstallationService.InstallFromURI.InstallOptions for details. See CIM_SoftwareInstallationService.InstallFromURI.InstallOptions for details.
578Defer target/system reset Defer target/system reset
579Force installation Force installation
580Install Install
581Update Update
582Repair Repair
583Password Password
584Uninstall Uninstall
585Log Log
586SilentMode SilentMode
587AdministrativeMode AdministrativeMode
588ScheduleInstallAt ScheduleInstallAt
589See CIM_SoftwareInstallationService.InstallFromURI.InstallOptionsValues for details. See CIM_SoftwareInstallationService.InstallFromURI.InstallOptionsValues for details.
590This method is used to change the order of boot sources for the persistent boot configuration specified by the property CIM_PhysicalComputerSystemView.PersistentBootConfigOrder. This method is used to change the order of boot sources for the persistent boot configuration specified by the property CIM_PhysicalComputerSystemView.PersistentBootConfigOrder.
591An ordered array of strings representing the order of boot sources. An ordered array of strings representing the order of boot sources.
592Reference to the job spawned if the operation continues after the method returns. (May be null if the task is completed). Reference to the job spawned if the operation continues after the method returns. (May be null if the task is completed).
593This method is used to set the one time boot source for the next boot on this computer system. This method is used to set the one time boot source for the next boot on this computer system.
594A string representing the boot source for next boot. A string representing the boot source for next boot.
595This class defines a view class for a physical computer system. This class defines a view class for a physical computer system.
5962.35.0 2.35.0
597A string describing the data structure of the information in the property, RecordData. If the RecordFormat string is , RecordData should be interpreted as a free-form string.

To describe the data structure of RecordData, the RecordFormat string should be constructed as follows:
- The first character is a delimiter character and is used to parse the remainder of the string into sub-strings.
- Each sub-string is separated by the delimiter character and should be in the form of a CIM property declaration (i.e., datatype and property name). This set of declarations may be used to interpret the similarly delimited RecordData property.
For example, using a \'*\' delimiter, RecordFormat = "*string ThisDay*uint32 ThisYear*datetime SomeTime"
may be used to interpret: RecordData = "*This is Friday*2002*20020807141000.000000-300".
A string describing the data structure of the information in the property, RecordData. If the RecordFormat string is , RecordData should be interpreted as a free-form string.

To describe the data structure of RecordData, the RecordFormat string should be constructed as follows:
- The first character is a delimiter character and is used to parse the remainder of the string into sub-strings.
- Each sub-string is separated by the delimiter character and should be in the form of a CIM property declaration (i.e., datatype and property name). This set of declarations may be used to interpret the similarly delimited RecordData property.
For example, using a \'*\' delimiter, RecordFormat = "*string ThisDay*uint32 ThisYear*datetime SomeTime"
may be used to interpret: RecordData = "*This is Friday*2002*20020807141000.000000-300".
598A string containing LogRecord data.
If the corresponding RecordFormat property is , or cannot be parsed according to the recommended format, RecordData should be interpreted as a free-form string. If the RecordFormat property contains parseable format information (as recommended in the RecordFormat Description qualifier), the RecordData string SHOULD be parsed in accordance with this format. In this case, RecordData SHOULD begin with the delimiter character and this character SHOULD be used to separate substrings in the manner described. The RecordData string can then be parsed by the data consumer and appropriately typed.
A string containing LogRecord data.
If the corresponding RecordFormat property is , or cannot be parsed according to the recommended format, RecordData should be interpreted as a free-form string. If the RecordFormat property contains parseable format information (as recommended in the RecordFormat Description qualifier), the RecordData string SHOULD be parsed in accordance with this format. In this case, RecordData SHOULD begin with the delimiter character and this character SHOULD be used to separate substrings in the manner described. The RecordData string can then be parsed by the data consumer and appropriately typed.
599A locale indicates a particular geographical, political, or cultural region. The Locale specifies the language used in creating the RecordForLog data. If the Locale property is empty, it is assumed that the default locale is en_US (English).
The locale string consists of three sub-strings, separated by underscores:
- The first sub-string is the language code, as specified in ISO639.
- The second sub-string is the country code, as specified in ISO3166.
- The third sub-string is a variant, which is vendor specific.
For example, US English appears as: "en_US_WIN", where the "WIN" variant would specify a Windows browser-specific collation (if one exists). Since the variant is not standardized, it is not commonly used and generally is limited to easily recognizable values ("WIN", "UNIX", "EURO", etc.) used in standard environments. The language and country codes are required; the variant may be empty.
A locale indicates a particular geographical, political, or cultural region. The Locale specifies the language used in creating the RecordForLog data. If the Locale property is empty, it is assumed that the default locale is en_US (English).
The locale string consists of three sub-strings, separated by underscores:
- The first sub-string is the language code, as specified in ISO639.
- The second sub-string is the country code, as specified in ISO3166.
- The third sub-string is a variant, which is vendor specific.
For example, US English appears as: "en_US_WIN", where the "WIN" variant would specify a Windows browser-specific collation (if one exists). Since the variant is not standardized, it is not commonly used and generally is limited to easily recognizable values ("WIN", "UNIX", "EURO", etc.) used in standard environments. The language and country codes are required; the variant may be empty.
600An enumerated value that describes the severity of the Indication from the notifier\'s point of view:
1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property.
3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed.
4 - Minor should be used to indicate action is needed, but the situation is not serious at this time.
5 - Major should be used to indicate action is needed NOW.
6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result).
7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it\'s too late to take remedial action.
2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the Indication is purely informational or its severity is simply unknown.
An enumerated value that describes the severity of the Indication from the notifier\'s point of view:
1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property.
3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed.
4 - Minor should be used to indicate action is needed, but the situation is not serious at this time.
5 - Major should be used to indicate action is needed NOW.
6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result).
7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it\'s too late to take remedial action.
2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the Indication is purely informational or its severity is simply unknown.
601The RecordForLog class is used to instantiate records to be aggregated to a Log. The RecordForLog class is used to instantiate records to be aggregated to a Log.
6022.25.0 2.25.0
603The scoping Log\'s CreationClassName. The scoping Log\'s CreationClassName.
604The scoping Log\'s Name. The scoping Log\'s Name.
605CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified.
606RecordID, with the MessageTimestamp property, serve to uniquely identify the LogRecord within a MessageLog. Note that this property is different than the RecordNumber parameters of the MessageLog methods. The latter are ordinal values only, useful to track position when iterating through a Log. On the other hand, RecordID is truly an identifier for an instance of LogRecord. It may be set to the record\'s ordinal position, but this is not required. RecordID, with the MessageTimestamp property, serve to uniquely identify the LogRecord within a MessageLog. Note that this property is different than the RecordNumber parameters of the MessageLog methods. The latter are ordinal values only, useful to track position when iterating through a Log. On the other hand, RecordID is truly an identifier for an instance of LogRecord. It may be set to the record\'s ordinal position, but this is not required.
607A LogRecord\'s key structure includes a timestamp for the entry. If the timestamp for the entry is unknown, the value 99990101000000.000000+000 SHOULD be used. A LogRecord\'s key structure includes a timestamp for the entry. If the timestamp for the entry is unknown, the value 99990101000000.000000+000 SHOULD be used.
608A free-form string describing the LogRecord\'s data structure. A free-form string describing the LogRecord\'s data structure.
609The LogRecord object can describe the definitional format for entries in a MessageLog, or can be used to instantiate the actual records in the Log. The latter approach provides a great deal more semantic definition and management control over the individual entries in a MessageLog, than do the record manipulation methods of the Log class. It is recommended that the data in individual Log entries be modeled using subclasses of LogRecord, to avoid the creation of LogRecords with one property (such as RecordData) without semantics.
Definitional formats for LogRecords could be specified by establishing a naming convention for the RecordID and Message Timestamp key properties.
The LogRecord object can describe the definitional format for entries in a MessageLog, or can be used to instantiate the actual records in the Log. The latter approach provides a great deal more semantic definition and management control over the individual entries in a MessageLog, than do the record manipulation methods of the Log class. It is recommended that the data in individual Log entries be modeled using subclasses of LogRecord, to avoid the creation of LogRecords with one property (such as RecordData) without semantics.
Definitional formats for LogRecords could be specified by establishing a naming convention for the RecordID and Message Timestamp key properties.
6102.11.0 2.11.0
611Name of the target PCSV device Name of the target PCSV device
612SMBios Guid of the target PCSV device SMBios Guid of the target PCSV device
613IPv4AddressOrigin identifies the method by which the IPv4 Address,
Subnet Mask, and Gateway were assigned to the NIC.
IPv4AddressOrigin identifies the method by which the IPv4 Address,
Subnet Mask, and Gateway were assigned to the NIC.
614DHCP DHCP
615BOOTP BOOTP
616IPv4 Address of the target PCSV device IPv4 Address of the target PCSV device
617IPv4 Subnet Mask of the target PCSV device IPv4 Subnet Mask of the target PCSV device
618IPv4 Default Gateway of the target PCSV device IPv4 Default Gateway of the target PCSV device
619LAN MAC Address of the target PCSV device LAN MAC Address of the target PCSV device
620SEL Free space in Bytes SEL Free space in Bytes
621This is a wrapper method used to set both the one time boot source and persistent boot source added to support the PCSVDevice cmdlets. This just calls the other two methods internally. The API users for this class should call the other methods directlly insted of this. This method will only change one setting at a time, if you pass values for both paramters, then this method will fail. This is a wrapper method used to set both the one time boot source and persistent boot source added to support the PCSVDevice cmdlets. This just calls the other two methods internally. The API users for this class should call the other methods directlly insted of this. This method will only change one setting at a time, if you pass values for both paramters, then this method will fail.
622This is a wrapper method used to change the network configuration of the BMC. This is a wrapper method used to change the network configuration of the BMC.
623IPv4AddressOrigin identifies the method by which the IPv4 Address, Subnet Mask, and Gateway were assigned to the NIC. IPv4AddressOrigin identifies the method by which the IPv4 Address, Subnet Mask, and Gateway were assigned to the NIC.
624This is a wrapper method used to change the BMC user password. This is a wrapper method used to change the BMC user password.
625CurrentCredential is a delimited string containing both the current username and password, separated by a colon. CurrentCredential is a delimited string containing both the current username and password, separated by a colon.
626NewPassword will be stored on the BMC as the new password for the user specified by the CurrentCredential parameter. NewPassword will be stored on the BMC as the new password for the user specified by the CurrentCredential parameter.
627This is a wrapper method used to read BMC SEL log. This is a wrapper method used to read BMC SEL log.
628Return BMC SEL entries as an array of MSFT_PCSVLogRecord instances Return BMC SEL entries as an array of MSFT_PCSVLogRecord instances
10001The operation options for this call must contain an option with the following name: %1. The %1 operation option must be of type: %2; and in the following format: username:password. The operation options for this call must contain an option with the following name: %1. The %1 operation option must be of type: %2; and in the following format: username:password.
10002An error %1!X! occurred while parsing the credentials. The %2 operation option must be in the following format: username:password. An error %1!X! occurred while parsing the credentials. The %2 operation option must be in the following format: username:password.
10003The operation options for this call must contain an option with the following name: %1. The %1 operation option must be of type: %2. The operation options for this call must contain an option with the following name: %1. The %1 operation option must be of type: %2.
10004The %1 operation option must be of type %2. The %1 operation option must be of type %2.
10005The requested management protocol type is not supported. Supported types are WSMAN (1) and IPMI (2). The requested management protocol type is not supported. Supported types are WSMAN (1) and IPMI (2).
10006The requested authentication type is not supported. The supported authentication types are: Default, Digest, and Basic. The requested authentication type is not supported. The supported authentication types are: Default, Digest, and Basic.
10007The requested power state is not supported. The supported power states are: Enabled(2), Disabled(3), and Reset(11). The requested power state is not supported. The supported power states are: Enabled(2), Disabled(3), and Reset(11).
10008The requested boot source is not supported on this device. The requested boot source must be one of the values in the StructuredBootString array. The requested boot source is not supported on this device. The requested boot source must be one of the values in the StructuredBootString array.
10009The device attempted to start a session using an unsupported authentication algorithm. The supported Authentication algorithms are HMAC_SHA1 and NONE. The device attempted to start a session using an unsupported authentication algorithm. The supported Authentication algorithms are HMAC_SHA1 and NONE.
10010The device attempted to start a session using an unsupported integrity algorithm. The supported integrity algorithms are HMAC_SHA1_96 and NONE. The device attempted to start a session using an unsupported integrity algorithm. The supported integrity algorithms are HMAC_SHA1_96 and NONE.
10011The device attempted to start a session using an unsupported confidentiality algorithm. The supported confidentiality algorithms are AES_CBC_128 and NONE. The device attempted to start a session using an unsupported confidentiality algorithm. The supported confidentiality algorithms are AES_CBC_128 and NONE.
10012The device does not implement any of the supported base profiles. The supported base profiles are: %1, %2, and %3. The device does not implement any of the supported base profiles. The supported base profiles are: %1, %2, and %3.
10013An unexpected %1 error %2!X! occurred while processing the request. An unexpected %1 error %2!X! occurred while processing the request.
10014The response received from the device was not valid. The response received from the device was not valid.
10015The operation did not complete successfully. The response contained the following IPMI Completion Code: %1!x!. The operation did not complete successfully. The response contained the following IPMI Completion Code: %1!x!.
10016Cannot connect to device using the given credentials. Verify the credentials and try again. Cannot connect to device using the given credentials. Verify the credentials and try again.
10017The device did not respond in the specified timeout period. The device did not respond in the specified timeout period.
10018The DMTF %1 profile is not implemented on the device or it is not implemented in the standard way. The DMTF %1 profile is not implemented on the device or it is not implemented in the standard way.
10019Restarting device using %1 Restarting device using %1
10020The operation failed. The device returned the following RMCP+ status code: %1!x!. The operation failed. The device returned the following RMCP+ status code: %1!x!.
10021Starting device using %1 Starting device using %1
10022Stopping device using %1 Stopping device using %1
10023Set one time boot source to %2 using %1 Set one time boot source to %2 using %1
10024Getting information from device using %1 Getting information from device using %1
10025Some capabilities or properties will not be available since the device does not implement the DMTF %1 Profile. Some capabilities or properties will not be available since the device does not implement the DMTF %1 Profile.
10026The operation is not supported for this device. The device only supports setting one boot source for Persistent Boot Order. The operation is not supported for this device. The device only supports setting one boot source for Persistent Boot Order.
10027The operation is not supported for this device type. This operation is supported for IPMI devices only. The operation is not supported for this device type. This operation is supported for IPMI devices only.
10028Set persistent boot order using %1 Set persistent boot order using %1
10029The parameters passed are not valid. Changing One Time Boot Source and Persistent Boot Order in a single operation is not supported. The parameters passed are not valid. Changing One Time Boot Source and Persistent Boot Order in a single operation is not supported.
10030The parameters passed are not valid. Please pass a valid value for one of the boot settings. The parameters passed are not valid. Please pass a valid value for one of the boot settings.
10031The operation is not supported on this system. The system does not have a Microsoft IPMI compatible device. The operation is not supported on this system. The system does not have a Microsoft IPMI compatible device.
10032Power state management operations are only supported for devices managed via an out-of-band channel. To manage the device using an out-of-band channel please provide device connection information e.g. TargetAddress, Credentials, ManagementProtocol etc. Power state management operations are only supported for devices managed via an out-of-band channel. To manage the device using an out-of-band channel please provide device connection information e.g. TargetAddress, Credentials, ManagementProtocol etc.
10034The operation did not complete successfully. IPv4AddressOrigin cannot be set to DHCP with static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway. The operation did not complete successfully. IPv4AddressOrigin cannot be set to DHCP with static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway.
10035The operation did not complete successfully. IPv4AddressOrigin cannot be set to STATIC without static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway. The operation did not complete successfully. IPv4AddressOrigin cannot be set to STATIC without static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway.
10036The operation did not complete successfully. %1 is not supported IPv4AddressOrigin value for IPMI protocol. The supported values are: STATIC(3) and DHCP(4) The operation did not complete successfully. %1 is not supported IPv4AddressOrigin value for IPMI protocol. The supported values are: STATIC(3) and DHCP(4)
10037The operation did not complete successfully. The IPv4 address '%1' is not a valid IPv4 address. The operation did not complete successfully. The IPv4 address '%1' is not a valid IPv4 address.
10038BMC network configuration change are only supported via an in-band channel. To change the network configuration, please execute this command on the remote host directly. BMC network configuration change are only supported via an in-band channel. To change the network configuration, please execute this command on the remote host directly.
10039BMC network configuration change receives an unexpected parameter type. A string is expected for IP address. BMC network configuration change receives an unexpected parameter type. A string is expected for IP address.
10040BMC password change received an unexpected parameter type. A delimited string is expected for current credential BMC password change received an unexpected parameter type. A delimited string is expected for current credential
10041BMC password change received an unexpected parameter type. A string is expected for new password. BMC password change received an unexpected parameter type. A string is expected for new password.
10042The current credential did not match those of a valid user on the BMC. The current credential did not match those of a valid user on the BMC.
100442 parameters (CurrentCredential and NewPassword) are required to change BMC user password. At least one of them is missing. 2 parameters (CurrentCredential and NewPassword) are required to change BMC user password. At least one of them is missing.
10045Username cannot be longer than 16 characters. Username cannot be longer than 16 characters.
10046Password cannot be longer than 20 characters. Password cannot be longer than 20 characters.
10048Cannot read System Event Log because erase operation is in progress. Cannot read System Event Log because erase operation is in progress.
10051Failed to reserve the System Event Log because an erase operation is in progress. Failed to reserve the System Event Log because an erase operation is in progress.
10052Cannot clear the System Event Log because the reservation was cancelled by an external event (e.g. a new entry was added, the device was reset, etc.). Cannot clear the System Event Log because the reservation was cancelled by an external event (e.g. a new entry was added, the device was reset, etc.).
10053Change network configuration using %1 Change network configuration using %1
10054Change user password using %1 Change user password using %1
10055Clear System Event Log using %1 Clear System Event Log using %1
10056Local Device Local Device
10057Gracefully shutting down device using %1 Gracefully shutting down device using %1
10058Activating SOL payload failed. SOL payload must be activated in the same session. Activating SOL payload failed. SOL payload must be activated in the same session.
0x90000001Microsoft-Windows-DAL-Provider Microsoft-Windows-DAL-Provider
0xB0000001The Unencrypted request data for IPMI request %1 The Unencrypted request data for IPMI request %1
0xB0000002The Decrypted response data for IPMI request %1 The Decrypted response data for IPMI request %1
0xB0000003Starts enumeration of PCSVDevice Starts enumeration of PCSVDevice
0xB0000004Stops enumeration of PCSVDevice Stops enumeration of PCSVDevice
0xB0000005Starts getting instance of PCSVDevice Starts getting instance of PCSVDevice
0xB0000006Stops getting instance of PCSVDevice Stops getting instance of PCSVDevice
0xB0000007Start RequestStateChange Start RequestStateChange
0xB0000008Stops RequestStateChange Stops RequestStateChange
0xB0000009Starts SetOneTimeBootSource Starts SetOneTimeBootSource
0xB000000AStops SetOneTimeBootSource Stops SetOneTimeBootSource
0xB000000BResult of PCSVDevice operation Result of PCSVDevice operation
0xB000000FInformation on IPMI Sent Data Information on IPMI Sent Data
0xB0000010Information on IPMI Received Data Information on IPMI Received Data
0xB0000011Get operations options Get operations options
0xB0000012Starts ModifyPersistentBootConfigOrder Starts ModifyPersistentBootConfigOrder
0xB0000013Stops ModifyPersistentBootConfigOrder Stops ModifyPersistentBootConfigOrder
0xB0000014Starts ChangeBootConfiguration Starts ChangeBootConfiguration
0xB0000015Stops ChangeBootConfiguration Stops ChangeBootConfiguration
0xB0000016Starts ChangeNetworkConfiguration Starts ChangeNetworkConfiguration
0xB0000017Stops ChangeNetworkConfiguration Stops ChangeNetworkConfiguration
0xB0000018Starts ChangeUserPassword Starts ChangeUserPassword
0xB0000019Stops ChangeUserPassword Stops ChangeUserPassword
0xB000001AStarts getting PCSV device log Starts getting PCSV device log
0xB000001BStops getting PCSV device log Stops getting PCSV device log
0xB000001CStarts clearing PCSV device log Starts clearing PCSV device log
0xB000001DStops clearing PCSV device log Stops clearing PCSV device log
0xB000001EThe request data for in-band IPMI request %1 The request data for in-band IPMI request %1
0xB000001FThe response data for in-band IPMI request %1 The response data for in-band IPMI request %1

EXIF

File Name:pcsvDevice.dll.mui
Directory:%WINDIR%\WinSxS\amd64_microsoft-devicepro..-provider.resources_31bf3856ad364e35_10.0.15063.0_cs-cz_aae2533b93607ed5\
File Size:134 kB
File Permissions:rw-rw-rw-
File Type:Win32 DLL
File Type Extension:dll
MIME Type:application/octet-stream
Machine Type:Intel 386 or later, and compatibles
Time Stamp:0000:00:00 00:00:00
PE Type:PE32
Linker Version:14.10
Code Size:0
Initialized Data Size:136704
Uninitialized Data Size:0
Entry Point:0x0000
OS Version:10.0
Image Version:10.0
Subsystem Version:6.0
Subsystem:Windows GUI
File Version Number:10.0.15063.0
Product Version Number:10.0.15063.0
File Flags Mask:0x003f
File Flags:(none)
File OS:Windows NT 32-bit
Object File Type:Dynamic link library
File Subtype:0
Language Code:Czech
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:PCSV Proxy Provider for devices
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:pcsvDevice.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original File Name:pcsvDevice.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0

What is pcsvDevice.dll.mui?

pcsvDevice.dll.mui is Multilingual User Interface resource file that contain Czech language for file pcsvDevice.dll (PCSV Proxy Provider for devices).

File version info

File Description:PCSV Proxy Provider for devices
File Version:10.0.15063.0 (WinBuild.160101.0800)
Company Name:Microsoft Corporation
Internal Name:pcsvDevice.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original Filename:pcsvDevice.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Translation:0x405, 1200