Some comparison rule components are required. Others are
optional depending on the type of data that you want to compare and
the type of comparison rule that you create. Review the options summarized
here to determine which components to use for your business needs.
You can use the following components to create comparison rules:
- You must specify a unique comparison rule name that identifies
the rule.
- A brief description of the comparison rule is optional.
- You must specify values for the Data Set 1 and Data
Set 2 fields to specify what data sets to reconcile.
- Data Set 1 typically specifies an authorized
data set: ASSET or CI (configuration item).
- Data Set 2 typically displays the discovered
data set that corresponds to the value selected in Data
Set 1. If you select ASSET for Data Set 1,
the application displays DEPLOYED ASSET. If you select CI for Data
Set 1, it displays ACTUAL CI.
- Customers who install IBM® Tivoli® Change and Configuration
Management Database can
select the full CI comparison specification. Selecting the Full
CI Comparison check box creates a full configuration item
(CI) comparison rule that lets you compare CI relationships and their
associated specification attributes. You cannot use full CI comparison
rules in combination with data set filters, matches found, or attributes
equality components. If you select this option, the application disables
those sub tabs and they are read-only.
- Create a Data Set 1 filter to specify a
subset of Data Set 1 to reconcile against Data
Set 2. Data set filters are optional components unless
you include matches found clauses in the comparison rule. If you include
matches found clauses, you must have a filter for Data
Set 1 or Data Set 2, or both.
- Create a Data Set 2 filter to specify a
subset of Data Set 2 to reconcile against Data
Set 1. Data set filters are optional components unless
you include matches found clauses in the comparison rule. If you include
matches found clauses, you must have a filter for Data
Set 1 or Data Set 2, or both.
- You must define either a matches found comparison or attributes
equality comparison, but you cannot use both in one comparison rule.
- Create matches found comparison rule clauses to specify the ratio
of object instances in Data Set 1 to object
instances in Data Set 2 that you want to look
for in the comparison
- Create attributes equality comparison rule clauses to specify
how to compare the specific attribute or attributes of a child or
parent from Data Set 1 with specific attribute
or attributes of a child or parent in Data Set 2.
Comparison rule clause requirements
To create
data set filters, matches found comparisons, and attributes equality
comparisons, you create clauses that specify how to filter or process
data. Clauses must be valid expressions. If a clause is not valid,
an error message is displayed, and the comparison rule is not saved.
When you save a comparison rule, the following rules determine whether
clauses are valid expressions:
- Each open parenthesis must have a corresponding close parenthesis.
- The number in the Sequence field must be
unique. Sequence numbers are automatically generated in increments
of ten. You can also specify numbers manually. If you enter sequence
numbers in random order, the clauses are sorted and displayed in ascending
numeric order when you save the record.
- All rows except the row with the highest sequence number must
have a value specified in the Sequence Operator field.
- The row with the highest sequence number must not have a sequence
operator (After the clauses are sorted, this is the last row in the
table window).