May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Creating a New Rulebase

Creation of the database directory structure Adding  Rulesets to Rulebase Adding classes to the rulebase Removing legacy components  

Creation of the database directory structure

A new TEC rulebase can be located in any directory. It's stupid to put it deep in the maze of Tivoli hierarchy. To create a rule base one need to use the command:

wrb -cprb -path /rb/dev/myrb myrb

You will get the following directory structure created:

drwxr-xr-x 2 root root 1024 May 17 2005 TEC_CLASSES/
drwxr-xr-x 3 root root 1536 May 17 2005 TEC_RULES/
drwxr-xr-x 3 root root 512 May 5 2005 TEC_TEMPLATES/

In TEC_RULES directory you will have the following files:

-rw-r--r--   1 root     root          25 May  3 11:38
-rw-r--r--   1 root     other          0 May  3 11:38 rule_packs
-rw-r--r--   1 root     root           0 May  3 11:38 rule_sets
-rw-r--r--   1 root     other          0 May  3 11:38 rule_sets_EventServer
-rwxr-xr-x   1 root     root         725 Aug 11  2003 tec_forward.conf*

Now you need to remove legacy components:

cd /rb/myrb

rm -fr .rbtargets


rm rule_sets_EventServer*

The created rulebase is empty: it does not contain any rulesets of BAROC files. Now you need to import default rulesets and BAROC files. 

Adding  Rulesets to Rulebase

The following rulesets are supplied by IBM and constitute a minimum that needs to be imported into any new rule base. They are stored in the default_rb directory ( $BINDIR/TME/TEC/default_rb  or  /opt/tivoli/TMF/bin/solaris2/TME/TEC/default_rb on Solaris). The directory contains quite a lot of files:

cleanup.rls               event_filtering.rls       notify.rls           event_thresholds.rls      ov_default.rls
correlation.rls           forwarding.rls            rule_sets
db_cleanup.rls            heartbeat.rls             rule_sets_EventServer
dependency.rls           solaris2        im.rls                    tec_forward.conf
ebusiness.rls             maintenance_mode.rls      tecad_nv390fwd.rls  tecad_nv390msg.rls
escalate.rls              netview.rls               tecad_snaevent.rls
event_activity.rls           troubleticket.rls

The minimum set should include only five rulesets:

  1. tec_server.rls: The rule set for processing events at the Tivoli Enterprise Console event server. These rules handle events generated by the Tivoli Enterprise Console event server
  2. dependency.rls
  3. heartbeat.rls
  4. cleanup.rls
  5. maintenance_mode.rls

To import the rulesets into the rule base you need to use the command wrb -imprbrule, for example:

wrb -imprbrule $BINDIR/TME/TEC/default_rb/TEC_RULES/tec_server.rls myrb

Note: You can import the whole generic (the Default ) rulebase   but this imports a lot of junk, don't do it.

wrb -cprb -rulesets -overwrite Default myrb


Adding classes to the rulebase

Default rulebase contains a bunch of  BAROC classes:

DB2Agents.baroc                  itmwas_dm_events.baroc
DB2CpuUtilization.baroc          netview.baroc
DB2DatabaseStatus.baroc          root.baroc
DB2HostThroughput.baroc          sem_events.baroc
DB2InstanceStatus.baroc          tec.baroc
DB2_Event.baroc                  tecad_hpov.baroc
Tmw2k.baroc                      tecad_logfile.baroc
WebSphere_MQ_Channel.baroc       tecad_nt.baroc
WebSphere_MQ_Queue.baroc         tecad_nv390msg.baroc
WebSphere_MQ_QueueManager.baroc  tecad_nv6k.baroc
as400msg.baroc                   tecad_ov.baroc
dependency.baroc                 tecad_snaevent.baroc
director.baroc                   tecad_snmp.baroc
ebusiness.baroc                  tecadnw4.baroc
hb_events.baroc                  tecados2.baroc
ibm_director.baroc               troubleticket.baroc

The minimum set of classes that you need to load is:

  1. dependency.baroc
  2. hb_events.baroc
  3. root.baroc
  4. tec.baroc

The root.baroc and tec.baroc files are imported automatically when you create a rule base.

You need to use wrb -imprbclass to do that:

 wrb -imprbclass $BINDIR/TME/TEC/default_rb/TEC_CLASSES/dependency.baroc myrb

Note: You can import the whole generic (the Default ) rulebase  this imports a lot of jredundant rulesets (junk), so this is not a recommeded way to do this unless you have no other.

wrb -cprb -rulesets -overwrite Default myrb

Copying on old rulebase

The easiest way to populate newly created rulebase is to copy old rulebase into new

wrb -cprb -overwrite ntiv ntiru

You can also copy separately rulesets and BAROC classes using options -classes of wrb -cprb command.

Removing legacy components

After creation of a rulebase you need to remove legacy components that are remnants of  AIM  -- Availability Intermediate Manager -- discontinued product that was replaced with gateway based Zurich Correlation engine (Java application that is driven by XML tables).

cd /rb/myrules

rm -fr .rbtargets


rm rule_sets_EventServer*

After you remove those the system will not recreate them. See



wrb -crtrb -path /rb/myrule myrules

To check:

wrb -lsrb -path

wrb -lscurrb   -- displays the current database

Do not modify the default rule base. It should serve as a known good rule base.

The command wrb -lscurrb reports the name of the current working rule base name. Tivoli provides a default rule base called Default.

An existing rule base, such as Default, can be copied into the new rule base as a starting point. Only one rule base is active at any given time.  The import procedure copies the BAROC file into the TEC_CLASSES subdirectory and modifies the .load_classes file. The order in which the classes are loaded must be controlled because superclasses must be defined before subclasses because of multiple inheritance.

Whenever changes are made to a rule base, the rule base must be recompiled to make the modifications available when the rule base is loaded.



Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy


War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes


Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law


Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

Copyright © 1996-2021 by Softpanorama Society. was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to to buy a cup of coffee for authors of this site


The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019