Sophie

Sophie

distrib > Fedora > 13 > x86_64 > by-pkgid > e01f19d41597cbaefda70b1cbd9cf6b0 > files > 1176

cim-schema-docs-2.22.0-2.fc12.noarch.rpm

<head><META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" type="text/css" href="mof.css" xmlns:lxslt="http://xml.apache.org/xslt">
<title>DMTF Schema Documentation Schema Documentation</title>
</head><html>
<body bgcolor="White">
<hr> 
</hr>
<a name="CIM_RelatedElementCausingError"></a>
<H1>Class CIM_RelatedElementCausingError<BR>extends <a href="CIM_Dependency.html">CIM_Dependency</a>
</H1>This association defines the relationship between a failing managed element and the managed element that is causing the error. The cause and effect might be indirect. The cause might be simply that the lack of functionality of one component causes another component to be overworked. 
The association instance must exist as long as the cause-and- effect relationship exists.<h3>
					Table of Contents<br>
<a href="#c_hierarchy">Hierarchy</a>
<br>
<a href="#c_subclasses">Direct Known Subclasses</a>
<br>
<a href="#c_qualifiers">Class Qualifiers</a>
<br>
<a href="#c_properties">Class Properties</a>
<br>
<a href="#c_methods">Class Methods</a>
<br>
</h3>
<hr> 
</hr>
<H2>
<a name="c_hierarchy">Class Hierarchy</a>
</H2>
<a href="CIM_Dependency.html">CIM_Dependency</a>
<br data="@NAME"> &nbsp;   &nbsp;|<br> &nbsp;  &nbsp;+--<b>CIM_RelatedElementCausingError</b>
<br data="CIM_RelatedElementCausingError -- CIM_Dependency">
<H2>
<a name="c_subclasses">Direct Known Subclasses</a>
</H2>
<H2>
<a name="c_qualifiers">Class Qualifiers</a>
</H2>
<TABLE BORDER="1" CELLPADDING="1" WIDTH="100%">
<TR>
<TH>Name</TH><TH>Data Type</TH><TH>Value</TH>
</TR>
<TR>
<TD VALIGN="TOP">Association</TD><TD VALIGN="TOP">boolean</TD><TD VALIGN="TOP">true</TD>
</TR>
<TR>
<TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">This association defines the relationship between a failing managed element and the managed element that is causing the error. The cause and effect might be indirect. The cause might be simply that the lack of functionality of one component causes another component to be overworked. 
The association instance must exist as long as the cause-and- effect relationship exists.</TD>
</TR>
<TR>
<TD VALIGN="TOP">Experimental</TD><TD VALIGN="TOP">boolean</TD><TD VALIGN="TOP">true</TD>
</TR>
<TR>
<TD VALIGN="TOP">UMLPackagePath</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">CIM::Core::CoreElements</TD>
</TR>
<TR>
<TD VALIGN="TOP">Version</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">2.10.0</TD>
</TR>
</TABLE>
<H2>
<a name="c_properties">Class Properties</a>
</H2>
<H3>Local Class Properties</H3>
<TABLE WIDTH="100%" CELLPADDING="1" BORDER="1">
<TR>
<TH ROWSPAN="2"><B>Name</B></TH><TH ROWSPAN="2"><B>Data Type</B></TH><TH ROWSPAN="2"><B>Default Value</B></TH><TH COLSPAN="5"><B>Qualifiers</B></TH>
</TR>
<TR>
<TH>Name</TH><TH>Data Type</TH><TH>Value</TH>
</TR>
<TR>
<TH ROWSPAN="5" VALIGN="TOP">EffectCorrelation</TH><TD ROWSPAN="5" VALIGN="TOP">uint16</TD><TD ROWSPAN="5" VALIGN="TOP">10</TD>
</TR>
<TR>
<TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">An enumeration that very generally describes the correlation of the failure of the Antecedent to its effect on the Dependent. It describes the weight of the effect reported by an instance of this class. The effect of the Antecedent element can have a strong or heavy impact on the health of the Dependent element, or the impact can be weak or light.</TD>
</TR>
<TR>
<TD VALIGN="TOP">Required</TD><TD VALIGN="TOP">boolean</TD><TD VALIGN="TOP">true</TD>
</TR>
<TR>
<TD VALIGN="TOP">ValueMap</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">2, 10, ..</TD>
</TR>
<TR>
<TD VALIGN="TOP">Values</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Strong Correlated, Weakly Correlated, DMTF Reserved</TD>
</TR>
<TR>
<TH ROWSPAN="2" VALIGN="TOP">FailureRelationshipInitiated</TH><TD ROWSPAN="2" VALIGN="TOP">datetime</TD><TD ROWSPAN="2" VALIGN="TOP"></TD>
</TR>
<TR>
<TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">The time that this failure relationship was created. The datetime should be provided because it is helpful to know when the effect was initiated.</TD>
</TR>
<TR>
<TH ROWSPAN="2" VALIGN="TOP">Ranking</TH><TD ROWSPAN="2" VALIGN="TOP">uint16</TD><TD ROWSPAN="2" VALIGN="TOP">1</TD>
</TR>
<TR>
<TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">Because more than one errant Managed Element could cause a Managed Element to fail, this ranking is used to express the most significant cause. 
The Rank attribute is used to declare the ranking of a particular cause-and-effect relationship among all cause- and-effect relationships that are defined by instances of this association for a particular element. 
1 is the highest ranking. A rank of 1 declares that this cause-and-effect relationship is the most debilitating and should be addressed with priority over all other cause-and- effect relationships. As the rank increases, the effect imposed on the Antecedent Managed Element failure decreases. There should be only one instance of this association with a particular ranking value per Dependent instance. If there is more than one instance of the same ranking per Dependent instance, then the observer cannot determine from the model which cause-and-effect relationship to resolve first. 
The ranking of existing instances can change over time based on the prevailing conditions of the device.</TD>
</TR>
</TABLE>
<H3>Association References</H3>
<TABLE BORDER="1" CELLPADDING="1" WIDTH="60%">
<TR>
<TH>Name</TH><TH>Class Origin</TH><TH>Reference Class</TH>
</TR>
<TR>
<TH VALIGN="TOP">Antecedent</TH><TD VALIGN="TOP">CIM_RelatedElementCausingError</TD><TD VALIGN="TOP"><a href="CIM_ManagedElement.html">CIM_ManagedElement</a></TD>
</TR>
<TR>
<TH VALIGN="TOP">Dependent</TH><TD VALIGN="TOP">CIM_RelatedElementCausingError</TD><TD VALIGN="TOP"><a href="CIM_ManagedElement.html">CIM_ManagedElement</a></TD>
</TR>
</TABLE>
<h2>
<a name="c_methods">Class Methods</a>
</h2>
</body>
</html>