Class CIM_TraceLevelType


  extends CIM_ManagedElement
TraceLevelType defines the encoding and semantics of trace levels. A trace is data that is produced during the execution of program code in order to provide information on the behaviour of the code (e.g. textual data written to files). Traces may be used for error detection/analysis or debugging. Trace levels define the granularity and/or type of the traces that are to be produced by the program code. Depending on the program implementation, levels may be applied on the fly. The possible levels are also implementation dependent, since no general rules or standards exist. In consequence, program developers could reuse their existing trace level scheme. Traces are valuable information sources for management applications in cases of error detection/analysis. In order to correctly set trace levels to the level needed (exciting exhaustive tracing by accident may result in significant system resources consumption in terms of processing time and storage) and to efficiently interpret which level of detail to expect from traces already produced by some resource, the possible trace level values and their meaning (semantics) must be known by the user and/or the management application. The type does not define the location or access method of the traces, since traces of a particular type can have multiple locations as well as multiple access methods.
Details...
This class is not implemented.

Class Qualifiers

NameData TypeValueScopeFlavors
DescriptionstringTraceLevelType defines the encoding and semantics of trace levels. A trace is data that is produced during the execution of program code in order to provide information on the behaviour of the code (e.g. textual data written to files). Traces may be used for error detection/analysis or debugging. Trace levels define the granularity and/or type of the traces that are to be produced by the program code. Depending on the program implementation, levels may be applied on the fly. The possible levels are also implementation dependent, since no general rules or standards exist. In consequence, program developers could reuse their existing trace level scheme. Traces are valuable information sources for management applications in cases of error detection/analysis. In order to correctly set trace levels to the level needed (exciting exhaustive tracing by accident may result in significant system resources consumption in terms of processing time and storage) and to efficiently interpret which level of detail to expect from traces already produced by some resource, the possible trace level values and their meaning (semantics) must be known by the user and/or the management application. The type does not define the location or access method of the traces, since traces of a particular type can have multiple locations as well as multiple access methods.None TRANSLATABLE= true
UMLPackagePathstringCIM::Metrics::UnitOfWorkNone None
Versionstring2.19.0TOSUBCLASS= falseTRANSLATABLE= true

Local Class Properties

NameData TypeQualifiers
NameData TypeValueScopeFlavors
BaseTypeuint16
DescriptionstringDescribes the technical encoding of the trace level. 0: bit map = switches to turn on/off appropriate trace production (e.g. 0x00000010, 0x0000F000); the use of bit maps implies that the switches can be or-ed bitwise: Values[1] | Values[2] | ... . 1: number = plain numbers that define levels (e.g. 1, 2, 7); the recommended and most common encoding scheme 2: any other encoding scheme you could think of (e.g. mixture of bit maps and numbers).None TRANSLATABLE= true
ValueMapstring1, 2, 3None None
ValuesstringOther, Bitmap, NumberNone TRANSLATABLE= true
Captionstring
DescriptionstringThe Caption property is a short textual description (one- line string) of the object.None TRANSLATABLE= true
MaxLenuint3264None None
Descriptionstring
DescriptionstringThe Description property provides a textual description of the object.None TRANSLATABLE= true
ElementNamestring
DescriptionstringA user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties.None TRANSLATABLE= true
Generationuint64
DescriptionstringGeneration is an optional, monotonically increasing property that may be used to identify a particular generation of the resource represented by this class. If Generation is supported by the implementation, its value shall not be null. Except as otherwise specified, a value (including null) of Generation specified at creation time shall be replaced by null if Generation is not supported by the implementation or shall be a, (possibly different), non-null value if the implementation does support Generation. After creation and if supported, Generation shall be updated, at least once per access, whenever the represented resource is modified, regardless of the source of the modification. Note: the Generation value only needs to be updated once between references, even if the resource is updated many times. The key point is to assure that it will be different if there have been updates, not to count each update. Note: unless otherwise specified, the value of Generation within one instance is not required to be coordinated with the value of Generation in any other instance. Note:the semantics of the instance, (as defined by its creation class), define the underlying resource. That underlying resource may be a collection or aggregation of resources. And, in that case, the semantics of the instance further define when updates to constituent resources also require updates to the Generation of the collective resource. Default behavior of composite aggregations should be to update the Generation of the composite whenever the Generation of a component is updated. Subclasses may define additional requirements for updates on some or all of related instances. For a particular instance, the value of Generation may wrap through zero, but the elapsed time between wraps shall be greater than 10's of years. This class does not require Generation to be unique across instances of other classes nor across instances of the same class that have different keys. Generation shall be different across power cycles, resets, or reboots if any of those actions results in an update. Generation may be different across power cycles, resets, or reboots if those actions do not result in an update. If the Generation property of an instance is non-null, and if any attempt to update the instance includes the Generation property, then if it doesn't match the current value, the update shall fail. The usage of this property is intended to be further specified by applicable management profiles. Typically, a client will read the value of this property and then supply that value as input to an operation that modifies the instance in some means. This may be via an explicit parameter in an extrinsic method or via an embedded value in an extrinsic method or intrinsic operation. For example: a profile may require that an intrinsic instance modification supply the Generation property and that it must match for the modification to succeed.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
InstanceIDstring
DescriptionstringWithin the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following 'preferred' algorithm: : 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 creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness 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 resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance's NameSpace. For DMTF defined instances, the 'preferred' algorithm MUST be used with the set to 'CIM'.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
MaxLenuint3216None None
ModelCorrespondencestringCIM_UnitOfWorkDefinition.TraceLevelTypeIdNone None
OverridestringInstanceIDTOSUBCLASS= falseNone
TraceValuesuint32
ArrayTypestringIndexedNone OVERRIDABLE= false
DescriptionstringEach entry in the array is one possible value of the trace level of this type. Depending on the base type, these are either switches defined as bit maps (e.g. 0x00000001, 0x000000F0, ...) or plain numbers (1, 2, 3, ...). In either encoding, the value 0 is reserved for the equivalent of 'no trace'.None TRANSLATABLE= true
RequiredbooleantrueNone OVERRIDABLE= false
ValueDescriptionsstring
ArrayTypestringIndexedNone OVERRIDABLE= false
DescriptionstringThe index corresponds to TraceLevelType.TraceValues[]. The array provides human-readable descriptions of the semantics of each value entered in the TraceValues array.None TRANSLATABLE= true
RequiredbooleantrueNone OVERRIDABLE= false

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