Reference Guide

Table Of Contents
Table 53. ConcreteJob (continued)
Property Description
InstanceID
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely
identifies an instance of this class. 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 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. For DMTF-defined instances, the
preferred algorithm must be used with the <OrgID> set to CIM.
StructuredBootString
A string identifying the boot source using the format
<OrgID>:<identifier>:<index>, in which neither<OrgID>, <identifier> or <index>
contains a colon (:). The value of <OrgID>is a copyrighted, trademarked or otherwise
unique name that is owned by the entity defining the <identifier>, or is a registered ID
that is assigned to the entity by a recognized global authority. For DMTF defined
identifiers, the <OrgID> is set to CIM.
The <identifiers> are:
Floppy
Hard-Disk
CD/DVD
Network
PCMCIA
USB
The value of <index> is a non-zero integer.
DCIM_BootConfigSetting
Table 54. BootConfigSetting
Property Description
ElementName
The user-friendly name for this instance of SettingData. In addition, the user-friendly
name can be used as an index property for a search or query.
NOTE: The name does not have to be unique within a namespace.
InstanceID
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely
identifies an instance of this class. 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 the above preferred algorithm is not used, the defining entity must
190 Dell Command | Monitor 10.2.1 classes and properties