Reference Guide

DCIM_ServiceAffectsElement
Table 139. ServiceAffectsElement
Property Description
AffectedElement
The Managed Element that is affected by the Service.
AffectingElement
The Service that is affecting the ManagedElement.
AssignedSequence
AssignedSequence is an unsigned integer 'n' that indicates the relative sequence in
which order the ManagedElement instances are affected by the Service, which is
associated to the ManagedElement instances through this class. The implementation
of the Service uses the relative sequence to order all the managed elements
represented by ManagedElements associated through this class for servicing or
prioritizing. When n is a positive integer, it indicates a place in the sequence of
affected elements, with smaller integers indicating earlier positions in the sequence.
NULL or the special value 0 indicates don't care. If two or more affected elements
have the same non-zero sequence number, then the ordering between those
elements is irrelevant, but they must all be serviced in the appropriate order in the
overall sequence. A series of examples will make order of elements clearer: If all
elements affected have the same sequence number, regardless of whether it is 0 or
non-zero, any order is acceptable. The values, 1:ELEMENT A 2:ELEMENT B
1:ELEMENT C 3:ELEMENT D, indicate two acceptable orders: A,C,B,D or C,A,B,D,
since A and C can be ordered in either sequence, but only at the 1 position.
NOTE: The non-zero sequence numbers need not start with 1, and they need
not be consecutive. All that matters is their relative magnitude.
ElementEffects
An enumeration that describes the effect on the ManagedElement. This array
corresponds to the OtherElementEffectsDescriptions array, where the latter
provides details that are related to the high-level effects enumerated by this
property. Additional detail is required if the ElementEffects array contains the value 1
(Other).
Possible values are:
● 0 = Unknown
● 1 = Other
● 2 = Exclusive Use — Indicates that no other Service may have this association to
the element.
● 3 = Performance Impact — Deprecated in favor of Consumes, Enhances
Performance, or Degrades Performance. Execution of the Service may
enhance or degrade the performance of the element. This may be as a side-
effect of execution or as an intended consequence of methods provided by the
Service.
● 4 = Element Integrity — Deprecated in favor of Consumes, Enhances
Integrity, or Degrades Integrity. Execution of the Service may enhance or
degrade the integrity of the element. This may be as a side-effect of execution or
as an intended consequence of methods provided by the Service.
● 5 = Manages — The Service manages the element.
● 6 = Consumes — Execution of the Service consumes some or all of the
associated element as a consequence of running the Service. For example, the
Service may consume CPU cycles, which may affect performance, or Storage
which may affect both performance and integrity. (For instance, the lack of free
storage can degrade integrity by reducing the ability to save state. ) Consumes
may be used alone or in conjunction with other values, in particular, Degrades
Performance and Degrades Integrity. Manages and not Consumes should be
used to reflect allocation services that may be provided by a Service.
● 7 = Enhances Integrity — The Service may enhance integrity of the associated
element.
● 8 = Degrades Integrity — The Service may degrade integrity of the associated
element.
248
Dell Command | Monitor 10.3 classes and properties