pcsvDevice.dll.mui 设备的 PCSV 代理提供程序 b3f38adc87f361326c741d8fae9c3c16

File name:	pcsvDevice.dll.mui
Size:	58880 byte
MD5:	b3f38adc87f361326c741d8fae9c3c16
SHA1:	f12a0bfb415d62a9dc512e58a74d4b5c2a05965f
SHA256:	2d881573f44bc3f32e11c658cb89e96370324eb745df95b623699c7680875b50
Operating systems:	Windows 10
Extension:	MUI

If an error occurred or the following message in Chinese (Simplified) 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	Chinese (Simplified)	English
1	InstanceID 是一个可选属性，可用于在实例化 Namespace 的作用域内以不透明的方式唯一标识此类的实例。此类的各种子类可能会重写此属性，使其成为必要属性或键。这些子类可能还会修改首选的算法，以确保下面所定义的唯一性。 为确保在 NameSpace 内的唯一性，InstanceID 的值应使用以下“首选”算法来构造: : 其中， 和 以冒号(:)分隔，并且 必须包括创建或定义 InstanceID 的商业实体拥有的版权化、商标化或其他形式的唯一名称，或由公认的全球性机构为商业实体分配的注册 ID。(此要求与 Schema 类名的 _ 结构类似。)此外，为确保唯一性， 不得包含冒号(:)。在使用此算法时，InstanceID 中的第一个冒号必须出现在 和 之间。 由商业实体选择，不应重复用于标识不同的基础(实际)元素。如果不为 Null 并且未使用上面的“首选”算法，定义实体必须确保不在此提供程序或其他提供程序为此实例的 NameSpace 生成的任何 InstanceID 之间重复使用生成的 InstanceID。 对于 DMTF 定义的实例，如果未设置为 Null，则在使用“首选”算法时， 必须设置为 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.
2	Caption 属性是对象的简短文字描述(一行字符串)。	The Caption property is a short textual description (one- line string) of the object.
3	Description 属性提供关于对象的文字描述。	The Description property provides a textual description of the object.
4	对象的用户友好名称。此属性允许每个实例在其键属性、标识数据和描述信息之外定义一个用户友好名称。 请注意，ManagedSystemElement 的 Name 属性也被定义为用户友好名称。但是，通常为此属性创建子类作为 Key。在不引起任何不一致的情况下，同一属性不能既表示标识又表示用户友好名称。如果 Name 存在但不是 Key (例如对于 LogicalDevice 实例)，则 Name 属性和 ElementName 属性中可显示相同的信息。请注意，如果存在 CIM_EnabledLogicalElementCapabilities 的关联实例，则根据该类中定义的 ElementNameMask 和 MaxElementNameLen 属性的定义，此属性可能会受到限制。	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.
5	2.19.0	2.19.0
6	ManagedElement 是一个抽象类，为 CIM 架构中的非关联类提供一个公共超类(或继承树的顶部)。	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.
7	View 是一个抽象类，为提供托管资源的非规范化、聚合表示形式的类提供一个公共超类。每个子类的定义将包括一些属性，这些属性传播自用于为规范化视图中的资源建模的类的图表。类可以为资源类或关联。需要指定如何传播值(即源类和值转换)的定义。 可以将子类明确限制为只读。如果未将子类限制为只读，强烈建议设计者仔细考虑可能导致的数据同步和一致性问题。ElementView 关联可用于查找构成托管资源的规范化视图的实例。	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.
8	2.26.0	2.26.0
9	一个日期时间值，表示对象的安装时间。缺少值并不表示未安装对象。	A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.
10	Name 属性定义用于标识对象的标签。创建子类时，可以将 Name 属性重写为 Key 属性。	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.
11	表示元素的当前状态。定义了各种运行状态。许多枚举值都是一目了然。但是，也有少数值并非如此，下面将对这些值予以详细说明。 “已强调”表示元素正在工作，但是需要注意。过载、过热等都属于“已强调”状态。 “预计故障”表示元素表面上正在工作，但是预计不久会出现故障。 “服务中”说明元素正在接受配置、维护、清洁或其他方式的管理。 “无连接”表示监视系统了解此元素，但是一直无法与其建立通信。 “通信中断”表示 ManagedSystem 元素已知存在，并且过去曾成功建立连接，但是当前不可访问。 “已停止”和“已中止”类似，只是前者暗示正常有序地停止，而后者暗示紧急停止，元素的状态和配置可能需要更新。 “休止”表示元素处于非活动状态或静态。 “支持实体出错”表示此元素可能“正常”，但是此元素所依赖的另一个元素出现错误。由于低层网络问题而无法工作的网络服务或终结点就属于这种情况。 “已完成”表示该元素已完成操作。此值应与“正常”、“错误”或“已降级”组合使用，使客户端可以确定整个操作是已经正常地完成(已通过)、已经完成但出现错误(出现故障)，还是已经完成但是降级(操作已完成，但是未“正常”地完成或未报告错误)。 “电源模式”表示元素在 Associated PowerManagementService 关联中包含其他电源模式信息。 OperationalStatus 替换 ManagedSystemElement 中的 Status 属性，以便提供一致的枚举方法，满足实现数组属性的需要，从而可以从当前的环境迁移到未来的环境。以前之所以未进行此更改，原因是需要 DEPRECATED 限定符。由于在管理应用程序中广泛使用现有的 Status 属性，强烈建议提供程序或检测同时提供 Status 和 OperationalStatus 属性。此外，OperationalStatus 的第一个值应包含元素的主要状态。如果检测，Status (由于是单值)也应提供元素的主要状态。	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.
12	未知	Unknown
13	其他	Other
14	正常	OK
15	已降级	Degraded
16	已强调	Stressed
17	预计故障	Predictive Failure
18	错误	Error
19	不可恢复的错误	Non-Recoverable Error
20	正在启动	Starting
21	正在停止	Stopping
22	已停止	Stopped
23	服务中	In Service
24	无连接	No Contact
25	通信中断	Lost Communication
26	已中止	Aborted
27	休止	Dormant
28	支持实体出错	Supporting Entity in Error
29	已完成	Completed
30	电源模式	Power Mode
31	DMTF 保留	DMTF Reserved
32	供应商保留	Vendor Reserved
33	描述各种 OperationalStatus 数组值的字符串。例如，如果为 OperationalStatus 分配的值为“正在停止”，则此属性可能包含对象正在停止原因的解释。请注意，此数组中的条目与 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.
34	一个表示对象当前状态的字符串。定义了各种运行和非运行状态。此属性已弃用，取而代之的是 OperationalStatus，后者在其枚举中包括相同的语义。此更改出于以下 3 个原因: 1) 以数组的形式更准确地定义状态。当某个状态实际上是多值属性时(例如，某个元素的状态可能是“正常”和“已停止”)，此定义就能克服通过单个值描述状态的局限性。 2) MaxLen 为 10 的限制太严格，导致枚举值模糊不清。 3) 对 uint16 数据类型的更改在定义 CIM V2.0 时已讨论。但是，现有的 V1.0 实现使用的是字符串属性，不希望修改其代码。因此，Status 归属到 Schema 中。使用 DEPRECATED 限定符可以保留现有的属性，同时允许使用 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.
35	表示元素的当前运行状况。此属性表明此元素(不必是其子组件)的运行状况。可能的值为 0 到 30，其中 5 意味着元素运行完全正常，30 意味着元素运行完全不正常。定义的状态集如下: “不可恢复的错误”(30) - 元素以失败告终，并且无法恢复。此元素提供的所有功能均已丧失。 “严重故障”(25) - 元素运行不正常，并且可能无法恢复。 “主要故障”(20) - 元素失败。此组件的部分或全部功能可能已降级或无法使用。 “次要故障”(15) - 所有功能均可使用，但是有些功能可能已降级。 “已降级/警告”(10) - 元素正在工作，并且提供所有功能。但是元素未实现最佳效果。例如，元素可能未实现最佳性能或报告了可恢复的错误。 “正常”(5) - 元素运行完全正常，使用正常的操作参数工作，没有出现错误。 “未知”(0) - 实现此时无法报告 HealthState。 DMTF 在状态集中为以后增加 HealthStates 保留了未用的部分。	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.
36	已降级/警告	Degraded/Warning
37	次要故障	Minor failure
38	主要故障	Major failure
39	严重故障	Critical failure
41	CommunicationStatus 表示检测与基础 ManagedElement 的通信能力。CommunicationStatus 包含以下某个值:“未知”、“无”、“通信正常”、“通信中断”或“无连接”。 如果返回 Null，则表示该实现(提供程序)未实现此属性。 “未知”表示该实现一般情况下能返回此属性，但是当前无法完成此操作。 “不可用”表示该实现(提供程序)能返回此属性的值，但并非针对此特定硬件/软件，或者由于此属性并不提供任何有意义的信息(例如某个属性只是为了向另一个属性添加附加信息)，因而有意未使用此属性。 “通信正常”表示已与元素建立了通信，但是未传达任何服务质量信息。 “无连接”表示监视系统了解此元素，但是一直无法与其建立通信。 “通信中断”表示 ManagedElement 元素已知存在，并且过去曾成功建立联系，但是当前不可访问。	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.
42	不可用	Not Available
43	通信正常	Communication OK
44	作为 PrimaryStatus 的补充，DetailedStatus 提供其他状态详细信息。它包含以下某个值:“不可用”、“无其他信息”、“已强调”、“预计故障”、“错误”、“不可恢复的错误”或“支持实体出错”。详细的状态用于进一步阐述元素的 PrimaryStatus。 如果返回 Null，则表示该实现(提供程序)未实现此属性。 “不可用”表示该实现(提供程序)能返回此属性的值，但并非针对此特定硬件/软件，或者由于此属性并不提供任何有意义的信息(例如某个属性只是为了向另一个属性添加附加信息)，因而有意未使用此属性。 “无其他信息”表示元素如 PrimaryStatus 的“正常”状态所示在正常工作。 “已强调”表示元素正在工作，但是需要注意。过载、过热等都属于“已强调”状态。 “预计故障”表示元素表面上正在工作，但是预计不久会出现故障。 “不可恢复的错误”表示此元素出现需要人工干预的错误。 “支持实体出错”表示此元素可能“正常”，但是此元素所依赖的另一个元素出现错误。由于低层网络问题而无法工作的网络服务或终结点就属于这种情况。	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.
45	无其他信息	No Additional Information
46	OperatingStatus 提供元素运行状况的当前状态值，可用于提供有关 EnabledState 值的更多详细信息。当元素从一种状态向另一种状态过渡时，例如元素处于 EnabledState 与 RequestedState 之间的过渡以及其他过渡期，OperatingStatus 还可以提供过渡状态信息。 OperatingStatus 包含以下值之一: “未知”、“不可用”、“服务中”、“正在启动”、“正在停止”、“已停止”、“已中止”、“休止”、“已完成”、“正在迁移”、“正在迁出”、“正在迁入”、“正在拍摄快照”、“正在关闭”或“正在测试”。 如果返回 Null，则表示该实现(提供程序)未实现此属性。 “未知”表示该实现一般情况下能返回此属性，但是当前无法返回。 “无”表示该实现(提供程序)能返回此属性的值，但并非针对此特定硬件/软件，或者由于此属性并不提供任何有意义的信息(例如某个属性只是为了向另一个属性添加附加信息)，因而有意未使用此属性。 “正在维护”说明元素正在接受配置、维护、清洁或其他方式的管理。 “正在启动”说明元素正在初始化。 “正在停止”说明元素正在进入有序的停止状态。 “已停止”和“已中止”类似，只是前者暗示正常有序地停止，而后者暗示紧急停止，元素的状态和配置可能需要更新。 “休止”表示元素处于非活动状态或静态。 “已完成”表示该元素已完成操作。此值应与 PrimaryStatus 中的“正常”、“错误”或“已降级”组合使用，使客户端可以确定整个操作是已经正常地完成(已通过)、已经完成但出现错误(出现故障)，还是已经完成但是降级(操作已完成，但是未“正常”地完成或未报告错误)。 “正在迁移”说明元素正在主机元素之间移动。 “正在迁入”说明元素正在向某个新的主机元素移入。 “正在迁出”说明元素正在从主机元素移出。 “正在关闭”说明元素正在进入紧急停止状态。 “正在测试”说明元素正在执行测试功能。 “正在过渡”说明元素处于两种状态之间的过渡期，即该元素目前在前一状态和下一状态中均不完全可用。在没有其他适用的值可以表明到某个特定状态的过渡时，应使用此值。 “服务中”说明元素正在工作，可以使用。	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.
47	正在维护	Servicing
48	正在迁移	Migrating
49	正在迁出	Emigrating
50	正在迁入	Immigrating
51	正在拍摄快照	Snapshotting
52	正在关闭	Shutting Down
53	正在测试	In Test
54	正在转换	Transitioning
55	PrimaryStatus 提供了一个高级状态值，用来对应状态的红-黄-绿三种类型表示形式。该值应与 DetailedStatus 结合使用，这样才能提供 ManagedElement 及其子组件的高级和详细的运行状况状态。 PrimaryStatus 包括以下值之一: “未知”、“正常”、“已降级”或“错误”。“未知”表示该实现一般情况下能返回此属性，但是当前无法返回。 “正常”表示 ManagedElement 运行正常。 “已降级”表示 ManagedElement 运行在正常级别之下。 “错误”表示 ManagedElement 出现了错误状况。	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.
56	CIM_ManagedSystemElement 是系统元素层次结构的基类。任何可辨别的系统组件都能包含在此类中。系统组件的示例包括: - 应用程序服务器、数据库和应用程序等软件组件 - 文件、进程和线程等操作系统组件 - 磁盘驱动器、控制器、处理器和打印机等设备组件 - 芯片和卡等物理组件。	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.
57	2.22.0	2.22.0
58	CIM_LogicalElement 是所有代表抽象系统组件(例如文件、进程或 LogicalDevice)的系统组件的基类。	CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices.
59	2.6.0	2.6.0
60	表示作业状态的自由格式字符串。主状态反映在继承的 OperationalStatus 属性中。JobStatus 提供了其他特定于实现的详细信息。	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.
61	提交作业以执行的时间。如果值为全零，则表示所属元素无法报告日期和时间。因此，ScheduledStartTime 和 StartTime 是以相对于请求其值的时间的时间间隔形式报告的。	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.
62	当前作业计划开始的时间。此时间可以用实际日期和时间表示，也可以用相对于请求此属性的时间的时间间隔表示。如果值为全零表示作业已在执行。此属性已弃用，取而代之的是更富有表现力的计划属性(RunMonth、RunDay、RunDayOfWeek 和 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.
63	作业实际开始的时间。此时间可以用实际日期和时间表示，也可以用相对于请求此属性的时间的时间间隔表示。请注意，此属性也存在于 JobProcessingStatistics 类中。该类是捕获周期性作业的处理信息所必需的，因为只有“上次”运行时间才能存储在此单值属性中。	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.
64	作业已执行的时间间隔或总执行时间(如果作业已完成)。请注意，此属性也存在于 JobProcessingStatistics 类中。该类是捕获周期性作业的处理信息所必需的，因为只有“上次”运行时间才能存储在此单值属性中。	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.
65	作业应运行的次数。值为 1 表示该作业不是周期性的，而任何非零值则表示对重复执行此作业的次数限制。零表示对可以处理此作业的次数没有限制，但此作业在 UntilTime 过后或通过手动干预可终止。默认情况下，作业只被处理一次。	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.
66	应处理作业的月。指定 0 表示一月，指定 1 表示二月，依此类推。	The month during which the Job should be processed. Specify 0 for January, 1 for February, and so on.
67	一月	January
68	二月	February
69	三月	March
70	四月	April
71	五月	May
72	六月	June
73	七月	July
74	八月	August
75	九月	September
76	十月	October
77	十一月	November
78	十二月	December
79	一个月中应处理作业的天。对于此属性有两种不同的解释，具体取决于 DayOfWeek 的值。在一种情况下，RunDay 定义月中的第几天处理作业。当 DayOfWeek 为 0 时将使用这种解释。正整数或负整数指示应从月初还是月底计算 RunDay。例如，5 表示 RunMonth 中的第五天，而 -1 表示 RunMonth 中的最后一天。 当 RunDayOfWeek 不为 0 时，RunDay 是指月中第几天处理作业，该天数与 RunDayOfWeek 一起定义。例如，如果 RunDay 是 15 而 RunDayOfWeek 是星期六，则将在 RunMonth 中的第 15 天或之后的第一个星期六(例如，该月的第三个星期六)处理作业。如果 RunDay 是 20 而 RunDayOfWeek 是“-星期六”，则这表示 RunMonth 中的第 20 天或之前的第一个星期六。如果 RunDay 是 -1，而 RunDayOfWeek 是“-星期日”，则这表示 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.
80	与 RunDay 一起使用以指示星期几处理作业的正整数或负整数。RunDayOfWeek 设置为 0 表示该月的确切日期，如 3 月 1 日。正整数(代表星期日、星期一、...、星期六)表示在指定的 RunDay 或之后找到星期几。负整数(代表“-星期日”、“-星期一”、...、“-星期六”)表示在指定的 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
82	-星期五	-Friday
83	-星期四	-Thursday
84	-星期三	-Wednesday
85	-星期二	-Tuesday
86	-星期一	-Monday
87	-星期日	-Sunday
88	ExactDayOfMonth	ExactDayOfMonth
89	星期日	Sunday
90	星期一	Monday
91	星期二	Tuesday
92	星期三	Wednesday
93	星期四	Thursday
94	星期五	Friday
95	星期六	Saturday
96	午夜后应处理作业时的时间间隔。例如， 00000000020000.000000:000 指示应在本地时间或 UTC 时间(使用 LocalOrUtcTime 属性进行区分)两点钟或之后运行作业。	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.
97	此属性指示 RunStartInterval 和 UntilTime 属性中表示的时间表示本地时间还是 UTC 时间。这些时间值使用枚举值 2 (“UTC 时间”)在全球范围内同步。	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".
98	本地时间	Local Time
99	UTC 时间	UTC Time
100	一个时间，在该时间过后，作业将成为无效作业或应被停止。此时间可以用实际日期和时间表示，也可以用相对于请求此属性的时间的时间间隔表示。值为全 9 表示作业可以无限期运行。	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.
101	作业完成或失败时要通知的用户。	The User who is to be notified upon the Job completion or failure.
102	提交作业的用户，或导致创建作业的服务或方法名称。	The User that submitted the Job, or the Service or method name that caused the job to be created.
103	指示执行作业的紧迫性或重要性。数字越小，优先级越高。请注意，此属性也存在于 JobProcessingStatistics 类中。该类是捕获影响作业结果的设置信息所必需的。	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.
104	请求此值时已完成作业的百分比。请注意，此属性也存在于 JobProcessingStatistics 类中。该类是捕获周期性作业的处理信息所必需的，因为只有“上次”运行数据可以存储在此单值属性中。 请注意，值 101 是未定义的，不允许在此规范的下一个主要修订版中使用。	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.
105	百分比	Percent
106	指示作业在完成后是否应自动删除。请注意，周期性作业的“完成”由其 JobRunTimes 或 UntilTime 属性定义，或者由通过手动干预终止作业的时间定义。如果此属性设置为 false 并且作业已完成，则必须使用外部方法 DeleteInstance 来删除作业，而不是更新此属性。	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.
107	供应商特定的错误代码。如果作业完成时没有错误，则此值必须设置为零。请注意，此属性也存在于 JobProcessingStatistics 类中。该类是捕获周期性作业的处理信息所必需的，因为只有 “上次” 运行错误可以存储在此单值属性中。	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.
108	包含供应商错误描述的自由格式字符串。请注意，此属性也存在于 JobProcessingStatistics 类中。该类是捕获周期性作业的处理信息所必需的，因为只有 “上次” 运行错误可以存储在此单值属性中。	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.
109	描述要为未成功运行的作业执行的恢复操作。可能的值包括: 0 =“未知”，表示要执行的恢复操作是未知的 1 =“其他”，表示将在 OtherRecoveryAction 属性中指定恢复操作 2 =“不继续”，表示停止执行作业并相应地更新其状态 3 =“继续执行下一个作业”，表示继续执行队列中的下一个作业 4 =“重新运行作业”，表示应重新运行该作业 5 =“运行恢复作业”，表示使用 RecoveryJob 关系运行关联的作业。请注意，恢复作业必须已在它将从中运行的队列中。	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.
110	不继续	Do Not Continue
111	继续执行下一个作业	Continue With Next Job
112	重新运行作业	Re-run Job
113	运行恢复作业	Run Recovery Job
114	一个字符串，用于描述在实例的 RecoveryAction 属性为 1 (“其他”)时的恢复操作。	A string describing the recovery action when the RecoveryAction property of the instance is 1 ("Other").
115	KillJob 已弃用，因为在顺序关闭和立即终止之间未进行任何区分。CIM_ConcreteJob.RequestStateChange()提供了“终止(Terminate)”和“终止(Kill)”选项，来实现此区分。 该方法可以结束此作业和任何基础进程，并可删除任何“无关联的”关联。	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.
116	成功	Success
117	不支持	Not Supported
118	超时	Timeout
119	失败	Failed
120	拒绝访问	Access Denied
121	找不到	Not Found
122	供应商特定	Vendor Specific
123	指示终止作业时是否应自动删除作业。此参数优先于属性 DeleteOnCompletion。	Indicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion.
124	作业是一个表示工作的执行单元的 LogicalElement，例如脚本或打印作业。作业不同于进程的地方在于: 作业可以计划或排队，并且它的执行不限于单个系统。	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.
125	2.10.0	2.10.0
126	错误的主要分类。定义了以下值: 2 - 通信错误。此类错误主要与在两点之间传输信息所需要的过程和/或进程有关。 3 - 服务质量错误。此类错误主要与导致功能或性能下降的故障有关。 4 - 软件错误。此类错误主要与软件或处理故障有关。 5 - 硬件错误。此类错误主要与设备或硬件故障有关。 6 - 环境错误。此类错误主要与以下内容有关: 与设备或其他环境考虑事项相关的故障条件。 7 - 安全错误。此类错误与违反安全规则、检测到病毒，以及类似的问题有关。 8 -“过度订阅”错误。此类错误主要与分配充足的资源以完成操作时发生的故障有关。 9 -“资源不可用”错误。此类错误主要与访问所需资源时发生的故障有关。 10 -不受支持的操作错误。此类错误主要与不受支持的请求有关。	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.
127	通信错误	Communications Error
128	服务质量错误	Quality of Service Error
129	软件错误	Software Error
130	硬件错误	Hardware Error
131	环境错误	Environmental Error
132	安全错误	Security Error
133	“过度订阅”错误	Oversubscription Error
134	“资源不可用”错误	Unavailable Resource Error
135	不受支持的操作错误	Unsupported Operation Error
136	自由格式的字符串，用于在将 1 (“其他”)指定为错误类型时描述该错误类型。	A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.
137	唯一标识实体(拥有该实例中所述消息格式的定义)的字符串。OwningEntity 必须包含由定义该格式的商业实体或标准机构所拥有的版权化、商标化或其他形式的唯一名称。	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.
138	在 OwningEntity 的作用域中唯一标识消息格式的不透明字符串。	An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.
139	已设置格式的消息。此消息通过组合 MessageArguments 属性中指定的某些或所有动态元素构造而成，其中，静态元素由消息注册表中的 MessageID 或与 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.
140	包含此消息的动态内容的数组。	An array containing the dynamic content of the message.
141	一个枚举值，该值从通知程序的视角描述“指示”的严重性: 0 - 指示的“感知严重性”未知或不确定。 1 - 按 CIM 惯例，“其他”用于指示可以在 OtherSeverity 属性中找到的严重性值。 2 - 当提供信息性响应时，应该使用“信息”。 3 - 当适合让用户决定是否需要采取措施时，应该使用“降级/警告”。 4 - 应该使用“次要”来指示需要采取相应措施，但此时情况不严重。 5 - 应该使用“主要”来指示需要立即采取相应措施。 6 - 应该使用“严重”来指示需要立即采取相应措施，而且影响范围广泛(可能会很快导致关键资源无法提供)。 7 - 应该使用“致命/无法恢复”来指示发生了错误，但为时已晚，无法采取补救措施。 2 和 0 - 对于“信息”和“未知”，应当(分别)遵循其常见用法。确切地说，这些错误是纯信息性错误或者其严重性未知。	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.
142	信息	Information
143	次要	Minor
144	主要	Major
145	严重	Critical
146	致命/无法恢复	Fatal/NonRecoverable
147	用于描述引发错误的可能原因的枚举值。	An enumerated value that describes the probable cause of the error.
148	适配器/卡错误	Adapter/Card Error
149	应用程序子系统故障	Application Subsystem Failure
150	带宽减少	Bandwidth Reduced
151	连接建立错误	Connection Establishment Error
152	通信协议错误	Communications Protocol Error
153	通信子系统故障	Communications Subsystem Failure
154	配置/自定义错误	Configuration/Customization Error
155	拥塞	Congestion
156	数据已损坏	Corrupt Data
157	超出 CPU 周期限制	CPU Cycles Limit Exceeded
158	数据集/调制解调器错误	Dataset/Modem Error
159	信号降级	Degraded Signal
160	DTE-DCE 接口错误	DTE-DCE Interface Error
161	机箱门未关闭	Enclosure Door Open
162	设备故障	Equipment Malfunction
163	振动过度	Excessive Vibration
164	文件格式错误	File Format Error
165	检测到火灾	Fire Detected
166	检测到洪水	Flood Detected
167	帧错误	Framing Error
168	HVAC 问题	HVAC Problem
169	湿度无法接受	Humidity Unacceptable
170	I/O 设备错误	I/O Device Error
171	输入设备错误	Input Device Error
172	LAN 错误	LAN Error
173	检测到无毒物质泄露	Non-Toxic Leak Detected
174	本地节点传输错误	Local Node Transmission Error
175	帧丢失	Loss of Frame
176	信号缺失	Loss of Signal
177	材料供应耗竭	Material Supply Exhausted
178	多路复用器问题	Multiplexer Problem
179	内存不足	Out of Memory
180	输出设备错误	Output Device Error
181	性能降低	Performance Degraded
182	电源问题	Power Problem
183	压力不可接受	Pressure Unacceptable
184	处理器问题(内部计算机错误)	Processor Problem (Internal Machine Error)
185	泵故障	Pump Failure
186	超出队列大小	Queue Size Exceeded
187	接收故障	Receive Failure
188	接收器故障	Receiver Failure
189	远程节点传输错误	Remote Node Transmission Error
190	资源达到或接近容量	Resource at or Nearing Capacity
191	响应时间过长	Response Time Excessive
192	重新传输率过高	Retransmission Rate Excessive
193	软件程序异常终止	Software Program Abnormally Terminated
194	软件程序错误(结果不正确)	Software Program Error (Incorrect Results)
195	存储容量问题	Storage Capacity Problem
196	温度不可接受	Temperature Unacceptable
197	已超过阈值	Threshold Crossed
198	计时问题	Timing Problem
199	检测到有毒物质泄露	Toxic Leak Detected
200	传输故障	Transmit Failure
201	发送器故障	Transmitter Failure
202	基础资源无法使用	Underlying Resource Unavailable
203	版本不匹配	Version Mismatch
204	之前的警报已清除	Previous Alert Cleared
205	登录尝试失败	Login Attempts Failed
206	检测到软件病毒	Software Virus Detected
207	违反硬件安全	Hardware Security Breached
208	检测到拒绝服务	Denial of Service Detected
209	安全凭据不匹配	Security Credential Mismatch
210	访问未经授权	Unauthorized Access
211	收到警报	Alarm Received
212	指针缺失	Loss of Pointer
213	负载不匹配	Payload Mismatch
214	传输错误	Transmission Error
215	错误率过高	Excessive Error Rate
216	跟踪问题	Trace Problem
217	元素无法使用	Element Unavailable
218	缺少元素	Element Missing
219	多个帧缺失	Loss of Multi Frame
220	广播通道故障	Broadcast Channel Failure
221	收到的消息无效	Invalid Message Received
222	路由故障	Routing Failure
223	底板故障	Backplane Failure
224	标识符重复	Identifier Duplication
225	保护路径故障	Protection Path Failure
226	失去同步或同步不匹配	Sync Loss or Mismatch
227	终端问题	Terminal Problem
228	实时时钟故障	Real Time Clock Failure
229	天线故障	Antenna Failure
230	电池充电故障	Battery Charging Failure
231	磁盘故障	Disk Failure
232	频率跳转故障	Frequency Hopping Failure
233	冗余缺失	Loss of Redundancy
234	电源故障	Power Supply Failure
235	信号质量问题	Signal Quality Problem
236	电池正在放电	Battery Discharging
237	电池故障	Battery Failure
238	商业用电问题	Commercial Power Problem
239	风扇故障	Fan Failure
240	引擎故障	Engine Failure
241	传感器故障	Sensor Failure
242	保险丝故障	Fuse Failure
243	生成器故障	Generator Failure
244	电池电量不足	Low Battery
245	燃料不足	Low Fuel
246	水不足	Low Water
247	爆炸性气体	Explosive Gas
248	大风	High Winds
249	结冰	Ice Buildup
250	冒烟	Smoke
251	内存不匹配	Memory Mismatch
252	超出 CPU 周期	Out of CPU Cycles
253	软件环境问题	Software Environment Problem
254	软件下载故障	Software Download Failure
255	元素已重新初始化	Element Reinitialized
256	日志记录问题	Logging Problems
257	检测到泄露	Leak Detected
258	保护机制故障	Protection Mechanism Failure
259	保护资源故障	Protecting Resource Failure
260	数据库不一致	Database Inconsistency
261	身份验证失败	Authentication Failure
262	违反保密性	Breach of Confidentiality
263	电缆篡改	Cable Tamper
264	信息延迟	Delayed Information
265	信息重复	Duplicate Information
266	缺少信息	Information Missing
267	信息被修改	Information Modification
268	信息无序	Information Out of Sequence
269	密钥到期	Key Expired
270	不可否认的故障	Non-Repudiation Failure
271	活动超时	Out of Hours Activity
272	停止服务	Out of Service
273	过程错误	Procedural Error
274	意外信息	Unexpected Information
275	描述引发错误的可能原因的自由格式字符串。	A free-form string describing the probable cause of the error.
276	描述解决错误应采取的建议操作的自由格式字符串。	A free-form string describing recommended actions to take to resolve the error.
277	生成错误的实体(即，实例)的标识信息。如果已在 CIM 架构中为该实体建模，则此属性包含编码为字符串参数的实例路径。如果未建模，则此属性包含某个标识字符串(用于命名生成错误的实体)。路径或标识字符串的格式是根据 ErrorSourceFormat 属性设置的。	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.
278	可以根据此属性的值来解释 ErrorSource 属性的格式。这些值的定义如下所示: 0 - 未知。格式未知或者无法由 CIM 客户端应用程序提供有意义的解释。 1 - 其他。此格式由 OtherErrorSourceFormat 属性的值定义。2 - CIMObjectPath。根据 CIM 基础结构规范定义的 CIM 对象路径。注意: CIM 2.5 以及更早版本使用术语“对象名称”。	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.
279	CIMObjectPath	CIMObjectPath
280	为 ErrorSourceFormat 定义“其他”值的字符串。当 ErrorSourceFormat 设置为值 1 (“其他”)时，此值必须设置为一个非 NULL 值。对于 ErrorSourceFormat 的所有其他值，必须将此字符串的值设置为 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.
281	表示该实例特征的 CIM 状态代码。 此属性定义符合相应特征的 CIM 服务器或侦听器可能返回的状态代码。请注意，并非所有状态代码对于每个操作都有效。每个操作的规范都应该定义该操作可能返回的状态代码。 为 CIM 状态代码定义的值如下: 1 - CIM_ERR_FAILED。发生了更具体错误代码未包括的常规错误。 2 - CIM_ERR_ACCESS_DENIED。客户端无法访问 CIM 资源。 3 - CIM_ERR_INVALID_NAMESPACE。目标命名空间不存在。 4 - CIM_ERR_INVALID_PARAMETER。传递给方法的一个或多个参数值无效。 5 - CIM_ERR_INVALID_CLASS。指定的类不存在。 6 - CIM_ERR_NOT_FOUND。找不到请求的对象。 7 - CIM_ERR_NOT_SUPPORTED。不支持请求的操作。 8 - CIM_ERR_CLASS_HAS_CHILDREN。无法对该类执行操作，因为该类具有实例。 9 - CIM_ERR_CLASS_HAS_INSTANCES。无法对该类执行操作，因为该类具有实例。 10 - CIM_ERR_INVALID_SUPERCLASS。无法执行操作，因为指定的超类不存在。 11 - CIM_ERR_ALREADY_EXISTS。无法执行操作，因为已存在一个对象。 12 - CIM_ERR_NO_SUCH_PROPERTY。指定的属性不存在。 13 - CIM_ERR_TYPE_MISMATCH。提供的值与类型不符。 14 - CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED。无法识别或不支持查询语言。 15 - CIM_ERR_INVALID_QUERY。查询对于指定的查询语言无效。 16 - CIM_ERR_METHOD_NOT_AVAILABLE。无法执行外部方法。 17 - CIM_ERR_METHOD_NOT_FOUND。指定的外部方法不存在。 18 - CIM_ERR_UNEXPECTED_RESPONSE。返回的异步操作响应不是预期响应。 19 - CIM_ERR_INVALID_RESPONSE_DESTINATION。异步响应的指定目标无效。 20 - CIM_ERR_NAMESPACE_NOT_EMPTY。指定的命名空间不为空。 21 - CIM_ERR_INVALID_ENUMERATION_CONTEXT。提供的枚举上下文无效。 22 - CIM_ERR_INVALID_OPERATION_TIMEOUT。指定的命名空间不为空。 23 - CIM_ERR_PULL_HAS_BEEN_ABANDONED。指定的命名空间不为空。 24 - CIM_ERR_PULL_CANNOT_BE_ABANDONED。尝试放弃拉操作失败。 25 - CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED。不支持筛选的枚举。 26 - CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED。不支持发生错误时继续操作。 27 - CIM_ERR_SERVER_LIMITS_EXCEEDED。已超过 WBEM 服务器限制(例如，内存、连接数等)。 28 - CIM_ERR_SERVER_IS_SHUTTING_DOWN。WBEM 服务器正在关闭。 29 - CIM_ERR_QUERY_FEATURE_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.
282	CIM_ERR_FAILED	CIM_ERR_FAILED
283	CIM_ERR_ACCESS_DENIED	CIM_ERR_ACCESS_DENIED
284	CIM_ERR_INVALID_NAMESPACE	CIM_ERR_INVALID_NAMESPACE
285	CIM_ERR_INVALID_PARAMETER	CIM_ERR_INVALID_PARAMETER
286	CIM_ERR_INVALID_CLASS	CIM_ERR_INVALID_CLASS
287	CIM_ERR_NOT_FOUND	CIM_ERR_NOT_FOUND
288	CIM_ERR_NOT_SUPPORTED	CIM_ERR_NOT_SUPPORTED
289	CIM_ERR_CLASS_HAS_CHILDREN	CIM_ERR_CLASS_HAS_CHILDREN
290	CIM_ERR_CLASS_HAS_INSTANCES	CIM_ERR_CLASS_HAS_INSTANCES
291	CIM_ERR_INVALID_SUPERCLASS	CIM_ERR_INVALID_SUPERCLASS
292	CIM_ERR_ALREADY_EXISTS	CIM_ERR_ALREADY_EXISTS
293	CIM_ERR_NO_SUCH_PROPERTY	CIM_ERR_NO_SUCH_PROPERTY
294	CIM_ERR_TYPE_MISMATCH	CIM_ERR_TYPE_MISMATCH
295	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED
296	CIM_ERR_INVALID_QUERY	CIM_ERR_INVALID_QUERY
297	CIM_ERR_METHOD_NOT_AVAILABLE	CIM_ERR_METHOD_NOT_AVAILABLE
298	CIM_ERR_METHOD_NOT_FOUND	CIM_ERR_METHOD_NOT_FOUND
299	CIM_ERR_UNEXPECTED_RESPONSE	CIM_ERR_UNEXPECTED_RESPONSE
300	CIM_ERR_INVALID_RESPONSE_DESTINATION	CIM_ERR_INVALID_RESPONSE_DESTINATION
301	CIM_ERR_NAMESPACE_NOT_EMPTY	CIM_ERR_NAMESPACE_NOT_EMPTY
302	CIM_ERR_INVALID_ENUMERATION_CONTEXT	CIM_ERR_INVALID_ENUMERATION_CONTEXT
303	CIM_ERR_INVALID_OPERATION_TIMEOUT	CIM_ERR_INVALID_OPERATION_TIMEOUT
304	CIM_ERR_PULL_HAS_BEEN_ABANDONED	CIM_ERR_PULL_HAS_BEEN_ABANDONED
305	CIM_ERR_PULL_CANNOT_BE_ABANDONED	CIM_ERR_PULL_CANNOT_BE_ABANDONED
306	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED
307	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED
308	CIM_ERR_SERVER_LIMITS_EXCEEDED	CIM_ERR_SERVER_LIMITS_EXCEEDED
309	CIM_ERR_SERVER_IS_SHUTTING_DOWN	CIM_ERR_SERVER_IS_SHUTTING_DOWN
310	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED
311	自由格式的字符串，包含用户可读的 CIMStatusCode 描述。该描述可以扩展，但必须与 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.
312	2.22.1	2.22.1
313	CIM_Error 是一个特殊类，包含与某个 CIM 操作失败有关的严重性、原因、建议操作以及其他数据的相关信息。这种类型的实例可以作为某个 CIM 操作的响应的一部分。	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.
314	在实例化 Namespace 的作用域内，InstanceID 以不透明的方式唯一标识此类的实例。为了确保在 Namespace 中的唯一性，InstanceID 的值应使用下列“首选”算法构造: : 其中 和 通过冒号 ":" 分隔， 必须包括由创建或定义该 InstanceID 的商业实体所拥有的版权化、商标化或其他形式的唯一名称，或是由公认的全球性机构为商业实体分配的注册 ID。(此要求类似于架构类名的 _ 结构)。此外，为了确保唯一性， 不得包含冒号(":")。在使用此算法时，InstanceID 中的第一个冒号必须出现在 和 之间。 由商业实体选择，不应反复用于标识不同的基础(实际)元素。如果不使用上面的“首选”算法，定义实体必须确保不在此提供程序或其他提供程序为此实例的 NameSpace 生成的任何 InstanceID 间重复使用生成的 InstanceID。 对于 DMTF 定义的实例，使用“首选”算法时， 必须设置为 "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\'.
315	此作业实例的用户友好名称。此外，用户友好名称还可以用作搜索或查询的属性。(注意: 名称不必在命名空间中唯一。)	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.)
316	JobState 是一个指示作业运行状态的整数枚举。它还可以指示这些状态(例如，“正在关闭”和“正在启动”)之间的转换。下面是这些状态的简要说明: “新”(2)指示作业从未启动过。 “正在启动”(3)指示作业正在从“新”、“已暂停”或“服务”状态转换到 “正在运行”状态。 “正在运行”(4)指示作业正在运行。 “已暂停”(5)指示作业已停止，但可以采用一种无缝方式重新启动。 “正在关闭”(6)指示作业正在转换到“已完成”、“已终止(Terminated)”或“已终止(Killed)”状态。 “已完成”(7)指示作业已正常完成。 “已终止(Terminated)”(8)指示作业已被“终止(Terminate)”状态更改请求所停止。作业及其所有基础进程都已结束，并且只能以新作业的形式重新启动(此操作特定于作业)。 “已终止(Killed)”(9)指示作业已被“终止(Kill)”状态更改请求所停止。基础进程可能仍然运行，并且可能需要清理才能释放资源。 “异常”(10)指示作业处于异常状态，这可能表示存在错误情况。可能会通过特定于作业的对象来显示实际状态。 “服务”(11)指示作业处于特定于供应商的状态，该状态支持发现问题和/或解决问题。 “查询暂停”(12)等待客户端解析查询	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
317	新	New
318	正在运行	Running
319	已暂停	Suspended
320	已终止(Terminated)	Terminated
321	已终止(Killed)	Killed
322	异常	Exception
323	服务	Service
324	查询挂起	Query Pending
325	上次更改作业状态的日期或时间。如果作业状态未更改而此属性已填充，则必须将其设为 0 时间间隔值。如果已请求状态更改，但被拒绝或尚未处理，则不能更新此属性。	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.
326	作业在已完成执行(无论该执行成功还是失败)后保留的时间长度。该作业必须仍然存在一段时间，而不管 DeleteOnCompletion 属性的值如何设置。 默认值为 5 分钟。	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.
327	请求将作业的状态更改为 RequestedState 参数中指定的值。多次调用 RequestStateChange 方法可能导致之前的请求被覆盖或丢失。 如果返回 0，则表示任务已成功完成。任何其他返回代码均指示错误情况。	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.
328	已完成且没有错误	Completed with No Error
329	未知/未指定的错误	Unknown/Unspecified Error
330	在超时期限内无法完成	Can NOT complete within Timeout Period
331	参数无效	Invalid Parameter
332	正在使用	In Use
333	已检查方法参数 - 转换已启动	Method Parameters Checked - Transition Started
334	无效的状态转换	Invalid State Transition
335	不支持使用超时参数	Use of Timeout Parameter Not Supported
336	忙碌	Busy
337	保留的方法	Method Reserved
338	RequestStateChange 可更改作业的状态。可能的值如下所示: “启动”(2)将状态更改为“正在运行”。 “暂停”(3)暂时停止作业。目的是为了随后通过“启动”重新启动作业。在已暂停时可能会进入“服务” 状态。(此操作特定于作业。) “终止(Terminate)”(4)完全停止作业、保存数据、保留状态，并按顺序关闭所有基础进程。 “终止(Kill)”(5)立即终止作业，而不要求保存数据或保留状态。 “服务”(6)将作业置于特定于供应商的服务状态。可能会重新启动作业。	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.
339	启动	Start
340	暂停	Suspend
341	终止(Terminate)	Terminate
342	终止(Kill)	Kill
343	指定客户端预期转换到新状态所需的最长时间的超时期限。必须使用时间间隔格式来指定 TimeoutPeriod。值为 0 或 Null 参数指示客户端对于转换没有时间要求。 如果此属性不包含 0 或 Null，并且相应的实现不支持此参数，则必须返回“不支持使用超时参数”的返回代码。	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.
344	当作业正在执行或已终止而未出错时，此方法不返回 CIM_Error 实例。但是，如果由于某个内部问题或由于作业已被客户端终止而导致作业失败，则会返回一个 CIM_Error 实例。	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.
345	未指定的错误	Unspecified Error
346	如果作业的 OperationalStatus 不是“正常”，则此方法将返回一个 CIM 错误实例。否则，当作业“正常”时，则返回 Null。	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.
347	作业的具体版本。此类表示泛型的可实例化工作单元，例如批处理或打印作业。	A concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job.
348	InstanceID 是可用于在实例化 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.
349	此属性与 CIM_ComputerSystem 代表的逻辑计算机系统的 EnabledState 属性对应。有关 EnabledState 的详细信息，请参阅 CIM_EnabledLogicalElement.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.
350	已启用	Enabled
351	已禁用	Disabled
352	不适用	Not Applicable
353	已启用但脱机	Enabled but Offline
354	已延迟	Deferred
355	静止	Quiesce
356	此属性与 CIM_ComputerSystem 代表的逻辑计算机系统的 RequestedState 属性对应。有关 RequestedState 的详细信息，请参阅 CIM_EnabledLogicalElement.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.
357	关闭	Shut Down
358	无更改	No Change
359	脱机	Offline
360	测试	Test
361	重新启动	Reboot
362	重置	Reset
363	此属性与 CIM_ComputerSystem 代表的逻辑计算机系统的 OperationalStatus 属性对应。有关详细信息，请参阅 CIM_ManagedSystemElement.OperationalStatus 描述。	This property corresponds to the OperationalStatus property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.OperationalStatus Description for details.
364	正在重定位	Relocating
365	此属性与 CIM_ComputerSystem 代表的逻辑计算机系统的 HealthState 属性对应。有关详细信息，请参阅 CIM_ManagedSystemElement.HealthState。	This property corresponds to the HealthState property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.HealthState for details.
366	此属性指示该物理计算机系统上的 FRU 信息的可用性。有关详细信息，请参阅 CIM_PhysicalAssetCapabilities.FRUInfoSupported。	This property indicates the availability of the FRU Information on this physical computer system. See CIM_PhysicalAssetCapabilities.FRUInfoSupported for details.
367	此属性与 CIM_PhysicalFrame.Tag 对应。有关详细信息，请参阅 CIM_PhysicalFrame.Tag。	This property corresponds to CIM_PhysicalFrame.Tag. See CIM_PhysicalFrame.Tag for details.
368	此属性与 CIM_PhysicalFrame.Manufacturer 对应。有关详细信息，请参阅 CIM_PhysicalFrame.Manufacturer。	This property corresponds to CIM_PhysicalFrame.Manufacturer. See CIM_PhysicalFrame.Manufacturer for details.
369	此属性与 CIM_PhysicalFrame.Model 对应。有关详细信息，请参阅 CIM_PhysicalFrame.Model。	This property corresponds to CIM_PhysicalFrame.Model. See CIM_PhysicalFrame.Model for details.
370	此属性与 CIM_PhysicalFrame.SKU 对应。有关详细信息，请参阅 CIM_PhysicalFrame.SKU。	This property corresponds to CIM_PhysicalFrame.SKU. See CIM_PhysicalFrame.SKU for details.
371	此属性与 CIM_PhysicalFrame.SerialNumber 对应。有关详细信息，请参阅 CIM_PhysicalFrame.SerialNumber。	This property corresponds to CIM_PhysicalFrame.SerialNumber. See CIM_PhysicalFrame.SerialNumber for details.
372	此属性与 CIM_PhysicalFrame.Version 对应。有关详细信息，请参阅 CIM_PhysicalFrame.Version。	This property corresponds to CIM_PhysicalFrame.Version. See CIM_PhysicalFrame.Version for details.
373	此属性与 CIM_PhysicalFrame.PartNumber 对应。有关详细信息，请参阅 CIM_PhysicalFrame.PartNumber。	This property corresponds to CIM_PhysicalFrame.PartNumber. See CIM_PhysicalFrame.PartNumber for details.
374	此属性与 CIM_PowerUtilizationManagementCapabilities 的 PowerUtilizationModesSupported 属性对应。有关详细信息，请参阅 CIM_PowerUtilizationManagementCapabilities.PowerUtilizationModesSupported。	This property corresponds to PowerUtilizationModesSupported property of CIM_PowerUtilizationManagementCapabilities. See CIM_PowerUtilizationManagementCapabilities.PowerUtilizationModesSupported for details.
375	动态	Dynamic
376	静态	Static
377	此属性与 CIM_PowerUtilizationManagementService 的 PowerUtilizationMode 对应。有关详细信息，请参阅 CIM_PowerUtilizationManagementService.PowerUtilizationMode。	This property corresponds to the PowerUtilizationMode of the CIM_PowerUtilizationManagementService. See CIM_PowerUtilizationManagementService.PowerUtilizationMode for details.
378	无	None
379	此属性与 CIM_PowerAllocationSettingData.Limit 对应。有关详细信息，请参阅 CIM_PowerAllocationSettingData.Limit。	This property corresponds to CIM_PowerAllocationSettingData.Limit. See CIM_PowerAllocationSettingData.Limit for details.
380	计算机系统上数字传感器的用户友好名称。有关详细信息，请参阅 CIM_NumericSensor.ElementName。	User-friendly names of the numeric sensors on the computer system. See CIM_NumericSensor.ElementName for details.
381	数字传感器的状态。有关详细信息，请参阅 CIM_NumericSensor.EnabledState。	States of numeric sensors. See CIM_NumericSensor.EnabledState for details.
382	数字传感器的运行状态。有关详细信息，请参阅 CIM_NumericSensor.HealthState。	Health states of numeric sensors. See CIM_NumericSensor.HealthState for details.
383	数字传感器的当前状态。有关详细信息，请参阅 CIM_NumericSensor.CurrentState。	Current states of numeric sensors. See CIM_NumericSensor.CurrentState for details.
384	数字传感器的主要状态。有关详细信息，请参阅 CIM_NumericSensor.PrimaryStatus。	Primary statuses of numeric sensors. See CIM_NumericSensor.PrimaryStatus for details.
385	数字传感器返回的值的基本单位。有关详细信息，请参阅 CIM_NumericSensor.BaseUnits。	Base units of the values returned by the numeric sensors. See CIM_NumericSensor.BaseUnits for details.
386	摄氏度	Degrees C
387	华氏度	Degrees F
388	标准温度	Degrees K
389	伏特	Volts
390	安培	Amps
391	瓦特	Watts
392	焦耳	Joules
393	库仑	Coulombs
394	VA	VA
395	尼特	Nits
396	流明	Lumens
397	勒克斯	Lux
398	坎德拉	Candelas
399	千帕	kPa
400	PSI	PSI
401	牛顿	Newtons
402	CFM	CFM
403	RPM	RPM
404	赫兹	Hertz
405	秒	Seconds
406	分钟	Minutes
407	小时	Hours
408	天	Days
409	周	Weeks
410	密耳	Mils
411	英寸	Inches
412	英尺	Feet
413	立方英寸	Cubic Inches
414	立方英尺	Cubic Feet
415	米	Meters
416	立方厘米	Cubic Centimeters
417	立方米	Cubic Meters
418	升	Liters
419	液量盎司	Fluid Ounces
420	弧度	Radians
421	球面度	Steradians
422	转	Revolutions
423	周期	Cycles
424	重力	Gravities
425	盎司	Ounces
426	磅	Pounds
427	英尺-磅	Foot-Pounds
428	盎司-英寸	Ounce-Inches
429	高斯	Gauss
430	吉伯	Gilberts
431	亨利	Henries
432	法拉	Farads
433	欧姆	Ohms
434	西门子	Siemens
435	摩尔	Moles
436	贝克勒尔	Becquerels
437	PPM (百万分之)	PPM (parts/million)
438	分贝	Decibels
439	DbA	DbA
440	DbC	DbC
441	格雷	Grays
442	西弗特	Sieverts
443	色温开氏度	Color Temperature Degrees K
444	位	Bits
445	字节	Bytes
446	字(数据)	Words (data)
447	双字	DoubleWords
448	四字	QuadWords
450	帕斯卡	Pascals
451	数字传感器返回的值的单位乘数。有关详细信息，请参阅 CIM_NumericSensor.UnitModifier 描述。	Unit modifiers for the values returned by the numeric sensors. See CIM_NumericSensor.UnitModifier description for details.
452	有关详细信息，请参阅 CIM_NumericSensor.RateUnits。	See CIM_NumericSensor.RateUnits for details.
453	每微秒	Per MicroSecond
454	每毫秒	Per MilliSecond
455	每秒	Per Second
456	每分钟	Per Minute
457	每小时	Per Hour
458	每天	Per Day
459	每周	Per Week
460	每月	Per Month
461	每年	Per Year
462	有关详细信息，请参阅 CIM_NumericSensor.CurrentReading。	See CIM_NumericSensor.CurrentReading for details.
463	有关详细信息，请参阅 CIM_NumericSensor.SensorType。	See CIM_NumericSensor.SensorType for details.
464	温度	Temperature
465	电压	Voltage
466	电流	Current
467	转速计	Tachometer
468	计数器	Counter
469	交换机	Switch
470	锁定	Lock
471	湿度	Humidity
472	烟雾检测	Smoke Detection
473	存在	Presence
474	气流	Air Flow
475	电源消耗	Power Consumption
476	电力生产	Power Production
477	压力	Pressure
478	有关详细信息，请参阅 CIM_NumericSensor.OtherSensorTypeDescription。	See CIM_NumericSensor.OtherSensorTypeDescription for details.
479	有关详细信息，请参阅 CIM_NumericSensor.UpperThresholdNonCritical。	See CIM_NumericSensor.UpperThresholdNonCritical for details.
480	有关详细信息，请参阅 CIM_NumericSensor.UpperThresholdCritical 描述。	See CIM_NumericSensor.UpperThresholdCritical description for details.
481	有关详细信息，请参阅 CIM_NumericSensor.UpperThresholdFatal。	See CIM_NumericSensor.UpperThresholdFatal for details.
482	此属性代表该物理计算机系统上的基础日志的标识符。有关详细信息，请参阅 CIM_RecordLog.InstanceID。	This property represents the identifiers for the underlying logs on this physical computer system. See CIM_RecordLog.InstanceID for details.
483	有关详细信息，请参阅 CIM_RecordLog.MaxNumberOfRecords。	See CIM_RecordLog.MaxNumberOfRecords for details.
484	有关详细信息，请参阅 CIM_RecordLog.CurrentNumberOfRecords。	See CIM_RecordLog.CurrentNumberOfRecords for details.
485	有关详细信息，请参阅 CIM_RecordLog.OverWritePolicy。	See CIM_RecordLog.OverWritePolicy for details.
486	满时自动换行	Wraps When Full
487	从不覆盖	Never Overwrites
488	有关详细信息，请参阅 CIM_RecordLog.LogState。	See CIM_RecordLog.LogState for details.
490	擦除	Erasing
491	标识此物理计算机系统上的启动源的字符串。有关详细信息，请参阅 CIM_BootSourceSetting.StructuredBootString 描述。	Strings identifying the boot sources on this physical computer system. See CIM_BootSourceSetting.StructuredBootString description for details.
492	标识应在下一次启动计算机系统期间使用的持久启动配置(除非为下一次启动指定了 OneTimeBootSource)的启动顺序的元素数组。此数组中的每个元素的值都是引用 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.
493	此属性标识用于下一次一次性启动的启动源。此属性的值是引用 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.
494	此属性标识此物理计算机系统上的处理器的数目。	This property identifies the number of processors on this physical computer system.
495	有关详细信息，请参阅 CIM_ProcessorCapabilities.NumberOfProcessorCores。	See CIM_ProcessorCapabilities.NumberOfProcessorCores for details.
496	有关详细信息，请参阅 CIM_ProcessorCapabilities.NumberOfProcessorThreads。	See CIM_ProcessorCapabilities.NumberOfProcessorThreads for details.
497	有关详细信息，请参阅 CIM_Processor.Family。	See CIM_Processor.Family for details.
498	有关详细信息，请参阅 CIM_Processor.MaxClockSpeed。	See CIM_Processor.MaxClockSpeed for details.
499	有关详细信息，请参阅 CIM_Memory.BlockSize。	See CIM_Memory.BlockSize for details.
500	有关详细信息，请参阅 CIM_Memory.NumberOfBlocks。	See CIM_Memory.NumberOfBlocks for details.
501	有关详细信息，请参阅 CIM_Memory.ConsumableBlocks。	See CIM_Memory.ConsumableBlocks for details.
502	当前 BIOS 版本信息的主要版本号组件。	The major number component of the current BIOS version information.
503	当前 BIOS 版本信息的次要版本号组件。	The minor number component of the current BIOS version information.
504	当前 BIOS 版本信息的修订版本号组件。	The revision number component of the current BIOS version information.
505	当前 BIOS 版本信息的内部版本号组件。	The build number component of the current BIOS version information.
506	此物理计算机系统上当前管理固件的版本信息的主要版本号组件。	The major number component of the version information for the current management firmware on this physical computer system.
507	此物理计算机系统上当前管理固件的版本信息的次要版本号组件。	The minor number component of the version information for the current management firmware on this physical computer system.
508	此物理计算机系统上当前管理固件的版本信息的修订版本号组件。	The revision number component of the version information for the current management firmware on this physical computer system.
509	此物理计算机系统上当前管理固件的版本信息的内部版本号组件。	The build number component of the version information for the current management firmware on this physical computer system.
510	此物理计算机系统上当前管理固件的用户友好名称。	The user-friendly name for the current management firmware on this physical computer system.
511	此物理计算机系统上当前管理固件的版本字符串。	The version string for the current management firmware on this physical computer system.
512	此物理计算机系统上当前运行或上次运行的操作系统的类型信息。有关详细信息，请参阅 CIM_OperatingSystem.OSType。	Type information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.OSType for details.
513	此物理计算机系统上当前运行或上次运行的操作系统的版本信息。有关详细信息，请参阅 CIM_OperatingSystem.Version。	Version information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.Version for details.
514	此物理计算机系统上当前运行或上次运行的操作系统的 EnabledState。	EnabledState of the current or last running operating system on this physcial computer system.
515	字符串格式的 BIOS 版本信息。	The BIOS version information in string format.
516	有关详细信息，请参阅 CIM_ComputerSystem.Dedicated。	See CIM_ComputerSystem.Dedicated for details.
517	非专用	Not Dedicated
518	存储	Storage
519	路由器	Router
520	第 3 层交换机	Layer 3 Switch
521	中央办公室交换机	Central Office Switch
522	集线器	Hub
523	访问服务器	Access Server
524	防火墙	Firewall
525	打印	Print
526	I/O	I/O
527	Web 缓存	Web Caching
528	管理	Management
529	块服务器	Block Server
530	文件服务器	File Server
531	移动用户设备	Mobile User Device
532	中继器	Repeater
533	网桥/扩展器	Bridge/Extender
534	网关	Gateway
535	存储仿真器	Storage Virtualizer
536	媒体库	Media Library
537	ExtenderNode	ExtenderNode
538	NAS 头	NAS Head
539	独立 NAS	Self-contained NAS
540	UPS	UPS
541	IP 电话	IP Phone
542	管理控制器	Management Controller
543	底盘管理器	Chassis Manager
544	基于主机的 RAID 控制器	Host-based RAID controller
545	存储设备机箱	Storage Device Enclosure
546	台式计算机	Desktop
547	笔记本电脑	Laptop
548	虚拟磁带库	Virtual Tape Library
549	虚拟库系统	Virtual Library System
550	网络电脑/瘦客户端	Network PC/Thin Client
551	FC 交换机	FC Switch
552	以太网交换机	Ethernet Switch
553	有关详细信息，请参阅 CIM_System.IdentifyingDescriptions。	See CIM_System.IdentifyingDescriptions for details.
554	有关详细信息，请参阅 CIM_ComputerSystem.OtherDedicatedDescriptions。	See CIM_ComputerSystem.OtherDedicatedDescriptions for details.
555	有关详细信息，请参阅 CIM_System.OtherIdentifyingInfo。	See CIM_System.OtherIdentifyingInfo for details.
556	有关详细信息，请参阅 CIM_Processor.CurrentClockSpeed。	See CIM_Processor.CurrentClockSpeed for details.
557	有关详细信息，请参阅 CIM_Sensor.SensorContext。	See CIM_Sensor.SensorContext for details.
558	有关详细信息，请参阅 CIM_NumericSensor.LowerThresholdNonCritical。	See CIM_NumericSensor.LowerThresholdNonCritical for details.
559	有关详细信息，请参阅 CIM_NumericSensor.LowerThresholdCritical 描述。	See CIM_NumericSensor.LowerThresholdCritical description for details.
560	有关详细信息，请参阅 CIM_NumericSensor.LowerThresholdFatal 描述。	See CIM_NumericSensor.LowerThresholdFatal description for details.
561	用于更改此物理计算机系统的状态的外部方法。请求将元素的状态更改为 RequestedState 参数中指定的值。发生请求的状态更改时，EnabledState 和 RequestedState 将相同。如果多次调用 RequestStateChange 方法，之前的请求可能会被覆盖或丢失。 返回代码为 0 表明状态更改已成功启动。 返回代码为 1 表明不支持该方法。返回代码为 2 表明该方法失败。 返回代码为 4096 表明状态更改已成功启动，已创建 ConcreteJob 并在输出参数作业中返回其引用。	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.
562	作业已启动	Job Started
563	有关详细信息，请参阅 CIM_ComputerSystem.RequestedStateChange.RequestedState。	See CIM_ComputerSystem.RequestedStateChange.RequestedState for details.
564	延迟	Defer
565	可能包含对 ConcreteJob 的引用，创建 ConcreteJob 的目的是为了跟踪由方法调用启动的状态转换。	May contain a reference to the ConcreteJob created to track the state transition initiated by the method invocation.
566	有关详细信息，请参阅 CIM_ComputerSystem.TimeoutPeriod。	See CIM_ComputerSystem.TimeoutPeriod for details.
567	用于清除此物理计算机上的日志的外部方法。 请求清除日志中的所有条目。 如果请求成功执行，则返回值应为 0。如果不支持该请求，返回值应为 1。如果发生错误，返回值应为 2。返回代码为 4096 表明清除日志的请求已成功启动，已创建 ConcreteJob 并在输出参数作业中返回其引用。	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.
568	请求进行清除的日志的标识符。	Idenfier for the log that is requested to be cleared.
569	用于在此物理计算机系统上安装软件的外部方法。如果返回 0，表明该功能已成功完成，并且不需要 ConcreteJob 实例。如果不支持该请求，返回值应为 1。如果发生错误，返回值应为 2。如果返回 4096，将启动 ConcreteJob 以执行安装。将在输出参数作业中返回作业的引用。	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.
570	对作业的引用(如果作业已完成，则可能为 Null)。	Reference to the job (may be null if job completed).
571	有关详细信息，请参阅 CIM_SoftwareIdentity.Classifications。	See CIM_SoftwareIdentity.Classifications for details.
572	固件	Firmware
573	BIOS/FCode	BIOS/FCode
574	软件捆绑包	Software Bundle
575	管理固件	Management Firmware
576	有关详细信息，请参阅 CIM_SoftwareInstallationService.InstallFromURI.URI。	See CIM_SoftwareInstallationService.InstallFromURI.URI for details.
577	有关详细信息，请参阅 CIM_SoftwareInstallationService.InstallFromURI.InstallOptions。	See CIM_SoftwareInstallationService.InstallFromURI.InstallOptions for details.
578	延迟目标/系统重置	Defer target/system reset
579	强制实施安装	Force installation
580	安装	Install
581	更新	Update
582	修复	Repair
583	密码	Password
584	卸载	Uninstall
585	日志	Log
586	SilentMode	SilentMode
587	AdministrativeMode	AdministrativeMode
588	ScheduleInstallAt	ScheduleInstallAt
589	有关详细信息，请参阅 CIM_SoftwareInstallationService.InstallFromURI.InstallOptionsValues。	See CIM_SoftwareInstallationService.InstallFromURI.InstallOptionsValues for details.
590	此方法用于更改由属性 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.
591	一组表示启动源顺序的有序字符串。	An ordered array of strings representing the order of boot sources.
592	对衍生作业的引用(如果操作在方法返回后继续)。(如果任务已完成，则可能为 Null)。	Reference to the job spawned if the operation continues after the method returns. (May be null if the task is completed).
593	此方法用于为在此计算机系统上的下一次启动设置一次性启动源。	This method is used to set the one time boot source for the next boot on this computer system.
594	一个表示下一次启动的启动源的字符串。	A string representing the boot source for next boot.
595	此类定义物理计算机系统的视图类。	This class defines a view class for a physical computer system.
596	2.35.0	2.35.0
597	描述 RecordData 属性中信息的数据结构的字符串。如果 RecordFormat 字符串为 ，则 RecordData 应解释为自由格式字符串。 若要描述 RecordData 的数据结构，RecordFormat 字符串应以如下形式构造: - 第一个字符为分隔符，用于将字符串的其余部分分析为子字符串。 - 每个子字符串由分隔符分隔，并应采用 CIM 属性声明的格式(即，数据类型和属性名称)。这一组声明可用于解释以类似方式分隔的 RecordData 属性。 例如，如果使用 "*" 分隔符，RecordFormat = "*string ThisDay*uint32 ThisYear*datetime SomeTime" 可用于解释: 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".
598	包含 LogRecord 数据的字符串。 如果相应的 RecordFormat 属性为 ，或无法根据建议的格式进行分析，则 RecordData 应解释为自由格式字符串。如果 RecordFormat 属性包含可分析的格式信息(根据 RecordFormat Description 限定符中的建议)，RecordData 字符串应根据此格式进行分析。在这种情况下，RecordData 应以分隔符开头，并且此字符应当用于按照所述的方式分隔子字符串。然后，RecordData 字符串可以由数据使用者进行分析，并相应地进行类型化。	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.
599	区域设置表示特定的地理、政治或文化区域。区域设置指定在创建 RecordForLog 数据时使用的语言。如果 Locale 属性为空，则认为默认区域设置为 en_US (英语)。 区域设置字符串由三个用下划线分隔的子字符串组成: - 第一个子字符串是语言代码，如 ISO639 中所指定。 - 第二个子字符串是国家/地区代码，如 ISO3166 中所指定。 - 第三个子字符串是一个特定于供应商的变量。 例如，美国英语将显示为: "en_US_WIN"，其中 "WIN" 变量指定特定于 Windows 浏览器的排序规则(如果存在)。由于该变量未标准化，因此不常用，通常限制为在标准环境中使用的可轻松识别的值("WIN"、"UNIX"、"EURO" 等)。语言和国家/地区代码是必需的；变量可以为空。	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.
600	一个枚举值，该值从通知程序的视角描述“指示”的严重性: 1 - 按 CIM 惯例，“其他”用于指示可以在 OtherSeverity 属性中找到严重性值。 3 - 当适合让用户决定是否需要采取措施时，应该使用“降级/警告”。 4 - 应该使用“次要”来指示需要采取相应措施，但此时情况不严重。 5 - 应该使用“主要”来指示需要立即采取相应措施。 6 - 应该使用“严重”来指示需要立即采取相应措施，而且影响范围广泛(可能会很快导致关键资源无法提供)。 7 - 应该使用“致命/无法恢复”来指示发生了错误，但为时已晚，无法采取补救措施。 2 和 0 - 对于“信息”和“未知”，应当(分别)遵循其常见用法。确切地说，该指示是纯信息性指示或者其严重性未知。	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.
601	RecordForLog 类用于实例化要聚合到日志中的记录。	The RecordForLog class is used to instantiate records to be aggregated to a Log.
602	2.25.0	2.25.0
603	作用域 Log 的 CreationClassName。	The scoping Log\'s CreationClassName.
604	作用域 Log 的 Name。	The scoping Log\'s Name.
605	CreationClassName 表示实例创建时使用的类或子类的名称。此属性与该类的其他键属性一起使用时，可以唯一标识该类及其子类的所有实例。	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.
606	具有 MessageTimestamp 属性的 RecordID 用于唯一标识 MessageLog 中的 LogRecord。请注意，此属性与 MessageLog 方法的 RecordNumber 参数不同。后者只是顺序值，有助于在日志中执行迭代时跟踪位置。另一方面，RecordID 真正是 LogRecord 实例的标识符。可以将其设置为记录的顺序位置，但这不是必需的。	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.
607	LogRecord 的键结构包括项的时间戳。如果项的时间戳未知，则应使用值 99990101000000.000000+000。	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.
608	描述 LogRecord 的数据结构的自由格式字符串。	A free-form string describing the LogRecord\'s data structure.
609	LogRecord 对象可以描述 MessageLog 中的项的定义格式，也可以用于实例化 Log 中的实际记录。后一种方法提供的语义定义以及对 MessageLog 中各项的管理控制远远多于 Log 类的记录处理方法所提供的。建议使用 LogRecord 的子类为各 Log 项中的数据建模，以避免创建具有一个无语义属性(例如 RecordData)的 LogRecord。 可以通过为 RecordID 和 Message Timestamp 键属性建立命名约定来指定 LogRecord 的定义格式。	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.
610	2.11.0	2.11.0
611	目标 PCSV 设备的名称	Name of the target PCSV device
612	目标 PCSV 设备的 SMBios GUID	SMBios Guid of the target PCSV device
613	IPv4AddressOrigin 标识将 IPv4 地址、 子网掩码和网关分配到 NIC 时所用的方法。	IPv4AddressOrigin identifies the method by which the IPv4 Address, Subnet Mask, and Gateway were assigned to the NIC.
614	DHCP	DHCP
615	BOOTP	BOOTP
616	目标 PCSV 设备的 IPv4 地址	IPv4 Address of the target PCSV device
617	目标 PCSV 设备的 IPv4 子网掩码	IPv4 Subnet Mask of the target PCSV device
618	目标 PCSV 设备的 IPv4 默认网关	IPv4 Default Gateway of the target PCSV device
619	目标 PCSV 设备的 LAN MAC 地址	LAN MAC Address of the target PCSV device
620	SEL 可用空间(以字节为单位)	SEL Free space in Bytes
621	这是一种包装方法，用于设置为支持 PCSVDevice cmdlet 而添加的一次性启动源和持久性启动源。此方法仅在内部调用其他两个方法。此类的 API 用户应直接调用其他方法，而不是调用此方法。此方法一次只会更改一个设置，如果你为两个参数都传递了值，则此方法将失败。	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.
622	这是用于更改 BMC 网络配置的包装方法。	This is a wrapper method used to change the network configuration of the BMC.
623	IPv4AddressOrigin 标识将 IPv4 地址、子网掩码和网关分配到 NIC 时所用的方法。	IPv4AddressOrigin identifies the method by which the IPv4 Address, Subnet Mask, and Gateway were assigned to the NIC.
624	这是用于更改 BMC 用户密码的包装方法。	This is a wrapper method used to change the BMC user password.
625	CurrentCredential 是包含当前用户名和密码的冒号分隔字符串。	CurrentCredential is a delimited string containing both the current username and password, separated by a colon.
626	NewPassword 将在 BMC 中存储为 CurrentCredential 参数所指定的用户的新密码。	NewPassword will be stored on the BMC as the new password for the user specified by the CurrentCredential parameter.
627	这是用于读取 BMC SEL 日志的包装方法。	This is a wrapper method used to read BMC SEL log.
628	将 BMC SEL 条目作为 MSFT_PCSVLogRecord 实例的数组返回	Return BMC SEL entries as an array of MSFT_PCSVLogRecord instances
10001	此调用的操作选项必须包含一个具有以下名称的选项: %1。%1 操作选项必须为以下类型: %2；并且采用以下格式: 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.
10002	解析凭据时发生错误 %1!X!。%2 操作选项必须采用以下格式: username:password。	An error %1!X! occurred while parsing the credentials. The %2 operation option must be in the following format: username:password.
10003	此调用的操作选项必须包含一个具有以下名称的选项: %1。%1 操作选项必须为以下类型: %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.
10004	%1 操作选项必须为 %2 类型。	The %1 operation option must be of type %2.
10005	不支持请求的管理协议类型。支持的类型为 WSMAN (1) 和 IPMI (2)。	The requested management protocol type is not supported. Supported types are WSMAN (1) and IPMI (2).
10006	不支持请求的身份验证类型。支持的身份验证类型为:“默认”、“摘要”和“基本”。	The requested authentication type is not supported. The supported authentication types are: Default, Digest, and Basic.
10007	不支持请求的电源状态。支持的电源状态为:“已启用(2)”、“已禁用(3)”和“重置(11)”。	The requested power state is not supported. The supported power states are: Enabled(2), Disabled(3), and Reset(11).
10008	此设备不支持请求的启动源。请求的启动源必须为 StructuredBootString 数组中的值之一。	The requested boot source is not supported on this device. The requested boot source must be one of the values in the StructuredBootString array.
10009	设备已尝试使用不受支持的身份验证算法启动会话。支持的身份验证算法为 HMAC_SHA1 和 NONE。	The device attempted to start a session using an unsupported authentication algorithm. The supported Authentication algorithms are HMAC_SHA1 and NONE.
10010	设备已尝试使用不受支持的完整性算法启动会话。支持的完整性算法为 HMAC_SHA1_96 和 NONE。	The device attempted to start a session using an unsupported integrity algorithm. The supported integrity algorithms are HMAC_SHA1_96 and NONE.
10011	设备已尝试使用不受支持的保密性算法启动会话。支持的保密性算法为 AES_CBC_128 和 NONE。	The device attempted to start a session using an unsupported confidentiality algorithm. The supported confidentiality algorithms are AES_CBC_128 and NONE.
10012	该设备未实现任何受支持的基本配置文件。受支持的基本配置文件为: %1、%2 和 %3。	The device does not implement any of the supported base profiles. The supported base profiles are: %1, %2, and %3.
10013	处理请求时发生意外的 %1 错误 %2!X!。	An unexpected %1 error %2!X! occurred while processing the request.
10014	从该设备收到的响应无效。	The response received from the device was not valid.
10015	该操作未成功完成。响应包含了以下 IPMI 完成代码: %1!x!。	The operation did not complete successfully. The response contained the following IPMI Completion Code: %1!x!.
10016	无法使用给定的凭据连接到设备。请验证凭据，然后重试。	Cannot connect to device using the given credentials. Verify the credentials and try again.
10017	设备未在指定的超时期限内响应。	The device did not respond in the specified timeout period.
10018	未在该设备上实现 DMTF %1 配置文件，或未以标准方式实现该配置文件。	The DMTF %1 profile is not implemented on the device or it is not implemented in the standard way.
10019	正在使用 %1 重新启动设备	Restarting device using %1
10020	该操作失败。设备返回了以下 RMCP+ 状态码: %1!x!。	The operation failed. The device returned the following RMCP+ status code: %1!x!.
10021	正在使用 %1 启动设备	Starting device using %1
10022	正在使用 %1 停止设备	Stopping device using %1
10023	使用 %1 将一次性启动源设置为 %2	Set one time boot source to %2 using %1
10024	正在使用 %1 从设备获取信息	Getting information from device using %1
10025	由于该设备未实现 DMTF %1 配置文件，某些功能或属性将不可用。	Some capabilities or properties will not be available since the device does not implement the DMTF %1 Profile.
10026	此设备不支持该操作。该设备仅支持为永久性启动顺序设置一个启动源。	The operation is not supported for this device. The device only supports setting one boot source for Persistent Boot Order.
10027	此设备类型不支持该操作。只有 IPMI 设备支持此操作。	The operation is not supported for this device type. This operation is supported for IPMI devices only.
10028	使用 %1 设置永久性启动顺序	Set persistent boot order using %1
10029	传递的参数无效。不支持通过一个操作同时更改一次性启动源和永久性启动顺序。	The parameters passed are not valid. Changing One Time Boot Source and Persistent Boot Order in a single operation is not supported.
10030	传递的参数无效。请为某一个启动设置传递有效值。	The parameters passed are not valid. Please pass a valid value for one of the boot settings.
10031	此系统不支持该操作。此系统没有兼容 Microsoft IPMI 的设备。	The operation is not supported on this system. The system does not have a Microsoft IPMI compatible device.
10032	通过带外通道管理的设备仅支持电源状态管理操作。若要使用带外通道管理该设备，请提供设备连接信息，例如 TargetAddress、凭据和 ManagementProtocol 等。	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.
10033	此设备类型不支持该操作。只有 IPMI 设备支持该操作。	The operation is not supported for this device type. This operation is supported for IPMI devices only.
10034	该操作未成功完成。在使用 IPv4Address、IPv4SubnetMask 或 IPv4DefaultGateway 的静态值的情况下，不能将 IPv4AddressOrigin 设置为 DHCP。	The operation did not complete successfully. IPv4AddressOrigin cannot be set to DHCP with static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway.
10035	该操作未成功完成。在不使用 IPv4Address、IPv4SubnetMask 或 IPv4DefaultGateway 的静态值的情况下，不能将 IPv4AddressOrigin 设置为 STATIC。	The operation did not complete successfully. IPv4AddressOrigin cannot be set to STATIC without static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway.
10036	该操作未成功完成。%1 不是 IPMI 协议支持的 IPv4AddressOrigin 值。支持的值是: STATIC(3) 和 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)
10037	该操作未成功完成。IPv4 地址“%1”不是有效的 IPv4 地址。	The operation did not complete successfully. The IPv4 address '%1' is not a valid IPv4 address.
10038	仅支持通过带内通道进行 BMC 网络配置更改。若要更改网络配置，请在远程主机上直接执行此命令。	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.
10039	BMC 网络配置更改收到意外的参数类型。IP 地址需要字符串。	BMC network configuration change receives an unexpected parameter type. A string is expected for IP address.
10040	BMC 密码更改收到了意外的参数类型。应该为当前凭据提供一个分隔的字符串	BMC password change received an unexpected parameter type. A delimited string is expected for current credential
10041	BMC 密码更改收到了意外的参数类型。应该为新密码提供一个字符串。	BMC password change received an unexpected parameter type. A string is expected for new password.
10042	当前凭据与 BMC 中有效用户的凭据不匹配。	The current credential did not match those of a valid user on the BMC.
10044	需要提供 2 个参数(CurrentCredential 和 NewPassword)来更改 BMC 用户密码，但至少缺少了其中的一个。	2 parameters (CurrentCredential and NewPassword) are required to change BMC user password. At least one of them is missing.
10045	用户名长度不能超过 16 个字符。	Username cannot be longer than 16 characters.
10046	密码长度不能超过 20 个字符。	Password cannot be longer than 20 characters.
10048	无法读取系统事件日志，因为正在进行清除操作。	Cannot read System Event Log because erase operation is in progress.
10051	无法保留系统事件日志，因为正在进行清除操作。	Failed to reserve the System Event Log because an erase operation is in progress.
10052	无法清除系统事件日志，因为外部事件(例如，添加了新条目、重置了设备等)已取消保留。	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.).
10053	使用 %1 更改网络配置	Change network configuration using %1
10054	使用 %1 更改用户密码	Change user password using %1
10055	使用 %1 清除系统事件日志	Clear System Event Log using %1
10056	本地设备	Local Device
10057	正在使用 %1 正常关闭设备	Gracefully shutting down device using %1
10058	激活 SOL 有效负载失败。必须在同一个会话中激活 SOL 有效负载。	Activating SOL payload failed. SOL payload must be activated in the same session.
0x90000001	Microsoft-Windows-DAL-Provider	Microsoft-Windows-DAL-Provider
0xB0000001	IPMI 请求 %1 的未加密请求数据	The Unencrypted request data for IPMI request %1
0xB0000002	IPMI 请求 %1 的解密响应数据	The Decrypted response data for IPMI request %1
0xB0000003	开始枚举 PCSVDevice	Starts enumeration of PCSVDevice
0xB0000004	停止枚举 PCSVDevice	Stops enumeration of PCSVDevice
0xB0000005	开始获取 PCSVDevice 的实例	Starts getting instance of PCSVDevice
0xB0000006	停止获取 PCSVDevice 的实例	Stops getting instance of PCSVDevice
0xB0000007	启动 RequestStateChange	Start RequestStateChange
0xB0000008	停止 RequestStateChange	Stops RequestStateChange
0xB0000009	启动 SetOneTimeBootSource	Starts SetOneTimeBootSource
0xB000000A	停止 SetOneTimeBootSource	Stops SetOneTimeBootSource
0xB000000B	PCSVDevice 操作的结果	Result of PCSVDevice operation
0xB000000F	有关 IPMI 发送的数据的信息	Information on IPMI Sent Data
0xB0000010	有关 IPMI 收到的数据的信息	Information on IPMI Received Data
0xB0000011	获取操作选项	Get operations options
0xB0000012	启动 ModifyPersistentBootConfigOrder	Starts ModifyPersistentBootConfigOrder
0xB0000013	停止 ModifyPersistentBootConfigOrder	Stops ModifyPersistentBootConfigOrder
0xB0000014	启动 ChangeBootConfiguration	Starts ChangeBootConfiguration
0xB0000015	停止 ChangeBootConfiguration	Stops ChangeBootConfiguration
0xB0000016	启动 ChangeNetworkConfiguration	Starts ChangeNetworkConfiguration
0xB0000017	停止 ChangeNetworkConfiguration	Stops ChangeNetworkConfiguration
0xB0000018	启动 ChangeUserPassword	Starts ChangeUserPassword
0xB0000019	停止 ChangeUserPassword	Stops ChangeUserPassword
0xB000001A	开始获取 PCSV 设备日志	Starts getting PCSV device log
0xB000001B	停止获取 PCSV 设备日志	Stops getting PCSV device log
0xB000001C	开始清除 PCSV 设备日志	Starts clearing PCSV device log
0xB000001D	停止清除 PCSV 设备日志	Stops clearing PCSV device log
0xB000001E	带内 IPMI 请求 %1 的请求数据	The request data for in-band IPMI request %1
0xB000001F	带内 IPMI 请求 %1 的响应数据	The response data for in-band IPMI request %1

File Name:	pcsvDevice.dll.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-devicepro..-provider.resources_31bf3856ad364e35_10.0.15063.0_zh-cn_4dbf0905617cb545\
File Size:	58 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:	58368
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:	Chinese (Simplified)
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	设备的 PCSV 代理提供程序
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

pcsvDevice.dll.mui is Multilingual User Interface resource file that contain Chinese (Simplified) language for file pcsvDevice.dll (设备的 PCSV 代理提供程序).

File Description:	设备的 PCSV 代理提供程序
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:	0x804, 1200