The wrules_check command provides you with the ability to assess the impact on an existing set of rules whenever BAROC event classes designs are changed. Use this command to verify which rules can be impacted by these event class definition changes.

The Rules check utility is shipped with IBM Tivoli Monitoring and is installed as part of Tivoli Enterprise Console Event Synchronization.. This utility is installed in the $BINDIR/TME/TEC/OM_TEC/bin directory. It does not require any specific directory configuration if the required privileges for access to the input files and output files are granted.

To run the Rules Check command you must have:

• Read access to the *.rls and *.baroc files that will be used as inputs.
• Write access to the output that is used to store the results of the check.
• When no -cd and -rd options are specified, the user issuing the command must have the proper TME® authorization, and verify the level of wrb subcommands that are required.

where:

-h

Displays this help and exits.

-v

Displays the rules check utility version and exits.

-f class_file

Used to specify a file containing classes and class attributes to be checked. This file has the following format:

 class a[,attribute,...,attribute] [;class z[attributeZ,...,attributeZ]] 

-rd rules_directory

Used to specify a directory containing the rulesets (*.rls) to be checked. If not provided, the TEC_RULES subdirectory for the actively loaded rule base is used by default.

-cd baroc_classes_directory

Used to specify a directory containing the BAROC event class definitions files (*.baroc) to be used as input. If not provided the TEC_CLASSES subdirectory for the actively loaded rule base is used by default.

-of output_file

Used to specify the name of the output file.

Format of the output file

Parsing <rule_base_dir>/<rulefile_1.rls> 

rules impacted by class:
CLASS_1: <rule_1_within rulefile_1,rls>, ..., 
   <rule_n_within rulefile_1.rls_n>
   <attribute_name_1>:<rule_1_within rulefile_1.rls>
      ... 
   ...
CLASS_n:<rule_1_within rulefile.rls>
   <attribute_name_1>:<rule_1_within rulefile_1.rls>...
   <attribute_name_n>:<rule_1_within rulefile_1.rls>,...
   <rule_n_within rulefile_1.rls_1>
*****************************************************************
  ...  
  ... 
*****************************************************************
Parsing <rule_base_dir>/<rulefile_n.rls>
CLASS_1: <rule_1_within rulefile_n,rls>, ..., 
   <rule_n_within rulefile_n.rls_n>
   <attribute_name_1>:<rule_1_within rulefile_n.rls>
      ... 
*****************************************************************
           multiple inheritance sample output
*****************************************************************
<file_1 baroc>has the following classes with multiple inheritance:
CLASS_1  
...   
CLASS_n
*****************************************************************
...
... 
*****************************************************************
<file_n baroc>has the following classes with multiple inheritance:
 CLASS_1  
...   
*****************************************************************
        outside operator sample output  
*****************************************************************
rules impacted by outside operator: 
CLASS_1:<rule_1_within rulefile_n.rls>, ...,<rule_n_within 
   rulefile_n.rls> ... 
CLASS_n:<rule_1_within rulefile_n.rls>  

The following is an example for the wrules_check command:

   wrules_check -rd C:\temp\itmg5\TEC_RULES -cd C:\temp\itmg5\TEC_CLASSES EVENT

The results of the output file from the above command are:

Parsing C:\temp\itmg5\TEC_RULES\ 
..
..

rules impacted by class:
DB2_Down_Status:
    status:lower_itm,redo_db2_was
DB2_High_ApplicationAgent_TotSystemCpuTime:
    status:lower_itm,redo_db2_was
DB2_High_ApplicationAgents_Workload:

************************************************************

Parsing C:\temp\itmg5\TEC_RULES\

rules impacted by class:
TEC_Heartbeat_missed:
    severity:heartbeat_missed

rules impacted by outside operator:
Omegamon_Base:process_sit_events_only
Sentry2_0_Base:process_sit_events_only
TEC_Generic:process_sit_events_only

************************************************************