class CIM_Magazine : CIM_StorageMediaLocation

Description:

StorageMediaLocations are typically slots or spaces where removable media are located. However, a specific kind of MediaLocation is a Magazine. This entity represents a single physical container with multiple StorageMediaLocations in it. All the MediaLocations within the Magazine are added/removed together. Often, this container has a Barcode or other label for identification. This is the unique data captured in the CIM_Magazine class. Magazine's label properties are defined exactly as are labels for PhysicalMedia.

Definition:

Feature Type Class Origin Qualifiers
InstanceID string CIM_ManagedElement
Description 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: <OrgID>:<LocalID> Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>. <LocalID> is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If 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 <OrgID> set to CIM.
Caption string CIM_ManagedElement
Description The Caption property is a short textual description (one- line string) of the object.
MaxLen 64
Description string CIM_ManagedElement
Override Description
Description A textual description of the PhysicalElement.
MappingStrings MIF.DMTF|FRU|003.3
ElementName string CIM_ManagedElement
Override ElementName
MappingStrings MIB.IETF|Entity-MIB.entPhysicalName
Description 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.
InstallDate datetime CIM_ManagedSystemElement
Description A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.
MappingStrings MIF.DMTF|ComponentID|001.5
Name string CIM_ManagedSystemElement
Description 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.
MaxLen 1024
OperationalStatus uint16[] CIM_ManagedSystemElement
Description 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.
ValueMap 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..
Values "Unknown" [0]
"Other" [1]
"OK" [2]
"Degraded" [3]
"Stressed" [4]
"Predictive Failure" [5]
"Error" [6]
"Non-Recoverable Error" [7]
"Starting" [8]
"Stopping" [9]
"Stopped" [10]
"In Service" [11]
"No Contact" [12]
"Lost Communication" [13]
"Aborted" [14]
"Dormant" [15]
"Supporting Entity in Error" [16]
"Completed" [17]
"Power Mode" [18]
"DMTF Reserved" [..]
"Vendor Reserved" [0x8000..]
ArrayType Indexed
ModelCorrespondence CIM_ManagedSystemElement.StatusDescriptions
StatusDescriptions string[] CIM_ManagedSystemElement
Description 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.
ArrayType Indexed
ModelCorrespondence CIM_ManagedSystemElement.OperationalStatus
Status string CIM_ManagedSystemElement
Deprecated CIM_ManagedSystemElement.OperationalStatus
Description 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.
ValueMap OK, Error, Degraded, Unknown, Pred Fail, Starting, Stopping, Service, Stressed, NonRecover, No Contact, Lost Comm, Stopped
MaxLen 10
HealthState uint16 CIM_ManagedSystemElement
Description 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.
ValueMap 0, 5, 10, 15, 20, 25, 30, ..
Values "Unknown" [0]
"OK" [5]
"Degraded/Warning" [10]
"Minor failure" [15]
"Major failure" [20]
"Critical failure" [25]
"Non-recoverable error" [30]
"DMTF Reserved" [..]
Tag string CIM_PhysicalElement
Key TRUE
Description An arbitrary string that uniquely identifies the Physical Element and serves as the key of the Element. The Tag property can contain information such as asset tag or serial number data. The key for PhysicalElement is placed very high in the object hierarchy in order to independently identify the hardware or entity, regardless of physical placement in or on Cabinets, Adapters, and so on. For example, a hotswappable or removable component can be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist and can even be inserted into a different scoping container. Therefore, the key for Physical Element is an arbitrary string and is defined independently of any placement or location-oriented hierarchy.
MaxLen 256
CreationClassName string CIM_PhysicalElement
Key TRUE
Description 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.
MaxLen 256
Manufacturer string CIM_PhysicalElement
Description The name of the organization responsible for producing the PhysicalElement. This organization might be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the Vendor property of CIM_Product.
MaxLen 256
MappingStrings MIB.IETF|Entity-MIB.entPhysicalMfgName, MIF.DMTF|FRU|003.4
Model string CIM_PhysicalElement
Description The name by which the PhysicalElement is generally known.
MaxLen 256
MappingStrings MIB.IETF|Entity-MIB.entPhysicalDescr, MIF.DMTF|FRU|003.5
SKU string CIM_PhysicalElement
Description The stock-keeping unit number for this PhysicalElement.
MaxLen 64
SerialNumber string CIM_PhysicalElement
Description A manufacturer-allocated number used to identify the Physical Element.
MaxLen 256
MappingStrings MIB.IETF|Entity-MIB.entPhysicalSerialNum, MIF.DMTF|FRU|003.7
Version string CIM_PhysicalElement
Description A string that indicates the version of the PhysicalElement.
MaxLen 64
MappingStrings MIB.IETF|Entity-MIB.entPhysicalHardwareRev, MIF.DMTF|FRU|003.8
PartNumber string CIM_PhysicalElement
Description The part number assigned by the organization that is responsible for producing or manufacturing the PhysicalElement.
MaxLen 256
MappingStrings MIB.IETF|Entity-MIB.entPhysicalModelName
OtherIdentifyingInfo string CIM_PhysicalElement
Write TRUE
Description OtherIdentifyingInfo captures data in addition to Tag information. This information could be used to identify a Physical Element. One example is bar code data associated with an Element that also has an asset tag. Note that if only bar code data is available and is unique or able to be used as an Element key, this property would be null and the bar code data would be used as the class key, in the Tag property.
MappingStrings MIB.IETF|Entity-MIB.entPhysicalAlias
PoweredOn boolean CIM_PhysicalElement
Description Boolean that indicates whether the PhysicalElement is powered on (TRUE) or is currently off (FALSE).
ManufactureDate datetime CIM_PhysicalElement
Description The date that this PhysicalElement was manufactured.
VendorEquipmentType string CIM_PhysicalElement
Description A vendor-specific hardware type for the PhysicalElement. It describes the specific equipment type for the element, as defined by the vendor or manufacturer.
MappingStrings MIB.IETF|Entity-MIB.entPhysicalVendorType
UserTracking string CIM_PhysicalElement
Write TRUE
Description User-assigned and writeable asset-tracking identifier for the PhysicalElement.
MappingStrings MIB.IETF|Entity-MIB.entPhysicalAssetID
CanBeFRUed boolean CIM_PhysicalElement
Description Boolean that indicates whether this PhysicalElement can be FRUed (TRUE) or not (FALSE).
MappingStrings MIB.IETF|Entity-MIB.entPhysicalIsFRU
RemovalConditions uint16 CIM_PhysicalPackage
Description The RemovalCapabilites property is used to describe the conditions under which a PhysicalPackage can be removed. Since all PhysicalPackages are not removable, this property defaults to 2, 'Not Applicable'.
ValueMap 0, 2, 3, 4
Values "Unknown" [0]
"Not Applicable" [2]
"Removable when off" [3]
"Removable when on or off" [4]
Removable boolean CIM_PhysicalPackage
Deprecated CIM_PhysicalPackage.RemovalConditions
Description The use of this property is being deprecated. Instead RemovalConditions should be used. The RemovalConditions property addresses whether a PhysicalPackage is removable with or without power being applied. A PhysicalPackage is Removable if it is designed to be taken in and out of the physical container in which it is normally found, without impairing the function of the overall packaging. A Package can still be Removable if power must be 'off' in order to perform the removal. If power can be 'on' and the Package removed, then the Element is both Removable and HotSwappable. For example, an extra battery in a laptop is Removable, as is a disk drive Package inserted using SCA connectors. However, the latter is also HotSwappable. A laptop's display is not Removable, nor is a non-redundant power supply. Removing these components would impact the function of the overall packaging or is impossible due to the tight integration of the Package.
Replaceable boolean CIM_PhysicalPackage
Deprecated No Value
Description The use of this property is being deprecated because it is redundant with the FRU class and its associations. A PhysicalPackage is Replaceable if it is possible to replace (FRU or upgrade) the Element with a physically different one. For example, some ComputerSystems allow the main Processor chip to be upgraded to one of a higher clock rating. In this case, the Processor is said to be Replaceable. Another example is a power supply Package mounted on sliding rails. All Removable packages are inherently Replaceable.
HotSwappable boolean CIM_PhysicalPackage
Deprecated CIM_PhysicalPackage.RemovalConditions
Description The use of this property is being deprecated. Instead RemovalConditions should be used. The RemovalConditions property addresses whether a PhysicalPackage is removable with or without power being applied. A PhysicalPackage is HotSwappable if it is possible to replace the Element with a physically different but equivalent one while the containing Package has power applied to it (ie, is 'on'). For example, a disk drive Package inserted using SCA connectors is both Removable and HotSwappable. All HotSwappable packages are inherently Removable and Replaceable.
Height real32 CIM_PhysicalPackage
Description The height of the PhysicalPackage in inches.
Units Inches
Depth real32 CIM_PhysicalPackage
Description The depth of the PhysicalPackage in inches.
Units Inches
Width real32 CIM_PhysicalPackage
Description The width of the PhysicalPackage in inches.
Units Inches
Weight real32 CIM_PhysicalPackage
Description The weight of the PhysicalPackage in pounds.
Units Pounds
PackageType uint16 CIM_PhysicalPackage
Description Enumeration defining the type of the PhysicalPackage. Note that this enumeration expands on the list in the Entity MIB (the attribute, entPhysicalClass). The numeric values are consistent with CIM's enum numbering guidelines, but are slightly different than the MIB's values. Unknown - indicates that the package type is not known. Other - The package type does not correspond to an existing enumerated value. The value is specified using the OtherPackageType property. The values "Rack" through "Port/Connector" are defined per the Entity-MIB (where the semantics of rack are equivalent to the MIB's 'stack' value). The other values (for battery, processor, memory, power source/generator and storage media package) are self-explanatory. A value of "Blade" should be used when the PhysicalPackage contains the operational hardware aspects of a ComputerSystem, without the supporting mechanicals such as power and cooling. For example, a Blade Server includes processor(s) and memory, and relies on the containing chassis to supply power and cooling. In many respects, a Blade can be considered a "Module/Card". However, it is tracked differently by inventory systems and differs in terms of service philosophy. For example, a Blade is intended to be hot-plugged into a hosting enclosure without requiring additional cabling, and does not require a cover to be removed from the enclosure for installation. Similarly, a "Blade Expansion" has characteristics of a "Blade" and a "Module/Card". However, it is distinct from both due to inventory tracking and service philosophy, and because of its hardware dependence on a Blade. A Blade Expansion must be attached to a Blade prior to inserting the resultant assembly into an enclosure.
ValueMap 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17
Values "Unknown" [0]
"Other" [1]
"Rack" [2]
"Chassis/Frame" [3]
"Cross Connect/Backplane" [4]
"Container/Frame Slot" [5]
"Power Supply" [6]
"Fan" [7]
"Sensor" [8]
"Module/Card" [9]
"Port/Connector" [10]
"Battery" [11]
"Processor" [12]
"Memory" [13]
"Power Source/Generator" [14]
"Storage Media Package (e.g., Disk or Tape Drive)" [15]
"Blade" [16]
"Blade Expansion" [17]
MappingStrings MIB.IETF|ENTITY-MIB.entPhysicalClass
ModelCorrespondence CIM_PhysicalPackage.OtherPackageType
OtherPackageType string CIM_PhysicalPackage
Description A string describing the package when the instance's PackageType property is 1 ("Other").
ModelCorrespondence CIM_PhysicalPackage.PackageType
VendorCompatibilityStrings string[] CIM_PhysicalPackage
Description An array of strings that identify the component that is compatible with, and can be inserted in a slot that reports this string as one of the array element in the VendorCompatibilityStrings This allows system administrators to determine whether it is appropriateto insert a package into a slot In order to ensure uniqueness within the NameSpace, each value defined by the vendor for use in the VendorCompatibilityStrings property SHOULD be constructed using the following 'preferred' algorithm: <OrgID>:<LocalID> Where <OrgID> and <LocalID> are separated by a colon ':', and where <OrgID> MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness <OrgID> MUST NOT contain a colon (':'). When using this algorithm, the first colon to appear in InstanceID MUST appear between <OrgID> and <LocalID>. <LocalID> is chosen by the business entity and SHOULD not be re-used to identify different underlying (real-world) elements.
ModelCorrespondence CIM_Slot.VendorCompatibilityStrings
IsCompatible method CIM_PhysicalPackage
Deprecated No Value
Description This method is being deprecated. A PhysicalPackage cannot determine if it is compatible with another object. The IsCompatible method verifies whether the referenced PhysicalElement may be contained by or inserted into the PhysicalPackage. The return value should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are 'translated' may also be specified in the subclass as a Values array qualifier.
LocationCoordinates string CIM_PackageLocation
Description LocationCoordinates represent the physical location of the the FrameSlot instance. The property is defined as a free-form string to allow the location information to be described in vendor-unique terminology.
LocationType uint16 CIM_StorageMediaLocation
Description The type of Location. For example, whether this is an individual Media "Slot" (value=2), a MediaAccessDevice (value=4) or a "Magazine" (value=3) is indicated in this property.
ValueMap 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
Values "Unknown" [0]
"Other" [1]
"Slot" [2]
"Magazine" [3]
"MediaAccessDevice" [4]
"InterLibrary Port" [5]
"Limited Access Port" [6]
"Door" [7]
"Shelf" [8]
"Vault" [9]
MediaTypesSupported uint16[] CIM_StorageMediaLocation
Description Certain StorageMediaLocations may only be able to accept a limited set of PhysicalMedia MediaTypes. This property defines an array containing the types of Media that are acceptable for placement in the Location. Additional information and description of the contained MediaTypes can be provided using the TypesDescription array. Also, size data (for example, DVD disc diameter) can be specified using the MediaSizesSupported array. Values defined here correspond to those in the CIM_Physical Media.MediaType property. This allows quick comparisons using value equivalence calculations. It is understood that there is no external physical difference between (for example) DVD- Video and DVD-RAM. But, equivalent values in both the Physical Media and StorageMediaLocation enumerations allows for one for one comparisons with no additional processing logic (i.e., the following is not required ... if "DVD-Video" then value="DVD").
ValueMap 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66
Values "Unknown" [0]
"Other" [1]
"Tape Cartridge" [2]
"QIC Cartridge" [3]
"AIT Cartridge" [4]
"DTF Cartridge" [5]
"DAT Cartridge" [6]
"8mm Tape Cartridge" [7]
"19mm Tape Cartridge" [8]
"DLT Cartridge" [9]
"Half-Inch Magnetic Tape Cartridge" [10]
"Cartridge Disk" [11]
"JAZ Disk" [12]
"ZIP Disk" [13]
"SyQuest Disk" [14]
"Winchester Removable Disk" [15]
"CD-ROM" [16]
"CD-ROM/XA" [17]
"CD-I" [18]
"CD Recordable" [19]
"WORM" [20]
"Magneto-Optical" [21]
"DVD" [22]
"DVD-RW+" [23]
"DVD-RAM" [24]
"DVD-ROM" [25]
"DVD-Video" [26]
"Divx" [27]
"Floppy/Diskette" [28]
"Hard Disk" [29]
"Memory Card" [30]
"Hard Copy" [31]
"Clik Disk" [32]
"CD-RW" [33]
"CD-DA" [34]
"CD+" [35]
"DVD Recordable" [36]
"DVD-RW" [37]
"DVD-Audio" [38]
"DVD-5" [39]
"DVD-9" [40]
"DVD-10" [41]
"DVD-18" [42]
"Magneto-Optical Rewriteable" [43]
"Magneto-Optical Write Once" [44]
"Magneto-Optical Rewriteable (LIMDOW)" [45]
"Phase Change Write Once" [46]
"Phase Change Rewriteable" [47]
"Phase Change Dual Rewriteable" [48]
"Ablative Write Once" [49]
"Near Field Recording" [50]
"MiniQic" [51]
"Travan" [52]
"8mm Metal Particle" [53]
"8mm Advanced Metal Evaporate" [54]
"NCTP" [55]
"LTO Ultrium" [56]
"LTO Accelis" [57]
"9 Track Tape" [58]
"18 Track Tape" [59]
"36 Track Tape" [60]
"Magstar 3590" [61]
"Magstar MP" [62]
"D2 Tape" [63]
"Tape - DST Small" [64]
"Tape - DST Medium" [65]
"Tape - DST Large" [66]
ArrayType Indexed
ModelCorrespondence CIM_PhysicalMedia.MediaType, CIM_StorageMediaLocation.MediaSizesSupported
MediaSizesSupported real32[] CIM_StorageMediaLocation
Description The sizes (in inches) of the particular MediaTypes that may be placed in the Location. Note, each entry of this array is related to the entry in the MediaTypesSupported array that is located at the same index.
Units Inches
ArrayType Indexed
ModelCorrespondence CIM_PhysicalMedia.MediaType, CIM_StorageMediaLocation.MediaSizesSupported, CIM_StorageMediaLocation.TypeDescriptions
MediaCapacity uint32 CIM_StorageMediaLocation
Description A StorageMediaLocation may hold more than one PhysicalMedia - for example, a Magazine. This property indicates the Physical Media capacity of the Location.
TypeDescriptions string[] CIM_StorageMediaLocation
Description This property provides additional detail related to the entries in the MediaTypesSupported array. This is especially critical when the MediaTypesSupported value is 1 ("Other"). Note, each entry of this array is related to the entry in MediaTypesSupported that is located at the same index.
ArrayType Indexed
ModelCorrespondence CIM_StorageMediaLocation.MediaTypesSupported
PhysicalLabels string[] CIM_Magazine
Description One or more strings on 'labels' on the Magazine. The format of the labels and their state (readable, unreadable, upside-down) are indicated in the corresponding LabelFormats and LabelStates array properties.
ArrayType Indexed
ModelCorrespondence CIM_Magazine.LabelStates, CIM_Magazine.LabelFormats
LabelStates uint16[] CIM_Magazine
Description An array of enumerated integers describing the states of each of the labels on a Magazine. The Labels themselves are listed in the PhysicalLabels property. Note, each entry of this array is related to the entry in PhysicalLabels that is located at the same index.
ValueMap 0, 1, 2
Values "OK/Readable" [0]
"Unreadable" [1]
"Upside Down" [2]
ArrayType Indexed
ModelCorrespondence CIM_Magazine.PhysicalLabels
LabelFormats uint16[] CIM_Magazine
Description An array of enumerated integers describing the formats of each of the labels on a Magazine. The Labels themselves are listed in the PhysicalLabels property. Note, each entry of this array is related to the entry in PhysicalLabels that is located at the same index.
ValueMap 0, 1, 2, 3, 4, 5
Values "Barcode" [0]
"Radio Frequency Identification" [1]
"OCR (Optical Character Recognition)" [2]
"MICR (Magnetic Ink Character Recognition)" [3]
"7 Character Barcode" [4]
"9 Character Barcode" [5]
ArrayType Indexed
ModelCorrespondence CIM_Magazine.PhysicalLabels

Typographical Conventions:

  1. Inherited properties are italicized.
  2. Local properties are bolded.
  3. Key properties are highlighted in gold

Generated by mof2html v.2.1.0(002). simplewbem.org Mon Nov 2 09:43:14 2009