Domain Names, Rule Testing, and Reporting

Customize the Knowledge Base › Components of Rules › Rule Construct Elements › Domain Names, Rule Testing, and Reporting

Domain Names, Rule Testing, and Reporting

Domain selection determines the data against which the rule is evaluated, the frequency with which the rule is tested and the Analysis Report section in which the conclusion is reported. See the following table. An interval record contains data for a single node in a cluster system.

Domain Name	Report Section	Testing Frequency
CLUSTER	Cluster analysis	Multiple times depending on the number of disks
COMMUNICATION	Local analysis	Multiple times per interval record depending on the number of terminal controllers
CONFIGURATION	Local analysis	Multiple times per interval record depending on the number of remote nodes within a cluster system
CPU	Local analysis	Multiple times per interval record depending on the number of processors in a multiprocessor system
DISK	Local analysis	Multiple times per interval record depending on the number of disk sub-records
FILE	Local analysis	Multiple times per interval record depending on the number of hot file sub-records
LOCAL	Local analysis	Once per interval record
LOCALC	Cluster analysis	Once per interval record
PROCESS	Local analysis	Multiple times per interval record depending on the number of process sub-records
SUMMARY	Local analysis	Once per node
TAPE	Local analysis	Multiple times per interval record depending on the number of tape sub-records

Optionally, you can display a trace each time a rule's condition is tested. During report generation, the Performance Manager displays the trace only on the terminal screen.

The following code is sample output using TRACE:

%RULETRACE of UM010 condition 1 is TRUE
%RULETRACE of UM010 condition 2 is FALSE

The Performance Manager displays this debugging information for each rule condition when the condition is evaluated and terminates with the first FALSE condition. It is possible that the Performance Manager does not output a trace for your rule. This occurs when another rule with a rule condition identical to one of your rule's conditions is evaluated to FALSE. In this case, the Performance Manager does not evaluate your rule because it is known to be false.

The relationship between domains and data cells is fixed. Rules are in domains. Data cells are in one or more domains.

Rules defined in the CLUSTER or SUMMARY domain can reference data cells only in the CLUSTER or SUMMARY domain, respectively.
Rules defined in the LOCAL domain can reference data cells in the LOCAL domain and in other domains, but only if there is an index specifier for the specific domain.
Rules defined in any of the remaining seven domains - COMMUNICATION, CONFIGURATION, CPU, DISK, FILE, PROCESS, or TAPE - can reference data cells in their own domains or the LOCAL domain. The rule can reference data cells in any other six domains only if there is an index specifier for the other domains.