ibm ® tivoli ® management solution for excha nge: user's...

IBM® Tivoli® Management Solution for Exchange

User’s GuideVersion 1.1

GC23-4721-00

IBM® Tivoli® Management Solution for Exchange

Copyright Notice

© Copyright IBM Corporation 2002 All rights reserved. May only be used pursuant to a Tivoli Systems SoftwareLicense Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer orLicense Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrievalsystem, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic,optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporationgrants you limited permission to make hardcopy or other reproductions of any machine-readable documentation foryour own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No otherrights under copyright are granted without prior written permission of IBM Corporation. The document is notintended for production and is furnished “as is” without warranty of any kind. All warranties on this documentare hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified,Tivoli Enterprise, Tivoli Ready, and TME are trademarks or registered trademarks of International BusinessMachines Corporation or Tivoli Systems Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they willbe available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, orservices is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used.Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionallyequivalent product, program, or service can be used instead of the referenced product, program, or service. Theevaluation and verification of operation in conjunction with other products, except those expressly designated byTivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patentapplications covering subject matter in this document. The furnishing of this document does not give you anylicense to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBMCorporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

Contents

About this guide . . . . . . . . . . viiWho should read this guide . . . . . . . . . viiWhat this guide contains . . . . . . . . . . viiPublications . . . . . . . . . . . . . . viii

Related publications . . . . . . . . . . viiiAccessing publications online . . . . . . . viiiOrdering publications . . . . . . . . . . ixProviding feedback about publications . . . . ix

Accessibility . . . . . . . . . . . . . . ixContacting customer support . . . . . . . . ixConventions used in this guide . . . . . . . . xTypeface conventions . . . . . . . . . . . x

Chapter 1. Product Overview. . . . . . 1IBM Tivoli Management Solution for Exchangeproduct architecture . . . . . . . . . . . . 1

Tier one: rules . . . . . . . . . . . . . 1Tier two: data store . . . . . . . . . . . 1Tier three: Tivoli Event Monitor and TivoliReporting and Graphing . . . . . . . . . 2

IBM Tivoli Management Solution for Exchangecomponents. . . . . . . . . . . . . . . 2

Chapter 2. Installing IBM TivoliManagement Solution for Exchange . . 5Installation overview . . . . . . . . . . . 5Preparing for installation . . . . . . . . . . 6Installing Microsoft Data Access Component . . . 10Installing local full or agent IBM Tivoli ManagementSolution for Exchange . . . . . . . . . . . 12Installing remote full or agent IBM TivoliManagement Solution for Exchange . . . . . . 22Installing Tivoli Web Event Monitor . . . . . . 29Installing SendTEC . . . . . . . . . . . . 35Uninstalling IBM Tivoli Management Solution forExchange . . . . . . . . . . . . . . . 40

Chapter 3. Working with the TivoliEnterprise Manager . . . . . . . . . 41Tivoli Enterprise Manager views . . . . . . . 41Tivoli Enterprise Manager and the network. . . . 42Customizing the Tivoli Enterprise Manager behavioroptions . . . . . . . . . . . . . . . . 42Changing the Source Rule Computer . . . . . . 45Finding IBM Tivoli Management Solution forExchange in the network . . . . . . . . . . 46Refreshing the network view . . . . . . . . 46Using the Tivoli Configuration Manager . . . . . 51

Chapter 4. Managing processes . . . . 55Displaying the Manage Processes dialog box andselecting a process . . . . . . . . . . . . 55Viewing process information . . . . . . . . 57Starting and stopping processes . . . . . . . 58

Performing operations on processes . . . . . . 58Creating processes . . . . . . . . . . . . 62

Chapter 5. Managing rules . . . . . . 65Displaying the Manage Rules dialog box andselecting a rule . . . . . . . . . . . . . 65Firing a rule . . . . . . . . . . . . . . 67Enabling or disabling a rule . . . . . . . . . 68Viewing rule information . . . . . . . . . . 69Managing rules within a process . . . . . . . 69

Chapter 6. Managing solutions . . . . 73Displaying the Tivoli Solutions Manager. . . . . 73Adding and removing solutions . . . . . . . 74Setting Tivoli Solutions Manager options . . . . 76Editing solution variables. . . . . . . . . . 77

Chapter 7. Working with the Tivoli RuleDesigner . . . . . . . . . . . . . . 81Creating a new rule using the New Rule Wizard . . 82Scheduling rules . . . . . . . . . . . . . 85Managing rule selections . . . . . . . . . . 89Managing rule conditions. . . . . . . . . . 92Managing rule actions . . . . . . . . . . . 96Documenting a rule . . . . . . . . . . . 103Editing rules graphically using the Tivoli RuleDesigner . . . . . . . . . . . . . . . 104Creating rules manually using the Tivoli RuleEditor . . . . . . . . . . . . . . . . 105Editing rules manually using the Tivoli Rule Editor 107

Chapter 8. Working with the TivoliStatistics Builder . . . . . . . . . . 111Understanding statistic domains . . . . . . . 112Working with statistic domains . . . . . . . 113Importing and exporting statistic domains . . . . 115Copying statistic domains . . . . . . . . . 115Working with performance monitor statisticdomains . . . . . . . . . . . . . . . 116Working with ASCII file statistic domains . . . . 118Working with ODBC database statistic domains 121Working with SNMP statistic domains . . . . . 124Working with COM statistic domains . . . . . 125

Chapter 9. Managing events . . . . . 129Understanding events in the Tivoli Event Monitor 129Accessing and understanding the Tivoli EventMonitor window . . . . . . . . . . . . 130Filtering events in Tivoli Event Monitor . . . . 134Setting event alerts in Tivoli Event Monitor . . . 145Configuring settings and filters in the EventConfiguration Manager . . . . . . . . . . 150Sending and receiving events between computers 159Managing events with Tivoli Web Event Monitor 165

iii

Chapter 10. Reporting and graphing 173Understanding reports and graphs in the TivoliReporting and Graphing Manager . . . . . . 173Creating a report . . . . . . . . . . . . 179Exporting a report . . . . . . . . . . . . 182Creating a graph . . . . . . . . . . . . 183Customizing graphs . . . . . . . . . . . 186Exporting a graph . . . . . . . . . . . . 188Creating batch reports and graphs . . . . . . 190Managing the batch folders. . . . . . . . . 191Customizing views of reports and graphs . . . . 193

Appendix A. Command line . . . . . 195Using the command line interface . . . . . . 195

Command line parameters and syntax . . . . 195Return values . . . . . . . . . . . . 195

Commands . . . . . . . . . . . . . . 196RoboMon /Ra . . . . . . . . . . . . 197RoboMon /Rd . . . . . . . . . . . . 198RoboMon /Re . . . . . . . . . . . . 199RoboMon /Rk . . . . . . . . . . . . 200RoboMon /Rl . . . . . . . . . . . . 201RoboMon /Rp . . . . . . . . . . . . 202RoboMon /Rr . . . . . . . . . . . . 203RoboMon /Rs . . . . . . . . . . . . 204RoboMon /Rv . . . . . . . . . . . . 205RoboMon /Sk . . . . . . . . . . . . 206RoboMon /Sp . . . . . . . . . . . . 207RoboMon /Ss . . . . . . . . . . . . 208RoboMon /Vd . . . . . . . . . . . . 209RoboMon /Vp . . . . . . . . . . . . 210RoboMon /Vw . . . . . . . . . . . . 211RoboMon /Ps . . . . . . . . . . . . 212

Appendix B. Troubleshooting . . . . 213Installation . . . . . . . . . . . . . . 213

Installing IBM Tivoli Management Solution forExchange . . . . . . . . . . . . . . 213Starting Tivoli services . . . . . . . . . 213Starting Tivoli Event Service . . . . . . . 213Simple Network Management Protocol . . . . 214Open Database Connectivity . . . . . . . 214Error messages during remote installation . . . 215Setting up Microsoft Exchange . . . . . . 215

Events and databases. . . . . . . . . . . 216Tivoli Event Service - Jet database . . . . . 216Tivoli Event Service using excessive centralprocessing unit capacity . . . . . . . . . 216Large event database . . . . . . . . . . 216Routing events across the network . . . . . 216Diagnosing problems in the Tivoli Remote EventService . . . . . . . . . . . . . . 216Diagnosing problems in the Tivoli Event Service 217

Untrusting domains and workgroups . . . . . 218Untrusting domains . . . . . . . . . . 218

Management functions . . . . . . . . 218Event and performance data forwarding . . 218

One-way trust relationships . . . . . . . 218Management functions . . . . . . . . 218Event and performance data forwarding . . 219

Workgroups . . . . . . . . . . . . . 219Installing to computers in a workgroup . . 219Managing remote computers in a workgroup 219Forwarding events and performance data inworkgroups . . . . . . . . . . . . 219Managing event and performance dataforwarding between a workgroup and adomain . . . . . . . . . . . . . 219

General product notes . . . . . . . . . . 219IBM Tivoli Management Solution for Exchangedatabases. . . . . . . . . . . . . . 219

Converting IBM Tivoli Management Solutionfor Exchange databases to SQL Servers . . . 219Compacting IBM Tivoli ManagementSolution for Exchange databases . . . . . 220

IBM Tivoli Management Solution for Exchangeand TCP/IP . . . . . . . . . . . . . 220

Network adapter . . . . . . . . . . 220TCP/IP host names . . . . . . . . . 220TCP/IP port numbers . . . . . . . . 221Forcing remote procedure call connections touse TCP/IP . . . . . . . . . . . . 221

IBM Tivoli Management Solution for Exchangerules . . . . . . . . . . . . . . . 221

Execution of multiple one-shot rules. . . . 221Variable usage in asynchronous rules . . . 221

IBM Tivoli Management Solution for Exchangeservices . . . . . . . . . . . . . . 221Uninstalling IBM Tivoli Management Solutionfor Exchange . . . . . . . . . . . . 222

Miscellaneous . . . . . . . . . . . . . 222Tivoli Statistics Builder . . . . . . . . . 222

Issues with Tivoli Enterprise Manager Service 222Issues with Microsoft Internet InformationServer . . . . . . . . . . . . . . 223

Microsoft® Exchange mail action . . . . . . 223IBM Tivoli Management Solution for Exchangerate statistics . . . . . . . . . . . . 223Central processing unit statistics on Windows2000 computers. . . . . . . . . . . . 223Windows NT® errors . . . . . . . . . . 224DISK_READ_PCT and DISK_WRITE_PCTstatistic values . . . . . . . . . . . . 224EVT_DATE and EVT_TIME statistic values . . 224Error when loading a dynamic link libraryduring an upgrade installation . . . . . . 224Adding columns or tables to performancedatabases. . . . . . . . . . . . . . 224Security for IBM Tivoli Management Solutionfor Exchange files . . . . . . . . . . . 224Maximum number of IBM Tivoli ManagementSolution for Exchange rule processes . . . . 225IP address for a computer name . . . . . . 225Defining timeout values for IP_REACHABLE 225Defining community name and timeout valuefor DHCP statistics . . . . . . . . . . 225Large icon view . . . . . . . . . . . 225

Appendix C. Rules syntax . . . . . . 227Structure of the rules . . . . . . . . . . . 227

Conditions . . . . . . . . . . . . . 227

iv IBM® Tivoli® Management Solution for Exchange: User’s Guide

CONDITION statement . . . . . . . . 228Expressions . . . . . . . . . . . . 229Expression functions . . . . . . . . . 230Expression operators . . . . . . . . . 236

Actions . . . . . . . . . . . . . . 236The ACTION statement . . . . . . . . 237

Schedules . . . . . . . . . . . . . 239Selections. . . . . . . . . . . . . . 240

Rule syntax . . . . . . . . . . . . . . 240Metacharacters . . . . . . . . . . . . 240Case-sensitivity. . . . . . . . . . . . 241Quoted text . . . . . . . . . . . . . 241General file statements . . . . . . . . . 242Including statements from another file . . . . 242Macros . . . . . . . . . . . . . . 242Symbol substitution . . . . . . . . . . 244Predefined symbols . . . . . . . . . . 246Predefined variables . . . . . . . . . . 247Object definitions . . . . . . . . . . . 248

SET. . . . . . . . . . . . . . . 248VARIABLE . . . . . . . . . . . . 249TEXT_BLOCK . . . . . . . . . . . 251SCHEDULE . . . . . . . . . . . . 251SELECT . . . . . . . . . . . . . 255RULE . . . . . . . . . . . . . . 257

Actions . . . . . . . . . . . . . . 260EVENT . . . . . . . . . . . . . 261

Appendix D. Action list . . . . . . . 263APPEND . . . . . . . . . . . . . . . 264CALCULATE . . . . . . . . . . . . . 265CHECK_BOUNDS. . . . . . . . . . . . 266CLOSE . . . . . . . . . . . . . . . 267COPY . . . . . . . . . . . . . . . . 268

CREATE . . . . . . . . . . . . . . . 269DECREMENT . . . . . . . . . . . . . 270DELETE . . . . . . . . . . . . . . . 271DISABLE . . . . . . . . . . . . . . . 272ENABLE . . . . . . . . . . . . . . . 274EVENT TYPE=MESSAGE . . . . . . . . . 276EVENT TYPE=PROBLEM . . . . . . . . . 279EVENT TYPE=TEXT . . . . . . . . . . . 283EVENT TYPE=WINDOWS . . . . . . . . . 285EXECUTE . . . . . . . . . . . . . . 287EXECUTE_SQL. . . . . . . . . . . . . 289EXIT . . . . . . . . . . . . . . . . 290EXPORT . . . . . . . . . . . . . . . 291IF . . . . . . . . . . . . . . . . . 294INCREMENT . . . . . . . . . . . . . 296LOG . . . . . . . . . . . . . . . . 297MAIL . . . . . . . . . . . . . . . . 299MODIFY . . . . . . . . . . . . . . . 301PRIORITY . . . . . . . . . . . . . . 303READ . . . . . . . . . . . . . . . . 304REMOVE. . . . . . . . . . . . . . . 306SNMP_SET . . . . . . . . . . . . . . 307SNMP_TRAP . . . . . . . . . . . . . 308TERMINATE . . . . . . . . . . . . . 310WAIT . . . . . . . . . . . . . . . . 311WORKING_SET . . . . . . . . . . . . 313WRITE . . . . . . . . . . . . . . . 315ZERO . . . . . . . . . . . . . . . . 317

Glossary . . . . . . . . . . . . . 319Glossary . . . . . . . . . . . . . . . 319

Index . . . . . . . . . . . . . . . 327

Contents v

vi IBM® Tivoli® Management Solution for Exchange: User’s Guide

About this guide

The IBM® Tivoli® Management Solution for Exchange User’s Guide describes how toinstall and use the software to manage computer resources.

The objectives of this guide include the following:v Define IBM Tivoli Management Solution for Exchange and how it can improve

delivery of information technology servicesv Outline basic IBM Tivoli Management Solution for Exchange capabilities,

implementation options, directory structure, and componentsv Install and deploy IBM Tivoli Management Solution for Exchangev Customize IBM Tivoli Management Solution for Exchange by editing existing

rules and optionally defining site-specific rulesv Provide information on where to obtain help with IBM Tivoli Management

Solution for Exchange

Who should read this guideThis guide is intended for system administrators who need to implement, use, orsupport IBM Tivoli Management Solution for Exchange. It explains the conceptsyou must know to use the IBM Tivoli Management Solution for Exchange productand how IBM Tivoli Management Solution for Exchange is integrated into theTivoli environment. Readers of this guide should have prior knowledge of theWindows NT® or Windows® 2000 operating system, the Tivoli environment, andExchange administration.

What this guide containsThis guide contains the following sections:v Chapter 1, “Product Overview” on page 1

Provides an overview of IBM Tivoli Management Solution for Exchange features.v Chapter 2, “Installing IBM Tivoli Management Solution for Exchange” on page 5

Provides installation procedures for IBM Tivoli Management Solution forExchange and related software programs.

v Chapter 3, “Working with the Tivoli Enterprise Manager” on page 41Provides an explanation of the Tivoli Enterprise Manager features andstep-by-step instructions for related procedures.

v Chapter 4, “Managing processes” on page 55Provides an explanation of the processes concepts and step-by-step instructionsfor related procedures.

v Chapter 5, “Managing rules” on page 65Provides an explanation of the rules concepts and step-by-step instructions forrelated procedures.

v Chapter 6, “Managing solutions” on page 73Provides information about controlling the execution of Tivoli solutions on anetwork and step-by-step instructions for related procedures.

v Chapter 7, “Working with the Tivoli Rule Designer” on page 81

vii

Provides information about Tivoli rules, including how to create and modifyrules.

v Chapter 8, “Working with the Tivoli Statistics Builder” on page 111Provides an explanation of the processes and concepts of the Tivoli StatisticsBuilder and step-by-step instructions for related procedures.

v Chapter 9, “Managing events” on page 129Provides an explanation of managing events in IBM Tivoli Management Solutionfor Exchange by using the Tivoli Event Monitor and the Tivoli EventConfiguration Manager.

v Chapter 10, “Reporting and graphing” on page 173Provides an explanation of how to create reports and graphs using TivoliReporting and Graphing.

v Appendix A, “Command line” on page 195Provides information on how to use the command line interface for IBM TivoliManagement Solution for Exchange.

v Appendix B, “Troubleshooting” on page 213Provides information on how to troubleshoot problems that can arise duringnormal operations of IBM Tivoli Management Solution for Exchange.

v Appendix C, “Rules syntax” on page 227Provides descriptions of the features and capabilities of Tivoli rules.

v Appendix D, “Action list” on page 263Provides explanations of the actions used for IBM Tivoli Management Solutionfor Exchange.

v “Glossary” on page 319Provides a description of terminology used in IBM Tivoli Management Solutionfor Exchange.

PublicationsThis section lists publications in the IBM Tivoli Management Solution for Exchangelibrary and any other related documents. It also describes how to access Tivolipublications online, how to order Tivoli publications, and how to submit commentson Tivoli publications.

Related publicationsThe Tivoli Glossary includes definitions for many of the technical terms related toTivoli software offered by IBM. The Tivoli Glossary is available, in English only, atthe following Web site:

http://www.tivoli.com/support/documents/glossary/termsm03.htm

Accessing publications onlineWhen IBM publishes an updated version of one or more online or hardcopypublications, they are posted to the Tivoli Information Center. You can accessupdated publications in the Tivoli Information Center from the following TivoliCustomer Support Web site:

http://www.tivoli.com/support/documents/

viii IBM® Tivoli® Management Solution for Exchange: User’s Guide

The Tivoli Information Center contains the most recent version of the books in theproduct library in PDF or HTML formats, or both. Translated documents are alsoavailable for some products.

If you print PDF documents on other than letter-sized paper, select the Fit to pagecheck box in the Adobe Acrobat Print dialog. Access this dialog when you clickFile → Print to ensure that the full dimensions of a letter-sized page are printed onthe paper that you are using.

Ordering publicationsYou can order many Tivoli publications online at the following Web site:

http://www.ibm.com/shop/publications/order

You can also order by telephone by calling one of these numbers:v In the United States: 800–879–2755v In Canada: 800–426–4968

For a list of telephone numbers in other countries, see the following Web site:

http://www.tivoli.com/inside/store/lit order.html

Providing feedback about publicationsWe are very interested in hearing about your experience with Tivoli products anddocumentation, and we welcome your suggestions for improvements. If you havecomments or suggestions about our products and documentation, contact us in oneof the following ways:v Send an e-mail to [email protected]

v Complete our customer feedback survey at the following Web site:http://www.tivoli.com/support/survey/

AccessibilityAccessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

Contacting customer supportIf you have a problem with any Tivoli product, you can contact Tivoli CustomerSupport. See the Tivoli Customer Support Handbook at the following Web site:

http://www.tivoli.com/support/handbook/

The handbook provides information about how to contact Tivoli CustomerSupport, depending on the severity of your problem, and the followinginformation:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv What information you should gather before contacting support

About this guide ix

Conventions used in this guideThis guide uses several typeface conventions for special terms and actions. Theseconventions have the following meaning:

Typeface conventionsBold Lowercase and mixed-case commands, command options, and flags that

appear within text appear like this in bold type. Graphical user interfaceelements and names of keys also appear like this in bold type.

Italic Variables, values you must provide, new terms, and words and phrasesthat are emphasized appear like this in italic.

MonospaceCommands, command options, flags that appear on a separate line, codeexamples, output, and message text appear like this in Monospace.

x IBM® Tivoli® Management Solution for Exchange: User’s Guide

Chapter 1. Product Overview

The IBM Tivoli Management Solution for Exchange product complements existingExchange tools and adds features for managing large numbers of Exchange serversand databases in a distributed environment. The software uses autonomous agentsrunning on each monitored server called intelligent solution sets, or rules, to detectand correct application problems. IBM Tivoli Management Solution for Exchangecan monitor and take appropriate actions for a wide variety of operating system,network, database and application problems. For example, the software can detecta hung database server, shut it down, and restart it.

Use IBM Tivoli Management Solution for Exchange to do the following:v Monitor a running computer for application problemsv Detect and solve problems before users experience failuresv Use rules to take appropriate corrective actionv Check results of corrective action and escalate corrections and notifications until

the problem is solved

IBM Tivoli Management Solution for Exchange product architectureThis section describes the three-tiered architecture of IBM Tivoli ManagementSolution for Exchange.

Tier one: rulesThe first tier consists of the IBM Tivoli Management Solution for ExchangeIntelligent Solution Sets (ISS) or rules. An IBM Tivoli Management Solution forExchange rule operates as an autonomous agent that monitors each server. It is anamed entity that is used to monitor a specific situation and take corrective action,and perform external notification. Rules consist of the following four majorcomponents:1. The schedule that defines when the rule executes2. The selections that define the entities (disks, files, processes) that the rules

should examine3. The conditions that the rule must monitor4. The actions that the rule must take based on the condition

Use the Tivoli Rule Designer to write and test individual Tivoli rules. You caninvoke the Tivoli Rule Designer from the Tivoli Enterprise Manager to write newrules or modify existing rules.

Tier two: data storeThe second tier consists of the data store where events are generated and routedthrough the Tivoli Event Configuration Manager. In the second tier, rules forwardevents detected in tier one to an ODBC-compliant database or multiple databasesfor centralized monitoring. An event occurs when an IBM Tivoli ManagementSolution for Exchange rule detects that user-specified criteria is met. For example, acritical service that stopped running generates an event. The Tivoli EventConfiguration Manager automatically routes events between computers asinstructed so that events can be consolidated for real-time centralized monitoring

1

or for remote actions. Events are routed in real-time with guaranteed deliveryusing a store and forward technology to ensure that initially undeliverable eventsare eventually delivered.

Tier three: Tivoli Event Monitor and Tivoli Reporting andGraphing

The third tier consists of the Tivoli Enterprise Manager, Tivoli Event Monitor, andTivoli Reporting and Graphing user interfaces. Tivoli Enterprise Manager providescommand and control of rules while the Tivoli Event Monitor and Tivoli Reportingand Graphing extract and display or report data real time from the database ordatabases. The Tivoli Event Monitor enables real time notification of all eventsthroughout the Tivoli Enterprise Manager. Tivoli Reporting and Graphing usesCrystal Reports and Pinnacle BPS Graphic control to provide interactive batchreporting and graphing capabilities. You can launch multiple Tivoli Event Monitorand Tivoli Reporting and Graphing interfaces.

IBM Tivoli Management Solution for Exchange componentsAll of the following IBM Tivoli Management Solution for Exchange componentsare supplied on the product CD and are automatically installed as part of theproduct with the full installation option. For more information on installationoptions, see Chapter 2, “Installing IBM Tivoli Management Solution for Exchange”on page 5.

Tivoli Enterprise ManagerThe Tivoli Enterprise Manager is a graphical interface that you can use tomanage the IBM Tivoli Management Solution for Exchange throughout thenetwork from one central location.

Tivoli Event MonitorThe Tivoli Event Monitor is a graphical interface that you can use tomonitor events across the network in real time. You can invoke the TivoliEvent Monitor from the Tivoli Enterprise Manager by clicking on theTivoli Event Monitor icon on the toolbar, or by selecting Tivoli EventMonitor from the Run drop-down menu.

Tivoli Reporting and GraphingTivoli Reporting and Graphing generates a variety of reports and graphson performance data, events, and problems. You can invoke TivoliReporting and Graphing from the Tivoli Enterprise Manager by clickingthe Tivoli Reporting and Graphing icon on the toolbar or by selectingTivoli Reporting and Graphingfrom the Run drop-down menu.

Tivoli Solutions ManagerTivoli Solutions Manager enables you to tailor thresholds and selections ofa running process without changing the process rule code and withoutstopping and restarting the process. Examples of tailoring are changing theCPU busy percentage threshold from 85% to 90% or changing the set ofprocesses to check that they are functioning properly. You can invoke theTivoli Solutions Manager from the Tivoli Enterprise Manager by clickingthe Tailor Tivoli Solutions icon in the toolbar or by selecting TailorSolutions... from the Manage drop-down menu.

Tivoli Event Configuration ManagerThe Tivoli Event Configuration Manager is also called the Event Server.Tivoli Event Configuration Manager automatically routes events betweencomputers, so that events can be consolidated for real time centralizedmonitoring or for remote actions. You can invoke the Tivoli Event

2 IBM® Tivoli® Management Solution for Exchange: User’s Guide

Configuration Manager from the Tivoli Enterprise Manager by clicking theConfigure the Event Server icon on the toolbar or by selecting EventServer ... from the Manage drop-down menu.

Tivoli Configuration ManagerThe Tivoli Configuration Manager provides complete management andcontrol of the configuration settings on any managed computer in thenetwork. You can invoke the Tivoli Configuration Manager from the TivoliEnterprise Manager toolbar by clicking the Configure Tivoli icon or byselecting Configuration... from the Manage drop-down menu.

Tivoli Rule DesignerThe Tivoli Rule Designer is a graphical tool that enables you to write andtest individual Tivoli rules. You can invoke the Tivoli Rule Designer fromthe Tivoli Enterprise Manager toolbar by clicking the Run the Tivoli RuleDesigner icon or by selecting Tivoli Rule Designer... from the Rundrop-down menu.

Tivoli Statistics BuilderThe Tivoli Statistics Builder is a tool that enables you to define Tivolistatistics from the Windows NT Performance Monitor database, an ASCIIfile, an ODBC database, or SNMP variables. A statistic is a named valuethat you can use in Tivoli rules. You can invoke the Tivoli Statistics Builderfrom the Tivoli Enterprise Manager toolbar by clicking the Create TivoliStatistics icon or by selecting Statistics... from the Manage drop-downmenu.

IBM Tivoli Management Solution for Exchange Command LineThe IBM Tivoli Management Solution for Exchange command lineexecutable is named RoboMon.exe, and is located in the bin subdirectoryunder the main installation directory. To execute commands, you must addthis directory to your path or include the path in the command. You canadd a directory to your path from the environment tab in the controlpanel’s system applet.

Chapter 1. Product Overview 3

Chapter 2. Installing IBM Tivoli Management Solution forExchange

This chapter describes how to install IBM Tivoli Management Solution forExchange and additional software programs to enhance the functions of IBM TivoliManagement Solution for Exchange.

Note: The term IBM Tivoli Management Solution for Exchange and the term TivoliEnterprise Management Solutions are used interchangeably in the product.

Table 1 provides an overview of the topics covered in this chapter:

Table 1. Guidelines for Installing IBM Tivoli Management Solution for Exchange

Goal Refer to

1. Understanding the different IBM TivoliManagement Solution for Exchange andrelated software installations

“Installation overview” on page 5

2. Preparing system and hardwarerequirements for installation of IBM TivoliManagement Solution for Exchange

“Preparing for installation” on page 6

3. Installing Microsoft Data AccessComponent (MDAC) as a prerequisite toIBM Tivoli Management Solution forExchange installation

“Installing Microsoft Data AccessComponent” on page 10

4. Installing a full or agent version of IBMTivoli Management Solution for Exchangeon a local machine

“Installing local full or agent IBM TivoliManagement Solution for Exchange” onpage 12

5. Installing a full or agent version of IBMTivoli Management Solution for Exchangeon a remote machine

“Installing remote full or agent IBM TivoliManagement Solution for Exchange” onpage 22

6. Installing Tivoli Web Event Monitor on alocal machine

“Installing Tivoli Web Event Monitor” onpage 29

7. Installing SendTEC on a local machine “Installing SendTEC” on page 35

8. Uninstalling IBM Tivoli ManagementSolution for Exchange to remove theproduct files

“Uninstalling IBM Tivoli ManagementSolution for Exchange” on page 40

Installation overviewIBM Tivoli Management Solution for Exchange is designed to run on computersthat are part of the same domain or on computers in different domains when thesedomains have a full two-way trust relationship. Not all of the features of IBMTivoli Management Solution for Exchange work between partially trusted domains.

IBM Tivoli Management Solution for Exchange provides two types of installations:full and agent.

A full installation installs the entire product with a graphical user interface (GUI).Full installation is recommended for complete management capabilities, including

5

Rule Engine, Reporting and Graphing, and Event Monitoring. When a fullinstallation is complete, you can push installations out to other computers usingthe remote installation.

An agent installation installs the Rule Engine to provide monitoring capabilities,but does not install a GUI. Agent versions of IBM Tivoli Management Solution forExchange require no intervention by the user of the computer running the agentversion. Agent installations require less space on a computer than a fullinstallation. Computers with agent installations must be controlled from acomputer running the full installation. You can perform agent installs on newinstalls or over existing agents, but not over a full installation.

IBM Tivoli Management Solution for Exchange offers two methods of performinginstallations: local and remote.

A local installation is performed on a local computer. A local computer is acomputer that you access directly, not through a network or modem. You run asetup file from a CD-ROM that is inserted into that computer. Local installationscan install full or agent versions of IBM Tivoli Management Solution for Exchange.

A remote installation is pushed out from a computer in a trusted domain to acomputer in a trusting domain. The computer receiving the remote install must setpermissions allowing the installation. Remote installations can install full or agentversions of IBM Tivoli Management Solution for Exchange.

You can use a Web browser to manage IBM Tivoli Management Solution forExchange events by installing IBM Tivoli Management Solution for Exchange WebEvent Monitor.

You can send IBM Tivoli Management Solution for Exchange events to TivoliEnterprise Console by installing SendTEC. SendTEC translates and sends eventsfrom IBM Tivoli Management Solution for Exchange to Tivoli Enterprise Console.

IBM Tivoli Management Solution for Exchange supports Microsoft SystemsManagement Server software distributions. Microsoft Systems Management Serverprovides unattended installation.

Preparing for installationThis section describes the hardware and software requirements for IBM TivoliManagement Solution for Exchange and the preparations you must completebefore installation.

The following table lists the system, software, and hardware requirements forinstalling and deploying IBM Tivoli Management Solution for Exchange:

Table 2. System Requirements, IBM Tivoli Management Solution for Exchange

Full Install Agent Install

Operating System v Windows NT 4.0 service pack5 or higher

—OR—

v Windows 2000 on Intelhardware only

v Windows NT 4.0 service pack3 or higher

—OR—

v Windows 2000 on Intelhardware only

Processor Pentium: 200 Megahertz orfaster

Pentium: 200 Megahertz orfaster


Table 2. System Requirements, IBM Tivoli Management Solution for Exchange (continued)

Full Install Agent Install

Memory 60 MB minimum 60 MB minimum

Disk Space 61 MB of free disk space(approximately)

30 MB of free disk space(approximately)

Page File Space 50 MB free space minimum 60 MB free space minimum

To check the free page file space, press CTRL + ALT + DEL to open the task manager, go tothe Performance tab, and check Mem Usage on the status bar at the bottom of thewindow. The free page file space is the difference between the two numbers displayed.

Display Color display with a minimumresolution of 640x480

Not Applicable

Network The TCP/IP protocol must beavailable

The TCP/IP protocol must beavailable

Required Software Microsoft Data AccessComponent/Jet

Full installation requiresMicrosoft Data AccessComponent to fully operate. Forinstallation instructions, see“Installing Microsoft DataAccess Component” on page 10Note: Microsoft Data AccessComponent 2.6 does not includeAccess Drivers which must beinstalled separately.

v ODBC Driver for Access

—OR—

v Jet

You might need to installMicrosoft Jet on computersthat have an agentinstallation.

Optional: Use the planning sheet in Table 3 on page 8 to prepare informationrequired for a local installation.

Optional: Use the planning sheet in Table 4 on page 9 to prepare informationrequired for a remote installation.

Chapter 2. Installing IBM Tivoli Management Solution for Exchange 7

Tabl

e3.

Loca

lIns

talla

tion

Pla

nnin

gS

heet

Nam

eP

latf

orm

Dom

ain

Acc

oun

tP

assw

ord

Des

tin

atio

n(O

pti

onal

)S

MT

PM

ail

Ser

ver

(Op

tion

al)

Mic

roso

ftE

xch

ange

Pro

file

Nam

e

Nam

eof

the

loca

lco

mp

ute

ron

wh

ich

IBM

Tiv

oli

Man

agem

ent

Sol

uti

onfo

rE

xch

ange

soft

war

eis

tob

ein

stal

led

Op

erat

ing

syst

emof

the

loca

lco

mp

ute

r

Dom

ain

ofth

eu

ser

onth

elo

cal

com

pu

ter

Acc

oun

tn

ame

for

the

use

ron

the

loca

lco

mp

ute

r

Cor

resp

ond

ing

pas

swor

dfo

rth

eu

ser

onth

elo

cal

com

pu

ter

Pat

hon

the

loca

lco

mp

ute

rw

her

eth

eIB

MT

ivol

iM

anag

emen

tS

olu

tion

for

Exc

han

geso

ftw

are

isto

be

inst

alle

d

Nam

eof

the

SM

TP

mai

lse

rver

for

SM

TP

mai

lse

rvic

e

Mic

roso

ftE

xch

ange

Pro

file

nam

efo

rM

icro

soft

Exc

han

gem

ail

serv

ice


Tabl

e4.

Rem

ote

Inst

alla

tion

Pla

nnin

gS

heet

Nam

eP

latf

orm

Dom

ain

Acc

oun

tP

assw

ord

Des

tin

atio

n(O

pti

onal

)S

MT

PM

ail

Ser

ver

(Op

tion

al)

Mic

roso

ftE

xch

ange

Pro

file

Nam

e

Nam

eof

the

loca

lco

mp

ute

ron

wh

ich

IBM

Tiv

oli

Man

agem

ent

Sol

uti

onfo

rE

xch

ange

soft

war

eis

inst

alle

d

Op

erat

ing

syst

emof

the

rem

ote

com

pu

ter

Dom

ain

ofth

eu

ser

per

form

ing

the

rem

ote

inst

alla

tion

Acc

oun

tn

ame

for

the

use

rp

erfo

rmin

gth

ere

mot

ein

stal

lati

on

Cor

resp

ond

ing

pas

swor

dfo

rth

eu

ser

per

form

ing

the

rem

ote

inst

alla

tion

Pat

hon

the

loca

lco

mp

ute

rw

her

eth

eIB

MT

ivol

iM

anag

emen

tS

olu

tion

for

Exc

han

geso

ftw

are

isin

stal

led

Nam

eof

the

SM

TP

mai

lse

rver

for

SM

TP

mai

lse

rvic

e

Mic

roso

ftE

xch

ange

Pro

file

nam

efo

rM

icro

soft

Exc

han

gem

ail

serv

ice


Installing Microsoft Data Access Component

ObjectiveTo install Microsoft Data Access Component on a workstation so you can performa full installation of IBM Tivoli Management Solution for Exchange.

Background informationIBM Tivoli Management Solution for Exchange full installations require MicrosoftData Access Component to obtain the driver for Access. Install Microsoft DataAccess Component 2.1.2 or higher before a full install of IBM Tivoli ManagementSolution for Exchange.

IBM Tivoli Management Solution for Exchange agent installations need an Accessdriver, but do not need the entire Microsoft Data Access Component product tooperate. If you do not wish to install the entire Microsoft Data Access Componentproduct, but need an ODBC driver, you can install Microsoft Jet, the Microsoft JetOLE DB Provider.

Note: Microsoft Data Access Component version 2.6 does not include MicrosoftJet, the Microsoft Jet OLE DB Provider. To install Microsoft Jet, downloadthe program from the Microsoft web site.

Terminal Server computers that need an installation of IBM Tivoli ManagementSolution for Exchange have separate instructions for installing Microsoft DataAccess Component. Find instructions for installing Microsoft Data AccessComponent to Terminal Server computers in Microsoft Knowledge Base articleQ216149.

Before you beginCheck your computer for Microsoft Data Access Component or a Microsoft AccessDriver. For Windows NT, go to Settings → Control Panel → ODBC → Drivers forMicrosoft Access Driver. For Windows 2000, go to Settings → Control Panel →Administrative Tools → Data Sources. If your system already is installed withMicrosoft Data Access Component or a Microsoft Access Driver, you can begininstallation of IBM Tivoli Management Solution for Exchange.

When you finishProceed with installation of IBM Tivoli Management Solution for Exchange. See“Installing local full or agent IBM Tivoli Management Solution for Exchange” onpage 12 for installation instructions.

Procedure1. Close all running applications.2. Insert the product CD-ROM for IBM Tivoli Management Solution for Exchange.

Note: The term IBM Tivoli Management Solution for Exchange and the termTivoli Enterprise Management Solutions are used interchangeably in theproduct.

3. Double-click the CD-ROM drive to display the CD-ROM contents.4. Check the CD-ROM for a directory called Microsoft Data Access Component:

v No, Microsoft Data Access Component is not on the CD-ROM: DownloadMicrosoft Data Access Component from the Microsoft Web site and go toStep 5.—OR—

v Yes, Microsoft Data Access Component is on the CD-ROM: Go to Step 5.


5. Double-click the mdac.exe file to display the Microsoft Data Access 2.1 LicenseAgreement screen.

6. Click Yes in the license screen to display the Microsoft Data Access 2.1 Setupscreen.

7. Choose Continue on the Microsoft Data Access 2.1 Setup screen to display theMicrosoft Data Access 2.1 Setup screen.

8. Click on the large icon to begin installation of Microsoft Data AccessComponent. The following screen displays upon successful installation.


Installing local full or agent IBM Tivoli Management Solution forExchange

ObjectiveTo do a full or agent installation of IBM Tivoli Management Solution for Exchangeon a local computer so you can monitor running Windows NT systems to detectand correct system and application problems.

Background informationFor an understanding about local IBM Tivoli Management Solution for Exchangeinstallations, see “Installation overview” on page 5.

Before you beginYou must install Microsoft Data Access Component for a full installation of IBMTivoli Management Solution for Exchange to operate. For Microsoft Data AccessComponent installation instructions, see “Installing Microsoft Data AccessComponent” on page 10.

You must know the user domain, account, and password to complete accountinformation during installation of IBM Tivoli Management Solution for Exchange.

When you finishYou can change configuration information at any time after installation using theTivoli Configuration Manager.

No system restart is necessary following installation of IBM Tivoli ManagementSolution for Exchange.

Service Packs perform future upgrades.

Procedure1. Close all running applications.2. Insert the product CD-ROM.3. Double-click the CD-ROM drive to display the CD-ROM contents.4. Open the Tivoli Enterprise Management Solutions folder.


5. Optional: Double-click the Readme.hlp file to read additional informationabout installation.


6. Double-click the Setup.exe file to display the Welcome screen.

Additional Information: IBM Tivoli Management Solution for Exchangegenerates an installation log that logs the entire install process. You can checkinstallation progress in the C:\Program files\TEMS\TivoliInstallLog.txt file.

7. Click Next on the Welcome screen to display the Software LicenseAgreement screen.


8. Click Yes on the Software License Agreement screen to display the ChooseDestination Location screen.

9. Review the displayed location in the Destination Folder field and do one ofthe following:v Click Next to install IBM Tivoli Management Solution for Exchange to the

location displayed in the Destination Folder field and display the SetupType screen. Go to Step 10.—OR—

v Choose a different location by doing the following:a. Click Browse.b. Choose another destination.c. Click OK.d. Click Next to install IBM Tivoli Management Solution for Exchange to

the directory displayed in the Destination Folder field and display theSetup Type screen.

10. Click one of the following on the Setup Type screen:v Full to install the entire product including a GUI.


—OR—v Agent to install monitoring capabilities without a GUI.

Additional Information: A full installation installs the entire product with agraphical user interface (GUI). Full installation is recommended for completemanagement capabilities, including Rule Engine, Reporting and Graphing, andEvent Monitoring. When a full installation is complete, you can pushinstallations out to other computers using the remote installation.

An agent installation installs the Rule Engine to provide monitoringcapabilities, but does not install a GUI. Agent versions of IBM TivoliManagement Solution for Exchange require no intervention by the user of thecomputer running the agent version. Agent installations require less space ona computer than a full installation. Computers with agent installations mustbe controlled from a computer running the full installation. You can performagent installs on new installs or over existing agents, but not over a fullinstallation.

11. Click Next on the Setup Type screen to display the Select Program Folderscreen.

12. Do one of the following to name the program folder:


v Click Next on the Select Program Folder screen to keep the default foldername and display the Rules and Rule Processes screen.—OR—

v Choose a different program folder name by doing the following:a. Type the new folder name in the Program Folders text box.b. Click Next on the Select Program Folder screen to display the Rules

and Rule Processes screen.


13. Click one of the following Rules and Rule Processes options:v Install the newest Tivoli supplied rules and rule processes, replacing any

existing rules and rule processes of the same name

Choose this option if you have no existing rules, or to replace previousrules and rule processes. After installation, only the newest Tivoli suppliedrules and rule processes are present.—OR—

v Install the newest Tivoli supplied rules and rule processes, but keep acopy of any existing rules and rule processes of the same name

Choose this option to save previously set rules and rule processes and toinstall the newest rules and rule processes.—OR—

v Leave existing versions of Tivoli supplied rules and rule processes, anddo not replace them with newer versions

Choose this option to keep only the previous rules and rule processeswithout installing new rules and rule processes.


14. Click Next on the Rules and Rule Processes screen to display the StartCopying Files screen.

15. Click Next on the Start Copying Files screen to accept the current settingsand display the Tivoli Enterprise Management Solution Configurationscreen.

16. Click Next on the Tivoli Enterprise Management Solutions Configurationscreen to display the Configuration: Existing Account Information screen.

17. Enter the following account information in the text fields on theConfiguration: Existing Account Information screen:

Note: Enter the account information that IBM Tivoli Management Solution forExchange uses to access local and remote systems. The specifiedaccount must have appropriate rights.

DomainType the domain containing the user account for the installation.

AccountType the user account name. This field is case-sensitive.


PasswordType the corresponding password for the user account.

18. Click Next on the Configuration: Existing Account Information screen todisplay the Configuration: Mail Service Information screen.

19. Click one of the following options to e-mail reports from the reporting facility:v No Mail Service provides no mail notification and no Exchange mailbox

statistics. Click Next and go to Step 22.—OR—

v SMTP Mail provides mail notification, but no Exchange mailbox statistics.Click Next and go to Step 20.—OR—

v Microsoft Exchange provides both mail notification and Exchange mailboxstatistics. See Note below. Click Next and go to Step 21.

Note: You must configure the mail action for Microsoft Exchange on everycomputer where the mail action is used. This is also required for thecollection of Exchange mailbox and folder statistics. For instructionson configuring Microsoft Exchange, see “Setting up MicrosoftExchange” on page 215.

20. Optional for SMTP Mail: Do the following to configure IBM Tivoli ManagementSolution for Exchange to accept SMTP mail.a. Type the name of the mail server in the text box.b. Click Next to accept the mail server name.c. Go to Step 22.


21. Optional for Exchange Mail: Do the following to configure IBM TivoliManagement Solution for Exchange to accept Exchange mail:a. Type the Profile Name in the Profile Name text box.b. Click Next to accept the Profile Name.c. Go to Step 22.


22. Click any rules from the Configuration: AutoStart Rules screen toautomatically start every time your system restarts.

Additional Information: Installation detects applications on your system andpresents a corresponding set of rules for each application. IBM TivoliManagement Solution for Exchange rules are used to monitor hardware andsoftware components on your computer and can take actions based on theconditions found. After installation, the rules you select for automatic startbegin executing.

23. Click Next to display the Configuration Information: Complete screen.


24. Click Next to display the Setup Complete screen.

25. Click Finish to display the installed folders in your chosen directory.Installation is complete.


Installing remote full or agent IBM Tivoli Management Solution forExchange

ObjectiveTo do a full or agent installation of IBM Tivoli Management Solution for Exchangeon remote computers from a central location so you run monitoring functionsacross remote computers.

Background informationCross-domain remote installations follow the same security rules as accessing anyresource in a remote, trusting domain.

Note: You cannot perform remote installations from a trusting domain to a trusteddomain.

Before you beginVerify your network speed. If it is 10 MB or less, a local installation from theCD-ROM can be faster than a remote installation.

You can push out remote installations only from a full local installation. See“Installing local full or agent IBM Tivoli Management Solution for Exchange” onpage 12 for full local installation instructions.

When you finishYou can change configuration information at any time after the installation usingthe Tivoli Configuration Manager.

Procedure1. Establish a trusted domain relationship between the domains of the local and

remote computers.2. On the remote computer, do one of the following to grant administrator

privileges to the user of the initiating computer:v Windows NT Desktop:

a. Click Start in the Windows taskbar to display the Start menu.b. Select Programs in the Start menu to display the Programs menu.c. Select Administrative Tools (Common) in the Programs menu to

display the Administrative Tools (Common) menu.d. Click User Manager in the Administrative Tools (Common) menu to

access the User Manager window.e. Select the user you want to modify in the Username list.f. Add the user to the Administrators group as follows:

1) Double-click the user name to access the Users Properties window.2) Click the Groups button to access the Group Memberships dialog

box.3) Select Administrators in the Not member of list.4) Click Add to move Administrators to the Member of list.5) Click OK to return to the Users Properties window.6) Click OK to save your changes and return to the User Manager

window.

—OR—v Windows 2000 Desktop:


a. Click Start in the Windows taskbar to display the Start menu.b. Select Settings from the Start menu to display the Settings menu.c. Select Control Panel from the Settings menu to display the Control

Panel menu.d. Double-click Users and Passwords from the Control Panel menu to

access the Users and Passwords window.e. Click Advanced from the Users and Passwords window to display the

Advanced tab.f. Click Advanced in the Advanced User Management field to display the

Local Users and Groups screen.g. Double-click the Groups folder under Local Users and Groups (Local).h. Double-click Administrators to display the Administrators Properties

screen.i. Click Add to display the Select Users or Groups screen.j. Select the user who will run the installation for IBM Tivoli Management

Solution for Exchange from the Name list.k. Click Add.l. Click OK to return to the Administrator Properties screen.m. Click OK to save the administrator group assignments.

3. Log on to the local computer running a full installation of IBM TivoliManagement Solution for Exchange to begin the remote installation.

Note: Log on to the local computer with the account information that wasgranted privileges on the remote computers as described in Step 2.

4. Open IBM Tivoli Management Solution for Exchange by doing the following:a. Click Start to display the Start menu.b. Click Programs from the Start menu to display the Programs menu.c. Click Tivoli Enterprise Management Solutions from the Programs menu

to display the Tivoli Enterprise Management Solutions menu.d. Click Tivoli Enterprise Manager from the Tivoli Enterprise Management

Solutions menu.



5. Click Run to display the Run menu.

6. Click Tivoli Remote Installer from the Run menu to display the AccountInformation screen.

7. Type the following information in the text boxes:

Tivoli Installation Kit Directory:Do one of the following:v Type the path location of the IBM Tivoli Management Solution for

Exchange installation CD-ROM.—OR—

v Type the computer and path in UNC format(\\computer\directory) where the Tivoli Installation Kit Directoryis located.


Additional Information: You can browse for the location by clicking (...)to the right of the Tivoli Installation Kit Directory text box.

Tivoli Location for New Installations (Upgrade Installations will keep theircurrent location):

Type the path where IBM Tivoli Management Solution for Exchangewill be installed on all of the selected computers. This path is for newinstallations. Upgrade installations retain their current location.

DomainType the domain name of the local computer from which you aredoing the remote installation.

AccountType the account name that exists on the local computer and forwhich administrative privileges were assigned on the remotecomputers.

PasswordType the corresponding password for the account listed above.

8. Click Next on the Account Information screen to display the ComputerInformation screen.


9. Click the down arrow in the Default Type of installation field to display thedrop-down menu for type of installation.

10. Click one of the following installation types:v Agent

—OR—v Full

Additional Information: A full installation installs the entire product with agraphical user interface (GUI). Full installation is recommended for completemanagement capabilities, including Rule Engine, Reporting and Graphing, andEvent Monitoring. When a full installation is complete, you can pushinstallations out to other computers using the remote installation.

An agent installation installs the Rule Engine to provide monitoringcapabilities, but does not install a GUI. Agent versions of IBM TivoliManagement Solution for Exchange require no intervention by the user of thecomputer running the agent version. Agent installations require less space ona computer than a full installation. Computers with agent installations mustbe controlled from a computer running the full installation. You can performagent installs on new installs or over existing agents, but not over a fullinstallation.

11. Choose the target computer to receive the remote installation by doing one ofthe following:v Manually add a computer by doing the following:


a. Click Add Computer to display a text box labeled A New Computer.

b. Type the computer name in the text box.c. Click Add Computer.

—OR—v Browse for a computer by doing the following:

a. Click Browse to display the Add Computers screen.

b. Double-click on a displayed domain in the Available Computers field todisplay the computers for that domain.


c. Double-click the target computer in the Available Computers field tomove that computer to the Selected Computers field.

d. Click Apply.e. Click OK to add the computer.

12. Click Finish to display the Tivoli Remote Installation time commitment screen.

13. Do one of the following:


v Click Yes to begin remote installation.—OR—

v Click No to cancel the remote installation and return to the TivoliEnterprise Manager screen.

Additional Information: For multiple computer installations, the status bardisplays progress on a per computer basis. For example, one computer of fouris represented as 25%. Installations are completed one at a time.

Note: Single installs often show 0% complete until it is 100% complete. Youcan check that the install service is running on the remote system andexamine the TivoliInstallLog.txt file to verify.

14. Click OK when the installation has completed.

Installing Tivoli Web Event Monitor

ObjectiveTo install the IBM Tivoli Management Solution for Exchange Web Event Monitor soyou can manage IBM Tivoli Management Solution for Exchange events over theInternet.

Background informationNone.


Before you beginPre-installation and system requirements include:v IBM Tivoli Management Solution for Exchange, Version 1.1 or laterv Microsoft Internet Information Services 4.0 or laterv SQL Server 7 (SP2) or later (must use NT authentication)v An NT domain and user name for the designated Security administrator who

can restrict access of other usersv Internet Explorer 4.0 or later as the browser.v One of the following operating systems:

– Windows NT 4.0, Terminal Server Edition—OR—

– Windows 2000 Server/Advanced Server with Terminal Services enabled,running in Application Server mode

When you finishLocate IBM Tivoli Management Solution for Exchange Web Event Monitor at

http://[SERVER]/TivoliEventMonitor/

where [SERVER] is the fully qualified DNS name of the Microsoft InternetInformation Services server.

Access to the IBM Tivoli Management Solution for Exchange Web Event Monitorrequires an NT login accepted by the Microsoft Internet Information Servicesserver. Anonymous access is not supported.

Maximize IBM Tivoli Management Solution for Exchange Web Event Monitor byconfiguring all IBM Tivoli Management Solution for Exchange installations withinyour enterprise to forward events to the server.

Procedure1. Set Internet Explorer 4.0 Web browser settings to support Web Event Monitor

by doing the following:a. Open the Internet Explorer 4.0 Web browser.b. Click Tools to display the Tools menu.


1) Click Internet Options from the Tools menu to display the InternetOptions window.

2) Click General to display the General tab.3) Click Settings in the Temporary Internet Files field to display the

Settings screen.

4) Click Every visit to the page.Additional Information: Changing this setting ensures that Tivoli EventMonitor accepts new choices since it does not use cached pages.

5) Click OK.


c. Click Security in the Internet Options window to display the Security tab.

d. Click Local Intranet Zone for the Zone selection.e. Configure the browser by doing the following:

1) Click Custom Level to display the Security Settings screen.

2) Set the following configurations in the Security Settings screen:

Download signed ActiveX controlsClick Prompt.

Download unsigned ActiveX controlsClick Prompt.


Initialize and script ActiveX controls not marked as safeClick Prompt.

Run ActiveX controls and pluginsClick Enable.

Script Active X controls marked safe for scriptingClick Enable.

Submit non-encrypted form dataClick Prompt.

Active scriptingClick Enable.

Allow cookies that are stored on your computerClick Enable.

Additional Information: You must enable the browser to accept cookiesfor the Tivoli Web Event Monitor to work properly.

3) Click OK.f. Click Internet Zone for the Zone selection.g. Repeat Steps 1e1 through 1e3 as necessary.

2. Run the SQL Server service.Additional Information: For SQL Server 2000 installations, make sure the servicefor the instance you wish to install the central collection database on isrunning.

3. Close all running programs.4. Locate the setup.exe file by doing one of the following:

v Browse to the directory to which the IBM Tivoli Management Solution forExchange setup kit was downloaded and extracted.—OR—

v Browse to the directory on the IBM Tivoli Management Solution forExchange installation CD-ROM.

5. Double-click the setup.exe file to display the Welcome Screen.

6. Click Next on the Welcome Screen to display the Software LicenseAgreement screen.


7. Click Yes on the Software License Agreement screen to display the AccountInformation screen.

8. Complete the following information:

Domain:Type the domain containing the user account.

Username:Type the NT login username for the security administrator of theTivoli Web Event Monitor.

Additional Information: This user is responsible for:v adding new IBM Tivoli Management Solution for Exchange Event

Monitor usersv adding additional security administratorsv modifying security settings for existing users

The default selection for this account is the user performing theinstallation.

9. Click Next on the Account Information screen. A Creating SQL Databasescreen displays followed by a Start Copying Files screen.

Note: Setup can take five minutes or more. Do not interrupt the setupprocess.


10. Click Next on the Start Copying Files screen to copy files and display theSetup Complete screen.

11. Click Finish on the Setup Complete Screen to complete the installation.

Installing SendTEC

ObjectiveTo install SendTEC so you can forward events to the Tivoli Enterprise Console.

Background informationSendTEC sends events to the Tivoli Enterprise Console. The Tivoli EnterpriseConsole combines events from IBM Tivoli Management Solution for Exchange withevents from other sources making it the main point for event handling in theenterprise.

By using SendTEC with Tivoli Enterprise Management Solutions you can define acomplete event handling and management strategy that is set up and managedfrom a central location.


SendTEC runs in the background and requires no user interface.

Before you beginThe following software must be installed for SendTEC to work properly:v IBM Tivoli Management Solution for Exchangev Tivoli Event Integration Facility (EIF), an event adapter

SendTEC should be installed on the same computer that is consolidating all of theIBM Tivoli Management Solution for Exchange events.

When you finishNone.

Procedure1. Locate the SendTEC directory on the IBM Tivoli Management Solution for

Exchange product CD-ROM.2. Double-click the setup.exe file to display the Welcome screen.

3. Click Next on the Welcome screen to display the Choose Destination Locationscreen.


4. Review the displayed location in the Destination Folder field and do one ofthe following:v Click Next to install SendTEC to the location displayed in the Destination

Folder field and display the Select Program Folder screen.—OR—

v Choose a different location by doing the following:a. Click Browse.b. Choose another destination.c. Click OK.d. Click Next to install SendTEC to the directory displayed in the

Destination Folder field and display the Select Program Folder screen.

5. Do one of the following to name the program folder:v Click Next on the Select Program Folder screen to keep the default folder

name and display the Check Setup Information screen.—OR—

v Choose a different program folder name by doing the following:a. Type the new folder name in the Program Folders text box.b. Click Next on the Select Program Folder screen to display the Check

Setup Information screen.


6. Click Next on the Check Setup Information screen to display the SetupComplete screen.

7. Click Finish to complete the installation of the SendTEC product.Additional Information: Installing SendTEC does not create an ini file. Anexample version called demoSendTEC.ini is created in an examples directory.This file must be transferred to a configuration directory and edited beforestarting SendTEC. Perform the steps below to complete this procedure.

8. Edit the SendTEC configuration files by doing the following (for detailedconfiguration notes, see C:\Program Files\SendTEC\documentation):a. Locate the C:\ProgramFiles\SendTec\examples\config\demosendtec.ini file.b. Rename the demosendtec.ini file to sendtec.ini.c. Copy the sendtec.ini file into the C:\ProgramFiles\SendTec\config

directory.d. Open the sendtec.ini file in the C:\ProgramFiles\SendTec\config directory.e. Set the following parameters:

HOST_NAMEEnter the name or IP address of the host (running TEC server), to


which events are sent. SendTEC can send to only one receivinghost. See the documentation to set up multiple process instances.

SOCKETEnter the TEC port number. Tivoli TEC server listens for events.

PRODUCT_ID and PRODUCT_VERSIONIf SOCKET is set to 0, SendTEC finds the socket to use bycontacting the portmapper on the host defined in HOST_NAME.SendTEC finds the port number that serves the product specified byPRODUCT_ID and PRODUCT_VERSION. Check Tivoli documentation forthe correct product ID and version numbers.

EVENT_FILE_INEnter the file where SendTEC receives the events it processes.

MAX_FILE_AGE_INEnter the maximum age of any event file to be processed.

EVENT_FILE_OUTEnter the file to which SendTEC writes any normal or error events.

DEBUG_LEVELEnter the level of debug information to include in the outputinformation. Higher values provide more detail about the internalbehavior of the process. Level 0 provides no debug messages. Level3 provides initialization data, and record count and actionprocessing information.

DEBUG_FILEEnter the name of a file to which debug information is written.

ERROR_FILEEnter the name of a file to which errors are written.

f. Save the sendtec.ini file.9. Run the CreateServices.bat batch file in the bin subdirectory.10. Add the values below to the following registry key using REGEDIT to enable

IBM Tivoli Management Solution for Exchange to create ASCII .evt files tosend to the Tivoli Enterprise Console:In the HKEY_LOCAL_computer\SOFTWARE\TEMS\EventServer registry keyv Value Name: EventFileEnable

v Data Type: REG_DWORD

v Value: 1

11. Copy the included Baroc file to the Tivoli Enterprise Console Server.12. Start the SendTEC service by doing one of the following on a Windows 2000

or NT operating system:v Windows 2000:

a. Open the Control Panel.b. Open Administrative Tools.c. Open Services.d. Click SendTEC to select the SendTEC service.e. Click Action to display the Action menu.f. Click Start from the Action menu.

v Windows NT:

a. Open the Control Panel.


b. Open Services.c. Click SendTEC to select the SendTEC service.d. Click Start.

Uninstalling IBM Tivoli Management Solution for Exchange

ObjectiveTo uninstall IBM Tivoli Management Solution for Exchange so you can remove allof the program files from a computer.

Background informationUninstall removes all files in the IBM Tivoli Management Solution for Exchangedirectories.

Note: The term IBM Tivoli Management Solution for Exchange and the term TivoliEnterprise Management Solutions are used interchangeably in the product.

Before you beginNone.


Procedure1. Open the Control Panel by doing the following:

a. Click Start in the Windows taskbar to display the Start menu.b. Select Settings from the Start menu to display the Settings menu.c. Select Control Panel from the Settings menu to display the Control Panel

menu.2. Click the Add/Remove Programs icon.3. Select IBM Tivoli Management Solution for Exchange.4. Click Add/Remove.5. Click Yes to confirm uninstallation.


Chapter 3. Working with the Tivoli Enterprise Manager

The Tivoli Enterprise Manager is the central location where you manage andcontrol the operations of IBM Tivoli Management Solution for Exchange. You cancontrol the Tivoli Rule Engine through the Tivoli Enterprise Manager. The TivoliRule Engine executes a rule process, which is a set of one or more rules. Each rulemonitors a specific situation throughout the network. It notifies and takescorrective actions, if the situation occurs. For example, a rule can detect if adatabase server is hung, and if so, the rule can stop it and restart it. IBM TivoliManagement Solution for Exchange can monitor and take appropriate actions for awide variety of operating system, network, database, and application problems. Acomputer can execute one or more Tivoli Rule Engine processes. To learn moreabout rules and rule processes, see Chapter 5, “Managing rules” on page 65 andChapter 6, “Managing solutions” on page 73.

This chapter provides an explanation of the Tivoli Enterprise Manager features andstep-by-step instructions for related procedures. Table 5 provides an overview ofthe topics covered in this chapter.

Table 5. Guidelines for working with the Tivoli Enterprise Manager

Goal Refer to

1. Understanding Tivoli EnterpriseManager views

“Tivoli Enterprise Manager views” on page41

2. Understanding how Tivoli EnterpriseManager represents your network

“Tivoli Enterprise Manager and thenetwork” on page 42

3. Understanding and customizing theTivoli Enterprise Manager behavioroptions

“Customizing the Tivoli Enterprise Managerbehavior options” on page 42

4. Understanding and managing thesource rule display

“Changing the Source Rule Computer” onpage 45

5. Finding IBM Tivoli ManagementSolution for Exchange in the network

“Finding IBM Tivoli Management Solutionfor Exchange in the network” on page 46

6. Refreshing the network view “Refreshing the network view” on page 46

7. Managing domains “Managing domains” on page 47

8. Managing computers “Managing computers” on page 49

9. Working with the Tivoli ConfigurationManager

“Using the Tivoli Configuration Manager”on page 51

Tivoli Enterprise Manager viewsThe Tivoli Enterprise Manager runs in two modes: the Management View and theDevelopment View. The default mode is the Management View. TheManagement View displays and manages rule processes deployed throughout thenetwork. The Management View has two panes. The left pane displays icons thatrepresent containers, which are the network, domains, or computers, and the rightpane displays the contents of those containers.

The Development View also has a left and a right window pane, but panes areindependent of each other. The Development View enables you to write and

41

modify individual rules before deployment. Development View provides a view ofall existing rule processes. The left pane is the network display of domains,computers, rule processes, and the rules within the rule processes that the TivoliEnterprise Manager manages. The right pane displays rules. It contains theavailable source rules used to build new Tivoli rule processes or update existingTivoli rule processes. You can toggle between the two views from the TivoliEnterprise Manager View drop-down menu.

Tivoli Enterprise Manager and the networkThe Tivoli Enterprise Manager represents the network using a hierarchy thatincludes a domain and computer where the domain represents a group ofcomputers that share common account administration and security and theindividual computer is a member of a domain. When constructing a Tivoli ruleprocess, the source rules comes from a computer on the network. Additionally, theTivoli Enterprise Manager processes create and manage the rule process on anycomputer in the network.

The Tivoli Enterprise Manager fully complies with the Windows NT® securitysystem. Consequently, the computers that can be managed by the Tivoli EnterpriseManager are constrained by the underlying security in place on the network.

Customizing the Tivoli Enterprise Manager behavior options

ObjectiveTo set the IBM Tivoli Management Solution for ExchangeBrowse, Cache,Confirmation, and Process Start options to your specifications.

Background informationYou can customize the following options:

Browse optionsCustomizes the browsing behavior of the Tivoli Enterprise Manager.Browsing refers to the periodic consulting of the network for a list of


domains and computers in each domain. Browsing can also involvechecking the state of IBM Tivoli Management Solution for Exchange oneach computer in each domain.

Cache optionsMaintains and clears cache of the computers that it previously examined,speeding up network-wide operations. The first time you run the TivoliEnterprise Manager, caching is disabled by default.

Confirmation optionsSpecifies whether or not the Tivoli Enterprise Manager asks you forconfirmations before performing specific types of operations.

Process start optionsDetermines whether Tivoli Rule Processes start automatically when theyare first created.

Before you beginBrowse Options: The amount of time it takes to browse the network depends onthe size of your network (how many domains and how many computers in eachdomain) and how many computers in the network are running IBM TivoliManagement Solution for Exchange. Read the following browse option descriptionsto help you decide which browse option is appropriate for your system:

Confirmation Options: You can change whether or not the Tivoli EnterpriseManager asks you for confirmations after performing specific operations. Tocontrol confirmation behavior, click the View menu in the main Tivoli EnterpriseManager window and select the Options menu item. When the Options windowis displayed, select the Confirmation tab.

You can turn confirmations on or off independently for each of the followingoperations:


ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.1. Click View from the toolbar to display the View drop-down menu.2. Select Options... to display the Options... dialog box.3. Set the Browse settings

a. Click the Browse tab to display the Browse settings.b. Select one of the following options by clicking the corresponding radio

button:

Do not browse (add domains and computers manually)Does not to find the domains in a network or find the computers ina given domain. Enter domains and computers manually that youwant Tivoli Enterprise Manager to manage. This option is suitablefor large networks with few computers running IBM TivoliManagement Solution for Exchange. This setting is the defaultbrowse setting.

Browse, but do not check for Tivoli running (faster)Looks up domains in the network as well as computers in a givendomain. The Tivoli Enterprise Manager does not check to see if IBMTivoli Management Solution for Exchange is running on eachcomputer. This option is suitable for domains that have a small to

Chapter 3. Working with the Tivoli Enterprise Manager 43

moderate number of computers, where very few of the computersare running IBM Tivoli Management Solution for Exchange.

Perform a full browse, including checking for Tivoli runningLooks up domains the computers in a specified domain and checkeach computer for IBM Tivoli Management Solution for Exchange.A full browse is more convenient for the user but requires thehighest level of browse effort. This option is suitable for smalldomains or domains with the vast majority of the computersrunning IBM Tivoli Management Solution for Exchange.

c. Do one of the following to manage the cache:v Click the Clear cache installed state of Tivoli for up to one week check

box to enable the caching mechanism.—OR—

v Clear the check box to disable the caching mechanism.Additional Information: Tivoli Enterprise Manager automatically declaresentries in the cache stale after seven days. At any time you can empty thecache by clicking the Clear Cache Now button. When you clear the cache,Tivoli Enterprise Manager checks each remote computer for IBM TivoliManagement Solution for Exchange. Clearing the cache might beappropriate if you have just installed IBM Tivoli Management Solutionfor Exchange on several computers.

4. Set the Confirmation settings.a. Click the Confirmation tab to display the Confirmation settings.b. Select any combination of the following options.

Confirming Drag OperationsAsks for confirmation of drag and drop operations. If the Confirmall Drag Operations box is not checked, all drag and dropoperations are performed without confirmation.

Confirming Replacement OperationsAsks for confirmation before replacing the existing process or rule.If the Confirm all Replacement Operations box is not checked,operations that result in the replacement of existing processes orrules complete without confirmation.

Displaying Browse WarningsAsks for confirmation the browse operation. If the Confirm browseoperations box is not checked, operations that result in a browse ofthe domain complete without confirmation.

Displaying Success MessagesDisplays a message indicating an operation completes successfully.If the Display success messages box is not checked, you do notreceive a message indicating the operation was successful. The lackof a message indicates success. Operations that generate errors arealways generate a message.

5. Set the Process Start settingsa. Click the Process Start tab to display the Process Start option.b. Do one of the following:

v Select the Automatically start newly created processes check box.—OR—

v Deselect the Automatically start newly created processes check box.6. Do one of the following to apply your changes:


v Click OK.—OR—

v Click Apply.

Changing the Source Rule Computer

ObjectiveTo change the source rule computer so you can manage rules on differentcomputers. See Chapter 5, “Managing rules” on page 65 for more information onrules.

Background informationA source rule is a rule written by the Tivoli Rule Designer that is included whenconstructing Tivoli processes. The source rule display is on the right of the TivoliEnterprise Manager main window in the Development View. The source ruledisplay includes icons representing the rules. The text box above the source ruledisplay indicates the Source Rule domain, computer, and directory currentlyproviding the source rules used to build and augment Tivoli rule processes.

Different directories can provide different rules. For example, one directory mightprovide rules for an NT Server. Another might provide rules for Exchange or foran SQL Server. The set of directories that are available for source rule storage on aspecific computer is the set of subdirectories under the C:\ProgramFiles\TEMS\Rules directory, assuming IBM Tivoli Management Solution forExchange is installed in the default location of the C:\Program Files\TEMSdirectory. The format of the directory display in the text box is\\domain\computer\directory. This display includes a drop-down list that you canuse to change the source rule computer and directory.



ProcedureDo one of the following to change the source rule computer.v From the Source Rule Computer: text box in the right window pane of the

Tivoli Enterprise Manager1. Click the right arrow next to the Source Rule Computer: text box to display

the Source Rule Computer: drop-down list.2. Select a new source rule computer/directory from the list.

—OR——OR—v From the Change Source Rule Computer dialog box:

1. Display the Change Source Rule Computer dialog box:– Click the Change Source Rule Computer icon on the toolbar.

—OR—– Select Manage from the toolbar to display the Manage drop-down menu

and select Source Rule Computer....—OR—

– Right-click in the source rule display (not positioned on an individualrule) to display a drop-down menu and select Change Source RuleComputer....


2. Click the down arrow under Domain: to display the Domain options.3. Select a Domain.4. Click the down arrow under Computer: to display the Computer options.5. Select a Computer.6. Click the down arrow under Directory: to display the Directory options.7. Select a Directory.8. Select a source rule from the Available source rules list.

Additional Information: To view the properties of a source rule, click theProperties button under the Available source rules list. To view the sourcerule code, click the View Code button under the Available source rules list.

Finding IBM Tivoli Management Solution for Exchange in the network

ObjectiveTo search the network and add computers not managed by the Tivoli EnterpriseManager. This feature also refreshes the Tivoli Enterprise Manager view ofprocesses and rules for computers and domains already managed by TivoliEnterprise Manager. See the “Refreshing the network view” on page 46.

Background informationFinding computers managed by IBM Tivoli Management Solution for Exchange inthe network can be a lengthy process in large networks. You can also use thisfeature to determine if domains and computers have been added or removed fromthe network by other users. Tivoli Enterprise Manager does not discover domainsor computers that have become unavailable due to computer or network error.Tivoli Enterprise Manager can remove any previously managed domains orcomputers not discovered during the find operation.

The difference between Refresh Network View and Find Tivoli in Network is thatRefresh Network View updates only the process and rule listing for domains andcomputers already managed by the Tivoli Enterprise Manager. Unlike Find Tivoliin Network, Refresh Network View does not add new domains and computers tothe Tivoli Enterprise Manager. The Find Tivoli in Network option performs theRefresh Network View operations and adds domains and computers located onthe network that were not previously managed by the Tivoli Enterprise Manager.


When You FinishNone.

ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.1. Select File from the toolbar to display the File drop-down menu.2. Select Find Tivoli in Network.

Refreshing the network view

ObjectiveTo search all domains listed in the Tivoli Enterprise Manager for computers,processes, and rules currently running in each domain so the Tivoli EnterpriseManager view can be updated.


Background informationRefreshing the network view ensures that the configuration represented by theTivoli Enterprise Manager is synchronized with the actual configuration on eachcomputer in the domain. This feature is useful if changes have been made byanother Tivoli Enterprise Manager program running elsewhere in the network.

The difference between Refresh Network View and Find Tivoli in Network is thatRefresh Network View updates only the process and rule listing for domains andcomputers already managed by the Tivoli Enterprise Manager. Unlike Find Tivoliin Network, Refresh Network View does not add new domains and computers tothe Tivoli Enterprise Manager. The Find Tivoli in Network option performs theRefresh Network View operations and adds domains and computers located onthe network that were not previously managed by the Tivoli Enterprise Manager.



ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.1. Select View from the toolbar to display the View drop-down menu.2. Select Refresh Network View.

Managing domains

ObjectiveTo specify the domains for the Tivoli Enterprise Manager to manage so you cancreate, modify, and control the execution of Tivoli rule processes on some or all ofthe computers in a domain.

Background informationYou can manage any domain on the network to which you have security access.

The Manage Domains window contains an Available Domains list and aManaged Domains list. The available domain is empty when browsing is disabled.

Virtual domains provide a flexible way of grouping computers. Virtual domains donot physically exist, but are made by software to appear to physically exist. Avirtual domain is not a Windows NT domain and has no relationship to WindowsNT domains. An example of a virtual domain might have several Exchange serversthat actually exist in different Windows NT domains. You can group them togethercreating a virtual domain named Exchange and adding all of the Exchange seversto it.

The Tivoli Enterprise Manager can manage domains that are completely physical,completely virtual, or a combination of both. Additionally, a computer can be amember of more than one domain.

When Tivoli Enterprise Manager no longer manages a domain, operation of IBMTivoli Management Solution for Exchange on the domain’s computers is notaffected.


Domains already managed by the Tivoli Enterprise Manager are listed in theManaged Network View, found in the left window pane of the Tivoli EnterpriseManager.

Before you beginYou must be logged into a domain account. If your computer is in a domain butyou are not logged into a domain account, Windows NT security restrictionsprevent you from discovering available domains.

When you finishIf browsing is enabled, the Manage Domains window displays a View Computersbutton below the available and managed domain lists. If you select a domain andclick View Computers, the View Computers window is displayed. Finally, you cansee the properties of one or more computers by selecting the computers of interestand clicking Properties or right-clicking the mouse on a computer and selectingProperties from the drop-down menu.

Procedure1. Do one of the following to display the Manage Domains window.

v From the toolbar menu:a. Select Manage from the toolbar to display the Manage drop-down menub. Select Domains... from the drop-down menu.

—OR—v From the Managed Network View:

a. Right-click empty space in the Managed Network View to display adrop-down menu

b. Select Manage Domains.

2. You can perform one or more of the following options in the Manage Domainswindow:v Add a domain to the Managed Domains list using the following steps:

a. Select a domain from the Available Domains list.b. Click Add to move the domain into the Managed Domains list.

—OR—v Remove a domain from the Managed Domains list using the following steps:


a. Select a domain from the Managed Domains list.b. Click Remove to move the domain into the Available Domains list

—OR—v Add a virtual domain to the Managed Domains using the following steps:

a. Enter a domain name in the Add virtual domain: text box.b. Click Add Domain.

3. Click Apply or OK to commit the changes you made in the Manage Domainswindow.

4. Use the following steps to view the computers in a domain:a. Select a domain from the Available domains list or the Managed Domains

list.b. Click View Computers... to display the View Computers... dialog box.

Managing computers

ObjectiveTo create, modify, and control the execution of Tivoli processes on a computerwithin a domain managed by IBM Tivoli Management Solution for Exchange.

Background informationYou can manage computers that are in domains on the network to which you havesecurity access. You can choose to manage all the computers or you can manageonly a subset of the computers within a given domain. The computers that aremanaged by the Tivoli Enterprise Manager are listed in the Managed NetworkView.

Before you beginEnable browsing so you can determine if the computers you want Tivoli EnterpriseManager to manage are currently running on the network. See “Customizing theTivoli Enterprise Manager behavior options” on page 42 for information on browseoptions.


ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.1. Do one of the following to display the Manage Computers window.

v From the toolbar:a. Select Manage from the toolbar to display the Manage drop-down menu.b. Select Computers... from the drop-down menu.

—OR—v From empty space in the Managed Network View:

a. Right-click empty space in the Managed Network View to display adrop-down menu.

b. Select Manage Computer.


2. Click the down arrow on the Domain: text box to display a list of domains.3. Click the domain you want to work with to select it.

Additional Information: When you select a a domain, IBM Tivoli ManagementSolution for Exchange populates the Available Computers and ManagedComputer lists below the domain drop-down list according to their currentstate.

4. Select an Available Computer Display: option:a. Click the down arrow on the Available Computer Display: to display the

Available Computer Display: options.b. Select one of the following options:

Do not list computers in the domainDoes not list computers in the Available Computers list of theManage Computers dialog box. This is the only option availablewhen you disable the browse options. For more information onbrowsing, see “Customizing the Tivoli Enterprise Manager behavioroptions” on page 42.

List all available computers in the domainLists all available computers for the specified domain in theAvailable Computers list of the Manage Computers dialog box.This option is available when you enable browsing for computers.

List all available computers in the domain that are running IBM TivoliManagement Solution for Exchange

Lists all available computers for the specified domain in theAvailable Computers list of the Manage Computers dialog box, butonly if they are running IBM Tivoli Management Solution forExchange. This option is available only when full browsing isenabled.

5. Do one of the following to add or remove a computer from the domain youselected in Step 3:v Add a computer to the Managed Computers list:


a. Select a computer from the Available Computers list.b. Click Add to move the domain into the Managed Computers list.

—OR—v Manually add a computer to the Managed Computers list:

a. Type the name of a computer in the Add managed computer text box toadd a computer manually.

b. Click Add Computer.—OR—

v Remove a computer from the Managed Computer list:a. Select a computer from the Managed Computer list.

Additional Information: To check the properties of a computer beforeremoving it, select it from the Managed Computers list and clickProperties.

b. Click Remove to move the domain into the Available Computer list.6. Do one of the following to save and apply the changes you made in the

Managing Computers dialog box.v Click OK to apply the changes and close the dialog box.

—OR—v Click Apply the changes without closing the dialog box.

Using the Tivoli Configuration Manager

ObjectiveTo use the Tivoli Configuration Manager to set the configuration settings on eachcomputer in the network.

Background informationYou can control the configuration settings for individual computers or allcomputers, an individual domain or all domains, or the entire network from onecomputer.

Before you beginYou must perform this procedure from the Tivoli Configuration Manager. You canopen the Tivoli Configuration Manager from the Tivoli Enterprise Manager toolbar.

If you specify a Microsoft® Exchange profile name in the Mail Information tab,you must complete the following guidelines on every computer where the MAILaction is used or where these statistics are collected. For more more information,consult your Microsoft documentation.1. Install the Microsoft® Exchange client.2. Using the Microsoft Exchange Administrator, create a Tivoli mailbox.3. Using the User Manager, create a domain level account with administrator

privilege named Tivoli.4. Configure IBM Tivoli Management Solution for Exchange to use this account.

Enter the domain name, the account name (Tivoli), and the password.5. Log off and log back on to IBM Tivoli Management Solution for Exchange

under the new Tivoli account.6. Create a Microsoft® Exchange profile for IBM Tivoli Management Solution for

Exchange to use. This is typically done using the mail applet from within thecontrol panel or by clicking on the Inbox icon. Consult your Microsoftdocumentation for details.


7. Start the Tivoli Configuration Manager.8. Click next until you see the Mail Information tab.9. Enter the Microsoft® Exchange profile name in the Profile Name field. For

example, type MS Exchange Settings or Microsoft Outlook.10. Click Finish.11. Exit IBM Tivoli Management Solution for Exchange.12. Log off from the Tivoli account.


ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.1. Click Manage from the Tivoli Enterprise Manager toolbar to display the

Manage drop-down menu.2. Select Configuration... from the drop-down menu to open the Tivoli

Configuration Manager.3. Click one of the following to display configuration settings:

v Enterprise to display the configuration settings for the entire enterprise.—OR—

v A Domain_Name to display the configurations settings for a domain.—OR—

v A Computer_Name to display the configurations settings for a computer.

Additional Information: Configuration settings display in the Settings: pane if theitem you click has IBM Tivoli Management Solution for Exchange.

4. Click one or more of the following tabs to change configuration settings for theselected tab.

General InformationTo change date and time format and key expiration warnings:a. Select a date format.b. Select a time format.c. Click the box next the Show Key Expiration Warning to enable the

feature.—OR—Click the box next to the Show Key Expiration Warning to removethe check mark and disable the feature.

Account InformationTo configure IBM Tivoli Management Solution for Exchange to use theaccount specified by the Domain and Account fields:a. Type a domain in the domain text boxb. Type an account in the account text boxc. Type a password in the password text box.

Mail InformationTo define how IBM Tivoli Management Solution for Exchange sendsmail with the MAIL action:a. Select No Mail Service.

—OR—


b. Select SMTP Mail and type a mail server in the Mail Server textbox.—OR—

c. Select Microsoft® Exchange and type a profile name in the ProfileName text box.

Rule InformationTo change which rules start automatically when your systems starts:a. Check the box of an item if you want its rules to begin monitoring

whenever you restart your computer.b. Click Apply.

Collection InformationTo limit the number of entities a rule collects and to set an emaildelivery timeout to return a delivery receipt.a. Type a value in the Maximum Items field.

Additional Information: Set this number large enough to handle thelargest collection of entities any of your rules perform. If you do notset the number large enough, IBM Tivoli Management Solution forExchange might not be able to diagnose potential problems.

b. Type a value in seconds in the Email delivery timeout.Additional Information: You can write rules using domainMSExchangeEmail to send an email to a specified address andperform an action if a delivery receipt is not returned in the amountof time specified by the Email delivery timeout.

View To display the drop-down menu.a. Select Options... to display the Tivoli Configuration Manager

options dialog box.b. Check the Confirm all update operations check box to enable the

feature.c. Check the Display success messages check box to enable the

feature.


Chapter 4. Managing processes

A Tivoli process is a background process that runs on a Microsoft Windows NT®

computer. The process starts the Tivoli Rule Engine, which runs a defined set ofTivoli rules. Each rule performs a specific monitoring task and can take actionsappropriate to the conditions monitored. See Chapter 5, “Managing rules” on page65 for more information on rules.

The Tivoli Enterprise Manager makes it easy to construct a Tivoli rule process fromone or more rules written by the Tivoli Rule Designer. You control all aspects of aTivoli rule process through the Manage Processes dialog box. After you construct aTivoli rule process, you can manage it from the Tivoli Enterprise Manager.

This chapter provides an explanation of the process concepts and step-by-stepinstructions for related procedures. Table 6 on page 55 provides an overview of thetopics covered in this chapter.

Table 6. Guidelines for managing processes

Goal Refer to

1. Displaying the Manage Processes dialogbox and selecting processes to manage

“Displaying the Manage Processes dialogbox and selecting a process” on page 55

2. Starting and stopping processes “Starting and stopping processes” on page58

3. Viewing process information “Viewing process information” on page 57

4. Copying processes from one domain toanother

“Performing operations on processes” onpage 58

5. Moving processes from one domain toanother

6. Deleting processes

7. Changing the startup state of processes

8. Setting the debug level of processes

9. Creating processes “Creating processes” on page 62

Displaying the Manage Processes dialog box and selecting a process

ObjectiveTo display the Manage Processes dialog box and select an individual process tomanage.

Background informationYou perform this procedure from the Tivoli Enterprise Manager. Use the ManageProcesses dialog box to control a Tivoli rule process at the individual rule level.Managing rules includes the following: enabling and disabling rules; firing rules;examining rule properties; viewing process status; writing process code; andcopying, moving, renaming, and deleting individual rules.

Before you beginYou must start the Tivoli Enterprise Manager. You must perform the steps in theprocedure before you can manage a process.

55


ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.1. Do one of the following to display the Manage Processes dialog box:

a. Click Manage from the Tivoli Enterprise Manager toolbar to display theManage drop-down menu.

b. Select Processes... to display the Manage Processes dialog box.—OR—

a. Click the Processes icon from the toolbar.—OR—

a. Right-click empty space in the Managed Network View to display theManage drop-down menu.

b. Select Manage Processes... from the drop-down menu to display theManage Processes dialog box.—OR—

a. Right-click on a process within a computer to display the processdrop-down menu

b. Select Manage from the drop-down menu to manage the process.

2. Click the down arrow next to the Domain... text box to display the list ofavailable domains.Additional Information: If you do not see the domain that you want, you need toadd it to the available domains list. See “Managing domains” on page 47 formore information.

3. Select a domain from the Domain... text box list.4. Click the down arrow next to the Computer: text box to display the list of

available computers.


Additional Information: If you do not see the computer that you want, you needto add it to the available computers list. See “Managing computers” on page 49for more information.

5. Select a computer from the Computer... text box list.6. Click the down arrow next to the Process... text box to display the list of

available processes.7. Select a process from the Process... text box list.

Viewing process information

ObjectiveTo display the status, rule code, or scheduling properties of a process to obtaincomplete process information.

Background informationThe status of the process includes the the following information:v The date and time the process was started on the computerv The amount of time the process has been running on the computer in secondsv The CPU time used by the computer and the percentage of the CPU usedv A listing of each rule in the process, including the rule name and whether the

rule is enabled or disabled

The rule code consists of actual statements that are executed by the Tivoli RuleEngine. The rule code is in ASCII language. The rule code defines the schedules,selections, and actions that define the mission of the rule. The Tivoli Rule Designerwrites the rule code based on the choices you make in the Tivoli Rule Designergraphical user interface. Users can write the rule code using the Tivoli Rule Editor.See “Creating a new rule using the New Rule Wizard” on page 82.

The process properties include the following:v The domain and computer on which the process is maintainedv The process namev Whether or not the process is automatically started at system startup timev Whether or not the process is currently runningv A list of rules that make up the processv Each listed rule’s schedule

Before you beginComplete all steps in “Displaying the Manage Processes dialog box and selecting aprocess” on page 55.

When you finishClose the Manage Processes dialog box to return to the Tivoli Enterprise Manager.

ProcedureYou can perform this procedure from the Tivoli Enterprise Manager DevelopmentView.1. Display the Manage Processes dialog box. See Step1 on page 56 of “Displaying

the Manage Processes dialog box and selecting a process” on page 55 for moreinformation.

2. Select a domain, computer, and process as described in Steps 2 through 7 of“Displaying the Manage Processes dialog box and selecting a process” on page55.

Chapter 4. Managing processes 57

3. Do one of the following from the Process control panel of the ManageProcesses dialog box:v Click Status to display the rule status properties.

—OR—v Click Code to display the rule code.

—OR—v Click Properties to display the rule properties.

4. Click Close to close the window when you finish viewing rule status, code, orscheduling properties.

Starting and stopping processes

ObjectiveTo start a process so the Tivoli Rule Engine can execute the process rules, or stopsa process so the Tivoli Rule Engine can stop the rules.

Background informationWhen you start a process, it executes the Tivoli Rule Engine, which in turnexecutes the defined set of process rules. Each process rule monitors for specificconditions and can take appropriate action when specific conditions occur. Whenyou stop a process, the Tivoli Rule Engine stops the rules from monitoring forconditions.

Before you beginComplete all steps in “Displaying the Manage Processes dialog box and selecting aprocess” on page 55.


ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.

Do one of the following to start or stop a process:v Click Start from the Process control panel to start a process.

—OR—v Click Stop from the Process control panel to stop a process.

Additional Information: You can right-click a process from the Managed NetworkView of the Tivoli Enterprise Manager to display a drop-down menu that includesthe Start and Stop options.

Performing operations on processes

ObjectiveTo perform operations on a process to control the rules that monitor for specificconditions.

Background informationThis procedure guides you through the following tasks:

Copying a processA copy operation copies all of the rules of the process as well as thestartup state of the process. Within the Copy Process dialog box, the sourceprocess is the copied process. The new copy of the process is the target


process. The target process and source process have the same name butyou can change the target process name by typing a new name into theTarget process text box. You can put a target process on the samecomputer as the source process provided you give them different names.

Moving a processA move operation moves all of the rules of the process from the sourcecomputer to the target computer. The startup state of the process ispreserved. Within the Move Process dialog box, the source process is themoved process. The new name and location of the moved process is thetarget process. The target process and source process have the same namebut you can change the target process name by typing a new name into theTarget process text box. You can put a target process on the samecomputer as the source process provided you give them different names.

Renaming a processYou can rename a process within a computer. In the Rename Processwindow, the process you are renaming is listed in the Old process name:field. If an existing process already has the new name you have selected,you are notified and the rename operation fails. If the process was runningat the time of the process rename, the process stops and restarts after thesuccessful rename process operation.

Deleting a processIn the Delete Process dialog box, the Process to Delete: text box lists therule that is targeted for deletion. You can change the process to be deletedby typing over the existing process in the text box.

Changing the startup state of a processYou can configure a rule process to startup automatically when you startupthe system. You can also prevent a rule process from starting upautomatically when you start the system.

Setting the debug level of a processYou can configure a Tivoli rule process to run at different debug levels.Each debug level provides a successively higher level of debugginginformation for a running Tivoli rule process. Setting a nonzero debuglevel when you first create a rule process ensures they are executingaccording to plan. Debug information is written to a file in the followingformat:ProcessName_Computer _Output.Log

where:

ProcessName is the name of the Tivoli rule process

and

Computer is the name of the computer the process is running on.

The file is stored in the \logs subdirectory under the Tivoli EnterpriseManagement Solutions installation directory. For example, the full filespecification for the file that contains debug information for a processcalled MyProcess on a computer named Everest could be:C:\Program Files\TEMS\logs\MyProcess_Everest_output.log


Table 7 lists the debug level definitions.

Table 7. Debug levels

Level Definition

0 No debugging. This is the default setting.

1 Log each rule name as it executes.

2 Log each rule name as it executes, log automatic file closes.

3 Log each rule name as it executes, log automatic file closes, log each contextvalue for each rule as it executes.

4 Log each rule name as it executes, log automatic file closes, log each contextvalue for each rule as it executes, log the condition as well (true or false).

5 Log each rule name as it executes, log automatic file closes, log each contextvalue for each rule as it executes, log the condition as true or false, log eachaction taken.

Before you beginYou must complete all the steps in “Displaying the Manage Processes dialog boxand selecting a process” on page 55.


ProcedureYou can perform this procedure from the Tivoli Enterprise Manager DevelopmentView.1. Display the Manage Processes dialog box. See Step 1 on page 56 of

“Displaying the Manage Processes dialog box and selecting a process” onpage 55 for instructions.Additional Information: Click Modify Process Rules to display the ModifyProcess Rules dialog box. See “Managing rules within a process” on page 69for more information.

2. Do one of the following to alter the process startup state from the ManageProcesses dialog box:v Check the Process automatically runs at startup box to put a check mark in

the box and to run the process automatically when the systems starts.—OR—

v Check the Process automatically runs at startup box to remove the checkmark from the box and to prevent the process from running at systemstartup.

3. Click Debug Level... to display the Process Debugging Level dialog box.4. Click the radio button the corresponds to the debug level you want to set.5. Click OK to commit debug level setting and close the Process Debugging

Level dialog box.6. Do one of the following from the Rule Control panel of the Manage

Processes dialog box:a. Click Copy to display the Copy Process dialog box.b. Go to Step 7 on page 61.

—OR—a. Click Move to display the Move Process dialog box.b. Go to Step 7 on page 61.


—OR—a. Click Rename display the Rename Process dialog box.b. Go to Step 9 on page 61.

—OR—a. Click Delete to display the Delete Process dialog box.b. Go to Step 8 on page 61.

7. Use the following steps to copy or move a process from one computer toanother:a. Click the down arrow on the Source Domain: text box to display the

Source Domain: drop-down list.b. Select a domain.c. Click the down arrow on the Source Computer: text box to display the

Source Computer: drop-down list.d. Select a computer.e. Click the down arrow on the Source Process: text box to display the

Source Process: drop-down list.f. Select a process.g. Select a rule.h. Click the down arrow on the Target Domain: text box to display the

Target Domain: drop-down list.i. Select a domain.j. Click the down arrow on the Target Computer: text box to display the

Target Computer: drop-down list.k. Select a computer.l. Verify the target process.

Additional Information: If the process in the Target process: text box is notthe desired target process, you can type in the name of a different process.

m. Do one of the following to commit the changes:v Click Apply to commit the changes.

—OR—v Click OK to commit the changes and close the dialog box.

n. Go back to Step 6 on page 60 if you want to move, rename, or delete aprocess.—OR—Go to Step 11 on page 61.

8. Click OK to delete the process in the text box.—OR—a. Type the name of the process you want to delete.b. Click OK to delete the process and close the Delete Process dialog box.c. Go back to Step 6 on page 60 if you want to copy, rename, or move a

process.—OR—Go to Step 11 on page 61.

9. Type a new name for the process in the text box.10. Click OK to commit the change to the process name.11. Click Close to close the Manage Process dialog box.


Creating processes

ObjectiveTo create a new process to manage rules.

Background informationCreating a new rule process includes the following tasks:v Selecting the target domain and computer for the process.v Specifying a name for the process.v Selecting the rules for the process to execute.v Indicating if the process runs automatically at system startup or not.

Before you beginYou must perform this procedure from the Tivoli Enterprise ManagerDevelopment View. See “Tivoli Enterprise Manager views” on page 41 for moreinformation.

When you finishYou must click OK or Apply to commit changes you make in the Create RuleProcess dialog box.

ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.1. Do one of the following to display the Create Rules Process dialog box

a. Select File from the Tivoli Enterprise Manager toolbarb. Select Create Rule Process... .

—OR—a. Display the Manage Process... dialog box. See “Displaying the Manage

Processes dialog box and selecting a process” on page 55 for moreinformation.

b. Click New from the Process Control panel of the Manage Process... dialogbox.—OR—

a. Right-click a process within the Tivoli Managed Network pane of the TivoliEnterprise Manager to display a drop-down menu.

b. Select Create Process....2. Click the down arrow on the domain text box to display the domain

drop-down menu.3. Select a domain.4. Click the down arrow on the Computer text box to display the Computer

drop-down menu.5. Select a computer.6. Specify a process name in the Process: text box.

Additional Information: After you specify a domain and computer, the TivoliEnterprise Manager generates a default name for the process. You can changethe default process name by typing a new name in the Process: text box. TheTivoli Enterprise Manager only allows you to type letters and numbers.

7. Do the following to select rules for the process to execute.a. Click the multiple rules you want to add to the Selected Rules: list from the

Available rules: list to highlight them.b. Click Add to add the highlighted rules to the Selected Rules: list.


8. Do one of the following:v Click the Start process now and automatically at system startup check box

to start the process automatically when the systems starts.—OR—

v Click the Start process now and automatically at system startup check boxto remove the check mark and prevent the process form startingautomatically when the systems starts.

9. Do one of the following to commit the changes you make in the Create RuleProcess dialog box.v Click Apply to commit the changes.

—OR—v Click OK to commit the changes and close the Create Rule Process dialog

box.


Chapter 5. Managing rules

An IBM Tivoli Management Solution for Exchange rule is a named entity used to amonitor specific situation and if necessary, take corrective action and performexternal notification. A rule operates as an autonomous agent proactivelymonitoring each server. A rule can, for example, detect if a database server isunresponsive and stop and restart it. IBM Tivoli Management Solution forExchange can monitor and take appropriate actions for a variety of operatingsystem, network, database, and application problems. A computer can execute oneor more Tivoli Rule Engine processes, each consisting of a set of Tivoli rules.

Rules consist of the following components:v The schedule that defines when the rule executesv The selections which define the entities (disks, files, processes) the rules should

examinev The conditions for which the rules must lookv Actions the rule should take if the condition is found to be true or false

You can also write, test, and edit rules using the Tivoli Rule Designer. SeeChapter 7, “Working with the Tivoli Rule Designer” on page 81 for moreinformation.

This chapter provides an explanation of the rules concepts and step-by-stepinstructions for related procedures. Table 8 provides an overview of the topicscovered in this chapter.

Table 8. Guidelines for Managing Rules

Goal Refer To

1. Displaying the Manage Rules dialogbox and selecting a rule to manage

“Displaying the Manage Rules dialog boxand selecting a rule” on page 65

2. Firing a rule “Firing a rule” on page 67

3. Enabling or disabling a rule “Enabling or disabling a rule” on page 68

4. Viewing the Status of a Rule “Viewing rule information” on page 69

5. Viewing the Code of a Rule

6. Viewing the Properties of a Rule

7. Defining the Rules of a Process “Managing rules within a process” on page698. Copying a rule from one process to

another process

9. Moving a rule from one process toanother process

10. Renaming a rule within a process

11. Deleting a rule from a process

Displaying the Manage Rules dialog box and selecting a rule

ObjectiveTo display the Manage Rules dialog box and select an individual rule to manage.

65

Background informationYou perform this procedure from the Tivoli Enterprise Manager. Use the ManageRules dialog box to control a Tivoli rule process at the individual rule level.Managing rules includes the following: enabling and disabling rules; firing rules;examining rule properties; viewing rule status and code; and copying, moving,renaming, and deleting individual rules.

Before you beginYou must start the Tivoli Enterprise Manager. You must perform the steps in thisprocedure before you can manage a rule.


ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.1. Do one of the following to display the Manage Rules dialog box:

a. Click Manage from the Tivoli Enterprise Manager toolbar to display theManage drop-down menu.

b. Select Rules... to display the Manage Rules dialog box.—OR—

a. Click the rule icon from the toolbar.—OR—

a. Right-click empty space in the Managed Network View to display theManage drop-down menu.

b. Select Manage Rules... from the drop-down menu to display the ManageRules dialog box.—OR—

a. Right-click on a rule within a process to display the rule drop-down menub. Select Manage from the drop-down menu to manage the rule.

2. Click the down arrow next to the Domain... text box to display the list ofavailable domains.


Additional Information: If you do not see the domain that you want, you need toadd it to the available domains list. See “Managing domains” on page 47 formore information.

3. Select a domain from the Domain... text box list.4. Click the down arrow next to the Computer: text box to display the list of

available computers.Additional Information: If you do not see the computer that you want, you needto add it to the available computers list. See “Managing computers” on page 49for more information.

5. Select a computer from the Computer... text box list.6. Click the down arrow next to the Process... text box to display the list of

available processes.7. Select a process from the Process... text box list8. Select the rule you want to manage from the Select a rule: list.

Firing a rule

ObjectiveTo execute a rule manually to check for conditions and perform necessary actionsimmediately.

Background informationThe only types of rules that you can fire are rules that have an asynchronousschedule. You cannot fire a rule with the interval, time of day, or one-shotschedules. IBM Tivoli Management Solution for Exchange does not perform therequest and returns an error if you attempt to fire a rule with a schedule typeother than asynchronous. See “Scheduling rules” on page 85 for more informationon scheduling rules.

The Tivoli Rule Engine can execute one rule at a time. When you fire a rule, theTivoli Rule Engine, if idle, executes the rule immediately. If the Tivoli Rule Enginereceives a request to fire a rule while it is currently executing a rule or while othersare waiting to be executed, it fires the rule after completing previous requests.

Before you beginYou perform this procedure from the Manage Rules dialog box. You mustcomplete the steps in “Displaying the Manage Rules dialog box and selecting arule” on page 65.

When you finishIf the rule fires successfully, the success message window is displayed. Click OK toclose the message window.

If the rule does not fire, an error message displays.

ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.

Chapter 5. Managing rules 67

1. Display the Manage Rules dialog box. See step 1 on page 66 of “Displaying theManage Rules dialog box and selecting a rule” on page 65 for moreinformation.

2. Select a rule from the Select a rule: list.3. Click Fire from the Rule Control panel of the Manage Rules dialog box.

Enabling or disabling a rule

ObjectiveTo enable a rule so the Tivoli Rule Engine can execute it when its next scheduledexecution time occurs or to disable a rule to prevent the Tivoli Rule Engine fromexecuting it.

Background informationA rule is in its normal state when it is enabled.

When you disable a rule, you prevent the Tivoli Rule Engine from executing thedisabled rule until you enable it again. You can enable a rule upon requestmanually, or you can enable a rule under program control by another rule.

When you disable a rule, it is only disabled while in the currently running ruleprocess. If you stop and restart the process for any reason, disabled rules areenabled.

Before you beginYou perform this procedure from the Manage Rules dialog box. See “Displayingthe Manage Rules dialog box and selecting a rule” on page 65 for moreinformation on how to display the Manage Rules dialog box.


ProcedureYou can perform this procedure from the Tivoli Enterprise Manager.1. Display the Manage Rules dialog box. See step 1 on page 66 of “Displaying the

Manage Rules dialog box and selecting a rule” on page 65 for moreinformation.

2. Select a rule or multiple rules from the Select a rule: list.3. Do one of the following from the Rule Control panel of the Manage Rule

dialog box:v Click Enable to enable the selected rule or rules.

—OR—v Click Disable to disable the selected rule or rules.


Viewing rule information

ObjectiveTo display the status, code, or scheduling properties of a rule to obtain completerule information.

Background informationThe rule status includes the name of the rule and whether the rule is enabled ordisabled.

The rule code consists of actual statements that are executed by the Tivoli RuleEngine. The rule code is in ASCII language. The rule code defines the schedules,selections, and actions that define the mission of the rule. The Tivoli Rule Designerwrites the rule code based on the choices you make in the Tivoli Rule Designergraphical user interface. Users can write the rule code using the Tivoli Rule Editor.See Chapter 7, “Working with the Tivoli Rule Designer” on page 81.

The scheduling properties include the rule description, rule author, rule name, thetype of schedule the rule uses, the details of the schedule including whether or notit is enabled or disabled, and what the user selections and thresholds are, if any.


When you finishClose the view window when you finish viewing rule status, code, or properties.

ProcedureYou can perform this procedure from the Tivoli Enterprise Manager DevelopmentView.1. Display the Manage Rules dialog box. See step 1 on page 66 of “Displaying the



dialog box:v Click Status to display the rule status properties.

—OR—v Click Code to display the rule code.

—OR—v Click Properties to display the rule properties.

4. Click Close to close the window when you finish viewing rule status, code, orscheduling properties.

Managing rules within a process

ObjectiveTo define the rules of a process, copy, or move rules from one process to another,and to rename or delete a rule within a process.


Background informationDefining the processes of a rule is the same as modifying the rule of a process.Modifying the process rules includes adding rules to and removing rules from aprocess, or changing the order of the rules in a process.

The source rule is the copied rule within the Copy Rule dialog box. The new copyof the rule is the target rule. The target rule and source rule have the same namebut you can change the target rule name by typing a new name into the Targetrule text box. You can put a target rule in the same process as the source ruleprovided you give then different names. After the target rule is created, it is placedat the end of the target process rule list. If confirmation options are set to requireconfirmation for replacement options, the following message is displayed whenyou try to copy to an existing target rule:

If confirmation options are set not to require confirmation for replacement options,an existing target rule is replaced with a copy of the source rule without priorconfirmation. If the target process is running during the time in which you copy arule, it is stopped and restarted after the rule is copied into the target process.

Within the Move Rule dialog box, the source rule is the moved rule. The newname and location of the moved rule is the target rule. The target rule and sourcerule have the same name but you can change the target rule name by typing a newname into the Target rule text box. You can put a target rule in the same process asthe source rule provided you give them different names. The target rule is placedat the end of the target process rule list.

You can rename a rule within a process. In the Rename Rule window, the rule youare renaming is listed in the Old rule name: field. If you type a new name for anexisting rule in the process that already exists, you are notified and the renameoperation fails. If the rule process was running at the time of the rule rename, itstops and restarts after the successful rename rule operation.

In the Delete Rule dialog box, the Rule to Delete: text box lists the rule that istargeted for deletion. If the rule process is running at the time you delete the rule,it stops and restarts after the successful delete rule operation. If the rule to delete isthe only rule in the rule process, the rule process is also deleted.



ProcedureYou can perform this procedure from the Tivoli Enterprise Manager DevelopmentView.1. Display the Manage Rules dialog box. See Step 1 on page 66 of “Displaying the




dialog box:a. Click Rules... to display the Modify Process Rules dialog box.b. Go to Step 4 on page 71.

—OR—a. Click Copy to display the Copy Rule dialog box.b. Go to Step 5 on page 71.

—OR—a. Click Move to display the Move Rule dialog box.b. Go to Step 5 on page 71.

—OR—a. Click Rename display the Rename Rule dialog box.b. Go to Step 6 on page 72.

—OR—a. Click Delete to display the Delete Rule dialog box.b. Go to Step 8 on page 72.

4. Do the following to modify the process rule:a. Click the down arrow on the Domain: text box to display the Domain:

drop-down list.b. Select a domain.c. Click the down arrow on the Computer: text box to display the Computer:

drop-down list.d. Select a computer.e. Click the down arrow on the Process: text box to display the Process:

drop-down list.f. Select a process.g. Do one of the following to modify a process rule:

1) Select a rule or rules from the Available Rules: list.2) Click Add to move the selected rules to the Selected Rules: list.

—OR—1) Select a rule or rules from the Selected Rules: list.2) Click Remove to move the selected rules to the Available Rules: list.

Additional Information: Click Source to open the Change source rulecomputer dialog box. See “Changing the Source Rule Computer” onpage 45 for more information.

h. Do one of the following to commit the changes:v Click Apply to commit the changes.

—OR—v Click OK to commit the changes and close the Modify Process Rule

dialog box.5. Use the following steps to copy or move a rule from one process to another:

a. Click the down arrow on the Source Domain: text box to display theSource Domain: drop-down list.

b. Select a domain.c. Click the down arrow on the Source Computer: text box to display the

Source Computer: drop-down list.


d. Select a computer.e. Click the down arrow on the Source Process: text box to display the Source

Process: drop-down list.f. Select a process.g. Click the down arrow on the Source Rule: text box to display the Source

Rule: drop-down list.h. Select a rule.i. Click the down arrow on the Target Domain: text box to display the Target

Domain: drop-down list.j. Select a domain.k. Click the down arrow on the Target Computer: text box to display the

Target Computer: drop-down list.l. Select a computer.m. Click the down arrow on the Target Process: text box to display the Target

Process: drop-down list.n. Select a process.o. Do one of the following to commit the changes:

v Click Apply to commit the changes.—OR—

v Click OK to commit the changes and close the dialog box.6. Type a new name for the rule in the text box.7. Click OK to commit the change to the rule name.8. Click OK to delete the rule in the text box.

—OR—a. Type the name of the rule you want to delete.b. Click OK to delete the rule and close the Delete Rule dialog box.

9. Click Close to close the Manage Rules dialog box.


Chapter 6. Managing solutions

A solution is a pre-defined rule process designed to monitor a specific application.IBM Tivoli Management Solution for Exchange offers the following six solutions:v Adminv Exchangev Exchange 2000v SQL Server 2000v SQL Server 6.5v SCL Server 7

Solutions differ from ordinary rule processes in that you can tailor their behaviorwhile the solution is running.

This chapter provides information about controlling the execution of Tivolisolutions on a network and step-by-step instructions for related procedures. Table 9provides an overview of the topics covered in this chapter.

Table 9. Guidelines for managing solutions

Goal Refer to

1. Viewing and understanding the TivoliSolutions Manager

“Displaying the Tivoli SolutionsManager” on page 73

2. Defining a set of solutions “Adding and removing solutions” onpage 74

3. Setting confirmation or successnotifications

“Setting Tivoli Solutions Manageroptions” on page 76

4. Changing thresholds or selections of arunning process

“Editing solution variables” on page 77

Displaying the Tivoli Solutions Manager

ObjectiveTo display the Tivoli Solutions Manager so you can manage solutions.

Background informationThe Tivoli Solutions Manager uses variables to update computers throughout yourIBM Tivoli Management Solution for Exchange network. A variable is a placeholderfor a value or a set of values. The values control the behavior of solutions.Through the Tivoli Solutions Manager, you can edit variables on all IBM TivoliManagement Solution for Exchange computers in your network from a centrallocation. The following displays the Tivoli Solutions Manager graphical userinterface.

Before you beginYou must perform this procedure from the Tivoli Enterprise ManagerDevelopment View.


73

Procedure1. Click Manage from the Tivoli Enterprise Manager to display the Manage

drop-down menu.2. Select Statistics... from the Manage drop-down menu to display the Tivoli

Solutions Manager.

Adding and removing solutions

ObjectiveTo define the set of solutions so you can view and manage them through the TivoliEnterprise Manager.

Background informationThe Tivoli Enterprise Manager window displays a list of solutions for eachcomputer managed by IBM Tivoli Management Solution for Exchange. You canincrease or decrease the size of this list for a computer or group of computers. Ifyou remove any solutions, you can add them back into the managed list at anytime.

When you select a domain or enterprise, the first computer in the domain orenterprise displays a list of solutions, and the available or managed state ofsolutions. Usually all computers in the domain or enterprise have the same set ofsolutions. Solutions that are not explicitly listed are not altered when computerswithin the same domain or enterprise have different solution sets.

The Solution Set Driver File: Each solution managed by the Tivoli SolutionsManager must have a .sdd (solutions set driver) file. This file has the same nameas the solution and a file extension of .sdd. For example, the solution set driver filefor Exchange2000 is Exchange2000.ssd. This file must exist in the IBM TivoliManagement Solution for Exchange \config folder. If you are adding rules to anexisting solution, add entries for variables that are used in your new rules to theexisting solution set driver file. If you are creating a new solution, you must alsocreate a new solution set driver file. Blank lines can exist anywhere in the file, and


comments can be added by beginning a line with an exclamation point. The firstthree lines in the solution set driver file must be:RoboMon Solution Set Driver FileMajor Version Number: 1Minor Version Number: 0

You must add the following lines for each variable that Tivoli Solutions Managermanages:Name: The name of the variable used in the rule or rulesDisplay Name: The name of the variable displayed by the Tivoli SolutionsType: The data type of the variable (I, F, or S)Minimum Value: The minimum value of the variable (numeric data types only)Maximum Value: The maximum value of the variable (numeric data types only)Default Value: The default (initial) value of the variableUnits: The units associated with the valueBrief Description: The brief description displayed by the Tivoli Solutions ManagerFull Description: The full description displayed by the Tivoli Solutions Manager

Creating or Updating the Solution Variable File: Each solution has a defaultvariable file where each variable used in all of its rules is maintained. This file is inthe IBM Tivoli Management Solution for Exchange \config folder and is namedsolution.var where solution is the name of the solution. For example, the defaultvariable file for Exchange2000 is Exchange2000.var.

From a command window, execute the following command in the IBM TivoliManagement Solution for Exchange \bin folder:UpdateVarFile solution

where solution is the name of the solution.

This command creates a variable in the solution’s default variable file for eachvariable defined in the solutions set driver file (.ssd), if it does not currently existin the variable file. If you add new variables to the solution set driver file and runthis command, these variables are created in the default variable file. Also,executing this command populates all the variables in the default variable filewhen you create a new solution and a corresponding solutions set driver file.

Keeping Threshold Variables Updated: Each solution must include a rule thatreads all threshold variables used in the solution. This rule name isRefresh_solution_Variables, where solution is the name of the solution. See thefollowing example:

Example: Refresh_Performance_Variables

This rule is comprised of a list of READ actions, one for each threshold variable.You must also add any new threshold variable that you added to the solution tothis list of READ actions.

Before you beginYou must perform this procedure from the Tivoli Enterprise Manager window.


Procedure1. Click the entity (enterprise, domain, or computer) for which you want to

change solutions in the Managed Network view of the Tivoli EnterpriseManager window.

Chapter 6. Managing solutions 75

2. Click Manage on the toolbar to display the Manage drop-down list.3. Click Add/Remove Solutions to display the Add/Remove Solutions dialog

box.Additional Information: The top part of the dialog box includes a label and anicon that indicates the entity you are about to change.

4. Do the following from the Add/Remove Solutions dialog box:a. Select one or more solutions from the Available solutions list that you want

to add to the selected entity.b. Click Add to move the solutions to the Managed solutions list.c. Select one or more solutions from the Managed solutions list that you want

to remove from the selected entity.d. Click Remove to move the undesired solutions to the Available solutions

list.

Note: If a solution is running when you remove it from the Managedsolutions list, it automatically stops.

—OR—e. Click Select All under the Available solutions list or the Managed

solutions list.f. Click Add or Remove to move all of the selected solutions to the other list.

—OR—g. Double-click a solution to transfer it from one list to another.h. Click OK to apply the changes to the lists.

—OR—i. Click Cancel to cancel the changes to the lists.

Setting Tivoli Solutions Manager options

ObjectiveTo set Tivoli Solutions Manager so you can control whether the Tivoli SolutionsManager asks you for confirmations before performing specific operations.

Background informationThe confirmation options control whether certain operations require confirmationand whether or not success messages display. Error messages always display; theyare not optional. Two options are available:

Confirm all update operationsSelect this option to have the Tivoli Solutions Manager identify andconfirm the operation you are about to perform. Tivoli Solutions Managerperforms requested operations without asking for confirmation if you donot select this option.

Display success messagesIf you select this option, the Tivoli Solutions Manager informs you whenthe requested operation completes successfully. If you do not select thisoption, you do not receive a message indicating the operation wassuccessful. The lack of a messages indicates success.

Before you beginYou must perform this procedure from the Tivoli Enterprise Manager.


When you finishNone

ProcedureYou can perform this procedure from the Tivoli Enterprise Manager –Management View.1. Click View on the Tivoli Solutions Management toolbar to display the View

drop-down menu.2. Click Options on the View drop-down menu to display the Options dialog

box.3. Check or uncheck one or both of the following options:

v Confirm all update operations

Additional Information: Tivoli Solutions Manager asks you to confirm theoperation when Confirm all update operations is checked. Click Yes toperform the operation, or No to cancel the operation.

v Display success message

Additional Information: Tivoli Solutions Manager informs you that a requestedoperation was successfully performed when Display success message ischecked. Click OK to dismiss the success message.

Editing solution variables

ObjectiveTo change thresholds or selections of a running process so you can control the waythe solutions behave.

Background informationA variable is a placeholder for a value or a set of values. The values control howthe solution behaves. Using variables in a rule’s selections and condition is the keyto managing the rule with the Tivoli Solutions Manager. When a rule executes, thevalue of each variable used is read from the default variable file of the rule. Youcan change the value of these variables with the Tivoli Solutions Manager, whichwrites the changed value to the default variable file. The next time the ruleexecutes, the new value is used without the need to change the rule or restart therule process.

See the following examples:v A rule’s condition is:

CPU_BUSY_PCT >CPU_BUSY_PCT_MAX

CPU_BUSY_PCT is the percentage of the computer’s CPU that was busy during theinterval. CPU_BUSY_PCT_MAX is a variable in the rule’s default variable filecontaining the maximum value permitted for CPU_BUSY_PCT. If CPU_BUSY_PCTexceeds this value, the true actions of the rule execute.

v A rule’s selection for PROCESS_NAME is:{PROCESS_NAME_SEL}

PROCESS_NAME_SEL is a variable in the rule’s default variable file containing a listof process names (separated by commas) that the rule examines. The ruleexecutes for each process specified in this list. Variables must be enclosed inbraces when used in selections.

A solution set includes the variables. The following parts comprise a variable:


v Namev Valuev Typev Unitsv Description

Before you beginYou must perform this procedure from the Tivoli Enterprise Manager.


Procedure1. Click on enterprise, domain, or computer for which you want to change

solutions in the Tivoli Enterprise Manager window.Additional Information: The available solution sets and their variables display onthe right side of the screen.

Note: Editing variables on the enterprise or a domain changes the variables onall of the computers in the selected enterprise or domain.

2. Display the Tivoli Solutions Management window:a. Click Manage on the Tivoli Enterprise Manager – Management View

toolbar to display the Manage drop-down menu.b. Click Tailor Solutions on the Manage drop-down menu to display the

Tivoli Solutions Management window.

—OR—a. Right-click on a computer or process in the Managed Network View

window (left pane) to display a pop-up menu.b. Click Tailor or Tailor Solutions on the pop-up menu.

3. Click the tab in the Solution Sets window (right pane) that is labeled with thename of the solution that contains the variable you want to change.Additional Information: The Variable Display window is below the tab andcontains a list of variables used by the solution. For each variable in the list thefollowing information is provided next to the variable name: value, type, units,and description.

4. Edit the variable:a. Click on a variable in the Variable Display window.b. Display the Edit Variable window:

1) Click File on the Tivoli Solutions Management toolbar to display theFile drop-down menu.

2) Click Edit Variable on the File drop-down menu.

—OR—1) Right-click on the variable in the list to display a pop-up menu.2) Click Edit Variable on the pop-up menu.

—OR—1) Double-click the variable in the list.


Additional Information: The variable to be edited is listed in the drop-downlist at the top of the Edit Variable window.

c. Click on the Variable Name drop-down list in the Edit Variable windowand select another variable to change the variable to be edited.Additional Information: When a different variable is chosen, the informationin the Edit Variable window changes to the information that is appropriatefor the selected variable.

d. Type the desired value for the variable in the Value field.Additional Information: The value of a variable can be changed according toits variable type. For example, if the variable type is “integer” and you tryto change the variable’s value to “a”, an error message is displayed.

e. Click Refresh to restore the current settings of the variable and keep theEdit Variable window open to change another variable.—OR—

f. Click Default to restore the predefined value of the variable and keep theEdit Variable window open to change another variable.—OR—

g. Click Apply to apply the change to the current variable and keep the EditVariable window open to change another variable.

h. Click Yes or No in the message box asking if you want to update thechanges you made to the current variable.v If yes, click OK in the message box stating that updating was successful.

—OR—v Click OK to apply the change to the current variable and close the Edit

Variable window.i. Click Cancel to cancel the changes and close the Edit Variable window.

5. Exit the Tivoli Solutions Manager:a. Click File on the Tivoli Solutions Manager toolbar.b. Click Close.


Chapter 7. Working with the Tivoli Rule Designer

This chapter provides information about Tivoli rules, including how to create andmodify rules. Table 10 provides an overview of the procedures for creating andediting rules.

Table 10. Guidelines for creating and editing Tivoli rules

Goal Refer to

Creating New Rules

1. Creating a new rule with the Tivoli RuleDesignerv Using the New Rule Wizardv Using the Tivoli Rule Designer

– Creating the schedule for a rule– Creating the selections for a rule– Creating the conditions for a rule– Creating the actions for a rule– Creating the documentation for a rule

“Creating a new rule using the New RuleWizard” on page 82

“Scheduling rules” on page 85

“Managing rule selections” on page 89

“Managing rule conditions” on page 92

“Managing rule actions” on page 96

“Documenting a rule” on page 103

2. Creating rules manually using the TivoliRule Editor

“Creating rules manually using the TivoliRule Editor” on page 105

Editing Rules

3. Modifying rules with the Tivoli RuleDesigner

“Editing rules graphically using the TivoliRule Designer” on page 104

4. Modifying rules manually using the TivoliRule Editor

“Editing rules manually using the TivoliRule Editor” on page 107

A Tivoli rule is a named entity that monitors a specific situation and takesappropriate corrective action or performs external notification, or both. A Tivolirule contains four basic components that you can manage through the Tivoli RuleDesigner:

ScheduleThe schedule for a rule determines when the rule executes.

SelectionA set of selections defines which entities IBM Tivoli Management Solutionfor Exchange collects and uses to evaluate the rule condition. Examples ofentities are disks, files, and processes.

ConditionThe rule condition is an expression that evaluates to ″true″ or ″false″. If nocondition is entered, the rule evaluates to ″true″. A condition can includeany of the following items: statistics, user-defined statistics, variables,predefined variables, constants, operators, and functions.

ActionA Tivoli rule executes actions based on the evaluation of the rule condition.Actions determine how a Tivoli rule operates with other IBM TivoliManagement Solution for Exchange components. Actions also determinehow IBM Tivoli Management Solution for Exchange corrects problemsfound on your computer. A rule must have at least one action.

81

Rules reside in rule files. You can place all rules in a single rule file or use severalrule files to organize your rules.

IBM Tivoli Management Solution for Exchange provides defined rules to whichyou can add new rules that are relevant to your organization. Rules are written inrule code statements and executed by the Tivoli Rule Engine. Rule code defines therule name as well as the conditions, actions, schedule, and selections. Rule code iswritten in ASCII.

You can create and edit rules through the Tivoli Rule Designer in the followingtwo ways:v The Tivoli Rule Designer graphical interface, from which you select the New

Rule Wizard to create new rules.—OR—

v The Tivoli Rule Editor, an ASCII-based editor in which you type rule definitionlanguage code.

Creating a new rule using the New Rule Wizard

ObjectiveTo create a new rule through a graphical interface that satisfies uniquerequirements such as adding an email or paging action.

Background informationThere is a maximum of 50 rule processes per computer.

You can give a rule any name, but spaces cannot be included in that name.

The rule description is optional and does not affect the execution of the rule. Youcan use the rule description so other users can understand why the rule wascreated.


When you finishAfter completing the four parts of the New Rule Wizard and clicking Finish, youmust use the Tivoli Rule Designer to specify at least one action for the rule(“Managing rule actions” on page 96). You can also document the rule(“Documenting a rule” on page 103), set the rule schedules (“Scheduling rules” onpage 85), specify rule selections (“Managing rule selections” on page 89), andspecify rule conditions (“Managing rule conditions” on page 92) in the Tivoli RuleDesigner. You can complete these operations in any order.

ProcedureYou can perform this procedure from the Development View or ManagementView in the Tivoli Enterprise Manager window.1. Start the New Rule Wizard by doing one of the following in the Development

View or Management View:v Use the New Rule Wizard in the Development View or Management View:

a. Select File from the toolbar to display the File drop-down menu.b. Select New Rule from the drop-down menu to display the New Rule

Wizard - Step 1 dialog box.

—OR—


v Use the Tivoli Rule Designer in the Development View or ManagementView:a. Select Run from the toolbar to display the Run drop-down menu.b. Select Tivoli Rule Designer from the Run drop-down menu to display

the Tivoli Rule Designer.Additional Information: If you are in Development View, an existing ruleis displayed in the Tivoli Rule Designer if your source directory has rulesin it. The New Rule Wizard window is displayed in Development Viewif there are no rules in the source directory. The New Rule Wizardwindow is always displayed in Management View.

c. Do one of the following if the Tivoli Rule Designer window displays anexisting rule:– Use the menus:

1) Select File from the Tivoli Rule Designer toolbar to display theFile drop-down menu.

2) Select New Rule from the File drop-down menu to display theNew Rule Wizard - Step 1 dialog box.

—OR—– Click the New Rule icon to display the New Rule Wizard - Step 1

dialog box.—OR—

– Double-click on white space in the right pane of the Tivoli EnterpriseManager windowDevelopment View.

2. Do the following to name and describe the rule:a. Type the name of the new rule in the text box for the rule name.

Chapter 7. Working with the Tivoli Rule Designer 83

Additional Information: This name must be unique within its directory. Thename must begin with a character of the alphabet.

b. Type a rule description.Additional Information: The rule description is optional and does not affectthe execution of the rule.

c. Do one of the following:v Click Next to display the New Rule Wizard - Step 2 dialog box.

—OR—v Click Cancel to cancel the creation of the new rule.

3. Do the following to specify the statistic domain for the rule:a. Select the rule’s statistic domain from the list.

Additional Information: A short description of the statistic domain isdisplayed under the list of statistics. If you want to see a list of the statisticsfor the domain, click View Statistics to display the Statistics Listingwindow. Click Close when you finish viewing statistics. See Chapter 8,“Working with the Tivoli Statistics Builder” on page 111 for moreinformation about statistic domains.

b. Do one of the following:v Click Next to display the New Rule Wizard - Step 3 dialog box.

—OR—v Click Back to go back to Step 1 of the New Rule Wizard and change the

name or description of the rule.—OR—

v Click Cancel to cancel the creation of the new rule.4. Do the following to select a type of schedule for the rule:

a. Select one of the scheduling options:

Interval (e.g. run every 60 minutes)interval-based schedules are the most common type of schedule. Foran interval-based schedule, you must specify the interval orfrequency you want for rule execution in the Tivoli Rule Designerwindow after you finish the New Rule Wizard options.

Time of day (e.g. run at 8:00 AM and 5:00 PM)Time of day schedules run at one or more times of the day that youspecify. You specify or change Time of Day schedules in the TivoliRule Designer window after you finish the New Rule Wizardwindow.

Run only once when the Tivoli rule process is startedA rule that runs only once executes when you start the Tivoli ruleprocess. This kind of schedule is often used for rules that initializevariables used in other rules or to announce that a Tivoli ruleprocess has started.

Run manually (from the user interface or from an action of another rule)A rule that runs manually (asynchronous rule) can be executed onlyfrom the Tivoli Enterprise Manager main window, or from anotherrule using the Execute Rule action.

b. Do one of the following:v Click Next to display the New Rule Wizard - Final dialog box.

—OR—


v Click Back to go back to Step 2 of the New Rule Wizard to change thestatistic domain.—OR—

v Click Cancel to cancel the creation of the new rule.5. Review the properties for the rule and display the Tivoli Rule Designer by

doing one of the following:v Click Finish to display the Tivoli Rule Designer so you can specify or

modify the rule documentation, schedule, selections, condition, or actions.—OR—

v Click Back to go back to Step 3 of the New Rule Wizard to change the typeof schedule for the rule.—OR—

v Click Cancel to cancel the creation of the new rule.

Scheduling rules

ObjectiveTo set up the schedule that defines when the rule executes.

Background informationThe Schedule window of the Tivoli Rule Designer shows the schedule type youselected in the procedure, Creating a New Rule Wizard (Step 4 on page 84). If youselected an Interval or Time of Day schedule, you can now specify restrictions forthese types of schedules.

The initial value assigned to an interval-based schedule is one hour, which meansthe rule executes every hour on the hour. Rules do not execute at the firstscheduled interval when the rule is started. The rule’s statistics are initialized atthe time of the first scheduled interval when the rule is started. In subsequentintervals, the value of statistics that reflect activity during the interval can becalculated for a full interval.

Time of Day schedules run at one or more times of the day that you specify. Youcan specify or change Time of Day schedules in the following two ways:v Type the time or times in the Time of day field of the Schedule window.

—OR—v Access the Times of Day window where you can set times.

There are six options for restricting schedules. Interval schedules can be restrictedby using the Part of the Day restriction. Both Interval and Time of Day schedulescan be restricted by the other five measures of time. Table 11 contains a list of theoptions and an example of each option for restricting schedules.

Table 11. Examples of options for restricting a schedule

Options Example

Part of the Day (Interval only) A rule executes every 15 minutes, but only betweenthe hours of 8:00 AM and 5:00 PM.

Days of the Week A rule executes only Monday through Friday.

Days of the Month A rule executes only on the first day of the month.

Weeks of the Month A rule executes only on the first week of the month.

Months of the Year A rule executes only during June and December.


Table 11. Examples of options for restricting a schedule (continued)

Dates A rule executes only between March 1, 2002, andMay 30, 2002.

Before you beginComplete the procedure, “Creating a new rule using the New Rule Wizard” onpage 82, which displays the Tivoli Rule Designer.

When you finishAfter scheduling a rule, you must complete all of the other operations in the TivoliRule Designer that you have not yet completed, including Selections (“Managingrule selections” on page 89), Condition (“Managing rule conditions” on page 92),Actions (“Managing rule actions” on page 96), and Documentation (“Documentinga rule” on page 103). You can complete these operations in any order. At aminimum, you must specify an action for the rule.

ProcedureYou can perform this procedure from the Tivoli Rule Designer only.1. If the Schedule window is not active in the New Rule Designer window, click

the Schedule tab.

2. If you need to change the type of schedule you selected in the New RuleWizard procedure, Step 4 on page 84, select a different schedule type:v Interval

v Time of day

v Run only once when the Tivoli rule process is started

v Run manually (from the user interface or from an action of another rule)

3. Depending on the schedule type you chose, do one of the following:v If you chose Interval, go to Step 4 on page 87.v If you chose Time of day, go to Step 5 on page 87.


4. To specify the interval for an Interval schedule, do one of the following:v Type a value (in the hours:minutes:seconds format) in the field next to the

Interval option.—OR—

v Use the arrows to change the value.5. To specify the time or times of day, do one of the following:

v Type a list of times separated by commas in the Time of day field.—OR—

v Click Modify next to the Time of day field to display the Times of Daywindow.

6. To use the Times of Day window to add a time of day to the current list oftimes, do the following:a. Do one of the following:

v Type a new value in the Time to add field.—OR—

v Use the arrows to change the value.b. Do one of the following:

v Click Add to add this time to the list.—OR—

v Click Cancel to close this window and discard any changes.7. To use the Times of Day window to change a time in the list of current times:

a. Click the time value you want to change in the Current times of day field.b. Click Modify.

Additional Information: The time you selected is displayed in the Time to addfield.

c. Do one of the following:v Type a new value.

—OR—v Use the arrows to change the value.

d. Click Update to replace the time in the list with the new time.e. Click OK when finished updating the times.

—OR—f. Click Cancel to close this window and discard any changes.

8. To use the Times of Day window to remove a time from the current list oftimes:a. Click the time value you want to remove in the Current times of day field.b. Click Remove.c. Click OK when finished removing times.

—OR—d. Click Cancel to close this window and discard any changes.

9. To use the Times of Day window to remove all entries from the current list oftimes:a. Click Remove All.b. Click OK.

—OR—c. Click Cancel to close this window and discard any changes.


10. To set restrictions for Interval or Time of day schedules, see “Setting part ofthe day and dates” on page 88 or “Setting days, weeks, and months” onpage 89.

11. Save the schedule.a. Click File to display the File drop-down menu.b. Click Save from the drop-down menu to save the choices made in the

Tivoli Rule Designer window.

Setting part of the day and dates1. Select Part of the day or Dates in the Restrictions list.

Additional Information: When setting part of a day, the measure is a range ofhours, minutes, and AM or PM. When setting dates, the measure is a range ofmonths, days, and years.

2. Click Modify to specify the part of the day or date in the Parts of the Day orDates window.

3. To add a part of the day or date range, do the following:a. Set the desired beginning and ending time or date in the Part of the day to

add or Date range to add fields by doing the following:1) Click the time or date component in either field.2) Do one of the following:

v Type a new value.—OR—

v Use the arrows to change the value of the selected component.b. Click Include or Exclude if you are setting a date range.

Note: Parts of the day restrictions do not include these options. For dates, itmakes sense to specify only a date range to exclude if it is containedwithin a wider date range to include.

c. Click Add to add the specified range to the list.d. Click OK when you are finished specifying the list of ranges.

4. To change a range, do the following:a. Select the range you want to change in the Current date ranges or Current

parts of the day field.b. Click Modify to load the range into the two fields under Date range to add

or Part of the day to add.c. Modify one or both of the range fields.d. Click Update to replace the range in the list.e. Do one of the following:

v Click OK to apply the change.—OR—

v Click Cancel to cancel the change.5. To remove a range in the current list:

a. Select the range you want to remove.b. Click Remove.c. Click OK.

6. To remove all entries from the list of ranges:a. Click Remove All.b. Click OK.


Setting days, weeks, and months1. Select a restriction from the following options in the Restrictions list:

v Days of the week

v Days of the month

v Weeks of the month

v Months of the year

2. Click Modify under the Restrictions list to display the window appropriate forthe restriction.

3. Do one of the following:v Click the days, weeks, or months that you want the rule to run.

—OR—v Click Set All to check all days, weeks, or months.

—OR—v Click Clear All to uncheck all days, weeks, or months.

4. Do one of the following:v Click OK after you select the desired days, weeks, or months to display the

selection in the Restrictions list of the Schedule window.—OR—

v Click Cancel to close this window and discard any changes.

Managing rule selections

ObjectiveTo define which entities (such as disks, files, and processes) the rule shouldexamine.

Background informationSelections limit the instances of the statistic domain that are considered for ruleexecution. Rule selections are meaningful only for rules in one of the enumeratedstatistic domains. There is a note near the bottom of the Selections window thatstates, ″No selections are permitted for a scalar rule if the statistic domain for therule is scalar.″

Format for Selections: Selections are a list of values or value ranges separated bycommas. A dash (″-″) separates the beginning and ending values of the range. Aninstance of the statistic domain is selected if the value of the selection statistic isone of the values in the list, or if it is contained within one of the ranges in the list.A selection can have only one item in the list, reducing it to a single value orrange.

There are three types of selections:v Simple Selectionsv Selections with Wildcardsv Selections with Exceptions

Simple selections: Selection statistics contain numeric or alphanumeric stringvalues. The formatting syntax in the examples below applies to both kinds ofstatistics, but there are a few differences. When a range is specified for numericstatistics, it is evaluated numerically; when a range is specified for string statistics,it is evaluated alphabetically. Therefore, a numeric statistic with a value of ″2″ falls


within the range of ″1-10″. However, a string statistic with a value of ″2″ does notfall within the range of ″1-10″, since ″2″ is alphabetically greater than ″10″.

Also, the letters ″B″ (for Begin) and ″E″ (for End) can be used to refer to thesmallest and largest possible values of a range. Therefore, the range ″B-99″ meansany number less than or equal to 99. Similarly, the range ″1000-E″ means anynumber greater than or equal to 1000.

Examples of simple selections:

1. The value must be 1

1. 100 The value must be between 1 and 100

TOM,DICK,HARRY The value must be either ″TOM″, ″DICK″ or ″HARRY″

Selections with wildcards: Two special wildcard characters, ″*″ and ″%″, can be usedfor string selection values, except in ranges. The ″*″ character matches any set ofcharacters. For example, the selection value of ″A*″ matches any value beginningwith an ″A″. The selection value of ″*XYZ*″ matches any value containing thecharacters, ″XYZ″.

The ″%″ character matches any single character. For example, the selection value of″A%CD″ matches any value containing four characters, where the first character is″A″, the third character is ″C″, and the fourth character is ″D″. Any character canbe second. The all-inclusive wildcard value of ″*″ is the only time a wildcard valuecan be used in a numeric selection.

Examples of selections containing wildcards:

TOM,DICK,H* The value must be either ″TOM″, ″DICK″, or anything beginningwith an ″H″

A*,CA-F,*X The value must either begin with an ″A″, fall in the range between″CA″ and ″F″, or end with an ″X″

ABC% The value must be exactly four characters long, beginning with″ABC″

%_* The value must begin with a single character followed by an ″_″

Selections with exceptions: Exceptions can be specified by entering ″E=″ followed bya list of values or ranges. When a list is specified in an exception, it must beenclosed in parentheses. A single value in an exception list can also containwildcard characters if it is for a string statistic. The use of exceptions is meaningfulonly when a wider selection is also included. An instance of the statistic domain isselected if the value matches one of the non-exception values or ranges, and doesnot match one of the exception values or ranges.

Examples of selections that include exceptions:

T*,E=(TOM,TED),DICK Anything beginning with a ″T″, but excluding ″TOM″ and″TED″, or ″DICK″

AB*,E=(ABC-ABX) Anything beginning with ″AB″ but excluding anything inthe range between ″ABC″ and ″ABX″

A*,E=*X Anything beginning with an ″A″, but not ending with an″X″


E=(10,20-29,33) Everything except the following: 10, anything between 20and 29, and 33


When you finishAfter specifying the selections for a rule, you must complete all of the otheroperations in the Tivoli Rule Designer that you have not yet completed, includingSchedule (“Scheduling rules” on page 85), Condition (“Managing rule conditions”on page 92), Actions (“Managing rule actions” on page 96), and Documentation(“Documenting a rule” on page 103). You can complete these operations in anyorder. At a minimum, you must specify an action for the rule.

ProcedureYou can perform this procedure from the Tivoli Rule Designer only.1. Click the Selections tab.

2. Select a different statistic from the Statistic drop-down list if the statisticdomain is enumerated and the desired statistic is not showing.Additional Information: A description of the statistic is displayed under thestatistic name.

3. Type the selections for this statistic in the Selection field.Additional Information: See “Format for Selections” on page 89.

4. Click Add to add the statistic and its associated selection to the CurrentSelections list.

5. Repeat Steps 2–4 of this procedure to enter additional selections.

Note: The instances of the statistic domain considered for rule execution arethose that match all selections. Each additional selection that you enter


has the potential of further reducing the number of instances the rule isconsidering. You cannot enter more than one selection for the samestatistic. If you try to do this, the second entry replaces the existing onein the list.

6. To modify one of the Current Selections, do the following:a. Click an item in the Current Selections list.b. Click Modify to display the statistic and its selection in the Statistic and

Selection fields above the list of current selections.c. Modify the selection in the Selection field.d. Click Update to put the modified selection back into the Current Selections

list.7. To remove one of the Current Selections, do the following:

a. Click an item in the Current Selections list.b. Click Remove to remove the statistic and its selection from the Current

Selections list.

Managing rule conditions

ObjectiveTo define the conditions for a rule to monitor.

Background informationThe rule’s condition is an expression that evaluates to ″True″ or ″False″. A rulealways evaluates to ″True″ if no condition is entered. A rule’s condition can includeany of the following items:

StatisticsValue or set of values that your computer collects. A statistic’s value (orvalues) remains unchanged during the execution of the rule.

User-defined statisticsStatistics that are defined by the user based on the values of Tivolistatistics, constants, and operators. A user-defined statistic’s value (orvalues) remains unchanged during the execution of the rule.

VariablesPlaceholder for a value or set of values that can be changed by the actionsof a rule. Variables can be explicitly set to a value or they can be set to theresult of an expression. Variables provide programming capabilities. Theyenable you to pass information between different rules.

Predefined variablesOne of a group of variables that contains information maintained by theexecuting role, such as status of the last action executed and the number oftimes the rule detected a problem. IBM Tivoli Management Solution forExchange includes several predefined variables that contain informationabout the execution of the rule.

ConstantsNumbers or string literals

OperatorsArithmetic, logical, and precedence operators such as +, =, and OR

FunctionsPerform various operations


The following are examples of a rule condition:v The CPU is more than 85% busy:

CPU_BUSY_PCT > 85

v A computer is not reachable with TCP/IP:IP_REACHABLE = 0

v A service is not running:SERVICE_STATE <> ″RUNNING″

v A disk has less than 15% free space or it has less than 30 megabytes free:(DISK_FREE_PCT< 15) OR (DISK_FREE_MB < 30)

v A process used no CPU time and has a working set of more than 1 millionbytes:(PROCESS_CPU_PCT = 0) AND (PROCESS_WORKING_SET_BYTES > 1000000)

v An event in the Windows NT event log has a subtype of ″ERROR″ and wasgenerated within the last day (86400 seconds):(EVT_SUBTYPE = ″ERROR″) AND (EVT_AGE_SECONDS < 86400)


When you finishAfter specifying the conditions for a rule, you must complete all of the otheroperations in the Tivoli Rule Designer that you have not yet completed, includingSchedule (“Scheduling rules” on page 85), Selections (“Managing rule selections”on page 89), Actions (“Managing rule actions” on page 96), and Documentation(“Documenting a rule” on page 103). You can complete these operations in anyorder. At a minimum, you must specify an action for the rule.

ProcedureYou can perform this procedure from the Tivoli Rule Designer only.


1. Click the Condition tab.

2. To include the value of a statistic in the expression for the condition, do thefollowing:a. If the statistic you want to select is in a domain that is different from the

one in the Domain drop-down list, select a different domain.

Note: Other than the rule’s statistic domain, only statistics from the scalardomains can be selected.

Additional Information: The list of statistics in the Statistic list changes tocontain the statistics for the selected domain.

b. Do one of the following:v Select the name of the desired statistic in the Statistic list.

—OR—v Type the statistic name in the Expression field.

Additional Information: A description of the statistic is displayed below theStatistic list.

c. Click Add Statistic to add the statistic to the rule’s condition, which isdisplayed in the Expression field.

3. Include user-defined statistics, variables, and predefined variables by doing thefollowing:a. Select existing User Defined Statistics, Variables, or Predefined Variables

from the Class list.Additional Information: A list of items appropriate for the selected class isdisplayed in the field below the Class list.

Note: You are not required to reference variables to be used in the rulecondition. You can enter any variable in the rule condition by typingthe variable name in the Expression field.


b. Select the item you want to add from the list of items under the Class list.Additional Information: A description of the item is displayed below theStatistic list.

c. Do one of the following:v Click Add Statistic or Add Variable under the list of user statistics to add

the statistic or variable to the rule condition.—OR—

v Type the statistic or variable name in the Expression field.

Additional Information: The statistic or variable is displayed in the Expressionfield.

4. Define or modify user-defined statistics if desired:

Note: Forming the expression that defines the statistic is similar to forming therule condition. The expression for a statistic can include only statisticnames, arithmetic operators, parentheses, and constants. A user-definedstatistic’s value (or values) remains unchanged during the execution ofthe rule.

a. Select User Defined Statistic in the Class drop-down list.Additional Information: A User Statistics description is displayed under theStatistic field.

b. Select the name of the statistic in the list under the Class list if you aremodifying a previously defined user-defined statistic.

c. Click Define User Statistic to display the User Defined Statistics window.d. Do one of the following:

v Type the name of the user statistic you want to add in the User statisticname field.—OR—

v Select an existing user statistic to modify.e. Select the desired domain in the Domain field if the statistic you want to

add is in a different domain.f. Select the statistic you want to add from the Statistic field.

Additional Information: The name of the statistic and a description of thestatistic is displayed in the field under the Statistic field.

g. Click Add Statistic to display the statistic in the Expression field.h. Do one of the following:

v Add other statistics, arithmetic operators, parentheses, and any neededconstants to the expression to form the expression that defines thestatistic.—OR—

v Type the statistic names, arithmetic operators, parentheses, and constantsinto the Expression field.

i. Do one of the following:v Click Apply to add the user-defined statistic to the User statistic list and

define another user-defined statistic.—OR—

v Click OK to add the user-defined statistic to the User statistic list andreturn to the Condition window.—OR—


v Click Cancel to cancel defining or modifying the user-defined statistic.5. Include operators, functions, or constants in the expression for the condition as

desired:a. Select Operators, Functions, or Constants from the Class list.

Additional Information: A list of available items for the selected class isdisplayed in the field under the Class list, except for constants.

b. Select the desired item from the list under the Class list if you selectedOperators or Functions.Additional Information: The name of the operator or function and adescription of the item is displayed in the field below the Statistic list.

c. Make sure the cursor in the Expression field is in the desired location, anddo one of the following to add an operator to the expression as needed:v Click Add Operator.

—OR—v Click the button containing the operator symbol located below the

Expression field.—OR—

v Type the operator symbol in the Expression field.d. Do one of the following to add a function to the expression as needed:

v Click Add Function.—OR—

v Type the function in the Expression field.e. Type the constant (number or string literal) into the Expression field to add

a constant to the expression as needed.

Note: String constants must be enclosed in double quotes, and arecase-sensitive.

Additional Information: Examples of constants:

90

1. 5

″DISK″

6. Use the following options as needed while writing the expression:v Click Undo to undo the effect of your last action.v Click Redo to redo the last undo action.v Click Clear to clear the expression.v Click Revert to return the expression to its original form.v Click Test to check the validity of the expression.

Managing rule actions

ObjectiveTo specify one or more actions for a rule so you can use the rule to detect andcorrect system and application problems.

Background informationRule actions are divided into the following four categories:


Notification actionsA Tivoli rule communicates with you and with other IBM TivoliManagement Solution for Exchange components by executing a notificationaction. For example, you can write a rule to provide notification of anevent and send an e-mail problem report. The rule action can dropinsignificant events, escalate important events, or respond to definedrelationships of multiple events.

Corrective actionsThe corrective actions are used to correct problems found on yourcomputer. These actions make changes to your computer. For example, arule can be written to remove a large unused file. Also, a rule can correct aproblem found on your computer by executing an operating systemcommand.

Rule control actionsThe rule control actions are used to control the execution of the currentrule and other rules. For example, a rule can detect a problem and enableanother rule for further investigation. Also, a rule can conditionally executeits actions by executing the If action.

Variable management actionsThe variable management actions control variables. Variables addprogramming capabilities to rules.

Table 12 contains a list of the actions for each of the four action categories.

Table 12. Actions for each action category

Actioncategory

Notificationactions

Correctiveactions

Rule Controlactions

Variablemanagementactions

Actions v Export

v Log

v Mail

v Message Event

v Page

v Problem Event

v SNMP Trap

v WindowsEvent

v Copy

v Execute OSCommand

v Execute SQL

v Priority

v Remove

v SNMP Set

v Terminate

v Working Set

v Disable

v Else

v Else If

v Enable

v End

v Execute Rule

v Exit

v If Action

v Modify

v Wait

v Append

v Calculate

v Check Bounds

v Close

v Create

v Decrement

v Delete

v Increment

v Read

v Write

v Zero

Types of actions: Actions are always maintained by action type. The followingaction types can be applied to a rule action:

True True actions execute whenever the rule condition is true.

False False actions execute whenever the rule condition is false.

New New actions execute the first time the rule condition is true, or if the rulecondition is currently true but was false in the previous interval. The useof new actions with different update actions can implement a problemescalation policy that treats problems more seriously after the first time theproblem is found.


UpdateUpdate actions execute if the rule condition is true and was also true in theprevious interval. The use of new actions with different update actions canimplement a problem escalation policy that treats problems more seriouslyafter the first time the problem was found.

Close Close actions execute if the rule condition is false but was true in theprevious interval. Close actions close a problem that once existed but isnow no longer a problem.

ProloguePrologue actions are meaningful only for rules that execute in enumeratedstatistic domains. The prologue actions execute once regardless of the rulecondition before the execution of the rule in the enumerated statisticdomain. A common use for prologue actions is to initialize counters orother variables.

EpilogueEpilogue actions are meaningful only for rules that execute in enumeratedstatistic domains. The epilogue actions execute once regardless of the rulecondition after the execution of the rule in the enumerated statistic domain.A common use for epilogue actions is to output or analyze summaryinformation. For example, an epilogue action can output the number ofprocesses for which the rule condition is true.


When you finishAfter specifying the actions for a rule, you must complete all of the otheroperations in the Tivoli Rule Designer that you have not yet completed, includingSchedule (“Scheduling rules” on page 85), Selections (“Managing rule selections”on page 89), Condition (“Managing rule conditions” on page 92), andDocumentation (“Documenting a rule” on page 103). You can complete theseoperations in any order. After specifying at least one action, you can save the rule.



1. Click the Actions tab in the Tivoli Rule Designer window.

2. To add an action to an empty list of actions or to the end of a list of actions, dothe following:a. Make sure no existing action is selected.b. Select the desired action from the Action list.

Additional Information: See Table 12 on page 97 for a list of actions. Also,notice the description of the selected action in the Actions window next tothe Action list. For detailed information about each action, refer toAppendix D, “Action list” on page 263.

c. Select the action type that you want to apply to the action from the Actiontype drop-down list.

d. Click Add to display the window specific to the selected action.e. Complete the options in the action-specific window to add the new action

to the end of the list of existing actions for the action type.Additional Information: All action-specific windows do not have the samerequirements or options. See the following procedures in this manual foroptions that are applicable to many of the action-windows:v “Setting a single or multiple values across rules in the action-specific

window” on page 101v “Changing computers from the action-specific window” on page 102v “Defining an expression for an action from the action-specific window”

on page 1023. To insert an action in a list of existing actions, do the following:

a. Select the action before which you want to insert the new action from theExisting actions list.

b. Select the desired action in the Action list.c. Select the desired action type for the action in the Action type list.d. Click Insert to display the action-specific window.


e. Complete the action-specific window.f. Click OK to display the new action before the selected action in the Existing

Actions list.4. To to change the type of action, do the following:

a. Select the action you want to change from the Existing actions list.b. Click Change Type to display the Change Action type dialog box.c. Select the new type of action in the Action type list.d. Click OK.

Additional Information: The new action type is displayed next to the action inthe Existing actions list.

5. To modify an action, do the following:a. Select the action from the Existing Actions list.b. Click Modify to display the action-specific window.c. Make the desired changes in the action-specific window.d. Click OK to apply the changes.

Additional Information: The changes are displayed next to the action in theExisting actions list of the Action window.

6. To activate or inactivate an action, do the following:Additional Information: When an action is initially added, it is active as indicatedby the check mark next to the action type.a. To activate an inactive action, do the following:

1) Select the action.2) Click Activate.

Additional Information: The ″X″ changes to a check mark.b. To inactivate an action, do the following:

1) Select the action from the Existing actions list.2) Click Inactivate.

Additional Information: The check mark changes to an ″X″. Inactiveactions are ignored when the rule executes. When you view the rulecode, an inactive action is displayed as a comment. The advantage ofinactivating an action over removing it is that it is easier to re-activate itat a later time. Also, you might want to build some capabilities into arule (such as deleting files or processes) that you do not want toimmediately execute.

7. To remove an action, do the following:a. Select the action.b. Click Remove.

8. To undo a removed action and return a previously removed action to the list ofexisting actions, click Undo Remove.

9. To change the position of an action (within its type) in the Existing Actions list,do the following:

Note: You cannot move an action outside of its type when changing the orderof actions because actions are always maintained by action type.

a. Select the action to move.b. Click Move Up to move the action up in the list.c. Click Move Down to move the action down in the list.


Setting a single or multiple values across rules in the action-specific window:Select or clear the Set to global scalar for all rules check box.

Additional Information: If you check Set to global scalar for all rules, the variablehas a single value across all rules executing in the same rule process. If notchecked, the behavior depends on the rule statistic domain. For enumerateddomains, the variable has a value for each instance of the statistic domain in whichthe rule executes. For scalar domains, the variable has a single value.

Formatting symbols from the action-specific window:

1. Do one of the following:v If you need to insert a symbol and the symbol buttons are present and

active, click Insert Symbol.v If you need to edit a previously inserted symbol, do the following:

a. Select a symbol you want to edit.b. Click Edit Symbol to display the Symbol Formatting window.

2. If the statistic for which you want to substitute a symbol is in a domain that isdifferent from the one in the Domain drop-down list, select a different domain.

Note: Other than the rule statistic domain, only statistics from scalar domainscan be selected.

Additional Information: The list of statistics in the Statistic field changes tocontain the statistics for the selected domain.

3. Do one of the following:v Select the name of the statistic from the Statistic list.

Additional Information: A description of the statistic is displayed below theStatistic list, and the statistic name is moved to the Symbol to format fieldin the lower portion of the window.—OR—

v Type the statistic name in the Symbol to format field.4. Select Predefined Symbols, Predefined Variables, User Defined Statistics, or

Variables from the Class list.Additional Information: A list of items appropriate for the selected class isdisplayed under the Class drop-down list.

Note: Variables do not have to be referenced in the rule to enable symbolsubstitution.

5. Do one of the following:v Select the desired item from the list under the Class list.

—OR—v Type the name of the statistic, symbol, or variable into the Symbol to format

field.

Additional Information: The name of the item and a description of the selecteditem is displayed below the Statistic list, and the item name is moved to theSymbol to format field in the lower portion of the window.

6. Select the desired format option from the Format list:v Natural (string or number)

v Date

v Time

v Date and Time


7. Select the desired option for explicit length, explicit precision, zero fill, anddigit separators from the Options list:v Explicit Length specifies the number of characters to allocate for the value of

the symbol. If the length of the symbol is more than this number, it istruncated. If it is less than this number, space is added to equal ExplicitLength (unless Zero Fill is also selected).

v Explicit Precision is valid for numeric values when the Format is Natural.Explicit Precision is the number of digits displayed to the right of thedecimal point. If this value is zero, the decimal point is not displayed. Forexample, a value of 3.1 with an explicit precision of two is displayed as″3.10″.

v Zero Fill pertains to naturally formatted numbers only if the Explicit Lengthoption is selected. If specified, the Zero Fill number is padded with zeroesrather than spaces. For example, a value of twenty that is right justified andzero filled to an explicit length of three and a precision of zero is displayedas ″020″.

v Insert Digit Separators pertains to naturally formatted numbers only. Ifspecified, the number is displayed with a digit separator (usually a comma)every three digits. For example, a value of one million is displayed as″1,000,000″.

8. Select one of the following desired justification options in the Justify list if theExplicit Length formatting option is selected:v Left

v Center

v Right

Note: The justification option is available only when the Explicit Length optionis selected.

9. Click OK when you are finished selecting options.

Changing computers from the action-specific window:

1. Click Change Computer if the Change Computer button is active and youneed to change the computer that is set to run the rule.Additional Information: The Computer Selection window is displayed.

2. Click Local Computer or Remote Computer in the Computer Selectionwindow.

Note: Symbol substitution, which allows you to substitute the current value ofa symbol (such as a statistic or variable) in text, is supported for theRemote Computer selection.

3. Type the name of the desired remote computer in the Remote Computer fieldif you selected Remote Computer.

4. Click Insert Symbol or Edit Symbol to go to the Symbol Formatting window.5. Click OK when finished.

Defining an expression for an action from the action-specific window:

1. Click Define Expression if the Define Expression button is active and you needto write an expression.


Note: The method to define an expression for an action is identical to definingan expression for a rule condition. In the Tivoli Rule Designer, theDefine an Expression window for an action is almost identical to theCondition window.

2. Use the following steps of the procedure, Managing rule conditions:v To include statistics, Step 2 on page 94v To include user-defined statistics, variables, or predefined variables, Step 3

on page 94v To define or modify user-defined statistics, Step 4 on page 95

Documenting a rule

ObjectiveTo provide information about a rule for future reference.

Background informationA rule’s documentation consists of the description and the author. If you typed adescription when you created the rule (New Rule Wizard — Step 1), thatinformation is displayed in the Description field of the Documentation window.The Class field indicates the domain name.


When you finishAfter documenting a rule, you must complete all of the other operations in theTivoli Rule Designer that you have not yet completed, including Actions(“Managing rule actions” on page 96), Schedule (“Scheduling rules” on page 85),Selections (“Managing rule selections” on page 89), and Condition (“Managingrule conditions” on page 92). You can complete these operations in any order. At aminimum, you must specify an action for the rule.



1. Click the Documentation tab.

2. Type or revise information about what the rule is checking, what actions it isset to take, and any dependencies with other rules in the Description field.

3. Type the name of the person, group, or organization that wrote the rule in theAuthor field.

Editing rules graphically using the Tivoli Rule Designer

ObjectiveTo modify rules by changing the condition, action, schedule, or selection.




ProcedureYou can perform this procedure from the Tivoli EnterpriseManager—Development View window only.1. Do one of the following to select the rule you want to modify and open the

Tivoli Rule Designer:v Use the Tivoli Enterprise Manager main toolbar:

a. Select the name of the rule you want to modify in the right pane of theTivoli Enterprise Manager window.

b. Select Run from the toolbar to display the Run drop-down menu.c. Select Tivoli Rule Designer to display the Tivoli Rule Designer.


—OR—v Double click on the name of the rule you want to edit in the right pane of

the Tivoli Enterprise Manager window.2. Select any of the five tabs in the Tivoli Rule Designer console to make desired

changes in the information in these windows. See the following procedures inthis manual for each tab:v “Scheduling rules” on page 85v “Managing rule selections” on page 89v “Managing rule conditions” on page 92v “Managing rule actions” on page 96v “Documenting a rule” on page 103

3. Do the following to save the modifications:a. Select File from the toolbar to display the File drop-down menu.b. Do one of the following:

v Select Save Rule from the drop-down menu to save the rule.—OR—

v Select Save Rule As from the drop-down menu to save the rule with adifferent name.

4. Do the following to exit the Tivoli Rule Designer:a. Select File from the toolbar to display the File drop-down menu.b. Select Close from the File drop-down menu to close the Tivoli Rule

Designer.

Creating rules manually using the Tivoli Rule Editor

ObjectiveTo use internal rule language to write a new rule to satisfy unique requirements.

Background informationIBM Tivoli Management Solution for Exchange provides defined rules to whichyou can add new rules that are relevant to your organization. Rules are written inrule code statements and executed by the Tivoli Rule Engine. Rule code defines therule name as well as the conditions, actions, schedule, and selections. Rule code iswritten in ASCII.




This procedure describes how to use the Tivoli Rule Editor to create new rules.

Before you beginYou must know how to use rule syntax to write new rules manually. See the onlineRule Writing Reference for information about how to use rule syntax, orAppendix C, “Rules syntax” on page 227.



ProcedureYou can perform this procedure from the Tivoli Enterprise Manager windowDevelopment View or Management View.1. Start the New Rule Wizard by doing one of the following in the Development

View or Management View:v Use the New Rule Wizard in the Development View or Management View:

a. Select File from the toolbar to display the File drop-down menu.b. Select New Rule from the drop-down menu to display the New Rule

Wizard - Step 1 dialog box.

—OR—v Use the Tivoli Rule Designer in the Development View or Management

View:a. Select Run from the toolbar to display the Run drop-down menu.b. Select Tivoli Rule Designer from the Run drop-down menu to display

the Tivoli Rule Designer.Additional Information: If you are in Development View, an existing ruleis displayed in the Tivoli Rule Designer if your source directory has rulesin it. The New Rule Wizard is displayed in Development View if thereare no rules in the source directory. The New Rule Wizard is alwaysdisplayed in Management View.

c. Do one of the following if the Tivoli Rule Designer displays an existingrule:– Use the menus:

1) Select File from the Tivoli Rule Designer toolbar to display the Filedrop-down menu.

2) Select New Rule from the File drop-down menu to display theNew Rule Wizard - Step 1 dialog box.

—OR—– Click the New Rule icon to display the New Rule Wizard - Step 1

dialog box.

—OR—v Double-click on white space in the right pane of the Tivoli Enterprise

Manager—Development View window .2. Do the following to name and describe the rule:

a. Type the name of the new rule in the text box for the rule name.Additional Information: This name must be unique within its directory. Thename must begin with a character of the alphabet.

b. Type a rule description.Additional Information: The rule description is optional and does not affectthe execution of the rule.

3. Select the Manually Edit the Rule check box.4. To cancel the creation of the new rule, click Cancel.


5. Click Finish to display the Tivoli Rule Editor window for writing or editingthe rule.

6. Type or edit the rule according to Appendix C, “Rules syntax” on page 227.7. Do the following to save the rule while writing or editing the rule and when

finished writing or editing the rule:a. Select File from the toolbar to display the File drop-down menu.b. Click Save Rule on the File drop-down menu to save the rule.

8. Do the following to verify the rule syntax:a. Select Run from the toolbar to display the Run drop-down menu.b. Click Verify on the Run drop-down menu.

Editing rules manually using the Tivoli Rule Editor

ObjectiveTo use internal rule language to edit an existing rule to satisfy uniquerequirements.

Background informationIBM Tivoli Management Solution for Exchange provides defined rules to whichyou can add new rules that are relevant to your organization. Rules are written inrule code statements and executed by the Tivoli Rule Engine. Rule code defines therule name as well as the conditions, actions, schedule, and selections. Rule code iswritten in ASCII.





This procedure describes how to use the Tivoli Rule Editor to edit new rules.

Before you beginYou must know how to use rule syntax to write new rules manually. See the onlineRule Writing Reference, or Appendix C, “Rules syntax” on page 227 forinformation about how to use rule syntax.


ProcedureYou can perform this procedure from the Tivoli EnterpriseManager—Development View window only.1. Do one of the following to select the rule to edit, and to open the Tivoli Rule

Designer or Tivoli Rule Editor:v Use the Tivoli Rule Designer:

a. Select the name of the rule you want to modify in the right pane of theTivoli Enterprise Manager window.

b. Select Run from the toolbar menu to display the Run drop-down menu.c. Select Tivoli Rule Designer from the Run drop-down menu to display

the Tivoli Rule Designer.

—OR—v Double-click on the name of the rule you want to edit in the right pane of

the Tivoli Enterprise Manager window Development View.Additional Information: If the rule was created manually, it is displayed inASCII in the Tivoli Rule Editor window. If the rule was created with theTivoli Rule Designer, it is displayed in the Tivoli Rule Designer.

2. If the rule is displayed in the Tivoli Rule Designer, do the following to convertthe rule to ASCII:a. Select Rule from the toolbar to display the Rule drop-down menu.b. Select Convert to ASCII from the drop-down menu to display the Tivoli

Rule Editor.Additional Information: A warning is displayed stating that this action willconvert the rule to internal ASCII and that if you save the rule later, youcannot modify it graphically with the Tivoli Rule Designer.

3. Click No to keep the Tivoli Rule Designer in view if you do not want to editthe rule manually.

4. To edit the rule manually, do the following:a. Click Yes to display the Tivoli Rule Editor with the rule displayed in

ASCII.b. Edit the rule according to the rule syntax in Appendix C, “Rules syntax” on

page 227.c. Do one of the following:

v Save the rule in the internal language by doing the following:1) Select File from the toolbar to display the File drop-down menu.2) Do one of the following:

– Select Save from the File drop-down menu to save the rule in theinternal language.


—OR—– Select Save As to save the rule in the internal language with a

different name.

—OR—v Close the window without saving to discard the changes.

d. Do the following to verify the rule syntax:1) Select Run from the toolbar to display the Run drop-down menu.2) Select Verify from the Run drop-down menu.


Chapter 8. Working with the Tivoli Statistics Builder

IBM Tivoli Management Solution for Exchange can collect a large number ofstatistics that can be evaluated to determine the health of a software or hardwarecomponent. The Tivoli Statistics Builder is used to define Tivoli statistics from theWindows NT® Performance Monitor database, an ASCII file, an ODBC database, orSNMP variables. A statistic is a named value that can be used in Tivoli rules.Statistics can contain numeric values or alphanumeric character strings. The TivoliStatistics Builder enables you to define how certain statistics obtain their values.When a Tivoli rule executes, the value of each statistic referenced is obtainedaccording to this definition.

The set of default statistics is fixed. However, additional statistics from theperformance monitor, databases, or external files can be defined and added asneeded. For example, if a computer is running a third-party product that postedstatistics to the performance monitor database, IBM Tivoli Management Solutionfor Exchange can retrieve and evaluate those statistics when they are added to theTivoli statistics database.

This chapter provides an explanation of the processes and concepts of the TivoliStatistics Builder and step-by-step instructions for related procedures. Table 13 onpage 111 provides an overview of the topics covered in this chapter.

Table 13. Guidelines for Managing Statistics

Goal Refer To

1. Understanding the different statisticdomains in the Tivoli Statistics Builderand how to use them

“Understanding statistic domains” on page112

2. Working with statistic domains tocontrol how process rule statistics obtaintheir values

“Working with statistic domains” on page113

3. Importing or exporting statistic domainsusing external definition (.edn) files sothat multiple sites can use the samestatistic domains.

“Importing and exporting statistic domains”on page 115

4. Copying statistic domains so you canuse them in at least one additionalcomputer on the network.

“Copying statistic domains” on page 115

5. Adding statistics to, modifying statisticswithin, and removing statistics from aPerformance Monitor Statistic Domainso you can define how the statistics inthe domain obtain their values.

“Working with performance monitor statisticdomains” on page 116

6. Adding statistics to, modifying statisticswithin, and removing statistics from anASCII file statistic domain so you candefine how the statistics in the domainobtain their values.

“Working with ASCII file statistic domains”on page 118

111

Table 13. Guidelines for Managing Statistics (continued)

Goal Refer To

7. Adding statistics to, modifying statisticswithin, and removing statistics from anODBC Database statistic domain so youcan define how the statistics in thedomain obtain their values.

“Working with ODBC database statisticdomains” on page 121

8. Adding statistics to, modifying statisticswithin, and removing statistics from anSNMP statistic domain so you candefine how the statistics in the domainobtain their values.

“Working with SNMP statistic domains” onpage 124

9. Adding statistics to, modifying statisticswithin, or removing statistics from aCOM statistic domain so you can definehow the statistics in the domain obtaintheir values.

“Working with COM statistic domains” onpage 125

Understanding statistic domainsA statistic domain is a group of statistics collected from the same source.v The Performance Monitor tab of the Tivoli Statistics Builder window displays

the list of statistic domains currently defined from the Windows NTPerformance Monitor database. IBM Tivoli Management Solution for Exchange isshipped with statistic domains defined for many of the Windows NTPerformance monitor objects. If you have layered or third-party software thatcreates additional Windows NT Performance monitor objects, you can use theTivoli Statistics Builder window to define new statistic domains for theseobjects.

v The ASCII File tab on the Tivoli Statistics Builder window displays the list ofstatistic domains currently defined from ASCII files. The Tivoli Statistics Buildercan define additional statistic domains from any ASCII file in tabular format.

v The ODBC Database tab displays the list of statistic domains currently definedfrom ODBC databases. You can define additional statistic domains from anyODBC database from the Tivoli Statistics Builder window.

v The SNMP tab displays the list of statistic domains currently defined fromSNMP variables.

v The COM tab displays the list of statistic domains currently defined from COMobjects. You can define additional statistic domains from any COM variable fromthe Tivoli Statistic Builder window.

The left side of the Tivoli Statistics Builder main window shows the view of thenetwork. Click on any computer to define or view Tivoli statistics for thatcomputer. The right side of the Tivoli Statistics Builder main window has fivetabs, one for each of the types of statistics domains.

The following information displays for each statistic domain:

Name Uniquely identifies the statistic domain.

DefinitionThis definition is either original or user. If the statistics domain definitionis original, it was shipped with IBM Tivoli Management Solution forExchange. A user definition is either a new statistic domain added by the


user or a statistic domain that has been modified. An original definitioncannot be removed. A user definition can either be removed or restored toits original definition, depending on whether or not there is an originaldefinition.

Type This is normally scalar or enumerated. However, for statistic domainsdefined from the Windows NT® Performance Monitor database, this canalso contain “Does not exist” or “Mismatch.” “Does not exist” means thatthe statistic domain does not exist as an object in the Windows NTPerformance Monitor database, and therefore these statistics cannot becollected. “Mismatch” means that the statistic domain type (Scalar orEnumerated) differs from the object in the Windows NT® PerformanceMonitor database. Use the “Fix mismatch” operation to change the statisticdomain type to match the object in the Windows NT Performance Monitordatabase.

DescriptionThe statistic domain description.

Working with statistic domains

ObjectiveTo work with statistic domains so you can control how process rule statisticsobtain their values.

Background informationThis procedure provides step-by-step instructions to perform the following tasks:

Modify a statistic domainModifies an existing statistic domain.

Remove a statistic domainRemoves a statistic domain from the Tivoli Statistics Builder.

Restore a statistic domain to the original definitionRestores a statistic domain to its original definition if it had an originaldefinition, and was then modified by the user.

Automatically fix a statistic domain mismatchA statistic domain mismatch occurs when a statistic domain type (Scalar orEnumerated) differs from the object in the Windows NT PerformanceMonitor database. A mismatch can occur only in Performance Monitorstatistic domains.



Procedure1. Open the Tivoli Enterprise Manager by doing the following:

a. Click Start to display the Start menu.b. Click Programs from the Start menu to display the Programs menu.c. Click Tivoli Enterprise Management Solutions from the Programs menu to

display the Tivoli Enterprise Management Solutions menu.d. Click Tivoli Enterprise Manager from the Tivoli Enterprise Management

Solutions menu to open Tivoli Enterprise Manager.

Chapter 8. Working with the Tivoli Statistics Builder 113

2. Open the Tivoli Statistics Builder by doing one of the following:v Click the Tivoli Statistics Builder icon.

—OR—v Use the menu option by doing the following:

a. Click Manage to display the Manage drop-down menu.b. Click Statistics from the Manage drop-down menu.

3. Do the following in any order to work with statistic domains:v Modify a statistic domain by doing the following:

a. Click the tab for the type of statistic domain you want to work with fromthe right pane of the Tivoli Statistics Builder.

b. Select the statistic domain you want to work with from the list.c. Click Domain from the Tivoli Statistics Builder to display the Domain

drop-down menu.d. Click Modify from the Domain drop-down menu to display the General

Information tab of the Statistic Domain dialog box.e. Make the modifications to the statistic domain in the General

Information tab of the Statistic Domain dialog box.

Note: For details on statistic domain modifications, see the following:– “Working with performance monitor statistic domains” on page

116– “Working with ASCII file statistic domains” on page 118– “Working with ODBC database statistic domains” on page 121– “Working with SNMP statistic domains” on page 124– “Working with COM statistic domains” on page 125

f. Click OK to save the changes.v Remove a statistic domain by doing the following:

a. Click Domain from the Tivoli Statistics Builder to display the Domaindrop-down menu.

b. Click Remove from the Domain drop-down menu to remove the selectedstatistic domain.

c. Click OK to close the Remove message box.v Restore a statistic domain to the original definition by doing the

following:


b. Click Restore Original from the Domain drop-down menu.c. Click OK to close the Statistic domain restored to the original definition

message box.v Automatically fix a statistic domain mismatch by doing the following:


b. Click Fix Mismatch from the Domain drop-down menu.c. Click OK to close the Mismatch fixed message box.


Importing and exporting statistic domains

ObjectiveTo import or export a statistic domain using .edn (external definition) files somultiple sites can use the same statistic domains.

Background informationYou can import a statistic domain on your hard drive into the Tivoli StatisticsBuilder or export a statistic domain to your hard drive from the Tivoli StatisticsBuilder. You might want to use the import feature to import the statistic domainfrom another site. For instance, you can also export a statistic domain to anexternal definition file (.edf) on your hard drive and email the external definitionfile to another site. When an IBM Tivoli Management Solution for Exchange user atthe other site receives the email containing the external definition file (.edf), theuser must then import the file to the Tivoli Statistics Builder before using it tocreate a statistic domain.

You can use the import/export feature only with ASCII File, ODBC Database, andSNMP statistic domains.



Procedure1. Click the tab for the statistic domain that you want to import or export in the

right pane of the Tivoli Statistics Builder window.2. Click Domain from the Tivoli Statistics Builder window to display the

Domain drop-down menu.3. Do one of the following from the Domain drop-down menu:

v Select Import to import an .edf file:a. Navigate to the directory where the file you want to import exists.b. Select the .edf file you want to import.c. Click Open to import the file into the Tivoli Statistics Builder and add the

new statistic domain.

—OR—v Select Export to export an .edf:

a. Navigate to the directory where you want to save the .edf.b. Click Save to create and save the .edf.

Copying statistic domains

ObjectiveTo copy a statistic domain so you can use the statistic domain in at least oneadditional computer on the network.





Procedure1. Click the tab for the statistic domain that you want to copy in the right pane of

the Tivoli Statistics Builder window.2. Click Domain from the Tivoli Statistics Builder to display the Domain

drop-down menu.3. Select Copy from the Domain drop-down menu to display the Copy to dialog

box.

4. Select one of the following options:v Copy to the entire enterprise

Go to Step 5.—OR—

v Copy to each computer in this domain

a. Click the down arrow on the text box to display the available domains.b. Select a domain from the list of available domains.c. Go to Step 5.

—OR—v Copy to this computer

a. Click the down arrow on the text box to display the available computers.b. Select a computer from the list of available computers.c. Go to Step 5.

5. Click OK to copy the statistic domain to the enterprise, domain, or computeryou selected.

Working with performance monitor statistic domains

ObjectiveTo add statistics to, modify statistics within, or remove statistics from aPerformance Monitor Statistic Domain so you can define how the statistics in thedomain obtain their values.


Background informationA statistic domain defined from the Windows NT® Performance Monitor databasecorresponds to a Windows NT object. Each counter in the Windows NT object canbe defined as a Tivoli statistic. For enumerated domains, the instance name canalso be defined as a Tivoli statistic. When these statistics are used in Tivoli rules,IBM Tivoli Management Solution for Exchange obtains a value for them byretrieving the value for the associated counter (or instance name) in the WindowsNT object.



Procedure1. Open the Tivoli Enterprise Manager by doing the following:

a. Click Start to display the Start menu.b. Click Programs from the Start menu to display the Programs menu.c. Click Tivoli Enterprise Management Solutions from the Programs menu to

display the Tivoli Enterprise Management Solutions menu.d. Click Tivoli Enterprise Manager from the Tivoli Enterprise Management

Solutions menu to open Tivoli Enterprise Manager.2. Open the Tivoli Statistics Builder by doing one of the following:

v Click the Tivoli Statistics Builder icon.—OR—

v Use the menu option by doing the following:a. Click Manage to display the Manage drop-down menu.b. Click Statistics from the Manage drop-down menu.

3. Select Performance Monitor to display the Performance Monitor tab.4. Do the following in any order to work with performance monitor statistics:

v Add a statistic in a performance monitor statistic domain by doing thefollowing:

a. Click the computer icon for the computer to which you want to add thestatistics domain from the Network Display field.

b. Click Domain to display the Domain drop-down menu.c. Click Add from the Domain drop-down menu to display theStatistic

Domain from the Windows NT Performance Monitor dialog box.d. Click General Information to display the General Information tab.e. Click the down arrow on the Statistic domain name: text box to display

the Statistic domain name: list.f. Select a statistic domain from the Statistic domain name: list.

Additional Information: The statistic domain type (enumerated or scalar)and the number of Windows NT counters that are not currently associatedwith Tivoli statistics are displayed.

g. Optional: Type a description of the statistic domain in the Description tab.h. Do one of the following:

– Add a statistic for each unused Windows NT counter, generating theTivoli statistic name and statistic description.1) Click Add All.


2) Go to Step 4i.

—OR—– Add statistics individually by doing the following:

1) Click Statistics to display the Statistics tab.2) Click the Windows NT Counter: down arrow to display the

Windows NT Counter: list.3) Select a Windows NT Counter from the drop-down list.4) Optional: Change the statistic name, the statistics description, or the

context status.i. Click OK to complete the procedure and close the dialog box.

v Modify a statistic in the performance monitor statistic domain by doingthe following:

a. Right-click the statistic domain that includes the statistic you want tomodify from the right pane of the Tivoli Statistics Builder window todisplay a drop-down menu.

b. Select Modify from the drop-down menu to display theStatistic Domainfrom the Windows NT Performance Monitor dialog box.Additional Information: When modifying a statistic domain, you cannotmodify the statistic domain name.

c. Click Statistics to display the Statistics tab.d. Select the statistic you want to modify from the Current statistics list.e. Click Modify.f. Make changes in either of the following text boxes:

– Statistic name:

– Statistic description:

g. Click OK to commit the changes.v Remove a statistic in the performance monitor statistic domain by doing

the following:

a. Select a statistic domain from the right pane of the Tivoli StatisticsBuilder window.

b. Click Domain from the Tivoli Statistics Builder toolbar to display theDomain drop-down menu.

c. Select Modify from the drop-down menu to display the Statistic Domainfrom the Windows NT Performance Monitor dialog box.

d. Click Statistics tab to display the Statistics text box.e. Select the statistic you want to remove from the Current Statistics list.f. Click Remove to remove the statistic.g. Click OK to commit the changes.

Working with ASCII file statistic domains

ObjectiveTo add statistics to, modify statistics within, or remove statistics from an ASCII filestatistic domain so you can define how the statistics in the domain obtain theirvalues.

Background informationDefine statistics from an ASCII file to enable IBM Tivoli Management Solution forExchange to convert the data from utilities or other applications into Tivoli


statistics. In some cases, IBM Tivoli Management Solution for Exchange can beinstructed to execute an operating system command that creates this file. In othercases, the file already exists. The ASCII file must be in tabular form, where thecolumns of the table are delimited by white space (spaces or tabs) or a defineddelimiter character (such as a comma or semi-colon). Each column corresponds to aTivoli statistic, and each record corresponds to an instance of an enumeratedstatistic domain. When a Tivoli rule references these statistics, it executes for eachrecord in the file. An ASCII file with one record can be used to define a scalarstatistic domain.



Procedure1. Open the Tivoli Statistics Builder.2. Select ASCII File to display the The ASCII File tab.3. Do the following in any order to work with ASCII File statistic domains:

v Add an ASCII File statistic domain by doing the following:


b. Click Domain from the Tivoli Statistics Builder window to display theDomain drop-down menu.

c. Select Add from the Domain drop-down menu to display the StatisticDomain from an ASCII File dialog box.

d. Click General Information to display the General Information tab.e. Type the name that identifies the statistic domain.

Note: The name must be unique across all Tivoli statistic domains.f. Optional: Type an operating system command in the OS Command: text

box to specify any operating system command that IBM TivoliManagement Solution for Exchange executes before reading the specifiedfile.

g. Specify the path name by doing one of the following:– Type the full path name of the ASCII file in the Data file: text box.

—OR—– Click Browse to find the file.

h. Click the down arrow next to the Delimiter: text box to display the list ofdelimiters.

i. Select a delimiter option.Additional Information: The list includes delimiters you can use to separatethe columns in the specified data file. WHITESPACE refers to any numberof spaces or tabs. You can type the delimiters in the text box instead ofselecting them from the list. If you specify a comma as a delimiter, youmust enclose it in quotes. See the following examples:– “,”– “,”,#

j. Choose one of the following processing options:– Read entire file at each collection


—OR—– Read from end of file after the first collection

—OR—– Read from end of file for every collection

k. Select Skip options.Additional Information: You can select multiple skip options. If you selectSkip Pattern, Skip to Pattern, or Skip from Pattern, you must enter astring in the text box indicated next to the skip option.

l. Optional: Click the Description tab to enter a description in the descriptiontext box.

m. Click the Statistics tab to display the Statistics dialog box.n. Do the following in the Statistics dialog box to add a statistics.

1) Type a name in the Statistic name: text box.2) Click the down arrow next to Data type: text box to display the list of

data type options.3) Select the data type.

Additional Information: If you select String for the data type, you musttype in a string length in the Length: text box or select a length fromthe list.

4) Optional: Type a description for the statistic in the Description tab.5) Select one of the following context options from the Context options:

field:– Context statistic defined in statistic list

Note: Check the Context statistic box next to the Statistic name:text box if the statistic uniquely identifies a record in the file.

—OR—– Generate a context statistic

—OR—– Scalar domain

Additional Information: The context statistic is the statistic that uniquelyidentifies the instance of an enumerated statistic domain. Forexample, process ID is the context statistic for the process statisticdomain because process ID is unique across all processes on yourcomputer.

o. Click Add to commit the changes and add the statistic.v Modify a statistic in the ASCII File Statistic Domain by doing the

following:


b. Click Modifyfrom the drop-down menu to display the Statistic Domainfrom the ASCII File dialog box.

c. Click Statistics to display the Statistics tab.d. Select a statistic from the Current statistics: list.e. Make changes in any of the following text boxes:

– Statistic name


– Data type

– Length

– Statistic description

f. Click OK to commit the changes.v Remove a statistic in the ASCII file statistic domain by doing the

following:



c. Select Modify from the drop-down menu to display the Statistic Domainfrom the ASCII File dialog box.

d. Click Statistics to display the Statistics tab.e. Select the statistic you want to remove from the Current statistics list.f. Click Remove to remove the statistic.g. Click OK to commit the changes.h. Click OK to commit the changes and close the Statistic Domain from the

Windows NT Performance Monitor dialog box.

Working with ODBC database statistic domains

ObjectiveTo add statistics to, modify statistics within, or remove statistics from an ODBCDatabase statistic domain so you can define how the statistics in the domain obtaintheir values.

Background informationDefine statistics from the ODBC database to enable IBM Tivoli ManagementSolution for Exchange to convert the data retrieved from an ODBC database intoTivoli statistics. Each column retrieved from the database corresponds to a Tivolistatistic, and each row retrieved from the database corresponds to an instance of anenumerated statistic domain. When a Tivoli rule references these statistics, itexecutes for each row retrieved from the database.



Procedure1. Open the Tivoli Statistics Builder from the Tivoli Enterprise Manager.2. Select ODBC Database to display the ODBC Database tab.3. Do the following in any order to work with ODBC Database statistic domains:

v Add an ODBC Database statistic domain by doing the following:

a. Click the computer icon for the computer that contains the statisticsdomain that you want to work with from the Network Display field.


c. Select Add from the drop-down menu to display the Statistic Domainfrom an ODBC Database dialog box.

d. Do the following from the General Information tab:


1) Type the name in the Statistic domain name text box that identifiesthe statistic domain.

Note: The name must be unique across all of the Tivoli statisticdomains.

2) Type a data source name to access the database in the Data source(DSN) text box.

3) Type the statement to query the database in the Select statement textbox.

4) Optional: Type the computer name that stores the database in theComputer text box.Additional Information: A blank entry refers to the local computer. Thiscorresponds to the ODBC HOST attribute.

5) Optional: Type the ODBC attribute/value pairs that are required toproperly access and process the database in the Connections options:text box.

6) Optional: Type the user identification string that you need to log intothe database in the User ID text box.Additional Information: This corresponds to the ODBC UID attribute. Ifblank, the value from the registry entry for the database is used if oneexists.

7) Optional: Type the password associated with the user ID used to loginto the database in the Password: field.Additional Information: This corresponds to the ODBC PWD attribute.If you leave this text box blank, the value from the registry entry forthe database, if one exists, is used.

8) Click the radio button that corresponds to one of the followingDatabase processing options:

– Read entire database at each collection

Each time a Tivoli rule that references any of the statistics in thisstatistic domain executes, the query to the database specified in theSelect statement is issued and all returned rows are processed.—OR—

– Read new rows defined by this date/time column

The first time a Tivoli rule that references any of the statistics inthis domain executes, the query to the database specified in theSelect statement is issued and all returned rows are processed.During subsequent executions of the rule, only newly added rowsin the database are processed. You must specify a date/timecolumn in the database that contains the date and time the rowwas added to the database.

e. Optional: Type a description in the Description tab.f. Click Statistics to display the Statistics tab.g. Do the following in the Statistics tab:

1) Type a name in the Statistic name: text box.2) Click the down arrow next to Data type: text box to display the list of

data type options.3) Select the data type.4) Optional: Type a description for the statistic the Description text box.


5) Select one of the following context options from the Context options:field:– Context statistic defined in statistic list

Additional Information: Check the Context statistic box next to theStatistic name: text box if the statistic uniquely identifies a recordin the file.—OR—

– Generate a context statistic

Additional Information: The context statistic is the statistic that uniquelyidentifies the instance of an enumerated statistic domain. Forexample, process ID is the context statistic for the process statisticdomain because process ID is unique across all processes on yourcomputer.

h. Click Add to commit the changes and add the statistic.v Modify a statistic in the ODBC data source statistic domain by doing the

following:

a. Right-click the statistic domain that includes the statistic you want tomodify from the right pane of the Tivoli Statistics Builder to display adrop-down menu.

b. Click Modifyfrom the drop-down menu to display the Statistic Domainfrom an ODBC Database dialog box.

c. Click Statistics to display the Statistics tab.d. Select a statistic from the Current statistics list.e. Make changes in any of the following text boxes:

– Statistic name

– Data type


– Context options

f. Optional: Move the selected statistic up or down in the list of Currentstatistics by doing one of the following:– Click Move Up to move the selected statistics up.

—OR—– Click Move Down to move the selected statistics down.

g. Click OK to commit the changes.v Remove a statistic in the ODBC data source statistic domain by doing the

following:



c. Select Modify from the drop-down menu to display the Statistic Domainfrom an ODBC Data Source dialog box.

d. Click Statistics to display the Statistics tab.e. Select the statistic you want to remove from the Current statistics list.f. Click Remove to remove the statistic.g. Click OK to commit the changes.


Working with SNMP statistic domains

ObjectiveTo add statistics to, modify statistics within, or remove statistics from an SNMPstatistic domain so you can define how the statistics in the domain obtain theirvalues.

Background informationDefine statistics from SNMP variables to enable IBM Tivoli Management Solutionfor Exchange to convert the data in the SNMP variables into Tivoli statistics. Eachdefined SNMP variable corresponds to a Tivoli statistic. This is the first of twosteps required to monitor SNMP variables. In this step, you associate SNMPvariables with Tivoli statistics, independent of the IP address of the SNMP device.The second step is the creation of a rule that uses these statistics with the TivoliRule Designer. You specify the IP addresses of the SNMP devices you want tomonitor in the rule’s selections. The selection statistic is the name of the statisticdomain followed by “_IP_NAME.” For example, the selection statistic for a statisticdomain named “CISCO” is “CISCO_IP_NAME.”



Procedure1. Open the Tivoli Statistics Builder from the Tivoli Enterprise Manager.2. Select SNMP to display the SNMP tab.3. Do the following in any order to work with SNMP statistics:

v Add a statistic to an SNMP statistic domain by doing the following:



c. Select Add from the drop-down menu to display the Statistic Domainfrom SNMP dialog box.

d. Type a name for the statistic in the General Information tab.

Note: The name must be unique across all of the Tivoli statistic domains.e. Optional: Type a description in the Description tab.f. Click Statistics to display the Statistics tab.g. Do the following in the Statistics tab:

1) Type a name in the Statistic name: text box.2) Type the object identifier of the SNMP variable in the OID: text box.3) Type a community name in the Community: text box.4) Click the down arrow next to the Data type: text box to display the

list of data type options.5) Select the data type.6) Type the timeout value in milliseconds used to retrieve the SNMP

variable in the Timeout (milliseconds): text box.7) Optional: Type a description for the statistic the Statistic description:

text box.


h. Click Add to commit the changes and add the statistic.v Modify a statistic in an SNMP Statistic Domain by doing the following:


b. Click Modify from the drop-down menu to display the Statistic Domainfrom SNMP dialog box.

c. Click Statistics to display the Statistics tab.d. Select a statistic from the Current statistics: list.e. Make changes in any of the following text boxes:

– Statistic name:

– OID:

– Community:

– Data type:

– Timeout (milliseconds):

– Statistic description:

f. Click OK to commit the changes.v Remove a statistic in an SNMP Statistic Domain:



c. Select Modify from the drop-down menu to display the Statistic Domainfrom SNMP: dialog box.

d. Click Statistics to display the Statistics tab.e. Select the statistic you want to remove from the Current statistics: list.f. Click Remove to remove the statistic.g. Click OK to commit the changes.

Working with COM statistic domains

ObjectiveTo add statistics to, modify statistics within, or remove statistics from a COMstatistic domain so you can define how the statistics in the domain obtain theirvalues.

Background informationDefine statistics from a COM object to enable IBM Tivoli Management Solution forExchange to convert the parameters of one or more methods of the COM objectinto Tivoli statistics. Each parameter corresponds to a Tivoli statistic. When youdefine Tivoli statistics for a parameter of a method, you must define Tivolistatistics for all of the parameters of the method. Parameters are either passed to orreturned from a method of a COM object (or both). When a parameter is passed toa method, you must define the value passed as a constant or a variable enclosed inbraces, for example, {VALUE1}. When a variable is passed, it must be defined inthe rule process default variable file at the time the rule executes. For parametersthat are used only to pass input to the method, the value of the correspondingTivoli statistic is equal to the value passed. For parameters that return a value fromthe method, the value of the corresponding Tivoli statistic is the returned valuefrom the method.


Build the list of statistics for the currently selected method. You must define onestatistic for each parameter of the method. The current number of parametersdefined and the total number of parameters for the selected method are displayedin the upper right corner of the window. The currently defined statistics for themethod are listed under Current statistics in the lower portion of the window.



Procedure1. Open the Tivoli Statistics Builder from the Tivoli Enterprise Manager.2. Click COM to display the COM statistic domains tab.3. Do the following in any order to work with the COM statistic domains:

v Add a COM statistic domain by doing the following:

a. Click the computer icon for the computer that contains the statisticsdomain that you want to work with from the Network Display field.


c. Select Add from the drop-down menu to display the Statistic Domainfrom a COM Object dialog box.

d. Do the following from the General Information tab:1) Type the statistic domain name in the Statistic domain name text box.

Note: The name must be unique across all of the Tivoli statisticdomains.

2) Type a program ID in the COM program ID: text box.Additional Information: Click Browse to browse a list of program IDsfor the COM objects on your computer. After you type or select or aprogram ID, all the methods for the COM object display.

3) Select a method from the Methods: list.


Additional Information: For each method you select, you must define aTivoli statistic for all of its parameters. The current number ofparameters defined and the total number of parameters for theselected method display under the list of methods. You can clickRemove to remove all Tivoli statistics for the method if you decidenot to define any statistics for the method.

e. Optional: Type a description in the Description tab.f. Click Statistics to display the Statistics tab.g. Do the following in the Statistics tab:

1) Click the down arrow next to the Parameters text box to display theparameters you must specify for the statistic.Additional Information: Only those parameters not currently associatedwith Tivoli statistics are available. The following displays when youselect a parameter:– Statistic name– Data type– Passing mechanism

2) Optional: Change the statistic name in the Statistic name: text box.3) Type the value to pass for parameters with a passing mechanism of In

or In/Out.

Note: If the value is a variable, enclose the name of the variable inbraces.

4) Optional: Type a description for the statistic the Statistic descriptiontext box.

h. Click Add to commit the changes and add the statistic.v Modify a statistic in the COM object source statistic domain by doing the

following:


b. Click Modify from the drop-down menu to display the Statistic Domainfrom a COM Object dialog box.

c. Click Statistics to display the Statistics tab.d. Select a statistic from the Current statistics list.e. Make changes in any of the following text boxes:

– Parameter name

– Statistic name

– Value


– Context options

f. Click OK to commit the changes.v Remove a statistic from the ODBC data source statistic domain by doing

the following:




c. Select Modify from the drop-down menu to display the Statistic Domainfrom an ODBC Data Source dialog box.

d. Click Statistics to display the Statistics tab.e. Select the statistic you want to remove from the Current statistics list.f. Click Remove to remove the statistic.g. Click OK to commit the changes.


Chapter 9. Managing events

This chapter explains how to manage events in IBM Tivoli Management Solutionfor Exchange by using the Tivoli Event Monitor and the Tivoli Event ConfigurationManager.

Table 14 provides an overview of the topics covered in this chapter.

Table 14. Guidelines for Managing Events in IBM Tivoli Management Solution for Exchange

Goal Refer to

1. Understanding how events are managed inthe Tivoli Event Monitor

“Understanding events in the Tivoli EventMonitor” on page 129

2. Understanding how to use the Tivoli EventMonitor graphical interface to view andmonitor events

“Accessing and understanding the TivoliEvent Monitor window” on page 130

3. Configuring the Tivoli Event Monitor todisplay selected events by using a monitoror view filter.

“Filtering events in Tivoli Event Monitor”on page 134

4. Setting an alert severity in the Tivoli EventMonitor so you can have audible alertsounds for specified events.

“Setting event alerts in Tivoli EventMonitor” on page 145

5. Configuring settings and filters in theTivoli Event Configuration Managerwindow so you can manage events andreduce network traffic.

“Configuring settings and filters in theEvent Configuration Manager” on page150

6. Sending and receiving events betweencomputers so you can manage eventsthroughout the network.

“Sending and receiving events betweencomputers” on page 159

7. Managing events using Tivoli Web EventMonitor so you can monitor events froman Internet browser.

“Managing events with Tivoli Web EventMonitor” on page 165

Understanding events in the Tivoli Event MonitorAn event is a notification of any significant change in the state of a systemresource, network resource, or network application. It carries information aboutitself, including the class, identity, severity, location, and description. Tivoli rulescreate events and write performance data on the local computer. An event can begenerated for a problem, for the resolution of a problem, or the successfulcompletion of a task.

The Tivoli Event Monitor is a graphical user interface used to view events. You canconfigure the monitor to display only the events you wish to view. The IBM TivoliManagement Solution for Exchange reads events from event databases.

Each computer running IBM Tivoli Management Solution for Exchange has a localTivoli Event Database where the events generated by that computer are stored.IBM Tivoli Management Solution for Exchange installs a Microsoft Jet OpenDataBase Connectivity database with the Data Source Name of RoboMon EventDatabase. Tivoli provides files if it is necessary to convert Microsoft Jet to SQLServer.

129

The local Tivoli Event Database collects events that are forwarded from othercomputers in addition to those generated locally. The database is also used totemporarily store events to be forwarded if the target machine is not available toreceive those events. See “Configuring settings and filters in the EventConfiguration Manager” on page 150 for information on configuring the collectionof events from other computers into one Tivoli Event Database.

The Event Server is a central server that routes events between computers so thatevents can be consolidated for centralized monitoring or for remote actions. Eventsare routed in real time with guaranteed delivery using remote procedure call (RPC)along with a store and forward technology to ensure initially undeliverable eventsare eventually delivered. The Event Server creates an entry for each incomingevent and evaluates the event against a rule base to determine whether it canrespond to or modify the event automatically. The Event Server also updates theevent monitor with the current event information. The Event Server:v Uses a push mechanism to send data across the network only when there is a

problem to report, making it scale well.v Sends events to one or multiple destinations.v Sends events to multiple destinations using either a flat configuration (all events

go to A and B) or hierarchical forwarding structure (events go to thelocal/regional center, all regional centers send events on to the corporate center).

v Works out of the box using an Access database, but can use any Open DataBaseConnectivity-compliant database for event/performance data storage (note Jetlimit).

The Tivoli Event Configuration Manager controls how IBM Tivoli ManagementSolution for Exchange routes events throughout the network. It also controls EventServer operational behaviors. The Tivoli Event Configuration Manager enables youto consolidate events and performance data from multiple computers.

Accessing and understanding the Tivoli Event Monitor window

ObjectiveTo access and understand the Tivoli Event Monitor so you can monitor events.

Background informationThe Tivoli Event Monitor is a graphical user interface used to view and monitorevents stored in a Tivoli Event Database. For more information about the TivoliEvent Monitor, see “Understanding events in the Tivoli Event Monitor” on page129.



Procedure1. Open IBM Tivoli Management Solution for Exchange.2. Open the Tivoli Event Monitor by doing one of the following:

v Click the Run Tivoli Event Monitor icon in the toolbar of IBM TivoliManagement Solution for Exchange.

—OR—


v Use the menu option by doing the following:a. Click Run to display the Run menu.b. Click Tivoli Event Monitor from the Run menu.

3. Choose which event database you want to view by doing the following:a. Click File to display the File menu.b. Click Open DSN from the File menu to display the available event

databases.c. Click on an event database from the Open DSN menu to display that event

database.4. Optional: Create additional event databases by doing the following:

a. Open the Control Panel.b. Optional: For Windows 2000 systems, double-click Administrative Tools.c. Double-click Data Sources (ODBC).d. Click Add to display the available drivers.e. Click a driver to use that driver for the database.f. Click Finish.

Additional Information: One reason to create additional databases is to view aTivoli Event Database on another computer. When viewing events on anothercomputer, go to Tools → Option → Mark As Read. Uncheck Mark As Read soyou do not inadvertently mark events as read in a database belonging tosomeone else.

5. Choose which monitor view to display by doing the following:a. Click Monitor to display the Monitor menu.b. Click Open from the Monitor menu to display the available monitor views.c. Click on a monitor view from the Monitor menu to display the selected

monitor view.6. Choose the events to view by doing one of the following:

v Use the menu option by doing the following:a. Click View to display the View menu.b. Click Current View from the View menu to display the View options.c. Click on a view option from the Current View menu to display the

events for that view.

—OR—v Click on a view icon as defined in Table 15.

Table 15. Tivoli Event Monitor View Icons

Icon Represents Type SubType FixedState Class

Open problems.Tivoli events.

P (problem) N (new) or U(updated)

N (not) or A(acknowledged)

None

Work in progress.Tivoli events.

P (problem) N (new) or U(updated)

P (progress) or F(fixed)

None

Closed problems.Tivoli events.

P (problem) C (closed) None None

Tivoli messages.Tivoli events.

M (message) R None None

Chapter 9. Managing events 131

Table 15. Tivoli Event Monitor View Icons (continued)

Icon Represents Type SubType FixedState Class

Tivoli SNMP traps.SNMP trap eventsthat were generatedby IBM TivoliManagementSolution forExchange.

M (message) S (SNMP) None None

Windows NT®

applicationmessages.

M (message) E (event) None Application

Windows NTsecurity messages.

M (message) E (event) None Security

Windows NTsystem messages.

M (message) E (event) None System

Other SNMP traps.SNMP trap eventsthat were notgenerated by IBMTivoli ManagementSolution forExchange.

M (message) S (SNMP) None None

OPCOM securitymessages.

M (message) O (OPCOM) None Security

OPCOM systemmessages.

M (message) O (OPCOM) None System

7. Mark an event as read by doing one of the following:v Double-click on the event.

—OR—v Use the right-click feature:

a. Right-click on the event.b. Click Mark All As Read.

—OR—v Use the menu:

a. Click Event to display the Event menu.b. Click Mark All As Read from the Event menu to mark an event as read.

Additional Information: Events that have not been read are displayed in bold.8. Mark an event as unread by doing one of the following:

v Use the right-click feature:a. Right-click on the event.b. Click Mark All As Unread.


a. Click Event to display the Event menu.


b. Click Mark All As Unread from the Event menu to mark an event asunread.

9. Mark all events as read in the Monitor or View menus by doing the following:a. Do one of the following to choose all the events to mark as read:

v Click View to display the View menu.—OR—

v Click Monitor to display the Monitor menu.b. Click Mark All as Read to mark all events in that monitor or view read.

10. Acknowledge an event by doing the following:a. Click Event to display the Event menu.b. Click Acknowledge All in the Event menu to mark an event as

acknowledged.

Additional Information: Unacknowledged events are potential alert events.Tivoli Event Monitor records the date and time of the eventacknowledgement, and the user name of the logged in account. The username can be changed through Tools → Option → Username.

11. Acknowledge all events in either Monitor or View display by doing thefollowing:a. Do one of the following to choose the grouping of events to mark as read:

v Click View to display the View menu.—OR—

v Click Monitor to display the Monitor menu.b. Click Acknowledge All from the Monitor or View menu.c. Click Yes on the confirmation screen to acknowledge all events in that

monitor or view.12. Automatically acknowledge events when read by doing the following:

a. Click Tools to display the Tools menu.b. Click Option from the Tools menu to display the Option menu.c. Click Acknowledge from the Option menu to automatically acknowledge

events that are displayed in the detail pane.13. Type an update to the progress of an event by doing the following:

a. Click Event to display the Event menu.b. Click Update Progress from the Event menu to display the Update

Progress text box.c. Type update information in the Update Progress text box.d. Click OK to record the update.

Additional Information: The text is displayed in the FixText field of the eventthat is not yet fixed. The event is acknowledged at this time, and left in awork-in-progress state. The text box records the user name, date, and time ofthe entry.

14. Update an event as a complete fix by doing one of the following:v Use the right-click feature:

a. Right-click on the event.b. Click Complete Fix to display the Complete Fix text box.c. Type the fix information in the Complete Fix text box.d. Click OK to record the fix and leave the event in a fixed state.



a. Click Event to display the Event menu.b. Click Complete Fix from the Event menu to display the Complete Fix

text box.c. Type the fix information in the Complete Fix text box.d. Click OK to record the fix and leave the event in a fixed state.

Filtering events in Tivoli Event Monitor

ObjectiveTo filter events by monitor or view so you can choose only the events you want toview.

Background informationTivoli Event Monitor is a graphical user interface that you can use to view events.You can configure the Tivoli Event Monitor to display events of your choice byusing a monitor or view filter. Events continue to be stored in the Event Database,but the Tivoli Event Monitor enables you to select only a portion of them to view.

Setting an event filter is temporary, enabling you to select only a subset of recordsor history based on a view. Temporary filters stop when you select a different view.



Procedure1. Open the Tivoli Event Monitor as described in “Accessing and understanding

the Tivoli Event Monitor window” on page 130.2. Do one of the following:

v Filter a monitor by doing the following:a. Choose the monitor you want to filter by doing the following:

1) Click Monitor to display the Monitor menu.2) Click Open from the Monitor menu to display the monitor options.3) Click on the monitor from the Open menu to select that monitor for

filtering.


b. Click Monitor to display the Monitor menu.

c. Click Filter from the Monitor menu to display the Filter screen.

—OR—v Filter events by view by doing the following:

a. Choose which view you want to filter by selecting one of the view icons.For icon definitions, see Table 15 on page 131.


b. Click View to display the View menu.

c. Click Filter in the View menu to display the Filter window.

3. Apply the filter to specific computers in the Computer tab by doing one of thefollowing:v Type the computer names separated by commas.

—OR—v Search for computers by doing the following:

a. Click Browse.b. Click any check boxes next to the computers to filter.


Additional Information: The filter is restricted to the computers specified. Anempty computer field means the filter is unrestricted and returns all computers.

4. Click Days/Time to display the Days/Time tab.

5. Type the following information in the Days/Time tab to define when the eventis active:

Event Days:Set the number of days before the current day to display events for thecurrent and prior days. The default is 30 days for the monitor filtersand 0 days (today only) for the view filters.

History Days:Set the number of additional days that events will be displayed whenthe temporary history filter is invoked. The default for this value is 1day.

From: Set the time of day the filter activates each day.


To: Set the time of day the filter ends each day.6. Click EventType/Class to display the EventType/Class tab.

7. Enter the following information:

EventType:

v Click Problem to accept incoming problem events.v Click Message to accept incoming message events.

EventSubType:

v Click New to accept new events.v Click Updated to accept updated events.v Click Closed to accept closed events.v Click Tivoli to accept Tivoli events.v Click NT Event to accept NT Events.v Click SNMP to accept SNMP events.v Click OPCOM to accept OPCOM events.

Class: Type the class identification generated by the IBM Tivoli ManagementSolution for Exchange rule.

Additional Information: Class should be an alphanumeric string that is nolonger than 32 characters. Class is filtered using a universal string.

SubClass:Type the subclass identification generated by the IBM TivoliManagement Solution for Exchange rule.

Additional Information: Subclass should be an alphanumeric string that isno longer than 32 characters. SubClass is filtered using a universalstring.


8. Click Severity to display the Severity tab.

Additional Information: Hold the cursor over a severity abbreviation to displaythe full name of the abbreviated severity.

9. Check any box to accept incoming events of a certain severity in the Severitytab.

10. Click Description to display the Description tab.

11. Enter the following information next to the corresponding radio button:

BriefText:Type the brief text to accept any event containing that text.

FullText:Type the full text to accept any event containing that text.

Both: Type the text that is both brief and full to accept any event containingthat text.


12. Click Fix/Acknowledge to display the Fix/Acknowledge tab.

13. Restrict which events are displayed based on the database fields relating to fixand acknowledge in the Fix/Acknowledge tab:

Fix Type Available:

v Click None to accept events that have no specified fix type.v Click Manual to accept events that have a manual fix type.v Click Automatic to accept events that have an automatic fix type.

Fixed State:

v Click (N)ot Fixed to accept events in a not fixed state.v Click (A)cknowledged to accept events in an acknowledged state.v Click Work in (P)rogress to accept events in a work in progress

state.v Click (F)ix Completed to accept events in a fix completed state.

Acknowledged by:Type the user name who acknowledged the event.

Fixer: Type the user name who is responsible for fixing the event.

Fix Text:Type notes about the event fix for documentation.


14. Click Advanced to display the Advanced tab.

15. Type the following information:

UserNameType the account used to log into the network to accept events fromthat user name.

RuleNameType the name of the IBM Tivoli Management Solution for Exchangerule that captured the event to accept events containing that rulename.

EntityContextType any identification generated by the IBM Tivoli ManagementSolution for Exchange rule to accept events containing that entitycontext.

SourceType the process from which an event was captured to accept eventscontaining that source.

Additional Information: Source is most often used with Windows NTEvents.

HandleType a name to be associated with the problem to accept eventscontaining that handle.

Additional Information: If this is not specified, a default one is formedby the rule engine. The default handle name includes the rule name,context, and the creation date and time of the event. Handle is mostoften used with Windows NT Events.

16. Click OK to save your filter settings.17. Optional: Arrange the view of the Monitor display by doing the following:

a. Click Monitor to display the Monitor menu.b. Click Open from the Monitor menu to display the list of event categories.c. Click the event category to view events for that category.d. Click View to display the the View menu.


e. Click Show Fields from the View menu to display the Show Fieldsscreen.

f. Double-click on an available field to move that field to the Show thesefields in this order field.Additional Information: Click on a field in the Show these fields in thisorder field and click Remove to move that field to the Available fieldscolumn.

g. Click on a field in the Show these fields in this order field.h. Do one of the following to change the order in which the fields are

displayed:v Click Move Up to move the field up in order of display.

—OR—v Click Move Down to move the field down in order of display.

Additional Information: Fields in parentheses indicate an icon rather thantext field. Severity is the severity text while (Severity) is the severity icon.

i. Click OK to save your changes and close the Show Fields screen.18. Optional: Sort the event display by doing the following:


a. Click View to display the View menu.

b. Click Sort from the View menu to display the Sort screen.

c. Double-click on an available field to move that field to the Sort ordercolumn.Additional Information: Click on a field in the Sort order column and clickRemove to move that field to the Available fields column.

d. Click on a field in the Sort order column.e. Move the field by doing one of the following:

v Click Move Up to move the field up in order of display.—OR—

v Click Move Down to move the field down in order of display.Additional Information: Click Ascending to display the field in ascendingorder. Click Descending to display the field in descending order.

f. Click OK to save your changes and close the Sort screen.


19. Optional: Choose a different view icon by doing the following:a. Click on the icon you wish to change. The example below shows the Open

Problems icon selected.

b. Click View to display the View menu.


c. Click Choose Icon from the View menu to display the Choose Icon screen.

d. Choose a different icon for the view by doing one of the following:v Click on the icon button.

—OR—v Scroll through the list of icons.

Additional Information: Click Delete to delete the selected view icon fromthe list of available view icons. Delete is not available for the standardicons. If you delete an icon that is in use by any monitor definition, theicon displays as the Generic icon. Click Add to add icons to the list ofavailable icons using the Add View Icon screen.

e. Click OK to select the icon for the specified view and close the ChooseView Icon screen. The selected icon appears in place of the previous icon.

Setting event alerts in Tivoli Event Monitor

ObjectiveTo set an alert severity in the Tivoli Event Monitor so you can have audible alertsounds for specified events.


Background informationAn alert event is an unacknowledged event that matches the alert severity criteriafor the displayed view. Alert events are marked with an exclamation point icon.Any view icon containing an alert event is marked with a red box around the icon.



Procedure1. Open the Tivoli Event Monitor as described in “Accessing and understanding

the Tivoli Event Monitor window” on page 130.2. Choose a group of events for which you want to set alerts by doing one of the

following:v Set event alerts for a monitor by doing the following:

a. Click Monitor to display the Monitor menu.b. Click Open from the Monitor menu to display the monitor options.c. Click on the monitor from the Open menu to select that monitor to set

alerts.

—OR—v Select a view icon for which you want to set alerts. For icon definitions, see

Table 15 on page 131.3. Click View to display the View menu.


4. Click Alert Severities from the View menu to display the Alert Severitiesscreen.

5. Click on a severity check box to create an alert state for all unacknowledgedevents for that severity.

6. Optional: Choose an alert sound by doing the following:a. Click Monitor to display the Monitor menu.


b. Click Alert Sounds from the Monitor menu to display the Alert Soundsscreen.

c. Click radio buttons for any of the nine severity levels to choose a soundalert for that event.

d. Optional: Choose an alternate sound by clicking Choose Sound to display aselection of sounds.

7. Optional: Choose the event text color and icon for severities by doing thefollowing:a. Click Monitor to display the Monitor menu.


b. Click Format Severity in the Monitor menu to display the Format Severityscreen.

c. Click on a severity check box to select the severity for modification.d. Optional: Click Choose Color to select a different text color for the severity.e. Optional: Click Choose Icon to select a different icon for the severity from

the Choose Severity Icon screen.f. Enable the sound function by doing the following:

1) Click Tools to display the Tools menu.

2) Click Option in the Tools menu to display the Options menu.3) Click Alert Sound Enabled to display a check mark next to the option to

enable the sound function.g. Optional: Choose to set an interval between alert sounds by doing the

following:1) Click Tools to display the Tools menu.2) Click Option in the Tools menu to display the Options menu.3) Click Alert Play Interval to display the Alert Play Interval screen.4) Type the number of seconds to occur between alert sounds.


Additional Information: The minimum is 10 seconds. At the end of thisinterval the event monitor determines whether a more severe alert hasoccurred and plays the sound, if any, associated with that severity levelprovided that Alert Sound Enabled is on.

h. Optional: Choose to set an alert snooze interval by doing the following:1) Click Tools to display the Tools menu.2) Click Option in the Tools menu to display the Options menu.3) Click Alert Snooze Interval to display the Alert Snooze Interval screen.4) Type the minimum number of seconds before an alert sound for a

severity level can repeat.Additional Information: At the end of this interval, a previously playedsound for a severity level expires. If there are still alerts of this severitylevel, the sound is eligible to play again.

Configuring settings and filters in the Event Configuration Manager

ObjectiveTo configure settings and filters in the Tivoli Event Configuration Managerwindow so you can manage events and reduce network traffic.

Background informationThe Tivoli Event Configuration Manager is designed to enable completemanagement and control of the Event Server from anywhere on the network. TheEvent Server provides reliable event delivery using database store and forward andremote procedure call (RPC). The Event Server uses Open DataBase Connectivityto operate on its local event database.

The Event Server provides an event forwarding architecture. This gives IBM TivoliManagement Solution for Exchange the ability for a computer to receive an eventfrom another computer and forward it to a third computer. The forwarding abilityhandles looping by incrementing the hops counter on each forward. An event isdiscarded when the hops counter exceeds the allowable number of hops (definedby a registry key, normally three). One of the debugging levels log events that aredropped if there are too many hops.

Within the event forwarding architecture, the originating computer and eventsequence number is preserved. This value forms the event record primary key. Itprevents the posting of duplicate events to the same computer through two ormore forwarding paths. This originating number and computer name is generatedwhen an event is loaded into the Local Inbox Database. The Open DataBaseConnectivity event database must support the identity characteristic on a column(SQL Server terminology). Writing an event to the Local Inbox Database generatesan incrementing sequence number.

Note: For Access, the identity characteristic is called auto numbering.

The Tivoli Event Configuration Manager is used to edit different Event Serverconfiguration categories across the Enterprise.

The Tivoli Event Configuration Manager represents the network using theWindows NT domain and computer networking hierarchy.

Event Server configuration settings are all of the miscellaneous forwarding, timing,retention, and optimization parameters for the Event Server.




Procedure1. Open IBM Tivoli Management Solution for Exchange.2. Open the Tivoli Event Configuration Manager by doing one of the following:

v Click the Tivoli Event Configuration Manager icon.

—OR—v Use the menu by doing the following:

a. Click Manage to display the Manage menu.


b. Click Event Server from the Manage menu to display the Tivoli EventConfiguration Manager screen.

3. Configure settings by typing the following:

Maximum hops:Type the maximum number of times an event can be forwarded fromcomputer to computer before it is discarded.

Inbox timer:Type the number of seconds the Event Server waits before polling theInbox for new events.

Outbox timer:Type the number of seconds the Event Server waits before retrying thesending of undeliverable remote events.

Log file age:Type the number of days to retain Event Server daily log files.

Debug mode:Type the level of debugging information that should be included in theevents.

Additional Information: Debugging information is written to a daily logfile in the IBM Tivoli Management Solution for Exchange\logsdirectory. The file is named Event_server_yyyy_mm_dd.LOG, where yyyyis the year, mm is the month and dd is the day. The levels of debuggingrange from 0 (no debugging) to 4 (full debugging). Level 1 is thenormal level for debugging. Debugging levels are synonymous withlogging levels.

Maintain events for (Auto Clean Filter):Type the number of days to automatically remove events from the localevent database.

Additional Information: The filter thread runs once daily at midnight toremove events from the local event database that match the filterspecification. The filter specification normally includes an event agefilter, so that events are cleaned based on age.


Maintain perf. data for (Performance Data Retention Age):Type the number of days to automatically remove performance datafrom the Performance database.

Additional Information: The filter thread runs once daily at midnight toremove events from the Performance database that match the filterspecification.

Performance routing timer:Type the number of seconds the Event Server waits before retrying tosend remote performance data.

4. Select Windows NT event filter in the Network Display field to display theWindows NT filter.

5. Enter the following information:

Receive Windows NT Events

v Click System to receive system events.v Click Security to receive security events.v Click Application to receive application events.v Type the number days in Attempt redelivery for to indicate how

many days the system attempts redelivery of events.

UserNames:Type the account used to log into the network to accept events fromthat user name.

Source:Type the process that an event was captured from to accept eventscontaining that source.

Sub Class:Type the subclass identification generated by the IBM TivoliManagement Solution for Exchange rule.

Additional Information: The subclass should be an alphanumeric stringthat is no longer than 32 characters.


Handle:Type a name to be associated with the problem to accept eventscontaining that handle.

Additional Information: If this is not specified a default one is formed bythe rule engine. The default handle name includes the rule name,context, and the creation date and time of the event.

6. Click SNMP trap filter in the Network Display field to display the SNMPTrap filter.

7. Type the following information:

SNMP Traps:Click to accept SNMP Trap events.

Attempt redelivery for

Type the number days the system attempts redelivery of events.

UserNames:Type the account used to log into the network to accept events fromthat user name.

Class: Type the class identification generated by the IBM Tivoli ManagementSolution for Exchange rule.

Additional Information: The Class should be an alphanumeric string thatis no longer than 32 characters. Class is filtered using a universe string.

Sub Class:Type the subclass identification generated by the IBM TivoliManagement Solution for Exchange rule.

Additional Information: The subclass should be an alphanumeric stringthat is no longer than 32 characters.

RuleName:Type the name of the IBM Tivoli Management Solution for Exchangerule that captured the event to accept events containing that rule name.


EntityContext:Type the entity context identification generated by the IBM TivoliManagement Solution for Exchange rule.

8. Click Local event filter in the Network Display field to display the Localevent filter.Additional Information: The local event filter is used to exclude Windows NTevents from being transferred to the current computer from any other source.

9. Apply the filter to specific computers in the Computer tab by doing one of thefollowing:v Enter the computer names in the universal string.

—OR—v Search for computers by doing the following:

a. Click Browse.b. Check boxes next to the any computer to filter.

Additional Information: The filter is restricted to the computers specified in theuniversal string in the Computer field of the Computers tab. An emptycomputer field means the filter is unrestricted and returns all computers.


10. Click EventType/Class tab to display the EventType/Class filter.

11. Check or type information as appropriate for the following options:

EventType:

v Click Problem to accept incoming problem events.v Click Message to accept incoming message events.

EventSubType:

v Click New to accept new events for the selected EventType events.v Click Updated to accept updated events for the selected EventType

events.v Click Closed to accept closed events for the selected EventType

events.v Click Tivoli to accept Tivoli events for the selected EventType

events.v Click Event Log to accept Event Log events for the selected

EventType events.v Click SNMP to accept SNMP events for the selected EventType

events.v Click Opcom to accept Opcom events for the selected EventType

events.

Class Type the class identification generated by the IBM Tivoli ManagementSolution for Exchange rule.

Additional Information: The Class should be an alphanumeric string thatis no longer than 32 characters. Class is filtered using a universalstring.

SubClassType the subclass identification generated by the IBM TivoliManagement Solution for Exchange rule.

Additional Information: The subclass should be an alphanumeric stringthat is no longer than 32 characters. SubClass is filtered using auniversal string.


12. Click Severity to display the Severity tab.

13. Check any severities you want to view.Additional Information: The Severity tab enables you to restrict the events tocertain severity levels. For example, you might want to remove the VMS(OpenVMS all) check box to filter out any event with a VMS severity. Notethat the Windows NT, VMS, and ISO severity levels are arranged to showtheir mapping to the corresponding IBM Tivoli Management Solution forExchange severity.

14. Click Description to display the Description tab.

15. Enter the following information next to the corresponding radio button:

Brief Text:Type the brief text to accept any event containing that text.

Full Text:Type the full text to accept any event containing that text.

Both: Type the text that contains both brief and full text to accept any eventcontaining that text.


16. Click Advanced to display the Advanced tab.

17. Type in this information:

UserNameType the account used to log into the network to accept events fromthat user name.

RuleNameType the name of the IBM Tivoli Management Solution for Exchangerule that captured the event to accept events containing that rulename.

EntityContextType the entity context identification generated by the IBM TivoliManagement Solution for Exchange rule.

SourceType the process from which an event was captured to accept eventscontaining that source.

HandleType a name to be associated with the problem to accept eventscontaining that handle.

Additional Information: If this is not specified a default one is formedby the rule engine. The default handle name includes the rule name,context, and the creation date and time of the event.

18. Optional: Enable or disable the Tivoli Event Configuration Manager to requireconfirmations before performing specific classes of operations by doing thefollowing:a. Click View to display the View menu.


b. Click Options from the View menu to display the Tivoli Event ServerConfiguration Option screen.

c. Do one of the following to enable or disable operation confirmationnotices:v Select Confirm all update operations to require confirmation before

performing an operation.—OR—

v Deselect Confirm all update operations to perform all operationswithout confirmation.

d. Do one of the following to enable or disable operation completion notices:v Select Display success messages to have Tivoli Event Configuration

Manager inform you when the operation was successfully performed.—OR—

v Deselect Display success messages to have Tivoli Event ConfigurationManager perform operations without notifying you of completion.

Sending and receiving events between computers

ObjectiveTo send events to another computer and receive events from another computer soyou can manage events throughout the network.

Background informationFor an understanding of events, see “Understanding events in the Tivoli EventMonitor” on page 129.



Procedure1. Open IBM Tivoli Management Solution for Exchange.2. Open the Tivoli Event Configuration Manager by doing one of the following:

v Click the Tivoli Event Configuration Manager icon.

—OR—v Use the menu by doing the following:


a. Click Manage to display the Manage menu.

b. Click Event Server from the Manage menu to display the Tivoli EventConfiguration Manager screen.

3. Do the following to send events to another computer:a. Click Sending events to in the Network Display field.


b. Click Send/Receive to display theSend/Receive menu.

c. Click Add/Remove from the Send/Receive menu to display the Sendingevents to screen.

d. Select computers to which to send events by doing one of the following:v Type the names of the computers in the Choose Computers field

separated by commas.—OR—


v Click Browse to select computers from a display of available computers.

e. Click OK to display the confirmation screen.Additional Information: Click Apply to apply the computers without leavingthe Sending events to screen.

f. Click Yes to confirm the computers to receive events.


g. Click OK to select the computers to receive events.

4. Remove a computer from receiving events by doing the following:a. Right-click on the computer icon that you wish to remove to display the

Remove pop-up menu.

b. Click Remove to display the remove confirmation box.c. Click OK to remove the computer receiving events list.

5. Send performance data to other computers by doing the following:


a. Click Sending Performance Data To in the Network Display field.

b. Click Send/Receive to display the Send/Receive menu.c. Click Add/Remove from the Send/Receive menu to display the Sending

performance data to screen.d. Choose computers to send performance data to by doing one of the

following:v Type the names of the computers in the Choose Computers field


v Click Browse to select computers from a display of available computers.

e. Click OK to send performance data to the selected computers.6. Receive Open VMS or UNIX events from other computers by doing the

following:


a. Click Receiving (OpenVMS or UNIX) events from in the Network Displayfield.

b. Click Send/Receive to display the Send/Receive menu.c. Click Add/Remove from the Send/Receive menu to display the Receiving

(OpenVMS or UNIX) events from screen.

d. Choose computers to receive OpenVMS or UNIX events from by doing oneof the following:v Type the names of the computers in the Choose Computers field


v Click Browse to select computers from a display of available computers.e. Click OK to receive OpenVMS or UNIX events from the selected computers.

Managing events with Tivoli Web Event Monitor

ObjectiveTo manage events using Tivoli Web Event Monitor so you can monitor events froman Internet browser.


Background informationFor an understanding of events, see “Understanding events in the Tivoli EventMonitor” on page 129.

Before you beginInstall Tivoli Web Event Monitor as described in “Installing Tivoli Web EventMonitor” on page 29.


Procedure1. Open Internet Explorer 4.0 Web browser.2. Type the following in the address field:

http://[SERVER]/TivoliEventMonitor/

where [SERVER] is the fully qualified domain name system (DNS) of theMicrosoft Internet Information Services server.Additional Information: Do the following to determine the SERVER name:a. Open the Control Panel.b. Do one of the following to open the list of Data Sources:

v Windows NT®:

1) Click ODBC Data Sources.2) Click System DSN to display the System DSN tab.

—OR—v Windows 2000:

1) Click Administrative Tools.2) Click Data Sources (ODBC).3) Click System DSN to display the System DSN tab.

c. Click RoboMon Event Database in the System Data Sources list.d. Click Configure to display the Microsoft SQL Server DSN Configuration

screen. The SERVER name displays in the text box labeled Which SQLServer do you want to connect to? If (local) appears, then SERVER is thename of the computer on which you are working.


3. Click one of the Server Health icons to view the following information:

Server Health — Overall ViewDisplays the overall health status of all computers known to the centralevent consolidator.

Server Health Detail View — Problem Machines OnlyDisplays the open problem events.

Server Health Detail View — All MachinesDisplays the severity of the events.

4. Click one of the Enterprise Views icons to view the following information:

Open ProblemDisplays all events in an open problem status.

Closed ProblemDisplays all events that are in a closed status.

Tivoli MessagesDisplays all Tivoli messages.

Event Log System MessagesDisplays all event log system messages.

Event Log Application EventsDisplays all event log application events.

Event Log Security MessagesDisplays all event log security messages.

SNMP TrapsDisplays all SNMP Trap events.

UNIX and VMS EventsDisplays all UNIX and VMS events.

5. Click one of the Application Views icons to view the following information:


Exchange Server EventsDisplays events relating to Exchange.

SQL Server EventsDisplays events relating to SQL Server.

6. Filter a view by doing the following:a. Click the Filteringicon in the left pane to display the Event Filtering screen.

b. Click selections to filter out all events except the selected categories.Additional Information: Select multiple selections within each of the filteringcategories by holding down the CTRL key and clicking on each selection.When moving to the next category, release the CTRL key until after the firstselection has been made within that list box, holding the CTRL key forsubsequent selections within that list box. Holding the CTRL key downbetween list boxes causes default selection of All Events to remain selected,negating all filtering for that field. The default selection of All Eventsindicates that no filtering is performed for that category.

c. Click Filter to save the settings.


7. Click the Security Settings icon in the left pane to display the SecurityFunctions screen and set the following security settings

v Do the following to add user roles or permissions:a. Click the Add a New Event Monitor User icon (top left icon in the left

pane) to display the Add New Users screen.

b. Type the DOMAIN\NAME for the user in the text box where NAME is theWindows user login name.

c. Choose permissions for the user based on the following choices:

Security AdminAllows the user to edit Security settings.


AdministratorAllows the user to access all views in the Tivoli Event Monitor,but not add other users.

EnterpriseAllows the user to access all Enterprise views (Open Problems,Closed Problems, Tivoli messages, Event Log messages, SNMPtraps, and VMS and UNIX events).

AdminAllows the user to access Admin events displayed in the TivoliEvent Monitor.

ExchangeAllows the user to access Exchange events displayed in the TivoliEvent Monitor.

SQL ServerAllows the user to access SQL Server events displayed in theTivoli Event Monitor.

d. Click Add User to add the user to Tivoli Event Monitor and display thenew user successfully added screen.Additional Information: Click the Edit Event Monitor user security settingsicon (top right icon in the left pane) to change user roles and permissionsat any time.

v Do the following to delete a Tivoli Event Monitor user:a. Click the Delete Event Monitor user icon (bottom left icon in the left

pane) to display the Delete Existing Users screen.

b. Click the down arrow in the Select User Name text box to display the listof current Tivoli Event Monitor users.

c. Click the user name to delete.d. Click Delete User to delete the user from roles and permissions in the

Tivoli Event Monitor.v Do the following to edit user preferences:


a. Click the Edit my preferences icon (bottom right icon in the left pane) todisplay the Preferences screen.

b. Select the number of seconds for the main Tivoli Event Monitor windowto refresh from the drop-down menu.

c. Click one of the following severity color preferences:– Show all severities as same color: Displays all event text in black and

can speed up performance.—OR—

– Use colors to designate severity: Displays event text in colorsaccording to severity:- Severity 1 or 2 = red- Severity 3 or 4 = amber- Severity 5 = blue- Severity 6 or greater = green

d. Click any of the following views to display as icons in the Tivoli EventMonitor Toolbar:– Enterprise

– Admin

– Exchange

– SQL Server

e. Click Update Preferences to save user settings.


Chapter 10. Reporting and graphing

This chapter explains how to create reports and graphs using Tivoli Reporting andGraphing in IBM Tivoli Management Solution for Exchange.

Table 16 provides an overview of the topics covered in this chapter.

Table 16. Guidelines for reporting and graphing in IBM Tivoli Management Solution forExchange

Goal Refer to

1. Understanding the Tivoli Reporting andGraphing Manager functions and options

“Understanding reports and graphs in theTivoli Reporting and Graphing Manager”on page 173

2. Generating a report from specified data “Creating a report” on page 179

3. Exporting a report for use in a Web site “Exporting a report” on page 182

4. Generating a graph from specified data “Creating a graph” on page 183

5. Working with graphs to display specificdata or type of graph

“Customizing graphs” on page 186

6. Exporting a graph for use in a Web site “Exporting a graph” on page 188

7. Creating batch reports and graphs to runautomatically

“Creating batch reports and graphs” onpage 190

8. Managing folders by batch “Managing the batch folders” on page 191

9. Changing reports and graphs to displayinformation in a specific manner

“Customizing views of reports andgraphs” on page 193

Understanding reports and graphs in the Tivoli Reporting andGraphing Manager

Tivoli Reporting and Graphing provides the ability to:v Graph or create reports on data consolidated from multiple computersv Customize report columns and summarization groupingsv Graph by time, hour summary, computer, or entity (such as disk, database, file,

process, and enterprise)v Save customized report and graph user definitionsv Export a report or graph in Hypertext Markup Language (HTML), Excel, or

Word formatv Run reports and graphs as a batch and automatically forward as an email

The Tivoli Reporting and Graphing creates reports and graphs from data archivedin a database. Most of the reports and graphs work with IBM Tivoli ManagementSolution for Exchange performance rules. The performance rules archiveperformance data at regular intervals to a database and must be running to createthat data necessary for reporting and graphing.

The Tivoli Performance Database contains the performance data used for reportingand graphing. IBM Tivoli Management Solution for Exchange performance rulespopulate the database. The Open Database Connectivity (ODBC) system datasource name (DSN) uses “RoboMon Performance Reporting” as the name for the

173

performance database that is accessed by the reports and graphsfor theperformance database accessed by the reports and graphs. The IBM TivoliManagement Solution for Exchange installation creates this data source name toreference the performance database on your local computer. You can access theperformance database on a different computer by changing this data source name.

Tivoli Reporting and Graphing has three different views: CIO, Management, andSysadmin. The CIO view contains reports and graphs that are of interest to aChief Information Officer. The Management view contains the full set ofmanagement reports and graphs. The Sysadmin view contains detailed reports andgraphs that are of interest to a system administrator.

The CIO and Management views include the following reports and graphs:

Summary reportDisplays a monthly activity summary for each hour of the day, excludingSaturdays and Sundays.

Computer bar graphDisplays computer data summarized in a bar graph format. Each barrepresents computer activity for the current month between the hours of9:00 AM and 5:00 PM, excluding Saturdays and Sundays.

Entity bar graphDisplays entity data summarized in a bar graph format. Each barrepresents entity activity for the current month between the hours of 9:00AM and 5:00 PM, excluding Saturdays and Sundays.

Hourly summary bar graphDisplays computer and entity data summarized in a bar graph format.Each bar represents activity or usage data for each hour of the day in thecurrent month, excluding Saturdays and Sundays.

Summary pie graphDisplays computer and entity data summarized in a pie chart format. Eachpie slice represents computer and entity data for the current monthbetween the hours of 9:00 AM and 5:00 PM, excluding Saturdays andSundays.

The Sysadmin view includes the following reports and graphs:

Detail reportsDisplays detailed activity data in report format.

Time line graphsDisplays detailed activity data in a time line graphical format.

CIO, Management, and Sysadmin views provide the following reports andgraphs:

Product CIO and Management Views Sysadmin Views

Exchange Summary Management Summary Report

Computer Summary Bar Graph

Hourly Summary Bar Graph

Detail Report

Exchange Storage Management Summary Report


Detail Report


Exchange Internet Management Summary Report



Detail Report

Time Line Graph

Exchange IMC Activity Management Summary Report

Connector Summary Bar Graph


Time Line Graph

Exchange Site Activity Management Summary Report

Site Summary Bar Graph


Time Line Graph

Exchange Server Activity Management Summary Report

Server Summary Bar Graph


Time Line Graph

Exchange User Activity Management Summary Report

User Summary Bar Graph


Time Line Graph

Exchange Domain Activity Management Summary Report

Domain Summary Bar Graph


Time Line Graph

Exchange 2000 General Management Summary Report



Detail Report

Exchange 2000 Chat Management Summary Report



Detail Report

Exchange 2000Conferencing

Management Summary Report



Detail Report

Exchange 2000 Storage Management Summary Report


Detail Report

Exchange 2000 MTAConnections




Detail Report

Time Line Graph

Exchange 2000 DomainActivity




Time Line Graph

Chapter 10. Reporting and graphing 175

Exchange 2000 IMC Activity Management Summary Report

Connector Summary Bar Graph


Time Line Graph

Exchange 2000 Site Activity Management Summary Report

Site Summary Bar Graph


Time Line Graph

Exchange 2000 ServerActivity


Server Summary Bar Graph


Time Line Graph

Exchange 2000 UserActivity


User Summary Bar Graph


Time Line Graph

Exchange 2000 Simple MailTransfer Protocol (SMTP)Activity




Time Line Graph

SQL Server 6.5 Summary Management Summary Report



Time Line Graph

SQL Server 6.5input/output (I/O)




Detail Report

Time Line Graph

SQL Server 6.5 Replication Management Summary Report



Detail Report

Time Line Graph

SQL Server 6.5 Activity Management Summary Report



Detail Report

Time Line Graph

SQL Server 6.5 ProcedureCache




Detail Report

Time Line Graph

SQL Server 6.5 Database Management Summary Report

Database Summary Bar Graph


Detail Report

Time Line Graph

SQL Server 6.5 Device Management Summary Report

Device Summary Bar Graph


Detail Report

Time Line Graph


SQL Server 6.5 Log File Management Summary Report

Log File Summary Bar Graph


Detail Report

Time Line Graph

SQL Server 7 Summary Management Summary Report



Detail Report

Time Line Graph

SQL Server 7 Memory Management Summary Report



Detail Report

Time Line Graph

SQL Server 7 Replication Management Summary Report



Detail Report

Time Line Graph

SQL Server 7 AccessMethods




Detail Report

Time Line Graph

SQL Server 7 BufferManager




Detail Report

Time Line Graph

SQL Server 7 Process Management Summary Report



Detail Report

Time Line Graph

SQL Server 7 DatabaseUsage




Detail Report

Time Line Graph

SQL Server 7 Database Logs Management Summary Report



Detail Report

Time Line Graph

SQL Server 7 Locks Management Summary Report

Lock Summary Bar Graph


Detail Report

Time Line Graph

SQL Server 2000 SystemCPU




Time Line Graph

SQL Server 2000 Statistic Management Summary Report

Instance Summary Bar Graph


Detail Report

Time Line Graph


SQL Server 2000 Backup Management Summary Report



Detail Report

Time Line Graph

SQL Server 2000 Logins Management Summary Report



Detail Report

Time Line Graph

SQL Server 2000 Latch Management Summary Report



Detail Report

Time Line Graph

SQL Server 2000 Memory Management Summary Report



Detail Report

Time Line Graph

SQL Server 2000 ReplicationDistribution




Detail Report

Time Line Graph

SQL Server 2000 LogreaderReplication




Detail Report

Time Line Graph

SQL Server 2000 ReplicationMerge




Detail Report

Time Line Graph

SQL Server 2000 AccessMethods




Detail Report

Time Line Graph

SQL Server 2000 BufferManager




Detail Report

Time Line Graph

SQL Server 2000 Process Management Summary Report



Detail Report

Time Line Graph

SQL Server 2000 DatabaseUsage




Detail Report

Time Line Graph

SQL Server 2000 DatabaseLogs




Detail Report

Time Line Graph


SQL Server 2000 Locks Management Summary Report

Lock Summary Bar Graph


Detail Report

Time Line Graph

Creating a report

ObjectiveTo create a report in the Tivoli Report and Graph Manager so you can viewperformance data in a graphical format.


Before you beginYou must be running the IBM Tivoli Management Solution for Exchangeperformance rules to collect report and graph data.


Procedure1. Open IBM Tivoli Management Solution for Exchange.2. Open the Tivoli Report and Graph Manager by doing one of the following:

v Click the Run Tivoli Reporting and Graphing icon.

—OR—v Use the menu options by doing the following:

a. Click Run to display the Run menu.b. Click Tivoli Reporting and Graphing from the Run menu.

3. Choose the report topic by doing one of the following:v Click the report on the left pane to display the criteria for that report.


—OR—v Double-click the report on the right pane to display the report criteria.

4. Customize the report criteria by doing the following:a. Define the following fields on the Main tab:

Title: Type in a title to display at the top of the report.

Include graphDo one of the following:v Select this check box to include a bar graph in the report.

—OR—v Deselect this check box to omit a bar graph from the report.

Additional Information: Double-click on any bar in the graph todisplay report information for that value. A new tab appears in theleft pane of the window.

Fields used:Select fields to display as columns in the report.

Additional Information: You can change the order of the fields byclicking the up or down arrow to the left of the field.

Groups:Select groups to define how the report is sorted and summarized.

Additional Information: You can change the sort order of the groupsby clicking the up or down arrow to the left of the field.

Computers:Select computers to include in the report.

Additional Information: The computers listed are all computers foundin the database table associated with this report.


Additional Information: Some reports display a list of entities in the Main tab.Entities refer to computer components for which there can be manyoccurrences, such as disks, processes, services, and databases. The listincludes all entities found in the database table associated with the report.Check any entities to include in the report.

b. Click Dates/Times to display the Dates/Times tab.

c. Click one of the following radio buttons in the Dates field. Enter additionalinformation for the selections below:

Days back:Type the number of days to report.

Date Type the date to report.

Date rangeType the beginning and ending dates to report.

d. Click the check boxes to display report data for days of the week in theDays of the week field.

e. Define the following information in the Times field:

All TimesDisplays all times in the report.

Time range:Type a beginning and ending time of day for the report.

5. Click Run to run and display the report.Additional Information: Reports display in a separate report window. You can goback to the Report and Graph Manager to do other tasks while the report


displays.

6. Optional: Save the report by doing the following:a. Click Save.b. Type a name for the version of this report.

7. Optional: Refresh report data by clicking the refresh data icon in the toolbar.The report is recreated using the data at the time of the refresh.

8. Optional: Search for any text within a report by doing the following:a. Enter the text in the search text box in the report window toolbar.b. Click the search icon (binoculars).

9. Optional: Navigate the report information by doing the following:

Click on a computer name or dateThe report jumps to the beginning of this grouping.

Click on the arrows in the window toolbarThe report pages forward, backward, or jumps to either the first or lastpage of the report.

Pass the cursor over any value displayed in the reportThe cursor changes to a magnifying glass. Double-click to show valuesfor only the grouping under the cursor. A new tab appears in the leftpane of the window. Click any of the tabs to display its associatedreport. To remove a tab and its associated report, click the X in thereport window toolbar.

Exporting a report

ObjectiveTo export a report so you can create the report in HTML format to use in a Website.




When you finishPoint an URL to the Web server directory that contains the exported report. Ifrequired, add security.

Procedure1. Open the report.2. Do one of the following to display the Export screen:

v Click the Export Report icon in the report window toolbar.—OR—

v Use the menu option by doing the following:a. Click File to display the File drop-down menu.b. Click Export from the File drop-down menu.

3. Click the down-arrow for the Format text box to display the format options.4. Select a format from the list.

Additional Information: Rich Text enables you to include the report as an emailattachment. HTML enables you to read the report in a Web page. CrystalReports (.rpt) enables you to import the report into Crystal reports.

5. Click the down-arrow for the Destination text box to display the destinationoptions.

6. Select a destination from the list.7. Click OK.

Creating a graph

ObjectiveTo create a graph so you can view the performance data in a graphical form.

Background informationGraphs display in a separate graph window. You can go back to the Report andGraph Manager to do other tasks after displaying the graph.



Procedure1. Open IBM Tivoli Management Solution for Exchange.2. Open the Tivoli Report and Graph Manager by doing one of the following:

v Click the Run Tivoli Reporting and Graphing icon.

—OR—v Use the menu options by doing the following:

a. Click Run to display the Run menu.


b. Click Tivoli Reporting and Graphing from the Run menu.

3. Choose your graph topic by doing one of the following:v Choose your graph topic on the left pane.

—OR—v Double-click the graph topic on the right pane.

4. Choose your criteria for the graph by doing the following:


a. Define the following criteria on the Main tab:

Fields used:Select fields to display as columns in the graph.

Additional Information: Change the order of the fields by clicking theup or down arrow to the left of the field.

Computers:Select computers to include in the graph.

Additional Information: The list includes all computers found in thedatabase table associated with this graph.

b. Click Dates/Times to display the Dates/Times tab.c. Define the following information on the Dates/Times tab:

Dates Click an option to define the date or date range of the graph.Complete the information for the following options:

Days backType the number of days to graph.

Date Type the date to graph.

Date rangeType the beginning and ending dates to graph.

Days of the weekType the days of the week to include in the graph.

Times Select an option to define the times of day you want to graph. ForTime range:, enter the beginning and ending times of day to graph.

5. Click Run to run the graph.6. Optional: Save the graph by doing the following:

a. Click Save.b. Type a name for the version of this graph.

7. Optional: Refresh graph data by doing the following:


a. Click View to display the View menu.b. Click Refresh Graph from the View menu to recreate the graph using the

data at the time of the refresh.8. Optional: Search for any text within a report by doing the following:

a. Enter the text in the search text box in the report window toolbar.b. Click the search icon (binoculars).

Customizing graphs

ObjectiveTo customize a graph so you can tailor the appearance of a graph.




Procedure1. Open the graph.


2. Click any of the icons in the graph window toolbar to display the GraphControl screen.

3. Do any of the following to change the appearance of your graph:v Change the Graph Type by doing the following:

a. Click one of the following:– 2D Gallery tab

—OR—– 3D Gallery tab

b. Click the desired graph type.c. Do one of the following:

– Click Apply Now to see the changes in your graph without closing thegraph control window.—OR—

– Click OK to make the changes in the graph and close the graphcontrol window.

v Change the 3D Appearance by doing the following:

a. Click 3D to display the 3D tab.b. Click the desired option.c. Do one of the following:

– Click Apply Now to see the changes in your graph without dismissingthe graph control window.—OR—

– Click OK to make the changes in the graph and dismiss the graphcontrol window.

v Add Trend Lines to a 2D Line Graph by doing the following:

a. Click Trends to display the Trends tab.b. Click one of the following statistic lines:

– Mean


—OR—– Minimum and maximum

—OR—– Standard deviation

c. Click one of the following: best fit line or curve.d. Do one of the following:



Additional Information: For 2D line graphs, you can use the mouse to zoomin to any part of the graph. Click on an icon in the upper left corner ofthe graph, and drag the mouse forming the rectangle to enlarge. Whenyou release the mouse button, the graph enlarges the selected rectangleinto the total size of the graph. Repeat the process for furtherenlargement of a graph section. Return the graph to its original full viewby selecting View → Full.

v Change Colors in your graph by doing the following:

a. Click Markers to display the Markers tab.b. Click on each data set and select a color.c. Do one of the following:



v Change titles in your graph by doing the following:

a. Click Titles to display the Titles tab.b. Type the text of the titles to display with the graph.c. Do one of the following:



Exporting a graph

ObjectiveTo export a graph so you can format the graph for use in a Web site.




When you finishPoint an URL to the Web server directory that contains the exported graph. Ifrequired, add security.

Procedure1. Open the graph.2. Click File to display the File menu.3. Click Export from the File menu to display the Export output screen.

4. Type a name for the JPEG file that will contain the graph in the Name of JPEGFile text box.Additional Information: Graphs are available as a .jpeg which is compressed andsuitable for emails or Web pages.

5. Optional: Do the following to export the graph to HTML for use in a Web page:a. Select the Export to HTML check box.b. Optional: Type a title to appear above the graph in the HTML Title above

graph text box.c. Optional: Type comments to appear above the graph in the HTML

comments above graph text box.d. Optional: Type comments to appear below the graph in the HTML

comments below graph text box.6. Click OK.


Creating batch reports and graphs

ObjectiveTo create reports and graphs in batches so you can save time by running themautomatically.

Background informationReports and Graphs can run automatically in batch. Four Admin rules(Hourly_Reports, Nightly_Reports, Weekly_Reports, and Monthly_Reports) run atthe appropriate interval to create reports and graphs that you specified in thecorresponding batch folder. Batch reports and graphs automatically export to a filein the format specified. You can choose to send this file in an email to one or morerecipients.

Before you beginAdmin rules must be running for automatic batch reports and graphs to generate.


Procedure1. Select the report or graph in the hierarchical tree in the left pane of the Tivoli

Reporting and Graphing.2. Click Edit to display the Edit menu.3. Click Add to Batch from the Edit menu.

4. Complete batch information for a report or graph in the following fields:

Title Type the name that is displayed for this report or graph whenmanaging the batch folders.


Additional Information: Choose a unique title to identify the report orgraph in the batch facility. When modifying the batch information for areport or graph, you cannot change its title.

Batch folderType the frequency to create the report or graph.

Additional Information: Choose from the available list or click AddFolder to create a new batch folder. Populating a new batch folder alsorequires you to add a new Admin rule associated with this folder.When modifying the batch information for a report or graph, you cannot change its batch folder.

Output directoryType the destination disk and directory for the report or graph. Clickthe box that contains “...” to browse.

Output formatType the format of the exported report or graph.

.RPT Used by Crystal Reports to translate information.

.RDF Report definition file.

.GDF Graph definition file.

.UDF User defined file.

.View Stored in RM directory & user profile.

.BRG Batch Reports and Graphs.

Output file nameType the name of the exported file. The file extension appears as theoutput format specified.

Email toType the email address of the recipients to receive the exported file inan email.

Note: To email reports and graphs, you must configure IBM TivoliManagement Solution for Exchange to use Microsoft Exchange asits mail service. In Tivoli Enterprise Manager, go to Manage →Configuration. In the Mail Information tab of the TivoliConfiguration Manager, select Microsoft Exchange as the mailservice and enter a Profile name.

If you enter at least one email recipient, you can specify the Subjectand the Body of the email message. You can also specify to delete thefile after it is emailed.

If you want to temporarily suspend the creation of the report or graph,check Exclude from batch cycle. Uncheck the box to resume thecreation of the report.

5. Click OK.

Managing the batch folders

ObjectiveTo add, modify, or remove reports and graphs from the batch folder so you canmanage reports and graphs.





Procedure1. Click Edit to display the Edit drop-down menu.2. Click Manage Batch from the Editdrop-down menu to display the Batch

Reports and Graphs screen.

3. Optional: Click Add Folder to create a new batch folder.

Note: Populating a new batch folder also requires you to add a new Adminrule associated with this folder.

4. Click on a title from the list.5. Do one of the following:

v Add the selected report or graph to the selected batch folder by doing thefollowing:a. Click Add.b. Enter the batch information for the report or graph.c. Click OK.

v Modify the batch information for a report or graph by doing the following:a. Click Modify.b. Make any desired modifications to the batch information for the report or

graph.c. Click OK.

v Remove a report or graph from batch by doing the following:a. Click Remove.b. Click Close to return to the main Report and Graph Manager window.


Customizing views of reports and graphs

ObjectiveTo customize views of reports and graphs so you can tailor the view of the reportor graph to your specifications.

Background informationEach view contains reports and graphs organized in folders in a hierarchical treeview. Each folder can contain other folders, reports and graphs. Each report orgraph can contain user settings for the report or graph.

You can customize an existing view by adding, removing, or reorganizing thereports and graphs contained in the view. You can also create a new empty view,create a copy of a view, or delete a view.



Procedure1. Create a new empty view by doing the following:

a. Right-click the white space in the view.b. Click New.c. Click User view to display the New User View screen.d. Type the name of the new view in the New User View screen.e. Click OK.f. Proceed to Step 2 to add a folder to a view.

2. Add a folder to a view by doing the following:a. Add a new top-level folder to the current view by doing the following:

1) Right-click the white space in the view.2) Select New.3) Select Folder to create a new folder for the top level of the view.4) Type the name of the new folder.

b. Add a folder in an existing folder by doing the following:1) Right-click the existing folder.2) Click Add.3) Click Folder to create a new folder in an existing folder.4) Type the name of the new folder.

Additional Information: You can now add folders in this folder, or you canadd reports and graphs to the folder.

3. Make a copy of a view by doing the following:a. Right-click the white space in the view.b. Click User views.c. Click Copy view as.d. Type the name of the new view in the New User View text box.e. Click OK to save the view and proceed to customization for the view.

4. Delete a view by doing the following:


a. Right-click the white space in the view.b. Click User views.c. Click Delete current user view.d. Click OK to delete the view.

5. Add a report or graph to a folder by doing the following:a. Right-click the folder.b. Click Add.c. Click one of the following:

v Report

—OR—v Graph

d. Select one or more existing report or graph definition files to add to thefolder.

e. Type the name of each report or graph.f. Check the box.g. Click OK.

6. Remove a folder from a view by doing the following:a. Right-click the folder.b. Click Remove.

7. Remove a report or graph from a folder by doing the following:a. Right-click the report or graph.b. Click Remove.

8. Remove a user setting for a report or graph by doing the following:a. Right-click the user setting.b. Click Remove.

9. Rename any element in the view by doing the following:a. Right-click the folder, report, graph, or user setting.b. Click Rename.c. Enter the new name.


Appendix A. Command line

This section contains information on how to use the command line interface (CLI)for IBM Tivoli Management Solution for Exchange.

Using the command line interfaceThe IBM Tivoli Management Solution for Exchange command line executable is theRoboMon.exe file. It is located in the \bin directory under the main installationdirectory. To execute commands, you must add this directory to your path orinclude the path in the command. You can add a directory to your path from theEnvironment tab in the Control Panel system applet.

To simplify use of the command line, add the product’s \bin directory to theWindows NT® directory search path. This can be done through the control panelapplet.

Command line parameters and syntaxThe first parameter specifies the command to execute. Any additional parameterscan be specified in any order.

You do not specify the /c parameter, the command executes on the local computer.

The following characters are used to define the command syntax:

[ ] Parameters in brackets are optional.

{ } Parameters in braces can be repeated zero or more times.

″ ″ You must place double quotes around names that contain spaces. Forexample: C:\> RoboMon /Rs /f "name with spaces.rul"

| You must quote a pipe when you use it in a variable context specification.For example: C:\ > RoboMon /Vw /f variables.var /n disk_full_thresh/c "ABC_PC|C" /t f /v 90.0.

Return valuesA multiple operation command returns values of 0, 1, or 2.

0 The command completed successfully

1 The command failed

2 The command partially failed

Return values 3 through 13 are returned only when you perform a singleoperation, such as a single rule file or system.

3 Invalid command line arguments were used

4 Insufficient command line arguments

5 Could not verify the rule file

6 Rule file does not exist

7 The server on a remote computer is unreachable

195

8 The rule is not running

9 The rule is not asynchronous

10 The rule is already running

11 The rule could not be started

12 An unexpected error occurred

13 An unknown error occurred

A partial failure can be received when a command is executed on two systems andit is successful on one system and fails on the other. When a command is executedfor multiple entities, it continues through the list regardless of whether thecommand is successful or not for each entity on the list.

CommandsThe commands used for IBM Tivoli Management Solution for Exchange areorganized alphabetically and divided into the following sections:

DescriptionA brief description of the command.

CLI syntaxThe command line interface (CLI) syntax.

CLI exampleAn example command line interface (CLI).


RoboMon /Ra

DescriptionAdds a specified range of rule files to the startup rule lists of a specified range ofcomputers.

CLI syntaxRoboMon /Ra

/f rulefile1{,rulefileN}[/c comp1{,compN}]

where:

/f rulefileNSpecifies the rule files added to the startup lists.

/c compNSpecifies the computers where the rule files are to be added.

CLI exampleThe following example adds the c:\myrules.rul rule file to the startup rule list oncomp1:RoboMon /Ra /f c:\myrules.rul /c comp1

Appendix A. Command line 197

RoboMon /Rd

DescriptionDisplays startup rule lists for a specified range of computers.

CLI syntaxRoboMon /Rd

[/c comp1{,compN}]

where:

/c compNSpecifies the computers where the startup rule lists reside.

CLI exampleThe following example displays the startup rule list for comp1 and comp2:RoboMon /Rd /c comp1 comp2


RoboMon /Re

DescriptionExecutes a specified range of asynchronous rules in the rule process for a specifiedrange of computers.

CLI syntaxRoboMon /Re

[/c comp1{,compN}]/n ruleproc

/rrule1 {,ruleN}

where:

/c compNSpecifies the computers where the rules will be executed.

/n ruleprocSpecifies the rule process.

/r ruleNSpecifies the asynchronous rules.

CLI exampleThe following example executes the new_files asynchronous rule in the myrulesrule process:RoboMon /Re /n myrules /r new_files


RoboMon /Rk

DescriptionStops the rule process on a specified range of computers.

CLI syntaxRoboMon /Rk

/n ruleproc

[/c comp1{,compN}]

where:


/c compNSpecifies the computers where the rules process is stopped.

CLI exampleThe following example stops the myrules rule process on comp1:RoboMon /Rk /n myrules /c comp1


RoboMon /Rl

DescriptionLists the running rule processes on a specified range of computers.

CLI syntaxRoboMon /Rl

[/c comp1{,compN}]

where:

/c compNSpecifies the computers where the lists of running rule processes is beinggenerated.

CLI exampleThe following example lists the currently running rule on comp1:RoboMon /Rl /c comp1


RoboMon /Rp

DescriptionObtains the status of the rule process running on a specified range of computers.

CLI syntaxRoboMon /Rp

/n ruleproc

[/c comp1{,compN}]

where:


/c compNSpecifies the computers from which the status of the rule process isobtained.

CLI exampleThe following example obtains the status of the myrules rule process on comp1:RoboMon /Rp /n myrules /c comp1


RoboMon /Rr

DescriptionRemoves a specified range of rule files from the startup lists of a specified range ofcomputers.

CLI syntaxRoboMon /Rr


where:

/f rulefileNSpecifies the rule files removed from the startup list.

/c compNSpecifies the computers from which the rule files are removed.

CLI exampleThe following example removes the c:\myrules.rul rule file from the startup rulelist on comp1:RoboMon /Rr /f c:\myrules.rul /c comp1


RoboMon /Rs

DescriptionStarts a specified range of rule files on a specified range of computers.

CLI syntaxRoboMon /Rs


where:

/f rulefileNSpecifies the rule files started.

/c compNSpecifies the computers on which the rule files are started.

CLI exampleThe following example starts a rule process using the c:\myrules.rul rule file oncomp1:RoboMon /Rs /f c:\myrules.rul /c comp1


RoboMon /Rv

DescriptionVerifies a specified range of rule files and creates a binary rule file, a listing file,and a verify error file.

CLI syntaxRoboMon /Rv

/f rulefile1{,rulefileN}/b binaryfile

/l listfile

/e errorfile

where:

/f rulefileNSpecifies the rule files verified.

/b binaryfileSpecifies the binary rule file created.

/l listfileSpecifies the listing file created.

/e errorfileSpecifies the verify error file created.

CLI exampleThe following example creates the c:\myrules.crl binary rule file from thec:\myrules.rul rule file:RoboMon /Rv /f c:\myrules.rul /b c:\myrules.crl


RoboMon /Sk

DescriptionStops the TCP/IP server on a specified range of computers.

CLI syntaxRoboMon /Sk

[/c comp1{,compN}]

where:

/c compNSpecifies the computers on which the server is stopped.

CLI exampleThe following example stops the TCP/IP server on comp1:RoboMon /Sk /c comp1l


RoboMon /Sp

DescriptionRetrieves the status of the TCP/IP server on a specified range of computers.

CLI syntaxRoboMon /Sp

[/c comp1{,compN}]

where:

/c compNSpecifies the computers on which the server status is retrieved.

CLI exampleThe following example obtains the status of the TCP/IP servers on comp1 andcomp2:RoboMon /Sp /c comp1 comp2


RoboMon /Ss

DescriptionStarts the TCP/IP server on a specified range of computers, retains files for aspecified number of days and sets the event file and the request log file.

CLI syntaxRoboMon /Ss

[/d retdays][/e eventfile][/r logfile][/c comp1{,compN}]

where:

/d retdaysSpecifies the number of days that the event is retained.

/e eventfileSpecifies the event file that is set.

/r logfileSpecifies the request log file that is set.

/c compNSpecifies the computers on which the server is started.

CLI exampleThe following example starts the TCP/IP server on comp1 and sets the event logfile to comp1.evt, the request log file to comp1.req, and event retention days to 7:RoboMon /Ss /e comp1.evt /r comp1.req /d 7


RoboMon /Vd

DescriptionDeletes a specified range of variables from the variable file on a specified range ofcomputers, specifies the level and the context, and prompts for confirmation beforeeach delete.

CLI syntaxRoboMon /Vd

[/i]/f varfile

[/l varlevel]/n var1{,varN}[/x varcontext][/c comp1{,compN}]

where:

[/i] Prompts for confirmation before each delete.

/f varfileSpecifies the variable file from which the variables are deleted.

/l varlevelSpecifies the variable level.

/n varNSpecifies the variables deleted.

/x varcontextSpecifies the variable context.

/c compNSpecifies the computers on which the variables are deleted.

CLI exampleThe following example deletes all variables from the automation.var file thatmatch the low_free_space_param_* pattern and prompts for confirmation beforeeach delete:RoboMon /Vd /f automation.var /n low_free_space_param_* /i


RoboMon /Vp

DescriptionDisplays a specified range of variables from the variable file on a specified rangeof computers and specifies level and context.

CLI syntaxRoboMon /Vp

/f varfile

[/l varlevel]/n var1{,varN}[/x varcontext][/c comp1{,compN}]

where:

/f varfileSpecifies the variable file from which the variables are displayed.


/n varNSpecifies the variables displayed.

/x varcontextSpecifies the variable context.

/c compNSpecifies the computers on which the variables are displayed.

CLI exampleThe following example displays all the variables from the automation.var file thatmatch the low_free_space_param_* pattern:RoboMon /Vp /f automation.var /n low_free_space_param_*


RoboMon /Vw

DescriptionWrites the variable name to the variable file on a specified range of computers;specifies the level, context, and type; and prompts for confirmation before eachwrite.

CLI syntaxRoboMon /Vw

[/i]/f varfile

[/l varlevel]/n varname

/t [i | f | s | t]/v varvalue

[/x varcontext][/c comp1{,compN}]

where:

[/i] Prompts for confirmation before each write.

/f varfileSpecifies the variable file to which the variable name is written.


/n varnameSpecifies the variable name written.

/t [i | f | s | t]Specifies one of the following variable types:

i integer

f floating point

s string

t text

/v varvalueSpecifies the value of the variable.

/x varcontextSpecifies the context of the variable.

/c compNSpecifies the computers on which the variables are written.

CLI exampleThe following example writes the thresh2 variable with a context of comp1, a levelof 0, and an integer value of 100 to the automation.var file:RoboMon /Vw /f automation.var /n thresh2 /x comp1 /t i /l 0 /v 100


RoboMon /Ps

DescriptionSends a message to a pager.

CLI syntaxRoboMon /Ps

/v vendor

/n phone-number

[/i pin][/c password][/p distribution-list][/m message-text][/f message-file][/d debug-file][/1 user-parameter-1][/2 user-parameter-2][/3 user-parameter-3][/4 user-parameter-4]

where:

/v vendorSpecifies the script to use in the pager information line.

/n phone-numberSpecifies the phone number to dial.

/i pin Specifies the personal identification number.

/c passwordSpecifies the password.

/p distribution-listIndicates that the message is queued to a database for queued paging andthe name of the distribution list to receive the page.

/m message-textSpecifies the message to send.

/f message-fileSpecifies the file containing the message to send. You must specify either amessage-text or a message-file, but not both.

/d debug-fileSpecifies the file to which debug information is written.

/N user-parameter-NSpecifies user parameters.

CLI exampleThe following example sends the message, Hello World, to a pager, defined by theTAP script using a telephone number of 5551212 and a personal identificationnumber of 774743. The script is passed COM1 as user parameter 1:RoboMon /Ps /v TAP /n 5551212 /i 774743 /m "Hello World" /1 COM1


Appendix B. Troubleshooting

This appendix includes information on how to troubleshoot problems that canarise during normal operations of IBM Tivoli Management Solution for Exchange.

The following troubleshooting topics are covered in this section:v Installationv Events and databasesv Untrusting domains and workgroupsv General product notesv Miscellaneous

Installation

Installing IBM Tivoli Management Solution for ExchangeWhen you install IBM Tivoli Management Solution for Exchange, theTivoliInstallLog.txt file is created in the IBM Tivoli Management Solution forExchange installation directory. If you experience any errors or problems duringinstallation, the contents of this file can help diagnose the cause of the problems.

The installation creates several registry keys. Use the following procedure to ensurethat all necessary registry keys are selected:1. From the registry editor, select the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\TEMS

2. From the registry menu, select either Export registry file or Save subtree as,and save to a file.

3. Repeat the process with the following six registry keys:HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_esrvHKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_evtsrvHKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_licsrvHKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_revtsrvHKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_RuleHKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_Tcp

Important information about your computer can be displayed by executing theMsinfo32.exe file, normally found in the C:\Program Files\CommonFiles\Microsoft Shared\MSInfo directory.

Starting Tivoli servicesThe most common reasons that the Tivoli services do not start are the account andpassword pair problems or insufficient privileges for the Tivoli services account.The Tivoli services must run from an account with administrator privileges. Afterthe installation, you can change the account and password, and start each of theTivoli services using the Services applet in the Control Panel.

Starting Tivoli Event ServiceUnder some circumstances, the Tivoli Event Service fails to start, often indicatingan error code of 2140.

213

Do the following to ensure that the Tivoli Event Service correctly opens an OpenDatabase Connectivity (ODBC) system data source named RoboMon EventDatabase:1. Click the Data Sources applet from the Control Panel.2. Check that the RoboMon Event Database data source exists in the System

DSN tab.3. Double-click RoboMon Event Database in the System DSN tab.4. Check that the EventDatabase.mdb database file is in the IBM Tivoli

Management Solution for Exchange \event\database directory.5. Check that the RoboMon Event Database data source does not exist in the

User DSN tab.6. Go to the following registry editor if the previous information is correct:

HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Debug

7. Create the following registry keys and value entries:

Note: Be cautious when modifying the Windows NT® registry.

Table 17. Tivoli Event Service error tracking

Key ErrorTracking

Value Entry Name RoboMon_evtsrv

Data Type DWORD

Value 1

Table 18. Tivoli Event Service instrumentation

Key Instrumentation


Data Type DWORD

Value 3

8. Restart the Tivoli Event Service from the Services applet of Control Panel.9. Send the following two files to your support representative:

v In the IBM Tivoli Management Solution for Exchange \logs directory, themost recent daily Event Server log file. For example:Event_Server_1999_01_15.log

v In the IBM Tivoli Management Solution for Exchange \debug directory, theRoboMon_evtsrv_ErrorTracking.log file.

Simple Network Management ProtocolYou must install the Simple Network Management Protocol (SNMP) for IBM TivoliManagement Solution for Exchange to collect TCP/IP statistics and to execute theSNMP_TRAP and SNMP_SET actions. If SNMP is installed after IBM TivoliManagement Solution for Exchange was installed, you must reinstall IBM TivoliManagement Solution for Exchange. See Chapter 2, “Installing IBM TivoliManagement Solution for Exchange” on page 5 for more information.

Open Database ConnectivityYou must install the Open Database Connectivity (ODBC) for IBM TivoliManagement Solution for Exchange to collect statistics from the ODBC data source,


to export data to an ODBC data source, or to execute an SQL statement. Inaddition, all database drivers must be compatible with the version of ODBCinstalled.

Error messages during remote installationIf your account does not have domain administration privileges, you receive thefollowing error when attempting a remote installation:The following computers did NOT install successfully:

ServerName - (An Unexpected Error has occured)

The following is the detailed message for the above error:Detail Message for ServerName: (find_install_drive) in dllmain_localinstall.cpp,

line 1275An Unexpect Error has occurred find_install_drive in dllmain_localinstall.cpp,

line 1268The network path was not found. (System Error 53) GetDiskFreeSpaceEx

If you attempt a remote installation and the IBM Tivoli Management Solution forExchange installation service is still active from previous attempts, you receive thefollowing error:The following computers did NOT install successfully:

ServerName - (An Unexpected Error has occurred)

The IBM Tivoli Management Solution for Exchange installation service cannotdelete itself, so it disappears after a reboot.

Setting up Microsoft ExchangeFor the IBM Tivoli Management Solution for Exchange mail action to work usingMicrosoft Exchange, you must perform the following manual configuration steps:1. Install the Microsoft Exchange client.2. Create a Tivoli mailbox with the Microsoft Exchange Administrator.3. Create a domain level account with administrator privileges named Tivoli

with the User Manager.4. Configure IBM Tivoli Management Solution for Exchange to use the Tivoli

account by entering the domain name, account name, and password.5. Log off and log back on under the new Tivoli account.6. Create a Microsoft Exchange profile for IBM Tivoli Management Solution for

Exchange to use. This is typically performed by using the mail applet fromthe Control Panel or by clicking the Inbox icon. See your Microsoftdocumentation for further details.

7. Start the Tivoli Configuration Manager.8. Click Next until you see the Mail Information tab.9. Enter the Microsoft Exchange profile name in the Profile Name field.

10. Click Finish.11. Exit IBM Tivoli Management Solution for Exchange.12. Log off of the Tivoli account.

These steps are required for the collection of Microsoft® Exchange mailbox andfolder statistics and you must perform them on every computer where the mailaction is used.

Appendix B. Troubleshooting 215

Events and databases

Tivoli Event Service - Jet databaseA problem in the Jet database driver installed with Microsoft® Access 97 can causedatabase queries to hang when running on a dual processor computer. You canexperience this problem if you run IBM Tivoli Management Solution for Exchangeon a dual processor computer, and the Tivoli Event Configuration Manager is notresponding or events are not being forwarded correctly. You can resolve thisproblem by installing a newer version of the Jet database driver. Refer to yourMicrosoft documentation for details.

Tivoli Event Service using excessive central processing unitcapacity

When the Tivoli Event Service uses excessive central processing unit (CPU)capacity, it is often due to exceptionally large quantities of events from theWindows NT event log or large quantities of Simple Network ManagementProtocol (SNMP). If this is the case, you can disable processing of these eventsusing the Tivoli Event Configuration Manager.

Do the following to disable the processing of events:1. Run Tivoli Event Configuration Manager.2. Set the Debug mode to 3 for your computer.3. Send the most recent .log file in this directory to your support representative.

Additional Information: When you set the Debug mode to 3, the Tivoli Event Servicelogs information about its behavior to a daily log file in the IBM TivoliManagement Solution for Exchange \event\logs directory.

Large event databaseThe size of the IBM Tivoli Management Solution for Exchange event database cangrow large from consolidating events from many computers over time. See“Converting IBM Tivoli Management Solution for Exchange databases to SQLServers” on page 219 or “Compacting IBM Tivoli Management Solution forExchange databases” on page 220 for details on controlling the size of yourdatabase.

Routing events across the networkWhen you run the Tivoli Event Monitor from any computer, you see the eventsfrom all computers that have been configured to forward events to this computer.The forwarding of events from one computer to another is specified in the TivoliEvent Configuration Manager. You must configure the IBM Tivoli ManagementSolution for Exchange to run from a domain account with administrator privilegesin order to forward events from one computer to another. It cannot be configuredto run from the local system account.

Diagnosing problems in the Tivoli Remote Event ServiceDo the following to diagnose problems in the Tivoli Remote Event Service:1. Click the Services applet from the Control Panel.2. Check that the Tivoli Remote Event Service is running on the computer that is

receiving events.3. Stop and restart the Tivoli Remote Event Service if it is running.


4. Go to the following registry editor if the Tivoli Remote Event Service is notrunning:HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Debug

5. Create the following registry keys and value entries:

Note: Be cautious when modifying the Windows NT registry.


Key ErrorTracking

Value Entry Name RoboMon_revtsrv

Data Type DWORD

Value 1

6. Restart the Tivoli Remote Event Service from the Services applet of ControlPanel.

7. Send the following file to your support representative:v In the IBM Tivoli Management Solution for Exchange \debug directory, the

RoboMon_revtsrv_ErrorTracking.log file.

Diagnosing problems in the Tivoli Event ServiceDo the following to diagnose problems in the Tivoli Event Service:1. Go to the following registry editor:

HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Debug

2. Create the following registry key and value entries:

Note: Be cautious when modifying the Windows NT registry.


Key ErrorTracking


Data Type DWORD

Value 1

3. Run the Tivoli Event Configuration Manager.4. Set the Debug level to 3 for both the computer sending events and the

computer receiving events.5. Restart the Tivoli Event Service on each computer.6. Send the following two files to your support representative:

v In the IBM Tivoli Management Solution for Exchange \logs directory, themost recent daily Event Server log file. For example:Event_Server_1999_01_15.log

v In the IBM Tivoli Management Solution for Exchange \debug directory, theRoboMon_evtsrv_ErrorTracking.log file.


Untrusting domains and workgroups

Untrusting domainsIBM Tivoli Management Solution for Exchange succeeds between untrustingdomains when the account exists locally on the target machine and the passwordmatches, but operations fail between untrusting domains when the followingsituations occur:v The account does not exist locally on the target machine.v The account exists locally on the target machine, but the password does not

match.

Management functionsTo perform management functions between untrusting domains, the account andpassword pair used to log on to the machine being used to administer IBM TivoliManagement Solution for Exchange must exist as a local account and passwordpair on the remote machine. It is critical that this account exist as a local accountand password pair on the remote machine, as opposed to a domain account in theremote, untrusting domain. Because the domains do not trust each other, domainaccounts are invalid.

Event and performance data forwardingTo forward events and performance data between untrusting domains, the accountand password pair assigned to the Tivoli services on the machine forwardingevents and performance data must exist as a local account and password pair onthe remote machine to be administered. It is critical that this account exist as alocal account and password pair on the remote machine, as opposed to a domainaccount in the remote, untrusting domain. Because the domains do not trust eachother, domain accounts are invalid.

One-way trust relationshipsIBM Tivoli Management Solution for Exchange succeeds in partially trustingenvironments when the account exists locally on the target machine and thepassword matches, but operations fail between untrusting domains when thefollowing situations occur:v The account does not exist locally or at the domain level on the target machine.v The account exists locally on the target machine, but the password does not

match.

Management functionsWhen managing a remote, trusting domain, as with untrusting domains, theaccount and password pair with which the user logs on is the key factor. Thelogon account and password pair must exist on the local machine or as a domainlevel account and password pair. If an account with the same user name but adifferent password exists on the local machine, the operation fails, regardless ofwhether the account and password pair is a valid domain account. Additionally,the information in the Tivoli Event Configuration Manager interface can beaccessed only if the account and password pair exists on the local machine. If adomain account is being used, the event configuration information for the remotemachine cannot be accessed. Events and performance data can still be forwarded,but the information displayed in the Tivoli Event Configuration Manager interfacecannot be accessed.

When attempting to manage the trusted domain from the trusting domain in aone-way trust relationship, the rules of operation for untrusting domains applies.


Event and performance data forwardingWhen forwarding events and performance data from a trusted domain to atrusting domain, as with untrusting domains, the account and password pair thatis assigned to the Tivoli services is the key factor. The account and password pairused by the Tivoli services must exist on either the local machine or as a domainlevel account and password pair. If an account with the same user name butdifferent password exists on the local machine, the operation fails, regardless ofwhether the account and password pair is a valid domain account.

When attempting to forward events from the trusting domain to the trusteddomain in a one-way trust relationship, the rules of operation for untrustingdomains applies.

Workgroups

Installing to computers in a workgroupWhen installing IBM Tivoli Management Solution for Exchange on computers thatare part of a workgroup, you must provide a domain name, account name, andpassword for the Tivoli services for each computer. Use the name of the localcomputer for the domain name, as opposed to the name of the workgroup. Theaccount and password pair must exist on the local computer.

Managing remote computers in a workgroupThe account and password pair with which the user logs on must exist as a localaccount and password pair on the remote machine to enable management ofremote computers within a workgroup.

Forwarding events and performance data in workgroupsThe account and password pair used by the Tivoli services must exist as a localaccount and password pair on the remote machine when forwarding events withinworkgroups.

Managing event and performance data forwarding between aworkgroup and a domainThe same rules for managing and forwarding between untrusting domains applywhen managing event and performance data forwarding between a workgroupand a domain.

General product notes

IBM Tivoli Management Solution for Exchange databases

Converting IBM Tivoli Management Solution for Exchangedatabases to SQL ServersIBM Tivoli Management Solution for Exchange event and performance databasesare initially installed as Jet databases. If you are consolidating events andperformance data from many computers, your databases can become too large fora Jet database. In this case, you can convert one or both of these databases to anSQL Server. Use one of the following procedures to convert your database to anSQL Server:

Converting your event database to an SQL Server, Version 6.5:

1. Create a database using SQL Server Enterprise Manager. Refer to yourMicrosoft documentation for more details.


2. From the SQL Server Enterprise Manager, highlight the newly created databaseand run the RoboMon_EventDatabase_CreateTables.SQL script to create thetables. This script is located in the IBM Tivoli Management Solution forExchange \config directory.

3. Update the ODBC system RoboMon Event Database data source to point toyour newly created SQL Server database.

Converting your event database to an SQL Server, Version 7:

1. Create a database using the SQL Server Enterprise Manager. Refer to yourMicrosoft documentation for more details.

2. From the SQL Server Enterprise Manager, highlight the newly created databaseand run the RoboMon_SQL7_EventDB_CreateTables.SQL script to create the tables.This script is located in the IBM Tivoli Management Solution forExchange \config directory.


Converting your performance database to an SQL Server, Version 6.5 or SQLServer, Version 7:

1. Create a database using the SQL Server Enterprise Manager. Refer to yourMicrosoft documentation for more details.

2. From the SQL Server Enterprise Manager, highlight the newly created databaseand run the RoboMon_PerformanceDatabase_CreateTables.SQL script to createthe tables. This script is located in the IBM Tivoli Management Solution forExchange \config directory.


Compacting IBM Tivoli Management Solution for ExchangedatabasesIBM Tivoli Management Solution for Exchange can automatically compact yourevent and performance databases with the RoboMon_compact.exe utility program.The Compact_Databases Admin rule does this automatically every night. TheRoboMon_compact.exe utility program is executed from a command line. You canspecify the following switches:

Note: Compacting databases can be performed only for Jet databases.

/E Compact the event database

/P Compact the performance database

/A Compact the event database and the performance database

/V Verbose mode

IBM Tivoli Management Solution for Exchange and TCP/IP

Network adapterIBM Tivoli Management Solution for Exchange uses TCP/IP network services. Youmust install a network adapter and the TCP/IP network protocol to use thisservice. Consult with your Windows NT® system administrator if you do not havea network adapter.

TCP/IP host namesThe computer name and the TCP/IP host name for each computer must beidentical for IBM Tivoli Management Solution for Exchange to run correctly. Set


these names through the Network applet available from the Control Panel. Set thecomputer name through the main screen of the Network applet and the TCP/IPhost name set from the TCP/IP protocol DNS configuration screen.

Windows NT automatically configures the computer name and the TCP/IP nameto be the identical unless the computer name contains a character that is illegalunder the DNS standard. In this case, the invalid character is replaced by theclosest legal character. Sometimes the TCP/IP host name can be changed to includethe illegal character. Sometimes you must change the computer name.

Note: The underscore character (’_’) is illegal in DNS and is substituted with adash (’-’) character.

TCP/IP port numbersIBM Tivoli Management Solution for Exchange reserves the TCP/IP port numbers5617-5700 for its exclusive use. If you are using a firewall, you must allow accessto these port numbers through the firewall. Ports 5617-5624 are used by theTCP/IP Service and the Rule Service, port numbers beginning with 5625 are usedby rule processes and are assigned in ascending order, and ports 5698-5700 areused by the Enterprise Service, the Event Service, and the Remote Event Service.

Forcing remote procedure call connections to use TCP/IPWhen a IBM Tivoli Management Solution for Exchange service on a remotecomputer performs a task on behalf of a user interface component, a remoteprocedure call (RPC) connection is made to perform the task. If the computer isspecified using an IP address, TCP/IP is used to establish the connection.Otherwise, a named pipe is used. You can force IBM Tivoli Management Solutionfor Exchange to always use TCP/IP when establishing an RPC connection bycreating the TcpIpForRpc registry value in the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Config

The data type must be DWORD, and the value must be 1. If this value entry doesnot exist, or if it exists with a value of 0, IBM Tivoli Management Solution forExchange uses the default mechanism of a named pipe or TCP/IP to establish anRPC connection.

IBM Tivoli Management Solution for Exchange rules

Execution of multiple one-shot rulesWhen a rule file contains multiple one-shot rules, they each execute completely, insequence. The collection for the first rule is performed, the rule is executed andany actions are performed. Then the second rule’s collection is performed, it isexecuted, and so forth.

Variable usage in asynchronous rulesWhen you execute an asynchronous rule, the memory is freed for any variablesthat you use in the rule. This means that the value of a variable set in anasynchronous rule is not available to other rules. To make the value available toother rules, you must write the variable to a file. This behavior is unique toasynchronous rules.

IBM Tivoli Management Solution for Exchange servicesA service is a program that can start up automatically when the system is bootedand can run without a user being logged on. All IBM Tivoli Management Solutionfor Exchange services are configured for automatic startup and are normally


running. They can be accessed directly through the Services applet in the ControlPanel. IBM Tivoli Management Solution for Exchange installs the followingservices:v TCP/IP Servicev Rule Servicev Event Servicev Remote Event Servicev Enterprise Manager Service

Uninstalling IBM Tivoli Management Solution for ExchangePerform the following procedure to uninstall IBM Tivoli Management Solution forExchange:1. Open the Control Panel by doing the following:

a. Click Start in the Windows taskbar to display the Start menu.b. Select Settings from the Start menu to display the Settings menu.c. Select Control Panel from the Settings menu to display the Control Panel

menu.2. Click the Add/Remove Programs icon.3. Select IBM Tivoli Management Solution for Exchange.4. Click Add/Remove.5. Click Yes to confirm uninstallation.

The uninstall operation removes all files in the IBM Tivoli Management Solutionfor Exchange directories.

Miscellaneous

Tivoli Statistics Builder

Issues with Tivoli Enterprise Manager ServiceThe Tivoli Statistics Builder uses the Microsoft RegQueryValueEx function with thepredefined HKEY_PERFORMANCE_DATA key to collect Windows NT® performanceobjects and counters. Under some circumstances this function can cause an accessviolation in the Tivoli Enterprise Manager service. This access violation occurswhen a Microsoft dynamic link library (DLL) used to retrieve data for a specificperformance object, known as a performance monitor extension, is corrupted.

Do the following when you receive an access violation:1. Restart the Tivoli Enterprise Manager service from the Services applet of

Control Panel.2. Determine which DLL is corrupt.3. Rename the DLL to ensure that this access violation does not occur again.

Note: The SQLCTR60.DLL file is often corrupted. This file is referenced by the valueentry of Library in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer\Performance

registry key.

Do the following to determine if the SQLCTR60.DLL file is corrupt:


Note: This procedure disables the collection of performance information in all SQLServer performance objects. Refer to your Microsoft documentation fordetails on how to resolve this issue.

1. Look in the following registry key to find the SQLCTR60.DLL file:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer\Performance

2. Rename the SQLCTR60.DLL file to XSQLCTR60.DLL.

Issues with Microsoft Internet Information ServerThe Microsoft® Internet Information Server, Version 4.0, can prevent the TivoliStatistics Builder from seeing performance monitor objects provided by InternetInformation Server. The Internet Information Server can also cause Tivoli RuleDesigner to produce errors when creating certain actions and when saving a rule.Refer to your Microsoft documentation for details on how to resolve these issues.

Microsoft® Exchange mail actionMicrosoft Exchange can cause the Tivoli mail action to fail when IBM TivoliManagement Solution for Exchange is configured to use Microsoft® Exchange forthe mail action. The action error log file, located in the IBM Tivoli ManagementSolution for Exchange \logs directory contains the error Unknown MAPI error.Refer to your Microsoft documentation for more details on how to resolve thisissue.

If you experience this problem, do one of the following:v Install Microsoft Exchange, Version 5.5, Service Pack 1v Configure IBM Tivoli Management Solution for Exchange to use SMTP, instead

of Microsoft® Exchange, for the mail action.v Disable IBM Tivoli Management Solution for Exchange so it does not collect

Asynchronous Communications Device Interface port statistics by creating theregistry value COMDisable with a data type of DWORD and a value of 1 in thefollowing registry key:HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Config

Performing this operation prevents you from collecting AsynchronousCommunications Device Interface port statistics, and prevents the Microsoft®

Transaction Server rules from operating correctly.

After making one of the previous changes, you must restart the rule process orprocesses before the mail action begins working.

IBM Tivoli Management Solution for Exchange rate statisticsRate statistics can occasionally exceed 100%. This occurs only when a rule is runon a very short interval and is caused by an inherent inaccuracy in the Windows®

NT timing mechanisms. The effect becomes insignificant with intervals over 30seconds.

Central processing unit statistics on Windows 2000 computersOn Windows® 2000 computers, the value of the following CPU usage statisticsreturns zeros:v CPU_BUSY_PCT

v CPU_DPC_PCT

v CPU_INTERRUPT_PCT

v CPU_PRIVILEGED_PCT


v CPU_USER_PCT

The total CPU usage can be calculated from the sum of the following processorstatistics across all processors:v PROCESSOR_BUSY_PCT

v PROCESSOR_PCT_DPC_TIME

v PROCESSOR_INTERRUPT_PCT

v PROCESSOR_PRIVILEGED_PCT

v PROCESSOR_USER_PCT

Windows NT® errorsA dialog box reading There is no disk in the drive. Please insert a disk into driveX: is occasionally displayed on some Windows NT® machines. IBM TivoliManagement Solution for Exchange does not continue until the dialog box isdismissed. Use one of the following workarounds to resolve this error:v Insert a disk into drive X.v Log on using a similarly privileged account other than Administrator. The dialog

box is displayed only when the current or last user is logged on using theAdministrator account.

DISK_READ_PCT and DISK_WRITE_PCT statistic valuesThe values of the DISK_READ_PCT and DISK_WRITE_PCT statistics are often zerowhen there has been disk activity. These statistics are collected from the DiskReads/ sec and Disk Writes/ sec values and counters in the Windows NTperformance database, which are incorrect values.

EVT_DATE and EVT_TIME statistic valuesThe values of the EVT_DATE and EVT_TIME statistics can be incorrect in sometime zones. This is due to a problem with the localtime function.

Error when loading a dynamic link library during an upgradeinstallation

You might receive an error when loading the MSJTER40.DLL file during an upgradeinstallation. Dismiss this error and continue the installation.

Adding columns or tables to performance databasesDo the following if you added rules to archive data to new columns or new tablesin the performance database:1. Modify the PerformanceEmpty.mdb file in the IBM Tivoli Management Solution

for Exchange \config directory.2. Use the following command to run the database compaction program that

converts and compacts your performance database:RoboMon_compact /P

Security for IBM Tivoli Management Solution for Exchangefiles

You can write IBM Tivoli Management Solution for Exchange rules to performactions on the local computer or on a remote computer. To prevent certain usersfrom writing or starting rules, install IBM Tivoli Management Solution forExchange on an NTFS file system so you can restrict access to rule files and


executable files. For example, you can require administrator privileges for key filessuch as RoboMon_Emgr.exe, RoboMon_esrv.exe, and RoboMon_rulsrv.exe. You canalso restrict access to all the files on key subdirectories such as the rules andprocesses subdirectories in the IBM Tivoli Management Solution for Exchangemain directory.

Maximum number of IBM Tivoli Management Solution forExchange rule processes

There is a maximum of 50 rule processes for each computer.

IP address for a computer nameAn IP Address can be specified in place of a computer name or specified after acomputer name. In both cases, IBM Tivoli Management Solution for Exchange usesthe IP Address instead of the computer name.

Defining timeout values for IP_REACHABLEBy default, IBM Tivoli Management Solution for Exchange uses a timeout value of5 seconds when determining the value of the IP_REACHABLE statistic. If thecomputer is not reachable in this length of time, it is considered unreachable andthe value of the IP_REACHABLE statistic is set to zero. You can modify thistimeout value by creating a registry value entry named IPTimeToReach in thefollowing registry key:HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Config

The data type must be DWORD, and the value must be the timeout value (inseconds) to use to determine if a computer is reachable. If this value entry does notexist, a timeout value of five seconds is used.

Defining community name and timeout value for DHCPstatistics

By default, IBM Tivoli Management Solution for Exchange uses a community nameof public and a timeout value of 3 seconds when collecting DHCP statistics. Youcan modify this behavior by creating registry value entries namedDHCPCommunity and DHCPTimeout in the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Config

The data type for DHCPCommunity must be String, and the data type forDHCPTimeout must be DWORD. The value of DHCPTimeout must be the timeoutvalue in seconds.

Large icon viewIf you are using the large icon view in the source rule display of the TivoliEnterprise Manager main window, the full name of some or all of the source rulesmight not display because your icon spacing setting is too small. If you arerunning Windows NT, Version 4.0, you can address this problem by performingthe following steps:1. Position the pointer anywhere on the background of the Windows NT desktop,

click the right mouse button and select the Properties menu item.2. Select the Appearance tab.3. Find the Item drop-down list and select Icon Spacing (Horizontal).4. Use the spin buttons on the right to increase the spacing size.


5. Click OK.6. Start or restart the Tivoli Enterprise Manager.7. Repeat the process if the results are still not satisfactory.


Appendix C. Rules syntax

Structure of the rulesThis section describes the features and capabilities of Tivoli rules. A Tivoli rule iscomposed of four basic elements: conditions, actions, schedules, and selections. Therule is structured to look for a condition on the system and at least one action toperform based on the evaluation of the condition. The schedule and selection of arule determine when and on which entities the rule is executed.

Tivoli rules are written in rule files. All rules can be placed in a single rule file orseveral rule files can be used for organize your rules. See Chapter 5, “Managingrules” on page 65 and Chapter 7, “Working with the Tivoli Rule Designer” on page81 for more information on rules.

ConditionsThe CONDITION statement contains a CONDITION expression that evaluates toTRUE or FALSE by IBM Tivoli Management Solution for Exchange. If a rule doesnot include a CONDITION statement, it always evaluates to TRUE. Conditionsrange from simple statements to highly sophisticated tests based on a variety ofthe following items:

StatisticsIBM Tivoli Management Solution for Exchange provides over 1,400statistics that can be used in condition testing to monitor conditions andevents on your system.

VariablesUnlike a statistic, a variable’s value can be set to a specific value oraccording to a formula specified in a rule. Variables provide programmingcapabilities, pass information between different rules, and enable you tosave information across reboots. Variables are global in nature; the value ofany variable in one rule is available to all other rules.

OperatorsIn CONDITION expressions, arithmetic (+ , - , * , / , % ), logical (NOT,AND , OR , XOR ), and relational (= , > , >= , < , <= , <> ) operators areused to perform calculations, determine percentages, test multiple orcompound conditions, and compare statistics to a numerical value. Thefollowing are examples of CONDITION expressions:v Variable X exceeds the value of variable Y.v Statistic B equals zero AND variable Z exceeds a threshold.v Statistics A and B added together exceed twenty.v Variable X OR variable Y equals or exceeds value of statistic C.

FunctionsFunctions are also available for manipulation of statistics and variables.Functions provide capabilities such as: sums, averages, and othercumulative values across multiple entities; sums and averages across time;and manipulation of string statistics such as file specifications.

Event correlationIBM Tivoli Management Solution for Exchange is capable of eventcorrelation, which enables the software to diagnose a problem by

227

evaluating multiple conditions with logical and relational operators. Forexample, a database server process that experiences heavy CPU usage atthe same time that the network experiences excessive traffic indicates anexcessive number of remote clients. IBM Tivoli Management Solution forExchange can evaluate both conditions and perform a specified series ofactions to correct the problem.

Event correlation can also be implemented through rules that interact withone another. For example, the action of one rule can execute another rulethat evaluates a related problem.

The following are examples of simple conditions:v CPU busy percentage exceeds a threshold.v A named process is missing.v Free space is below a minimum value.v A file is growing rapidly.

The flexibility of CONDITION statements enables IBM Tivoli Management Solutionfor Exchange to accurately diagnose a broad range of site-specific problems,measure the urgency of a situation, and implement corrective actions appropriateto specific circumstances. If a rule evaluates entities such as processes or files, IBMTivoli Management Solution for Exchange automatically performs iteration toevaluate the condition for each entity.

CONDITION statementDescription

The CONDITION statement defines a rule condition for IBM TivoliManagement Solution for Exchange to monitor. IBM Tivoli ManagementSolution for Exchange evaluates the CONDITION statement to evaluate arule. When statements are evaluated, a non-zero value is interpreted asTRUE and a zero value is interpreted as FALSE. The CONDITIONstatements are optional, but when the rule does not include a CONDITIONstatement, it is interpreted as having a CONDITION expression thatalways evaluates to TRUE. The CONDITION statement can appear onlywithin RULE definitions and cannot be named.

The following is a list of ACTION types that are executed when theCONDITION statement is evaluated:

ACTIONActions that follow this statement are executed when the conditionevaluates to TRUE. The ACTION statement executes one time foreach entity and for each rule.

CLOSE_ACTIONActions are executed the first time the rule is FALSE after beingTRUE. The CLOSE_ACTION statement executes one time for eachentity and for each rule.

EPILOGUE_ACTIONActions that follow this statement are executed after everythingelse executes for the rule. The EPILOGUE_ACTION statementexecutes whether the condition is TRUE or FALSE and one time foreach rule.


FALSE_ACTIONActions that follow this statement are executed when the conditionevaluates to FALSE. The FALSE_ACTION statement executes onetime for each rule.

NEW_ACTIONActions are executed the first time the rule is TRUE. TheNEW_ACTION statement executes one time for each rule.

PROLOGUE_ACTIONActions that follow this statement are executed before anythingelse executes for the rule. The PROLOGUE_ACTION statementexecutes whether the condition is TRUE or FALSE and one time foreach rule.

TRUE_ACTIONActions that follow this statement are executed when the conditionevaluates to TRUE. The TRUE_ACTION statement executes onetime for each entity and for each rule.

UPDATE_ACTIONActions are executed the second and each subsequent time the ruleis TRUE. The UPDATE_ACTION statement executes one time foreach entity and for each rule.

Note: An entity is dependent on what information is being collected. Forexample, a file or a process are both entities.

Syntax[CONDITION Expression]

ExamplesThe following example tests for the value of the FILE_DACL_EXISTSstatistic to be equal to 0:CONDITION FILE_DACL_EXISTS = 0

The following example tests for the size of a file to be greater than theaverage size of all of the files collected:CONDITION FILE_SIZE_BYTES > AVG$(FILE_SIZE_BYTES)

ExpressionsExpressions are used in the CONDITION, CALCULATE, IF, and STATISTICstatements. Three basic data types can be used in expressions: integer, floatingpoint, and string. When a string is used in an expression position that requires anumber, the string is converted to a numeric value according to the followingrules:v When the string is an ASCII number, that number is used.v When the string is not an ASCII number, the first letter is checked. If the letter is

one of Y, y, T, or t, a value of 1 is used; otherwise a value of 0 is used.

If a floating point number is used when an integer is required, the floating pointnumber is converted to an integer. If the floating point value is outside the legalrange of values for an integer, a value of 1 or -1 is used. The value is dependent onwhether the original value is positive or negative. If a number is used when astring is required, the ASCII representation of the number is used as the stringvalue.

All items in the expression are assumed to be statistics, user-defined statistics,variables, or constants. The operands must be statistic names, user-defined statistic

Appendix C. Rules syntax 229

names, variable names, numeric constants, or string constants that are contained inquotes. The statistic and variable names must not be enclosed in braces ({}).Variable values are retrieved from the rule engine memory structures. If thevariable does not exist in these structures, it is looked for in the default variablefile. If it is not in the default file, a value of zero is used.

The following example shows that the expression is true if the size of a file isgreater than the average size of all of the files collected:FILE_SIZE_BYTES > AVG$(FILE_SIZE_BYTES)

Expression functionsThe following functions can be used in expressions:

ASCII$(string)Returns the ASCII value of the first character in the passed string variable.

The following example evaluates to 65:

ASCII$("ABC")

AVG$(statistic [,context])Computes the average value of the specified statistic across all entities thatmatch the specified context variable. Context can be a single value or caninclude wildcards and lists. If the context results in a single value, theAVG$ is the same as the original value. For this function to provide anyservice, the context must contain a list or wildcards must not be specifiedat all.

The following example returns the average size in bytes of all disks:

AVG$(DISK_SIZE_BYTES)

The following example returns the average size in bytes of disks 0 and 1:

AVG$(DISK_SIZE_BYTES, "0,1")

CHAR$(integer-value)Returns a string consisting of one character equal to the passed ASCIIinteger value. If the passed integer value is not in the range 0 to 255, a nullstring is returned.

The following example evaluates to :

CHAR$(66)

CUM$(statistic, type [,context])Computes the requested type of value across all intervals for the specifiedstatistic. The AVERAGE, MINIMUM, MAXIMUM, and SUM types can berequested and the context can be a single value or can include wildcardsand lists.

The following example returns the minimum number of bytes for all disksacross all intervals:

CUM$(DISK_SIZE, MINIMUM )

The following example returns the average number of bytes for all disksacross all intervals:

CUM$(DISK_SIZE, AVERAGE)

CUR_DATE$(component)Returns the specified component from the current date and time. Thecomponent must be a variable name or a quoted string. The legal valuesfor the component include: DAY, MONTH, MONTH_NAME, YEAR,


HOUR, MINUTE, SECOND, DAY_OF_WEEK, DAY_OF_WEEK_NAME,DATE, TIME, DATE_TIME, DATE_ASCII, TIME_ASCII, andDATE_TIME_ASCII.

The following example evaluates to 8 (assuming that the current date isAugust 1, 1993) :

CUR_DATE$("MONTH")

The following example evaluates to ″AUGUST″:

CUR_DATE$("MONTH_NAME")

CVTFI$(number)Converts a floating point number to an integer. If the floating pointnumber exceeds the limits of an integer value, the return value is 1 whenthe floating point number is positive and -1 when the floating pointnumber is negative.


CVTFI$(123.45)

CVTFS$(number)Converts a floating point number to a string. The number is formattedwith a maximum of 10 decimal places.

The following example evaluates to 100.98:

CVTFS$(100.980)

CVTIF$(number)Converts an integer to a floating point number.


CVTIF$(1023)

CVTIS$Converts an integer to a string.

The following example evaluates to the 2034 string:

CVTIS$(2034)

CVTSF$(string)Converts a string to a floating point number. If the string is a valid ASCIIfloating point number, the number is the return value. If the string is not avalid ASCII number, the first character of the string is examined. If the firstcharacter is T, t, Y, or y, the return value is 1.0; if the first character is anyother character, the return value is 0.0.


CVTSF$("123.456")


CVTSF$("TEST")


CVTSF$("STRING")

CVTSI$(string)Converts a string to an integer. If the string is a valid ASCII integernumber, the number is the return value. If the string is not a valid ASCII


number, the first character of the string is examined. If the first character isT, t, Y, or y, the return value is 1; if the first character is any othercharacter, the return value is 0.


CVTSF$("123")


CVTSF$("TEST")


CVTSF$("STRING")

DATE$(number, component)Returns the specified component from a passed date. The component mustbe a variable name or a quoted string. The legal values for the componentinclude: DAY, MONTH, MONTH_NAME, YEAR, HOUR, MINUTE,SECOND, DAY_OF_WEEK, DAY_OF_WEEK_NAME, DATE, TIME,DATE_TIME, DATE_ASCII, TIME_ASCII, and DATE_TIME_ASCII. Thevalue of the number is a Tivoli numeric date, such as the value of theDATE statistic.


DATE$(34812, "DAY")

EDIT$(string, edit-options)Returns a string that is an edited version of the passed string. The editoptions are specified as string containing a comma separated list. In thecase of conflicting options, the last option specified is used. The legal editoptions are: LOWER_CASE, UPPER_CASE, NO_LEADING_SPACES,NO_TRAILING_SPACES, ONE_SPACE, and NO_SPACES.

The following example evaluates to ABCD:

EDIT$("A B C D", "UPPER_CASE,NO_SPACES")

ENVIRONMENT$(name)Returns the value of the specified environment variable. The name must bea variable name or a quoted string.

The following example evaluates to the value of the HOME registry entry:

ENVIRONMENT$(″HOME″)

FIELD$(string, delimiter, number)Returns a string, which is the field specified by the integer field numberfor the passed string and delimiter. The delimiter can be more than a singlecharacter.

The following example returns WED:

FIELD$("MON\TUE\WED\THU\FRI\SAT\SUN", "\", 3)

FIELD_COUNT$(string, delimiter)Returns an integer, which is the number of fields in the passed stringbased on the passed field delimiter. The delimiter can be more than asingle character. If the delimiter does not appear in the string and thestring is not null, 1 is returned.


FIELD_COUNT$("MON\TUE\WED\THU\FRI\SAT\SUN", "\")


The following example evaluates to 8 due to the leading delimiter:

FIELD_COUNT$("\MON\TUE\WED\THU\FRI\SAT\SUN", "\")

FIELD_POSITION$(string, delimiter, number)Returns an integer, which is the beginning byte position of the fieldspecified by the integer field number for the passed string and delimiter.The delimiter can be more than a single character. The byte positions beginat 1.


FIELD_POSITION$("MON\TUE\WED\THU\FRI\SAT\SUN", "\", 3)

FIND$(string, substring)Returns a number, which is the position within the string variable wherethe substring variable is located. The positions begin at 1.


FIND$("ROBOMON_SERVER", "MON")

FINDB$(string, substring)Returns a number, which is the position within the string variable wherethe substring variable begins. The positions begin at 1.


FINDB$("ROBOMON_SERVER", "MON")

FINDE$(string, substring)Returns a number, which is the position within the string variable wherethe substring variable ends. The positions begin at 1.


FIND$("ROBOMON_SERVER", "MON")

LENGTH$(string)Returns a number, which is the length of the string variable.


LENGTH$("ROBOMON_SERVER")

MAX$(statistic [,context])Computes the maximum value of the specified statistic across all of theentities that match the specified context. If the context results in a singlevalue, the MAX$ value is the same as the original value. For the functionto provide any service, the context must contain a list, wildcards, or not bespecified at all.

The following example returns the size of the biggest file collected:

MAX$(FILE_SIZE_BYTES)

The following example returns the size of file1:

MAX$(FILE_SIZE_BYTES, "file1")

The following example returns the size of the biggest file collected,beginning with the letters abc:

MAX$(FILE_SIZE_BYTES, "abc*")

MIN$(statistic [,context])Computes the minimum value of the specified statistic across all of theentities which match the specified context. If the context results in a single


value, the MIN$ value is the same as the original value. For the function toprovide any service, the context must contain a list, wildcards, or not bespecified at all.

The following example returns the size of the smallest file collected:

MIN$(FILE_SIZE_BYTES)


MIN$(FILE_SIZE_BYTES, "file1")

The following example returns the size of the smallest file collected,beginning with the letters abc:

MIN$(FILE_SIZE_BYTES, "abc*")

PADL$(string, padchars, length)Returns the passed string left padded with the passed padchars to thespecified length. If the passed string is already equal or longer than thespecified length then the string is simply returned as is. The padcharsstring is repeated until the desired length is reached. If necessary, a leadingportion of padchars are used to get to the specified length.

The following example evaluates to *****SAMPLE:

PADL$("SAMPLE", "*", 11)

The following example evaluates to /*/*/SAMPLE:

PADL$("SAMPLE", "/*", 11)

PADR$(string, padchars, length)Returns the passed string right padded with the passed padchars to thespecified length. If the passed string is already equal or longer than thespecified length then the string is simply returned as is. The padcharsstring is repeated until the desired length is reached. If necessary, a leadingportion of padchars are used to obtain the specified length.

The following example evaluates to SAMPLE*****:

PADR$("SAMPLE", "*", 11)

The following example evaluates to SAMPLE/*/*/:

PADR$("SAMPLE", "/*", 11)

REMOVE$(string, remove-string)Removes all characters from the input string that appear in the removestring. The remove string is a list of characters, not a pattern to bematched.

The following example evaluates to ABCDEFG:

REMOVE$("AyBzCyDzE F G", "y z")

REPLACE$(string, replace-string)Replaces all unprintable characters in the string argument with thecharacters in the replace-string argument. The <27> reference indicates anescape character.

The following example evaluates toSAMPLE***REPLACEMENT***STRING:

REPLACE$("SAMPLE<27>REPLACEMENT<27>STRING", "***")


ROUND$(number, precision)Returns a number round to the specified decimal places. A negativeprecision indicates a power of ten.


ROUND$(1054, -2)


ROUND$(10.54, 1)

SEG$(string, start-position, length)Returns a string that is a substring of the string variable that begins at theposition of the start position variable and has a length of the lengthvariable. The positions begin at 1.

The following example evaluates to server:

SEG$("ROBOMON_SERVER", 9, 6)

SEGL$(string, length)Returns a string that is a substring of the string variable that begins at thefirst character and has a length of the length variable.

The following example evaluates to RoboMon:

SEGL$("ROBOMON_SERVER", 7)

SEGR$(string, start-position)Returns a string that is a substring of the string variable that begins at theposition of the start position variable and ends with the last character ofthe string variable. The positions begin at 1.

The following example evaluates to server:

SEGR$("ROBOMON_SERVER", 9) evaluates to "server"

SEG1$(string, position)Returns a string that is the character at the position of the position variablein the string of the string variable. Positions begin at 1.

The following example evaluates to _:

SEG1$("ROBOMON_SERVER", 8)

STRING$(string, count)Returns a string consisting of the passed string variable repeated thenumber of times of the count variable.

The following example evaluates to abcabcabc:

STRING$("ABC", 3)

SUM$(statistic [,context])Computes the sum of the value of the specified statistic across all of theentities that match the specified context. Context can be a single value orcan include wildcards and lists.

The following example returns the sum of the sizes of all files collected:

SUM$(FILE_SIZE_BYTES)


SUM$(FILE_SIZE_BYTES, "file1")


The following example returns the sum of the sizes of all files collectedbeginning with the letters abc:

SUM$(FILE_SIZE_BYTES, "abc*")

TRUNC$(number, precision)Returns a number truncated to specified decimal places. A negativeprecision function indicates a power of ten.


TRUNC$(1034, -2)


TRUNC$(1.039, 2)

Expression operatorsTable 21

Table 21. Expression operators

Symbol Expression operator

() Precedence operator

v Multiplication

/ Division

% Modulus operator, or the remainder afterdivision.

& Bitwise AND

| Bitwise OR

~ Bitwise NOT

+ Addition for numbers and concatenation forstrings. For example: ABC+DEF results inABCDEF.

- Subtraction for numbers and removal of asubstring for strings. For example:ABCDEF-CD results in ABEF.

< Less than

<= Less than or equal

= Equal

>= Greater than or equal

> Greater than

<> Not equal

NOT Logical NOT

AND Logical AND

OR Logical OR

XOR Exclusive OR

ActionsIBM Tivoli Management Solution for Exchange provides default actions that can beused to automatically correct problems or notify personnel when particularconditions are detected. Specific series of actions can be designated for any


condition that can occur on your system. User-defined commands can also be usedin actions to enable unlimited problem correction and notification capabilities.

ACTION types and actions are placed in action blocks. The action block defineshow the series of ACTION types and actions respond to the evaluation of theCONDITION statement. Tivoli users can easily create sophisticated series of actionsthat apply increasingly severe measures as a problem escalates, evaluating multipleconditions before determining the appropriate action, and assuming manyresponsibilities performed by system management personnel. For entity-level rules,actions are performed for each entity that meets the criteria of the condition. See“Types of actions” on page 97for more information on ACTION types.

The ACTION statementThe ACTION statement is composed of the ACTION type and the action. Theaction block defines operations or tasks to be performed by the rule engine basedon the result of the condition. When the rule does not include a CONDITIONstatement, it is interpreted as having a CONDITION expression that alwaysevaluates to TRUE. The ACTION types can only be used within a rule statement.

The following list describes ACTION types that can be included in the ACTIONstatement:

ACTIONAn ACTION type that defines one or more actions to take if the rulecondition is TRUE. The ACTION type executes one time for each entitybased on the condition result.

CLOSE_ACTIONAn ACTION type that defines one or more actions to take for newly fixedproblems, which means that the rule condition is FALSE after having beenTRUE on the previous interval. The CLOSE_ACTION type executes onetime for each entity based on the condition result.

EPILOGUE_ACTIONAn ACTION type that defines one or more actions to take after everythingelse executes for the rule, regardless of the rule condition. TheEPILOGUE_ACTION type executes one time for each rule rather than onetime for each entity.

FALSE_ACTIONAn ACTION type that defines one or more actions to take if the rulecondition is FALSE. The FALSE_ACTION type executes one time for eachentity based on the condition result.

NEW_ACTIONAn ACTION type that defines one or more actions to take for a newlygenerated problem; meaning that the rule condition is true for the firsttime. The NEW_ACTION type executes one time for each entity based onthe condition result.

PROLOGUE_ACTIONAn ACTION type that defines one or more actions to take before anythingelse executes for the rule, regardless of the rule condition. ThePROLOGUE_ACTION type executes one time for each rule rather than onetime for each entity.

TRUE_ACTIONAn ACTION type that defines one or more actions to take if the rulecondition is TRUE. The TRUE_ACTION type executes one time for eachentity based on the condition result.


UPDATE_ACTIONAn ACTION type that defines one or more actions to take for a repeatingproblem, which means that the rule condition is FALSE after having beenTRUE on the previous interval. The UPDATE_ACTION type executes onetime for each entity based on the condition result.

Note: The rule condition is evaluated once for each entity. Different ACTION typescan be executed for each entity based on the result of the condition for eachentity. The rule engine tracks the condition result per entity so that theappropriate actions can be taken for each.

You must adhere to the following requirements for ACTION types:v At least one of the ACTION, TRUE_ACTION, FALSE_ACTION, NEW_ACTION,

UPDATE_ACTION, CLOSE_ACTION, PROLOGUE_ACTION, orEPILOGUE_ACTION type is required and must be the last section in a ruledefinition.

v ACTION types of the same type or condition must have unique names. Forexample, the TRUE_ACTION, NEW_ACTION, UPDATE_ACTION and ACTIONtypes are considered to be of the same condition in that they execute when thecondition is TRUE; the FALSE_ACTION and CLOSE_ACTION types areconsidered to be of the same condition in that they execute when the conditionis FALSE.

v Each ACTION statement must appear as one line in the file. The continuationcharacter must be used to extend the definition to multiple physical lines.

v The ACTION, NEW_ACTION, UPDATE_ACTION, CLOSE_ACTION,TRUE_ACTION, FALSE_ACTION, PROLOGUE_ACTION, ANDEPILOGUE_ACTION types must contain at least one action.

v Action names must be 1-31 characters in length. Alphanumeric characters andthe underscore are legal.

v Action names for similar types of action blocks must be unique within a rule.

The following are considerations when you are creating ACTION types:v Names are optional for ACTION types, but are suggested when there is more

than one ACTION type. If an ACTION type does not have a name, it is giventhe NULL name.

v If multiple ACTION types are executed based on the result of the condition, theyare executed in the order in which they appear. For example, a TRUE_ACTIONand a NEW_ACTION type both execute for an entity the first time the conditionis TRUE and are executed in the order they appear in the rule; a TRUE_ACTIONand UPDATE_ACTION type both execute when the condition is TRUEadditional times and also execute in the order in which they appear in the file.

v ACTION types that are never executed in the same rule execution for an entitydo not have to be in any particular order. For example, you can specify theNEW_ACTION, UPDATE_ACTION, and CLOSE_ACTION types in any orderbecause only one of these is executed.

v All non-comment lines between the ACTION, NEW_ACTION,UPDATE_ACTION, CLOSE_ACTION, TRUE_ACTION, FALSE_ACTION,PROLOGUE_ACTION, and EPILOGUE_ACTION types and the RULE,SCHEDULE, SELECT, TEXT_BLOCK, or VARIABLE actions following theACTION types, are considered to be ACTION statements.

v The $ACTION_STATUS and $ACTION_RESULT variables are set to thecompletion status of each action as it is performed. These are reserved variablenames and are always set by each action so that the next action can look at the


result of the previous action. The $ACTION_STATUS variable is the specificstatus of the action and the $ACTION_RESULT variable indicates only thesuccess (0) or failure (1) of the action.

SchedulesA rule’s schedule specifies when the rule is executed by IBM Tivoli ManagementSolution for Exchange. A rule can be executed at a specific time or throughout arange of minutes, hours, days, weeks, and months. If a range is specified, aninterval is required to determine the frequency of execution within the range. Theavailable scheduling elements include:

Table 22. Rule schedules

Schedule Examples

Interval Every 15 minutes

Times of Day 8 AM and 5 PM

Hours of the Day Hours 9 - 16 (9 AM - 5 PM)

Dates December 31, 1995

Days of the Month 1st through the 10th day of the month

Days of the Week Every day of the week except the 3rd day(Wed).

Weeks of the Month The 2nd week of the month

Months of the year The 6th and 12th months of the year (Juneand Dec)

This section describes functions and restrictions that apply to defining schedulesfor rules.

Initially disabled rulesIf you do not wish a rule to immediately begin executing when the RuleEngine is first started, you can disable the rule by including the DISABLEstatement. For example, if a rule checks for large inactive files, you candisable the rule at first and enable it only when disk space is low. Whenyou are ready for the rule to begin execution, you can enable the rulethrough the graphical user interface or through the action of another rule.

Asynchronous rulesA rule that is not regularly scheduled to execute is an asynchronous ruleand it is executed only on demand, either by a command issuedinteractively or from the ACTION statement of another rule. Asynchronousrules cannot have a schedule. If you require a task to be performed bothon a scheduled basis and on demand, you can achieve this by creating twodifferent rules.

One-shot rulesIf a rule is neither scheduled nor asynchronous, then it is a one-shot rule.A one-shot rule executes only one time, when the rule process is started.For example, a one-shot rule might be used to read variables from files sothat they are stored in memory.

Defining schedules for use in multiple rulesSchedules can be defined outside a rule that is named and referenced inmultiple rules. This eliminates the need to continually redefine a frequentlyused schedule. When a schedule is defined and named, it can be used byany succeeding rule. A named schedule is accessed by a rule using the USEstatement.


SelectionsTivoli rules that monitor entity-level conditions, such as disks or files, canselectively monitor only those entities that are of particular interest. For example, arule in the file domain can evaluate whether any large inactive files exist. The ruleselection specifies which of the available files must be evaluated. You can excludecertain files that are of no concern, such as executables that are part of theoperating system. Selections are self-configuring to automatically detect newentities that are displayed on the system after IBM Tivoli Management Solution forExchange is started.

Selections can be defined outside a rule that is named and referenced in multiplerules. This eliminates the need to continually redefine a frequently used selection.When a selection is defined and named, it can be used by any succeeding rule. Anamed selection is accessed by a rule using the USE statement.

Rule syntaxThis section provides a detailed presentation of Tivoli’s rule syntax, includingexamples of how the syntax is used.

MetacharactersThis section describes characters that have special meaning within the rule filesyntax.

CommentsAny text that follows an exclamation point (!) is considered comment textand is ignored. Comments can occur anywhere in a rule file, either onseparate lines or following rule syntax statements.

Continuation characterAny line in a rule file can end with a continuation character (-). Thissignifies that the statement continues on the next line. This must be the lastcharacter on the line.

Statement delimiterStatements are delimited by either the end of a line or by the statementdelimiter. The statement delimiter character is the semi-colon (;). Use of thestatement delimiter enables you to enter multiple statements on onephysical line in a rule file.

Quotation characterAny text that lies between two quotation characters (″ ″) is treated as literaltext. Case and spacing is maintained and the metacharacters (commentcharacter, continuation character, and statement delimiter) have no specialmeaning.

Literal characterAny metacharacter that is preceded by a literal character (^) is treated as asimple character with no special meaning. Unlike the other metacharacters,the literal character retains its special meaning within quotation characters.

White spaceWhite space can be used throughout the rule file between statements andkeywords. Any amount of white space can be used. When the rule file isparsed, this white space is recognized and discarded. You must use whitespace within an option value only when the white space is necessary.


Case-sensitivityMost of the text within rule-writing is case-insensitive. The following list itemsdefine a few general rules that apply:v Rule language keywords are case-insensitive.v Statistic names are case-insensitive.v Statistic values are case-sensitive.v Names of objects are case-insensitive. Some examples of objects include:

schedules, selections, variables, text blocks, rules, and actionsv Macro names are case-sensitive and you must reference them in the same way

that you define them.

Quoted textMost of the option values specified with a rule file do not require that you specifyvalues within quotes. For these options, if quotes are specified in an option value,they are maintained as part of the value. For example, if there is an optionspecified as TYPE=″MESSAGE″, where quotes are not required, the value used forthe type is ″MESSAGE″ and not MESSAGE. There are a few exceptions to the rule.

The following table shows options that have special meaning based on whetherquotes are present or not present:

Table 23. Special quote options

Action Keyword option

EVENT TYPE=MESSAGE FULL_TEXT, TEXT

EVENT TYPE=PROBLEM FULL_TEXT, TEXT

EVENT TYPE=TEXT TEXT

EVENT TYPE=WINDOWS TEXT

LOG TEXT

MAIL TEXT

In these options, quotes are required around the text value if the value is the actualtext to be used. If quotes are not present, the value is assumed to be the name of atext block. If quotes are present, they are removed and the contents are used as thevalue.

In the following options, quotes can be specified, but are not required. If specified,they are removed:

Table 24. Optionally specified options

Action Option

SELECT field=

EXECUTE OS_COMMAND

You must use quotes when making selections on fields with embedded spaces inthe values.

In expression statements, you must specify string constants with quotes. Thequotes are removed and the contents used as the value. If quotes are not present,the string is assumed to be a statistic or variable name.


General file statementsGeneral file statements are used for file-level text manipulation. They are parsed bythe preprocessor and the resulting output is passed to the rule engine. See“Including statements from another file” on page 242 and “Macros” on page 242for more information.

Including statements from another fileDescription

The INCLUDE statement enables you to include the contents of anotherfile into the current file. The contents of the specified file are read in at thepoint at which the INCLUDE statement is encountered. The contents of thespecified file are placed where the INCLUDE statement appeared.

The file can be specified using an absolute path name or a relative pathname. If an absolute path name is specified, IBM Tivoli ManagementSolution for Exchange looks for that file. If a relative path name isspecified, IBM Tivoli Management Solution for Exchange first looks for thefile relative to the directory of the current file, and if not found, looks forthe file relative to the directory in which IBM Tivoli Management Solutionfor Exchange is installed. For example, if IBM Tivoli Management Solutionfor Exchange is installed in the C:\Program Files\TMSE directory, and arule file in the C:\TEMP directory contains the INCLUDEuser\file_rules.inc statement, IBM Tivoli Management Solution forExchange first tries to find the C:\TEMP\user\file_rules.inc file. If it isnot found, IBM Tivoli Management Solution for Exchange tries to find theC:\Program Files\TMSE\user\file_rules.inc file.

SyntaxINCLUDE file

ExamplesThe following example includes contents of the C:\TMSE\user\macros.incfile at the point where this INCLUDE statement is encountered:INCLUDE C:\TMSE\user\user_macros.inc

MacrosDescription

The MACRO statement enables text expansion within rule files. By usingmacros, statements that are frequently repeated could be written once as amacro definition. In places where these statements are required, only themacro name and its optional arguments have to be specified.

The MACRO statement can be used to define a single line of text or it canbe used with the END_MACRO statement to define multiple lines of text.When defined, a macro can be referenced by name elsewhere in the rulefile. When the rule file is verified, the macro text is substituted whereverthe macro name appears.

Macros can have argument lists. The argument list enables substitution ofpassed parameters within the macro. The macro definitions referencearguments by enclosing them in question marks. The passed argumentvalue is used in place of the argument name enclosed in question marks.When an argument value passed to a macro is enclosed in quotes, theouter set of quotes is stripped before the argument is substituted in themacro.


Additionally, macro definitions can use the IF_PARAM types. This enablesoptional text inclusion based on argument values. When the IF_PARAMtype is used, the text following it is substituted if the specified macroparameter has the parameter-value value and the text before theELSE_PARAM or END_IF_PARAM type is substituted. When theIF_PARAM_NOT type is used, the text following it is substituted if thespecified macro parameter does not have the parameter-value value.

Text lines can also include embedded references to other macros defined inthe rule file.

SyntaxMACRO name [(parameter[,...])] text

or

MACRO name [(parameter[,...])] text

[IF_PARAM parameter parameter-value text ...

[ELSE_PARAM text ...] END_IF_PARAM]

[IF_PARAM_NOT parameter parameter-value text ...

ELSE_PARAM text ...] END_IF_PARAM] ... END_MACRO

ExamplesThe following example demonstrates the use of parameters by defining theOUTPUT_LOG macro. The macro has three parameters: FILE_NAME,TEXT, and STATUS:MACRO OUTPUT_LOG(FILE_NAME, TEXT, STATUS) IF (?STATUS? & 1)\THEN LOG FILE=?FILE_NAME?,TEXT="?TEXT?" END_IF END_MACRO

Later in the rule file, the OUTPUT_LOG macro is referenced as:OUTPUT_LOG(c:\TMSE\log\output.log,"The condition has been met",STAT)

This expands to:IF (STAT & 1) THEN LOG FILE=c:\TMSE\log\output.log,\TEXT="The condition has been met" END_IF

The following example demonstrates the use of the IF_PARAM typeconstruction and defines the OUTPUT_LOG macro. The macro has threeparameters: FILE_NAME, TEXT, and TYPE:MACRO OUTPUT_LOG(FILE_NAME, TEXT, TYPE) IF_PARAM TYPE 1 TRUE_ACTION\INCREMENT TRUE_COUNTER ELSE_PARAM FALSE_ACTION INCREMENT FALSE_COUNTER\END_IF_PARAM LOG FILE=?FILE_NAME?,TEXT="?TEXT?" END_MACRO

Later in the rule file the OUTPUT_LOG macro is referenced as:OUTPUT_LOG(c:\TMSE\log\output.log,"The condition has been met",STAT)OUTPUT_LOG(c:\TMSE\log\output.log,"condition is true",1)OUTPUT_LOG(c:\TMSE\log\output.log,"condition is false",0)

This expands to:TRUE_ACTIONINCREMENT TRUE_COUNTERLOG FILE=c:\TMSE\log\output.log, TEXT="condition is true"FALSE_ACTIONINCREMENT FALSE_COUNTERLOG FILE=c:\TMSE\log\output.log, TEXT="condition is false"


Symbol substitutionSymbol substitution enables for text expansion to be performed at rule executiontime rather than at rule parsing, as done for macro definitions. Symbol substitutionis valid only in rule action statements. If the symbol substitution results in aninvalid option for an action, the action is not performed.

Symbols are specified by enclosing a symbol name in braces ({}). Optionally, asymbol name can be followed by a colon and formatting information. Thisformatting information includes a length precision followed by a justificationoption that is contained within the braces.

The following chart shows the valid justification options which must be inuppercase characters:

Table 25. Valid justification options

Symbol Justification option

L Left justify

R Right justify

C Center

Z Zero fill a number to specified length

S Format a number with the digit separator asdefined by the registry entryROBOMON_DIGIT_SEPARATOR (assumesR if length is specified)

D Format a number as a date (assumes L iflength is specified)

T Format a number as a time (assumes L iflength is specified)

DT Format a number as a date-time (assumes Lif length is specified)

You must adhere to the following rules when specifying length precision:v Length precision is ignored when specified for a string symbol value.v When precision is specified without a length for numbers, the length necessary

to display the value with the specified precision.v Length precision is zero when not specified for an integer.v The default length precision is 2 when not specified for a float.v The Z option is meaningless without a length precision specification.v If no formatting is specified, the result is the length required to display the

value. The default length precision of 0 for integers and 2 for floats are used.

Table 26. Length precision specification

Value Format Result

110.333 10.2Z 0000110.33

1000 5S 1000

1000 7S 1000

1234.123 10 1234.12

sample_string 8 sample_s

sample_string 15R sample_string


Table 26. Length precision specification (continued)

Value Format Result

1234.123 (none) 1234.12

sample_string (none) sample_string

Symbol names can contain any of the following:

Predefined symbolsValues that the Tivoli rule engine determines when a rule is beingexecuted.

StatisticsValues that the Tivoli data collector collects from your system.

User-defined statisticsComputed values based on the value of statistics that you define withinrules.

VariablesVariables are named identifiers that maintain scalar values that you defineand change under program control. Variables provide programmingcapabilities when you use them to pass information between rules or tomaintain information across executions of a rule. You maintain variables onon-disk files or exist only for the duration of a rule engine process. Thereare three types of variables; integer, floating point and string.

If a symbol is a variable, its value is retrieved from the in memory structure of therule engine. Variables are loaded into memory using the READ action or aCALCULATE action.

When a symbol is encountered at run time, the symbol name is first comparedagainst the list of predefined symbols, then the list of statistic names, the list ofuser-defined statistics for the rule, and lastly it is treated as a variable name.

Iterative symbol substitution is performed with a maximum of 16 iterations. Forexample, when the message for a LOG action is a variable, the value of thisvariable includes symbols which are statistics whose values are included in thetext.

The following example shows a rule that has a log action:LOG FILE=c:\TMSE\user\sample.log,TEXT="{rule_output}"

The rule_output variable contains the following text as its value:The file {FILE_NAME} has {FILE_SIZE_BYTES} bytes.

Before the text is written to the log, the above string value is used in place of{rule_output} and is searched for additional symbols. The value of {FILE_NAME}and {FILE_SIZE_BYTES} are then replaced with the statistic values, giving you anend result of:The file c:\TMSE\user\sample.log has 125 blocks.

The following registry entries are used while performing the symbol substitution:

ROBOMON_DIGIT_SEPARATORDefines the digit separator that is used when a symbol value is substitutedin a delimited format.


ROBOMON_RADIX_POINTDefines the radix point.

ROBOMON_DATE_FORMATDefines the format that is used when you substitute a date string. The legalvalues are: US (default) or EUROPEAN.

ROBOMON_TIME_FORMATDefines the format that is used when you substitute a time string. Thelegal values are: 12HOUR (default) or 24HOUR.

Predefined symbolsThere are several predefined symbols that exist within the rule engine. These canbe used in braces ({}) actions. The following predefined symbols exist in the rulesyntax:

CONTEXTThe current rule context in a delimited form (|). The following exampledemonstrates a physical disk level rule that executes on the computer withthe name lion:|lion|0

DATE_STRThe current date formatted as a string. Use the value of theROBOMON_DATE_FORMAT registry entry is for formatting.

COMPUTERThe current computer on which the rule is executing.

PID The process ID of the current rule engine process.

RULEThe name of the rule currently executing.

TIME_STRThe current time formatted as a string. Use the value of theROBOMON_TIME_FORMAT registry entry for formatting.

USERNAMEThe user name under which the current rule engine process is executing.The user name is always SERVICE.

EXISTSPerforms entity existence checking. This is a value of either 0 (does notexist) or n (exists n times). You can use this symbol in the condition of arule and in actions. The entities for which existence checking is done aredetermined based upon the selections that you specify for a rule. Forexample, in a process level rule, if the first selection that you specify is forthe process command, the entity is the process command; if the firstselection that you specify is for the process username, the entity is theusername. The selection that you use cannot contain any wildcards. Foreach entity that you specify in the selection, the rule engine determineswhether or not the entity exists. The condition is evaluated and theappropriate actions are executed for each entity specified in the selections.If an entity does not exist, all other statistical values are zero (numericstatistics) or blank (string statistics). Actions are taken based on both theexistence and the non-existence of an entity in an existence checking rule.

In the following example, the check_for_process rule looks for the RoboTcp processevery 10 minutes. If the RoboTcp process does not exist (EXISTS=0), a mail


message is sent to the Admin user to indicate the nonexistence of this process. Ifthe RoboTcp process exists (EXISTS>0), a different mail message is sent to theAdmin user to indicate that the process exists.RULEcheck_for_process

SELECT PROCESS_NAME =(RoboTcp)

SCHEDULE INTERVAL=00:10:00

CONDITION

EXISTS=0

TRUE_ACTION

MAIL USER=Admin,TEXT="Process {PROCESS_NAME} does not exist"

FALSE_ACTION

MAIL USER=Admin,TEXT="Process {PROCESS_NAME} exists"

In the following example, the rule executes every 10 minutes and looks for aprocess name matching *sys. For each process that is found, a mail message is sentto the Admin user that indicates that the process exists. This is not considered tobe an existence-checking rule because it does not use the EXISTS symbol andtherefore cannot take action upon the nonexistence of a process name.RULE report_process_list

SELECT PROCESS_NAME=*sys


ACTION

MAIL USER=Admin,TEXT="Process {PROCESS_NAME} found"

Predefined variablesIn addition to any variables that you can define and use in your rules, there areseveral that are predefined by the rule engine. All of these variables are set basedon the result of the condition and you must reference only within actions.Predefined variables include the following:

$ACTION_RESULTResults of the last action executed.

0 Success

1 Error

$ACTION_STATUSIndicates a specific action result and the status of the last action executed.The value set depends on the action executed.

$PROBLEM_STATEThe problem state for the current context for the rule.

0 = non-problem

1 = NEW (newly generated problem)

2 = UPDATE (repeating problem)

3 = CLOSE (newly fixed problem)


$PROBLEM_COUNTNumber of times a problem is encountered since opened.

1 On OPEN

2 On UPDATE

3 On CLOSE

$TRUE_CONDITION_COUNTThe number of times the rule condition is TRUE across all entities whenreferenced in an EPILOGUE_ACTION type.

$FALSE_CONDITION_COUNTThe number of times the rule condition is FALSE across all entities whenreferenced in an EPILOGUE_ACTION type.

$NEW_CONDITION_COUNTThe number of times the rule condition defines a NEW problem across allentities when it is referenced in an EPILOGUE_ACTION type.

$UPDATE_CONDITION_COUNTThe number of times the rule condition defines an UPDATED problemacross all entities when it is referenced in an EPILOGUE_ACTION type.

$CLOSE_CONDITION_COUNTThe number of times the rule condition defines a CLOSED problem acrossall entities when it is referenced in an EPILOGUE_ACTION type.

Object definitionsThe process of writing rules involves defining all of the objects used by the rules.This includes text blocks, variables, schedules, and selections as well as the rules.The end of an object definition is determined by the start of a new objectdefinition, with the exception of text blocks.

The following sections describe the syntax used to define objects when writing arule.

SETDescription

The SET statement defines the default variable file that you use whenlooking for variable values. This file is used when an explicit file is notspecified when executing a variable action or when the variable isreferenced and it has not been previously read or defined. You can use thisoption to define the DATA_SOURCE default to use when one is notprovided in the EXECUTE_SQL action. Additionally, the SET statementenables you to define a level of debugging output that is generated by therule engine.

You must make the SET statement the first non-blank, non-comment line inthe rule file.

SyntaxSET [VARIABLE_FILE=filename] [[,]DATA_SOURCE=name][,DEBUG_LEVEL=n]

where:

DATA_SOURCESpecifies the default database to use for the EXECUTE_SQLactions. This must be a system data source name. If an


EXECUTE_SQL action does not explicitly specify a database to use,the database specified in the SET option is used.

DEBUG_LEVELSpecifies the level of debugging information to write to the ruleoutput log file. This file is located in the IBM Tivoli ManagementSolution for Exchange \log subdirectory and is namedRULE_COMPUTER_OUTPUT.LOG, where RULE is the name of the ruleprocess and COMPUTER is the name of the computer. Thefollowing lists the valid levels:

0 Contains no debugging information.

1 Outputs the name of each rule when it is executed.

2 Outputs the name of files which are automatically closed.

3 Outputs the context values for which each rule isexecuting.

4 Outputs the condition value of TRUE or FALSE.

5 Outputs the actions executed.

VARIABLE_FILESpecifies the default file from which to read or write variables. TheREAD and WRITE actions enable you to use the specification of avariable file. If a variable file is not explicitly specified, the filespecified in this SET option is used. When a READ action isexecuted, the value of the variable is saved in the memorystructures of the rule engine.

Additionally, when symbols are encountered that are not statisticsor user-defined statistics, they are assumed to be variables. If thevariable is not read through a READ action, the rule engineautomatically looks for the variable in the file specified using thisSET statement. When a variable is read in this manner, its value isnot saved in the memory structures of the rule engine.

SymbolsSymbols are not supported in the name of the VARIABLE_FILE or theDATA_SOURCE file.

ExamplesThe following example sets the default variable file to c:\TMSE\config-\automation.var and the default database to RoboMonData.SET VARIABLE_FILE=c:\TMSE\config\automation.var, DATA_SOURCE=RoboMonData

VARIABLEDescription

All variables are considered to be global variables and are available for usein multiple rules. Each variable has a context level associated with it and isavailable for use in all rules of that context level. The context level isexplicitly defined or the rule engine automatically determines it based onthe rule in which the variable is referenced. You can declare variables thathave a context level, but they do not require declaration. Scalar variablesare available for use in all rules, but you must declare them as scalar.

If you have a process rule that uses a variable that must have a value foreach process, you do not need to explicitly declare this variable. When youuse the variable in the rule, the rule engine automatically creates thisvariable for each process that it finds. If within this same process rule you


want to use a variable that has the same value for all processes, thisvariable is declared as a scalar variable. A rule references scalar variablesor variables that you declare at the same context level as the rule.

Variables are global within their context level. Therefore, rules of differentcontext levels can use variables with the same name. If you have a processrule and file rule that both use a variable named STATUS, there is a valuefor STATUS for each process in the process rule and for each file in the filerule. Another process rule references the process STATUS variable andanother file rule references the STATUS variable file. If the variable isdeclared to have a particular context level, it is always referenced at thespecified level.

The following restrictions apply to variables:v The variable name must be 1–127 characters in length; alphanumeric

characters, the underscore, and the dollar sign are legal.v You must give unique names to variables that are declared with a

specific level.v You cannot declare the same variable name at two different levels.v You can use the same variable name with different context levels, but do

not declare them or their context level defaults to the rule.

SyntaxVARIABLE name [,LEVEL=entity]

where:

name The variable name.

entity The entity name and must be a context statistic.

LEVELSpecifies the level of the variable. An instance of the variable existsfor each entity. If a level is not specified, only one instance of thevariable exists as a scalar variable.

SymbolsNone.

ExamplesThe following example defines the FILE_VARIABLE variable. A value existsin memory for this variable for each FILE_UNIQUE_NAME value in therule.VARIABLE FILE_VARIABLE, LEVEL=FILE_UNIQUE_NAME

In the following example, a rule calculates the page file usage of a processin kilobytes and places the result in the PROCESS_PAGE_FILE_KB variable.Additionally, the page file usage of all processes is summed together andplaced in the TOTAL_PAGE_FILE_KB variable. The TOTAL_PAGE_FILE_KBvariable is declared as a scalar variable and the PROCESS_PAGE_FILE_KBvariable is declared as a process level variable.VARIABLE TOTAL_PAGE_FILE_KB

VARIABLE PROCESS_PAGE_FILE_KB, LEVEL=PROCESS RULE


ACTION


CALCULATE PROCESS_PAGE_FILE_KB = PROCESS_PAGE_FILE_BYTES / 1024

CALCULATE TOTAL_PAGE_FILE_KB = TOTAL_PAGE_FILE_KB + PROCESS_PAGE_FILE_KB

TEXT_BLOCKDescription

Defines and names a block of text for substitution in any action statementwith a TEXT=text option. Text blocks are useful when you use similar textin multiple places in a rule definition file. You must define text blocksbefore referencing them in rules. Consider any text that appears betweenthe TEXT_BLOCK and END_TEXT_BLOCK statements to be text forsubstitution.

SyntaxTEXT_BLOCK name

text

...

END_TEXT_BLOCK

where:

name The variable name.

Embedded blank lines within the text block are removed. You must use the^ character on a line by itself if a blank line is maintained. This character isremoved at output time and replaced by a blank line.

SymbolsSymbol substitution is supported in the text, but not in the text blockname. Symbol substitution is performed each time the text block is used.

ExamplesThe following example defines the PROCESS_INFO text block. The ^character is used to maintain a blank line when the text block text isoutput and all statistic values are substituted each time this text block isused.TEXT_BLOCK PROCESS_INFO

Process: {PROCESS_NAME}

^

Process ID: {PROCESS_ID}

Elapsed Time: {PROCESS_ELAPSED_TIME}

CPU Pct: {PROCESS_CPU_PCT}

END_TEXT_BLOCK

SCHEDULEDescription

Defines and names a schedule for data collection and rule evaluation thatcan be used by any rule following it in the rule file. This defines a namedglobal schedule that is used by multiple rules. Schedules can also bedefined within rules. The definition of the schedule must be global ifmultiple rules always execute on the same schedule. You can define theschedule once and define the rules to use it.


You must specify the schedule components with multiple values in a list ofeither single values or ranges of values. You must separate the list items bycommas and enclose the list in parentheses. The hyphen is used to indicatea range and you can specify the exceptions by preceding the exceptionwith E=. If you need to exclude multiple values, specify a list enclosed inparentheses following the E=. The exception list can contain ranges andsingle values.

For example, (1-30,E=(5,10,15-18)) is a valid specification for days of themonth. Since this is a list, it is enclosed in parentheses. The two items ofthe list are 1-30 and E=(5,10,15-18). The exceptions are also a list and areenclosed in parentheses. You can also specify this example as(1-4,6-9,11-14,19-30).

The schedule definition must appear as one line in the file. You must usethe continuation character to extend the definition to multiple physicallines.

The following restrictions apply to schedules:v Schedule names must be 1-31 characters in length; alphanumeric

characters and the underscore are legal.v Schedule names must be unique within the rule file.v You must specify either the INTERVAL or TIMES variable.v If you specify the TIMES variable without the INTERVAL variable, you

the TIMES variable must be a list of times without ranges.

SyntaxSCHEDULE name, [DATES=(date[-date][,...])],

[DAYS=(number[-number][,...])],

[HOURS=(number[-number][,...])],

[INTERVAL=interval],

[MONTHS=(month[-month][,...])],

[TIMES=(time[-time][,...])],

[WEEKDAYS=(weekday[-weekday][,...])],

[WEEKS=(number[-number][,...])]

or

SCHEDULE name, {variable}

where:

DATES=(date[-date][,...])Specifies the dates on which the rule operates. You can specify thedates as a list of dates, date ranges and exclusions. Components ofdates that you do not specify are set to the value for the currentdate. For example:

DATES=(1/1/1994,7/4/1994)January 1, 1994 and July 4, 1994

DATES=(1/1/1994-6/30/1994)January 1, 1994 to June 30, 1994

DATES=(1/1-6/30,E=3/15)January 1st of the current year to June 30th of the currentyear with the exception of March 15th.


You must specify dates in the format defined by theROBOMON_DATE_FORMAT registry entry. The legal formats are:

US mm/dd/yy

EUROPEdd/mm/yy

DAYS=(number[-number][,...])Specifies the days of the month during which the rule operates.The days specification can be a single day or a range of days. A listof days and ranges can be specified if enclosed in parentheses.Exceptions are allowed. For example:

DAYS=(1,15)1st and the 15th day of month

DAYS=(1-15,E=8)The 1st to the 15th except for the 8th

HOURS=(number[-number][,...])Specifies the hours of the day during which the rule operates. Youcan specify the hours as a single hour or a range of hours andspecify a list of hours and ranges if enclosed in parentheses.Exceptions are allowed. For example:

HOURS=(9-16)9:00 AM to 4:59:59 PM

HOURS=(0-23,E=(12,17))All day except Noon to 1 PM and 5 PM to 6 PM

INTERVAL=intervalSpecifies the rule interval. You can specify the interval as a singleelapsed time. The minimum interval is one second(INTERVAL=00:00:01). For example:

INTERVAL=00:00:50 50 second interval

INTERVAL=00:10:00 10 minute interval

INTERVAL=3:15:30 3 hour, 15 minute and 30 second interval

MONTHS=(month[-month][,...])Specifies the months of the year during which the rule operates.You can specify the months by a single month or a range ofmonths and a list of months or ranges by enclosing in parentheses.Exceptions are allowed. For example:

MONTHS=(5-9)can through September MONTHS=(1-12,E=8)

MONTHS=(1-12,E=8)All year, except August

You can define macros for the months of the year as follows:MACRO JANUARY 1

MACRO FEBRUARY 2

MACRO MARCH 3

MACRO APRIL 4


MACRO MAY 5

MACRO JUNE 6

MACRO JULY 7

MACRO AUGUST 8

MACRO SEPTEMBER 9

MACRO OCTOBER 10

MACRO NOVEMBER 11

MACRO DECEMBER 12

TIMES=(time[-time][,...])Specifies the times of day during which the rule operates. You canspecify the times as a list of absolute times, absolute time ranges,and exclusions. You can specify times in 24-hour format or in12-hour format with AM or PM specifications with or without apreceding space. For example:

TIMES=(8:30-17:00)8:30 AM to 5:00 PM

TIMES=(8:30AM-5:00PM)8:30 AM to 5:00 PM

TIMES=(9:00-17:00,E=12:00-13:00)9 AM to 5 PM except Noon to 1 PM

TIMES=(0:00,6:00,12:00,18:00)Midnight, 6 AM, Noon and 6 PM

TIMES=(6:00 AM, 6:00 PM)6 AM and 6 PM

WEEKDAYS=(weekday[-weekday],...)Specifies the days of the week during which the rule operates. Youcan specify the weekdays by a single day or a range of days. Youcan specify a list of days or ranges if enclosed in parentheses.Exceptions are allowed. The days of the week are coded as follows:v Mondayv Tuesdayv Wednesdayv Thursdayv Fridayv Saturdayv Sunday

For example:

WEEKDAYS=(1-5)Monday through Friday

WEEKDAYS=(1-7,E=3)All week, except Wednesday

You can define macros for the days of the week as follows:MACRO MONDAY 1

MACRO TUESDAY 2

MACRO WEDNESDAY 3

MACRO THURSDAY 4


MACRO FRIDAY 5

MACRO SATURDAY 6

MACRO SUNDAY 7

WEEKS=(number[-number][,...])Specifies the weeks of the month during which the rule operates.You can specify the week by a single week or a range of weeks.You can specify a list of weeks or ranges if enclosed in parentheses.Exceptions are allowed. For example:

WEEKS=(1,3,5)1st, 3rd and 5th week of month

WEEKS=(1-5,E=2)All month, except 2nd week

You can determine the week of the month by the day of the monthas follows:

Days 1-7week 1

Days 8-14week 2

Days 15-21week 3

Days 22-28week 4

Days 29-endweek 5

ParametersSymbol substitution is supported in the DATES, DAYS, HOURS,INTERVAL, MONTHS, TIMES, WEEKDAYS, and WEEKS specifications.Symbol substitution is not supported in the schedule name.

You must have these symbols as variables in the default variable file. Theseare evaluated once during the rule file start and never again. In addition,you can make the entire specification after the name a single symbol. Thisenables the user to have one variable with the entire schedule definition orvariables for the individual component values.

The value of the variable does not contain additional symbol substitutionwhen a component value is a variable.

ExamplesThe following example defines the PRIME_TIME schedule that has aten-minute interval and executes during the hours of 8 through 17:SCHEDULE PRIME_TIME, INTERVAL=00:10:00, HOURS=8-17

The following example defines the PERIODIC schedule that executes at 6AM and 11 PM, Monday, Wednesday and Friday:SCHEDULE PERIODIC, TIMES=(6:00,23:00), WEEKDAYS=(1,3,5)

SELECTDescription

Defines and names the selections for data collection that any rule followingit can then use. Selections are used to reduce the quantity of data which is


collected and then processed by the rule engine. This results in shorterexecution times for the rules and a lower level of memory usage by therule engine process. It is important to carefully define selections so as toonly look at the entities in which you are interested.

You must define selection objects if there are multiple rules that need tooperate on the same set of entities. You can then write the rule to use thisselection object. If multiple rules do not have to use the identical set ofentities, selection objects are not necessary because you can define theselections directly within the rules. The selection object definitions mustappear in the file before any rule definitions that use them.

Some selections are based on numeric values and other selections are basedon alphanumeric string values. In either case, it is legal to give a list thatincludes single values or ranges of values. You must separate the list itemsby commas and enclose the list in parentheses. The hyphen is used toindicate a range and you can specify the exceptions by preceding theexception with E=. If you need to exclude multiple values, you mustspecify a list enclosed in parentheses following the E=. The exception listcan contain ranges and single values. The exception list can contain singlevalues or ranges of values. For example, the following is a valid integerselection: (1-100,E=(20-29,50)). You can also specify this selection as:(1-19,30-49,51-100).

A range selection includes all values greater than or equal to the start ofthe range and less than or equal to the end of the range.

Numeric selections can use B to indicate the beginning value and E toindicate the ending value. For example, if you want all entities that have avalue greater than or equal to 20, you specify the selection as 20-E. If youwant all entities with a value less than or equal to 100, you specify theselection as B-100.

String selections can also use wildcard characters. The % characterindicates any single character and the * character indicates any set ofcharacters. For example, A%C matches ABC, but does not match ABBCand A*C matches AC, ABC and ABBC. You cannot use wildcards whenspecifying ranges. You can use the ″″ characters to specify a null value in aselection.

The following restrictions apply to selections:v Selection names must be 1-31 characters in length; alphanumeric

characters and the underscore are legal.v Selection names must be unique within the rule field.v The selection definition must appear as one line in the file.v You must use the continuation character to extend the definition to

multiple physical lines.

SyntaxSELECT name, field=(value,...)[,field=(value,...)]

SELECT name, {variable}

where:

value A valid value for the field. A single value or a list of valuesenclosed in parentheses.

SymbolsSymbol substitution is supported in the field value selections. All items in


the select definition can be symbols. You must include these symbols asvariables in the default variable file. These are evaluated each time acollection is performed. This variable is read once at the start and neveragain. In addition, you can make the entire specification after the name ofa single symbol. This enables you to have one variable with the entireselect definition and variables for the individual component values. Theindividual components are read each time they are referenced.

When a field value is a variable, the value of the variable cannot containadditional symbol substitution. You can change field selections in thevariable file to dynamically affect a running rule process. If you change avariable that contains an entire selection specification, the variable does notaffect a running rule process because this is read-only when the rule starts.

ExamplesThe following example defines a selection of files from all win32 programsthat have 512,000 bytes or greater in size. You can use this selection inrules that are defined later in the file.SELECT LARGE_FILES, FILE_BINARY_TYPE=WIN32, FILE_SIZE_BYTES=512000-E

RULEDescription

Defines and names a condition to monitor, when to monitor it, and theaction to take if the condition occurs or does not occur. You can initiallydisable the rules which remain in this state until you enable it using theaction of another rule or through outside interaction with the rule engineprocess.

You can define a rule as asynchronous. You can execute these rules whenuse an outside interaction with the rule engine process. For example, youcan explicitly request to execute the rule by running the Tivoli graphicaluser interface or you can use another rule performing an EXECUTE RULEaction. These rules cannot have schedules associated with them.

You can also define a rule that is not scheduled or asynchronous. Theserules are called one-shot rules and execute only once when the rule engineprocess is first started.

The order of rules within the rule file is important. All one-shot rulesexecute in the order in which they appear in the file. Scheduled rules thatare executing on the same schedule also execute at the specified time andin the order in which they are defined in the rule file. If the execution of arule depends on the prior execution of another rule, you must write themin the rule file in the required execution order.

The following restrictions apply to rules:v Rule names must be 1-31 characters in length; alphanumeric characters

and the underscore are legal.v Rule names must be unique within a rule file.v Action names must be unique within a rule.v Statistic names must be 1-31 characters in length; alphanumeric

characters and the underscore are legal.v You can specify the USE, SCHEDULE, SELECT, COLLECT, and

STATISTIC statements in any order, but they must all precede theCONDITION and ACTION statements.

v The CONDITION statement is optional, but if specified, it must precedeall ACTIONS.


v You can use only one of the SCHEDULE or USE SCHEDULE statements.If you do not use either, the rule executes once when the rule process isfirst started.

v You can use only one of the SELECT or USE SELECT statements. If youdo not use either, everything is selected.

v A rule definition must contain at least one action block.

SyntaxThe order of the statements in the syntax definition is important. The USE,SCHEDULE, SELECT, COLLECT, and STATISTIC statements can be in anyorder, but they must precede the CONDITION and ACTION statements.The CONDITION statement is optional, but must precede any ACTIONstatements if it is specified.

RULE name [,ASYNCHRONOUS] [,DISABLED]

[USE [SCHEDULE=name], [SELECT=name]]

[SCHEDULE [DATES=(date[-date][,...])], [DAYS=(number[-number][,...])],

[HOURS=(number[-number][,...])], [INTERVAL=interval],

[MONTHS=(month[-month][,...])], [TIMES=(time[-time][,...])],

[WEEKDAYS=(weekday[-weekday][,...])],

[WEEKS=(number[-number][,...])]]

or

[SCHEDULE {variable}]

[SELECT field=(value,...)]

or

[SELECT {variable}]

[COLLECT STATISTCS=(name,...)]

[STATISTIC name expression

...] [CONDITION

condition-expression]

ACTION [name]

NEW_ACTION [name]

UPDATE_ACTION [name]

CLOSE_ACTION [name]

TRUE_ACTION [name]

FALSE_ACTION [name]

PROLOGUE_ACTION[name]

EPILOGUE_ACTION[name]

...

[ACTION [name]

...]

where:


ASYNCHRONOUSThe rule only executes on demand. The rule can execute either bythe action of another rule or by a command issued interactively bya user.

DISABLEDThe rule does not execute until explicitly enabled. The action,another rule in the rule file, or the user can enable the rule. At thatpoint, the rule executes according to its schedule definition.

USE Specifies the schedule or selections to use. The schedule orselections must have previously been defined and named using aSCHEDULE or SELECT definition.

SCHEDULEDefines this rule schedule for data collection and rule evaluation.You use the same syntax that you use to define a schedule outsideof a rule, except the name is not allowed. The schedule is given thesame name as the rule and the schedule definition must appear asone line in the file. You must use the continuation character toextend the definition to multiple physical lines.

SELECTDefines the selections for rule data collection. You use the samesyntax that you use to define selections outside of a rule, exceptthat a name is not allowed. The selections are given the same nameas the rule. The selection definition must appear as one line in thefile and you must use the continuation character to extend thedefinition to multiple physical lines.

COLLECT STATISTICS=(name,...)Defines a list of additional statistics that you must collect for theproper execution of the rule. The rule engine determines statisticsthat the rule requires to evaluate the condition and execute theactions. If there are statistics referenced in text that is storedexternally to the rule, then you must list these statistics in aCOLLECT statement. The statistics list must appear as one line inthe file and you must use the continuation character to extend thelist to multiple physical lines.

STATISTIC name=expressionDefines and names a user-defined statistic. When you declare this,you can use a user-defined statistic within a rule in the same wayas statistics that are built into IBM Tivoli Management Solution forExchange. You can define any number of user-defined statisticswithin a rule. You can use only these user-defined statistics in therule in which they are defined. These expressions can includestatistics and constants, but cannot include variables or otheruser-defined statistics. The statistic expression must appear as oneline in the file. The continuation character must be used to extendthe definition to multiple physical lines.

CONDITION and condition-expressionDefine the rule condition for IBM Tivoli Management Solution forExchange to monitor. The CONDITION section explains thecondition-expression in more detail. The condition-expression mustappear as one line in the file and after a line containing the wordCONDITION. You must use the continuation character to extendthe definition to multiple physical lines.


ACTIONMarks the beginning of one of the rule action blocks. There can bemultiple action blocks and each action block can contain multipleaction statements. The type of action block identifies when theaction statements within the block execute.

SymbolsNone.

ExamplesThe example is a sample rule:! Define a schedule with a 10 minute interval

SCHEDULE sample_schedule, INTERVAL=00:10:00

RULE sample

! Use the schedule defined above

USE SCHEDULE=sample_schedule

! Collect these statistics - they are used in log_file variable

COLLECT STATISTICS=(DATE_DAY,DATE_MONTH,DATE_YEAR)

! Is the process using a lot of CPU

CONDITION

PROCESS_CPU_PCT >30

! Yes - the process is using more than 30%

TRUE_ACTION

LOG -

FILE={log_file},

TEXT="{PROCESS_NAME} is using {PROCESS_CPU_PCT}% of the CPU"

! The process was using more than 30% - but is not any more

CLOSE_ACTION

LOG -

FILE={log_file},

TEXT="{PROCESS_NAME} is no longer – using excessive amounts of CPU"

Refer to c:\TMSE\examples\*.rul for several other sample rules.

ActionsMany of the actions available have a COMPUTER option that you can specify. Thisoption indicates that the action is performed on a computer other than the localcomputer or on the local computer by the Tivoli server process. If the COMPUTERoption is not specified in these actions, the action is performed directly by the ruleengine.

If the COMPUTER option is specified with the local computer name, the Tivoliserver process must be executing on the local computer because this is the processthat performs the action. If the COMPUTER option is specified with the name of a


remote computer, the Tivoli server process must be running on the local computerand on the named remote computer. The local Tivoli server process notifies theremote Tivoli server process to perform the requested action.

When an action is performed by the rule engine process, it does not continue untilthe action is completed. If an action is executed by the Tivoli server process, therule engine notifies the process to perform the action and continues on withadditional work. The rule engine waits for the Tivoli server process to complete theaction only if the next action executed is dependent on the result status of thecurrent action.

Within the description of each action, a note is made stating which processexecutes the action. In several actions it indicates both the rule engine and theTivoli server process. The server process executes the action when the COMPUTERoption is specified, otherwise the rule engine executes the action. See Appendix D,“Action list” on page 263 for a complete list of actions and their descriptions.

EVENTAn EVENT is an action that generates an event for display in the Tivoli EventMonitor. There are four types of events: MESSAGE, PROBLEM, TEXT, andWINDOWS. All types of events receive an automatic time stamp when yougenerate them.

MESSAGEEvents that include a user-specified brief text string, a class identification,severity number, and a detailed description of the problem. See “EVENTTYPE=MESSAGE” on page 276 for more details.

PROBLEMEvents that are similar to MESSAGE events, except that they have a handleassociated with them so that you can trace the history of problems.Additionally, they have a subclass specification and there is an ownerassociated with each event.

Each problem event is automatically assigned a state of new, updated, orclosed. A problem is new the first time it occurs, updated each subsequenttime that it occurs, and closed when the problem is removed. The TivoliEvent Monitor displays only the most recent event for a particularproblem. The Tivoli Event Monitor can use the handle to group togetherand display all associated events through the history option. ThePROBLEM events are the most powerful type of events available. See“EVENT TYPE=PROBLEM” on page 279 for more details.

TEXT Events that are the simplest type of events. These consist merely of a userspecified text string which briefly describes a problem. See “EVENTTYPE=TEXT” on page 283 for more details.

WINDOWSEvents that describe conditions that occur on a Windows NT system. IBMTivoli Management Solution for Exchange or any application that canhandle native Windows NT events and manage the WINDOWS event. See“EVENT TYPE=WINDOWS” on page 285.


Appendix D. Action list

IBM Tivoli Management Solution for Exchange is equipped with an extensive arrayof default actions that can be used to correct problems automatically and notifypersonnel when particular conditions are detected. A series of actions can bespecified for any condition that can occur on your system. User-defined commandscan also be used in actions to enable virtually unlimited problem correction andnotification capabilities.

The actions used for IBM Tivoli Management Solution for Exchange are organizedalphabetically and divided into the following sections:

DescriptionA brief description of the action.

CLI syntaxThe command line interface (CLI) syntax.

SymbolsA brief statement of whether or not symbol substitution is allowed.

CLI exampleAn example command line interface (CLI).

Process executionThe process used to execute the action, rule engine, or the Tivoli serverprocess.

263

APPEND

DescriptionAppends a new line character, <NL>, followed by the specified string to thespecified string variable. If this action creates a string greater than 16,000characters, the action is not performed without notification.

CLI syntaxAPPEND STRING=sting-to-append, VARIABLE=variable-name

where:

STRING=string-to-appendString appended to the specified string variable.

VARIABLE=variable-nameThe name of the string variable.

SymbolsSymbol substitution is supported in the STRING specification.

CLI exampleThe following example appends <NL> followed by the value of the FILE_NAMEstatistic to the file_list string variable:APPEND VARIABLE=file_list, STRING="{FILE_NAME}"

Process executionRule Engine


CALCULATE

DescriptionThe value of the variable specified that is updated in memory and is the value ofthe expression.

CLI syntaxCALCULATE variable=expression

where:

expressionA valid expression. All items in the expression are assumed to be statistics,user-defined statistics, variables, or constants. The operands must bestatistic names, user-defined statistic names, variable names, numericconstants, or string constants that are contained in quotes. Do not enclosethe statistic and variable names in braces ({}).

Variable values are retrieved from the rule engine memory structures; if thevariable does not exist in these structures, it searches the default variablefile. If it is not in the default file, a value of zero is used.

The data type of the result is based on the data types of the arguments inthe expression. The valid data types include integer, floating, or string.This determines the data type of the variable being calculated.

variableA variable name. If the variable to be set is declared with a VARIABLEstatement, it is calculated and the value is set for the context at the leveldeclared. If it was not declared to have a particular level, it is calculatedand the value is set for each entity at the lowest level of the data collectedby the current rule. For example, if a variable was declared to be scalar, thevalue is calculated and stored in memory as one value to be used by allentities. If the rule is a process level rule and the variable was notdeclared, there is one value of the variable for each process collected.

SymbolsNone.

CLI exampleThe following example shows that the FILE_WASTED_BYTES specification is anin-memory variable and all arguments on the right hand side are statistic names.The variable is set to the number of bytes wasted by the file. Assuming that thisvariable is not declared to be scalar, there is one value of theFILE_WASTED_BYTES specification for each file collected:CALCULATE FILE_WASTED_BYTES = ( (100*FILE_SIZE_BYTES) / (100-FILE_WASTED_PCT) )\

- FILE_SIZE_BYTES

The following example sets the value of the OUTPUT_TIME variable to be the datefollowed by a space and then the time:CALCULATE OUTPUT_TIME=DATE_STR+" "+TIME_STR


Appendix D. Action list 265

CHECK_BOUNDS

DescriptionMaintains the value of a variable within a certain range.

CLI syntaxCHECK_BOUNDS MAXIMUM=value, MINIMUM=value, VARIABLE=variable

where:

MAXIMUM=valueSpecifies the maximum allowable value for the variable.

MINIMUM=valueSpecifies the minimum allowable value for the variable.

VARIABLE=variableSpecifies the variable to check and, if necessary, adjust. This variable isrequired.

Note: You must specify the MAXIMUM and MINIMUM specifications and theMAXIMUM specification must exceed the MINIMUM specification.

The status of the action is returned as one of the following:

–1 Variable raised to the minimum value.

0 No adjustment to the variable was made.

1 Variable lowered to the maximum value.

SymbolsSymbol substitution is supported in the MINIMUM and MAXIMUM valuespecifications.

If the symbols in the MINIMUM or MAXIMUM specifications are variables, thevalue is first checked in the rule engine memory structures. If it does not existthere, the default variable file is checked. If it does not exist in the default variablefile, a value of zero is used.

CLI exampleIn the following example, the MAX_PROCESSORS variable is lowered to the valueof the PROCESSOR_COUNT statistic if its current value exceeds the statistic value:CHECK_BOUNDS VARIABLE=MAX_PROCESSORS, MAXIMUM={PROCESSOR_COUNT}



CLOSE

DescriptionCloses a currently open file, Open Database Connectivity (ODBC) data source, orjet database.

CLI syntaxCLOSE [DATA_SOURCE=data_source_name], [DATABASE=database_name],[FILE=filename], [COMPUTER=computer-name]

where:

COMPUTER=computer-nameSpecifies the name of the computer used to perform the close. This is thesame computer used to open the file.

DATABASE=database_nameSpecifies the name of the jet database to be closed. This is optional; youmust specify one of the DATA_SOURCE, DATABASE, or FILEspecifications. Databases that can be closed with this action are those thathave been opened by an EXPORT action.

DATA_SOURCE=data_source_nameSpecifies the name of the ODBC data source to be closed. This is optional;you must specify one of the DATA_SOURCE, DATABASE, or FILEspecifications. The ODBC data sources that can be closed with this actionare those that have been opened by an EXPORT action, EXECUTE_SQLaction, or a collection using a DOMAIN definition.

FILE=filenameSpecifies the name of file to be closed. This is optional; you must specifyone of the DATA_SOURCE, DATABASE, or FILE specifications. Files thatcan be closed with this action are those which have been opened by one ofthe following actions: CREATE, DELETE, EVENT, EXPORT, LOG, READ,WAIT, or WRITE .

SymbolsSymbol substitution is supported in the DATA_SOURCE, DATABASE, FILE, andCOMPUTER specifications.

CLI exampleThe following example closes the c:\TEMS\log\server.log file:CLOSE FILE=c:\TEMS\log\server.log

The following example closes the ODBC data source RoboMonData:CLOSE DATA_SOURCE=RoboMonData

Process executionRule EngineTivoli Server


COPY

DescriptionCopies an ASCII file to a specified destination. Optionally, you can perform thecopy operation on another computer and you can copy the file to a destination onanother computer.

CLI syntaxCOPY FILE=filename, DESTINATION=destination, [COMPUTER=computer-name],[DESTINATION_COMPUTER=computer-name]

where:

COMPUTER=computer-nameOptionally specifies the source computer for the copy operation. Thespecified file is opened and read on this computer. If this specification isomitted, the file is opened and read on the current computer.

DESTINATION=destinationSpecifies the location of where to copy the file. This location is required.

DESTINATION_COMPUTER=computer-nameOptionally specifies the destination computer for the copy operation. Thedestination file is created and written on this computer. If this specificationis omitted, the file is created on the local computer.

FILE=filenameSpecifies the name of the ASCII file to be copied. This specification isrequired.

Note: Only ASCII files can be copied with the COPY action. Do not specifythe name of a binary file.

SymbolsSymbol substitution is valid in the FILE, DESTINATION,DESTINATION_COMPUTER, and COMPUTER specifications.

CLI exampleThe following example uses the local computer to copy the c:\TEMS\user\user.rptto c:\temp\user.rpt file:COPY FILE=c:\TEMS\user\user.rpt, DESTINATION=c:\temp\user.rpt



CREATE

DescriptionCreates the named variable in the specified file.

CLI syntaxCREATE [CONTEXT=context_str], DATA_TYPE=type, [FILE=filename],[COMPUTER=computer-name], VALUE=value, VARIABLE=variable

where:

COMPUTER=computer-nameSpecifies the name of the computer on which to perform the file write.

CONTEXT=context_strSpecifies the context string to be associated with the variable written. Thismust be a delimited string with the | character as the delimiter. The firstfield of the context must be the computer name and subsequent fields canbe any of the valid context statistics as described in the Rule Contextsection.

DATA_TYPE=typeSpecifies the data type of the variable. The type is required and must beINTEGER, STRING, or FLOATING.

FILE=filenameSpecifies the file which to write. If the FILE specification is not specified,the default variable file is used. The file is opened if necessary and remainsopen until closed with the CLOSE action or until there has been no activitywith the file for a period of more than 12-hours.

VARIABLE=variableSpecifies the variable name to create in the variable file. This variable isrequired.

VALUE=valueSpecifies the value of the variable to be written to the file. This value isrequired.

SymbolsSymbol substitution is supported in the CONTEXT, DATA_TYPE, FILE,COMPUTER, and VALUE specifications. It is not valid in the variable name.

CLI exampleThe following example creates a TOTAL_BYTES variable in the default variable file.The variable has an integer value of 16,000,000 and a context of computer namesys1 and physical disk 0:CREATE VARIABLE=TOTAL_BYTES, CONTEXT=sys1|0, - VALUE=16000000, DATA_TYPE=INTEGER



DECREMENT

DescriptionDecrements the value of one or more variables by 1. The value of the variable isupdated in memory; if the variable is read from a disk, the on-disk value is notchanged.

CLI syntaxDECREMENT variable[,...]

where:

variableA comma-separated list of the names of the variables to be decremented.

The following rules apply to the variable that is decremented:v The value of the variable as stored in memory that is decremented by

one.v Variables are not loaded from disk or written to disk.v If a specific level was specified for the variable through a VARIABLE

statement, it is referenced for that particular context level.v If no level was specified, the current lowest context level is applied.v If the variable does not currently exist in memory it is created with a

value of -1.

SymbolsThere is no symbol substitution in this action.

CLI exampleThe following example decrements the in-memory value of the COUNTER variableby one:DECREMENT COUNTER



DELETE

DescriptionDeletes the named variable with the specified context from the specified file.

CLI syntaxDELETE CONTEXT=context_str, [FILE=filename], [COMPUTER=computer-name],VARIABLE=variable

where:

COMPUTER=computer-nameThe computer on which to perform the delete operation.

CONTEXT=context_strThe context to delete from the named variable. This must be a delimitedstring with the | character as the delimiter. The first field of the contextmust be the computer name and subsequent fields can be any of the validcontext statistics as described in the Rule Context section. This context isrequired.

FILE=filenameThe file from which to delete the variable. If the FILE specification is notspecified, the default variable file is used. The file is opened if necessaryand remains open until closed with the CLOSE action or until there hasbeen no activity with the file for a period of more than 12-hours.

VARIABLE=variableThe name of the variable to delete from the file. This variable name isrequired.

SymbolsSymbol substitution is supported in the CONTEXT, FILE, and COMPUTERspecifications. Symbol substitution is not valid in the variable name.

CLI exampleThe following example deletes the OPEN_FILES_LIMIT variable from the defaultvariable file for the context of the sys2 computer:DELETE VARIABLE=OPEN_FILES_LIMIT, CONTEXT=sys2



DISABLE

DescriptionDisables rules and actions indefinitely or for a defined period of time.

CLI syntaxDISABLE [ACTION[=(name[,...])]], [ALL], [FOR=time-period],[INTERVALS=number], [RULE[=[=(name[,...])]], [UNTIL=date-time]

where:

ACTION[=(name[,...])]Specifies the actions to disable. If an action name is not specified, thecurrent action is assumed. Wildcards are allowed.

ALL Specifies to disable the rule or action for all entities. If not specified, therule or action are disabled for the current context entity only.

FOR=time-periodSpecifies the length of time for which to disable the rule or action. This isspecified as an elapsed time in the format of HH:MM:SS.CC.

INTERVALS=numberSpecifies the number of intervals for which to disable the rule or action.

RULE[=(name[,...])]Specifies the rule to disable or the rules in which to disable the actions, ifACTION is included. If a rule name is not specified, the current rule isassumed. Wildcards are allowed.

UNTIL=date-timeSpecifies that you must disable the rule or action until the specified dateand time. The valid date-time format is dependent upon the value of theROBOMON_DATE_FORMAT registry entry. The date and time is specifiedfor the US time as follows:mm/dd/yy hh:mm:ss.cc

The date and time is specified for European time as follows:dd/mm/yy hh:mm:ss.cc

You must specify the RULE or ACTION specification. If only the RULEspecification is included, then the specified rule is disabled. If only the ACTIONspecification is included, then the specified action is disabled for the current rule. Ifboth are included, the specified action is disabled for the specified rule.

Only one of the INTERVALS, FOR, and UNTIL specifications can be included. Ifnone are specified, then the rule or action is disabled indefinitely.

The rule performs existence-checking in the following situations:v If you disable another rule, it is disabled for all context values when executing

for the non-existent entities.v The current rule can be disabled for the current context, which in this case

cannot be based on the actual context statistic, but on the exists selection statistic.The same rules apply to disabling actions.

The following situations can cause conflicts:


v If the action is performing a disable by context and the rule or action is alreadydisabled for all context values.

v If the action is performing a disable by context and the rule or action is alreadydisabled for that particular context value.

v If the action is performing an overall disable, and the rule is already disabled forparticular context values.

Perform the following recovery efforts when the preceding conflicts occur:v The context and timing information is maintained, but this might not have any

effect until the overall disable is removed.v The timing information is modified for the particular context to the values

specified in this action.v The overall disable is set with the specified timing information. The

context-disabled information remains intact because some context values can bedisabled for a longer period of time than the overall rule.

If a rule that has been previously enabled for a specific time period is disabled, theenabled information is removed and the disabled condition takes effect.

SymbolsSymbol substitution is supported in the ACTION, FOR, INTERVALS, RULE, andUNTIL specifications.

CLI exampleThe following example disables the SENDMAIL action in the current rule for allcontext values.DISABLE ACTION=SENDMAIL, ALL

The following example disables the FILE_SIZE_CHECK rule for three intervals forthe current disk being processed.DISABLE RULE=FILE_SIZE_CHECK, INTERVALS=3



ENABLE

DescriptionEnables rules or actions indefinitely or for a defined period of time.

CLI syntaxENABLE [ACTION[=(name[,...])]], [ALL], [FOR=time-period],[INTERVALS=number], [RULE[=[=(name[,...])]], [UNTIL=date-time]

where:

ACTION[=(name[,...])]Specifies the actions to enable. If an action name is not specified, thecurrent action is assumed. Wildcards are allowed.

ALL Specifies the rule or action for all entities to be enabled. If not specified,the rule or action is enabled for the current context entity only.

FOR=time-periodSpecifies the length of time for which to enable the rule or action. This isspecified as an elapsed time in the format of HH:MM:SS.CC.

INTERVALS=numberSpecifies the number of intervals for which to enable the rule or action.

RULE[=(name[,...])]Specifies the rule to enable or the rules in which to enable the actions, ifACTION is included. If a rule name is not specified, the current rule isassumed. Wildcards are allowed.

UNTIL=date-timeSpecifies that you must disable the rule or action until the specified dateand time. The valid date-time format is dependent upon the value of theROBOMON_DATE_FORMAT registry entry. Specify the date and time forthe US time as follows:mm/dd/yy hh:mm:ss.cc

Specify the date and time for European time as follows:dd/mm/yy hh:mm:ss.cc

You must specify the RULE or ACTION specification. If only the RULEspecification is included, the specified rule is enabled. If only the ACTIONspecification is included, the specified action is enabled for the current rule. If bothare included, the specified action is enabled for the specified rule.

Only one of the INTERVALS, FOR, and UNTIL specifications can be included. Ifnone are specified, the rule or action is enabled indefinitely.

The rule performs existence-checking in the following situations:v When executing for the non-existent entities, if another rule is to be enabled, it is

enabled for all context values.v The current rule can be enabled for the current context, which in this case

cannot be based on the actual context statistic, but on the exists selectionstatistic. The same rules apply to enabling actions.

The following situations can cause conflicts:


v If the action is performing an enable by context and the rule or action is alreadyenabled for all context values.

v If the action is performing an enable by context and the rule or action is alreadyenabled for that particular context value.

v If the action is performing an overall enable, and the rule is already enabled forparticular context values.

Perform the following recovery efforts when the preceding conflicts occur:v Maintain the context and timing information. This action might not take effect

until the overall enable is removed.v Modify the timing information for the particular context to the values specified

in this action.v Set the overall enable with the specified timing information. The context enabled

information remains intact because some context values can be enabled for alonger period of time than the overall rule.

If a rule was previously enabled for a specific time period and is disabled, theenabled information is removed and the disabled condition takes over.

SymbolsSymbol substitution is supported in the ACTION, FOR, INTERVALS, RULE, andUNTIL specifications.

CLI exampleThe following example enables the MAIL_ALL action in all rules with namesbeginning with the FILE_ specification:ENABLE ACTION=MAIL_ALL, RULE=FILE_*

The following example enables the OUTPUT_LOG action in all rules with namesbeginning with the PROCESS_ specification for the next 48 hours:ENABLE ACTION=OUTPUT_LOG, RULE=PROCESS_*, FOR=48:00:00



EVENT TYPE=MESSAGE

DescriptionGenerates a message event that is displayed in the Tivoli Event Monitor. Amessage event can include a severity rating, classifications, and brief and full textmessages.

CLI syntaxEVENT TYPE=MESSAGE [,CLASS=class] [,COMPUTER=computer-name][,DATABASE] [,FILE=filename] [,FULL_TEXT=text] [,HOLD_TIME=time_spec][,NOT_FIXABLE] [,NOT_VISIBLE] [,REAL_TIME] [,SEVERITY=severity][,SUBCLASS=subclass], TEXT=message

where:

TYPE=MESSAGESpecifies that a message event be generated.

CLASS=classSpecifies the class of the message event. If the class is not specified, theclass is left blank when the event is displayed. If the class is specified, itmust be an alphanumeric string. If FILE or REAL_TIME is specified, themaximum number of characters is nine and if the DATABASE specificationis specified, the maximum number of characters is 32.

COMPUTER=computer-nameIf the DATABASE specification is specified, the name of the sourcecomputer for the message is specified and is written to the Computer fieldof the event in the event database. Otherwise, the name of the localcomputer is written to the Computer field of the event. A computer nameis specified when IBM Tivoli Management Solution for Exchange collectsinformation on another computer, such as with Simple NetworkManagement Protocol (SNMP).

If the DATABASE specification or local computer are not specified, thisspecification designates the computer on which to generate the event.

DATABASESpecifies that the event to be written to the local Tivoli event database. Youmust specify the DATABASE, FILE, or REAL_TIME specification. If none ofthese three specifications are specified, the DATABASE specification isassumed. The Tivoli local events database is opened if necessary andremains open until closed with the CLOSE action or until there has beenno activity for a period of more than twelve hours.

FILE=filenameSpecifies the file to which to write the message event. You must specify theDATABASE, FILE, or REAL_TIME specification. If none of these threespecifications are specified, the DATABASE specification is assumed. Thefile is opened if necessary and remains open until closed with the CLOSEaction or until there has been no activity with the file for a period of morethan 12-hours.

FULL_TEXT=textSpecifies the full text of the message event.

HOLD_TIME=time_specSpecifies the total time to hold the event and attempt re-delivery if the


event is initially undeliverable to remote computers that are interested inthe event. When the hold time is exceeded, the Tivoli Event Server nolonger attempts to send the event to interested remote computers becausethe event is considered too old to be of interest remotely. The event is stillstored locally if it passes the local event database filter. If you do notspecify HOLD_TIME, the default is HOLD_TIME=24:00:00. TheHOLD_TIME specification is valid only for the DATABASE specificationbound events.

NOT_FIXABLESpecifies if the problem described by this event is fixable or not. Bydefault, message events are fixable manually. The NOT_FIXABLEspecification is valid only for the DATABASE bound events.

NOT_VISIBLESpecifies that the event must not be visible to the Tivoli Event Monitor. Bydefault, all events are visible. The NOT_VISIBLE specification is valid onlyfor the DATABASE bound events.

REAL_TIMESpecifies that a real-time message event be generated. You must specifyone of the DATABASE, FILE, or REAL_TIME specifications. If none ofthese three specifications are specified, DATABASE is assumed. TheREAL_TIME events are delivered directly to the Tivoli server where theyare routed to interested event consumers throughout the network inreal-time. The Tivoli server process must be running for this action to besuccessful.

SEVERITY=severitySpecifies the severity of the message event. The severity value must be anumber in the range of 1 to 9 if FILE or REAL_TIME is specified. Thelower the severity number, the more severe the event is considered to be.

The severity can also be one of the following strings if DATABASE isspecified:

S Success

I Information

MW Minor Warning

W Warning

E Error

CE Catastrophic Error

AS Audit Success

AF Audit Failure

CR Critical

MA Major

MI Minor

WA Warning

CL Cleared

IN Indeterminate


Note: The severity is optional. If not specified, the severity is given adefault value of 3 for the FILE or REAL_TIME events and W for theDATABASE bound events.

SUBCLASS=subclassSpecifies the subclass of the message event. If the subclass is not specified,the subclass is left blank when the event is displayed. The subclass mustbe an alphanumeric string that is no longer than 32 characters. TheSUBCLASS specification is valid only for the DATABASE bound events.

TEXT=messageSpecifies the text of the message event. This specification is required. TheTEXT and FULL_TEXT specifications can be specified using one of thefollowing three methods:v A quoted line of text. This text can include a new line <NL> to specify

multiple lines of text.v An external text file, that uses @filespec.v A TEXT_BLOCK name.

SymbolsSymbol substitution is supported in the CLASS, COMPUTER, FILE, FULL_TEXT,SEVERITY, SUBCLASS, and TEXT specifications. However, a symbol cannot beused for the TEXT_BLOCK name or in the external file specification but symbolscan be used within the contents of these specifications.

CLI exampleThe following are legal examples of TEXT=message:TEXT="This is a quoted line with a symbol {STATISTIC_1}

TEXT="Line 1 <NL> Line 2 <NL> Line 3"

TEXT=BLOCK_A

[email protected]

Note: The contents of the BLOCK_A and @message.txt specifications can includesymbols.

The following example generates a real-time message event. The class for the eventis the PROCESS specification, the severity is three, and the text is contained in theprocess_problem_text variable in the default variable file.EVENT TYPE=MESSAGE, CLASS=PROCESS, REAL_TIME, TEXT={process_problem_text},SEVERITY=3

Process executionNone


EVENT TYPE=PROBLEM

DescriptionGenerates a problem event to be displayed in the Tivoli Event Monitor. A problemevent is uniquely identified by an alphanumeric handle. When a new problemevent is generated, it is marked in the Tivoli Event Monitor as a NEW event. If thesame event is generated again without first being solved, its status is changed tothe UPDATED specification. When the problem is solved, the event status ischanged to the CLOSED specification. In addition, a problem event can include aseverity rating and classifications, as well as brief and full text messages.

CLI syntaxEVENT TYPE=PROBLEM [,CLASS=class] [,COMPUTER=computer-name][,DATABASE] [,FILE=filename] [,FULL_TEXT=text] [HOLD_TIME=time_spec][,MANUAL_FIX] [,NAME=handle-name] [,NOT_FIXABLE] [,NOT_VISIBLE][,REAL_TIME] [,SEVERITY=severity] [,SUBCLASS=subclass], TEXT=message

where:

TYPE=PROBLEMSpecifies that a problem event be generated. This specification is requiredto generate a problem event.

CLASS=classSpecifies the class of the problem event. If the class is not specified, theclass is left blank when the event is later displayed. If the class is specified,it must be an alphanumeric string. If the FILE or REAL_TIME specificationis specified, the maximum number of characters is 9 and if the DATABASEspecification is specified, the maximum number of characters is 32.

COMPUTER=computer-nameIf the DATABASE specification is specified, the name of the computer thatis the source of the problem is specified and is written to the Computerfield of the event in the event database. Otherwise, the name of the localcomputer is written to the Computer field of the event. A computer nameis specified when IBM Tivoli Management Solution for Exchange collectsinformation on another computer, such as with Simple NetworkManagement Protocol (SNMP).

If the DATABASE specification or local computer is not specified, thisspecification designates the computer on which to generate the event.

DATABASESpecifies to write the event to the local Tivoli event database. You mustspecify the DATABASE, FILE, or REAL_TIME specification. If none ofthese three specifications are specified, the DATABASE specification isassumed. The Tivoli local events database is opened if necessary andremains open until closed with the CLOSE action or until there has beenno activity for a period of more than twelve hours.

FILE=filenameSpecifies the file to which to write the problem event. You must specify theDATABASE, FILE, or REAL_TIME specification. If none of these threespecifications are specified, the DATABASE specification is assumed. Thefile is opened if necessary and remains open until closed with the CLOSEaction or until there has been no activity with the file for a period of morethan 12-hours.


FULL_TEXT=textSpecifies the full text of the problem event.

HOLD_TIME=time_specSpecifies the total time to hold the event and attempt re-delivery if theevent is initially undeliverable to the remote computers that are interestedin the event. When the hold time is exceeded, the Tivoli Event Server nolonger attempts to send the event to interested remote computers becausethe event is considered too old to be of interest remotely. The event is stillstored locally if it passes the local event database filter. If this specificationis not specified, the default is HOLD_TIME=24:00:00. The HOLD_TIMEspecification is valid only for the DATABASE bound events.

MANUAL_FIXSpecifies that the problem is fixable manually. By default, problem eventsare fixable automatically. The MANUAL_FIX specification is only valid forthe DATABASE bound events and only one of the MANUAL_FIX andNOT_FIXABLE specifications can be specified.

NAME=handle-nameSpecifies an identifying name to be associated with the problem. If this isnot specified, a default handle name is formed by the rule engine that ismade up of the rule name, followed by the context, followed by thecreation date and time of the event.

NOT_FIXABLESpecifies if the problem event is fixable. By default, problem events arefixable automatically. The NOT_FIXABLE specification is valid only for theDATABASE bound events and only one of the MANUAL_FIX orNOT_FIXABLE specifications can be specified.

NOT_VISIBLESpecifies that the event must not be visible to the Tivoli Event Monitor. Bydefault, all events are visible. The NOT_VISIBLE specification is valid onlyfor the DATABASE bound events.

REAL_TIMESpecifies that a real-time problem event be generated. You must specifyone of the DATABASE, FILE, or REAL_TIME specifications. If none ofthese three specifications are specified, the DATABASE specification isassumed. The REAL_TIME events are delivered directly to the Tivoli serverwhere they are routed to interested event consumers throughout thenetwork in real-time. The Tivoli server process must be running for thisaction to be successful.

SEVERITY=severitySpecifies the severity of the problem event. If the FILE or REAL_TIMEspecification is specified, the severity value must be a number in the rangeof 1 to 9. The lower the severity number, the more severe the event isconsidered to be.

If the DATABASE specification is specified, the severity can also be one ofthe following strings:

S Success

I Information

MW Minor Warning

W Warning


E Error


AS Audit Success

AF Audit Failure

CR Critical

MA Major

MI Minor

WA Warning

CL Cleared

IN Indeterminate

Note: The severity is optional and if not specified, it is given a defaultvalue of 3 for the FILE or REAL_TIME events and W for theDATABASE bound events.

SUBCLASS=subclassSpecifies the subclass of the problem event. If the subclass is not specified,the subclass is left blank when the event is later displayed. The subclassmust be an alphanumeric string which is no longer than 32 characters. TheSUBCLASS specification is valid only for the DATABASE bound events.

TEXT=messageSpecifies the text of the problem event. This specification is required. TheTEXT and FULL_TEXT specifications can be specified using one of thefollowing three methods:v A quoted line of text. This text can include a new line,<NL>, to specify

multiple lines of text.v An external text file, using @filespec.v A TEXT_BLOCK name.

SymbolsSymbol substitution is supported in the CLASS, COMPUTER, FILE, FULL_TEXT,NAME, SEVERITY, SUBCLASS, and TEXT specifications.

CLI exampleThe following example specifies the default handle name for a disk rule namedLOW_FREE_SPACE, with the physical disk 0, on a computer named tiger, on June13th 1997 at 9:00:00 AM:LOW_FREE_SPACE|tiger|0|06131997090000

The following are legal examples of TEXT=message:TEXT="This is a quoted line with a symbol {STATISTIC_1}


TEXT=BLOCK_A

[email protected]



The following example generates a real-time problem event. The class for the eventis the PROCESS specification, the severity is 3, the handle name is the rule context,and the text is contained in the PROCESS_PROBLEM text block.EVENT TYPE=PROBLEM, CLASS=PROCESS, REAL_TIME, TEXT=PROCESS_PROBLEM, NAME={CONTEXT}, \SEVERITY=3

Process executionNone.


EVENT TYPE=TEXT

DescriptionGenerates a text event to be displayed in the Tivoli Event Monitor. A text eventspecifies only a text message, without any severity rating or other eventclassification.

CLI syntaxEVENT TYPE=TEXT [,FILE=filename] [,COMPUTER=computer-name][,REAL_TIME],TEXT=message

where:

TYPE=TEXTSpecifies to generate a text event. This specification is required to generatea text event.

COMPUTER=computer-nameSpecifies the name of the computer on which to generate the event. If thisis not specified, the event is generated on the local computer.

FILE=filenameSpecifies the name of the file to write the event to. You must specify theFILE or REAL_TIME specification. The file is opened if necessary andremains open until closed with the CLOSE action or until there has beenno activity with the file for a period of more than twelve hours.

REAL_TIMESpecifies to generate a real-time text event. You must specify the FILE orREAL_TIME specification. The REAL_TIME events are delivered directly tothe Tivoli server where they are routed to interested event consumersthroughout the network in real-time. The Tivoli Server process must berunning for this action to be successful.

TEXT=messageSpecifies the text of the event. The TEXT specification can be specifiedusing one of the following three methods:v A quoted line of text. This text can include a new line <NL> to specify


SymbolsSymbol substitution is supported in the FILE, COMPUTER, and TEXTspecifications. However, a symbol cannot be used for the TEXT_BLOCK name or inthe external file specification but symbols can be used within the contents of thesespecifications.



TEXT=BLOCK_A

[email protected]


EVENT TYPE=WINDOWS

DescriptionGenerates a Windows NT event. Windows NT events are defined by the operatingsystem and can be interpreted both by IBM Tivoli Management Solution forExchange and by applications that can handle native Windows NT events.

CLI syntaxEVENT TYPE=WINDOWS [,FILE=filename] [,COMPUTER=computer-name][,REAL_TIME] [,SUBTYPE=subtype], TEXT=message

where:

TYPE=WINDOWSSpecifies that a Windows NT Event be sent to the Tivoli Server or to theWindows NT Event Logging facility. This specification is required togenerate a Windows NT Event.

COMPUTER=computer-nameSpecifies the name of the computer on which to generate the event. If thecomputer is not specified, the event is generated on the local computer.

FILE=filenameSpecifies the name of the Windows NT Event Facility file to which to writethe event. The SYSTEM and APPLICATION files can be used. You mustspecify the FILE or REAL_TIME specification. Other applications can readthe WINDOWS events that are generated with the FILE specification. Theuse of the FILE keyword indicates that the generated event must be sent tothe Windows NT Event Facility and not to the Tivoli Server.

REAL_TIMESpecifies that a real-time Windows NT event be generated. You mustspecify the FILE or REAL_TIME specification. The REAL_TIME events aredelivered directly to the Tivoli server where they are routed to interestedevent consumers throughout the network in real-time. The Tivoli Serverprocess must be running for this action to be successful. The use of theREAL_TIME keyword indicates that the generated event must be sent tothe Tivoli Server and not the Windows NT Event Facility.

SUBTYPE=event-typeSpecifies the event type of the Windows NT event. If the SUBTYPEspecification is not specified, the subtype of the event is theINFORMATION specification. The subtype field corresponds to the Typefield in the Windows NT Event Viewer facility. The following values arelegal:v Errorv Error eventv Warningv Warning eventv Informationv Information eventv Success Auditv Success Audit eventv Failure Audit


v Failure Audit event

TEXT=messageSpecifies the text of the Windows NT event. This specification is required.The TEXT specification can be specified using one of the following threemethods:v A quoted line of text. This text can include a new line <NL> to specify


SymbolsSymbol substitution is supported in the COMPUTER, SUBTYPE, and TEXTspecifications. However, a symbol cannot be used for the TEXT_BLOCK name or inthe external file specification but symbols can be used within the contents of thesespecifications.



TEXT=BLOCK_A

[email protected]


The following example generates a Windows NT event to the System log of theWindows NT event log facility. The category for the event is the PROCESSspecification, the sub type of the event is the WARNING specification, the fieldshows up as the type field in the Windows NT event log facility, and the text forthe event is contained in the PROCESS_PROBLEM text block.EVENT TYPE=WINDOWS, FILE=SYSTEM, SUBTYPE=WARNING, TEXT=PROCESS_PROBLEM



EXECUTE

DescriptionTo execute an operating system command or an asynchronous rule.

CLI syntaxEXECUTE OS_COMMAND=command, [LOG_FILE=log-file], [ASYNCHRONOUS],[COMPUTER=computer-name], RULE=(rule-name[,...])

where:

ASYNCHRONOUSIf the ASYNCHRONOUS specification is specified, the rule engine does notwait for the system command to complete before continuing execution.Starting several commands asynchronously can cause unexpectedinteractions. When multiple commands are started asynchronously, theoutput of each command is redirected to a different log file or to the NULlog file to prevent log file sharing violations from occurring.

COMPUTER=computer-nameSpecifies the computer on which to execute the command.

LOG_FILE=log-fileThe log file where output of a system command is redirected. If youspecify NUL, no output is produced and if you explicitly specify theredirection operators (>, >>) in the system command, you must not specifya log file.

OS_COMMAND=commandThe OS_COMMAND specification designates the operating systemcommand to execute. You must quote the command if it contains anycommas. The quotes are stripped before the command is passed to theoperating system. You must use two sets if the operating system requiresquotes.

The IBM Tivoli Management Solution for Exchange default location is themain installation directory. You must include the path name of thecommand if it is not in this directory or in a directory included in yoursystem path.

If you want to execute an operating system command that interacts withthe desktop, the Tivoli Rule Server must be running from the systemaccount. Also, you must enable the Allow Service to Interact withDesktop check box for the Tivoli Rule Server in the Services applet of theControl Panel.

Note: Enabling the Allow Service to Interact with Desktop check box canprevent you from executing actions that require network privilegessuch as accessing a remote drive.

RULE=(rule-name[,...])Specifies the rule to execute. Only rules that are ASYNCHRONOUS can beexecuted through this action. A list of rule names can be specified, butranges and wildcards are not valid. The rules are executed in the order inwhich they are listed.


SymbolsSymbol substitution is supported in the COMPUTER, LOG_FILE, OS_COMMAND,and RULE specifications.

CLI exampleThe following example starts c:\backup\backup.exe:EXECUTE OS_COMMAND=c:\backup\backup.exe

The following example starts the Tivoli TCP/IP server:EXECUTE OS_COMMAND=""c:\Program Files\TEMS\bin\RoboMon /Ss""

Note: Two sets of quotes are required because there is a space in the file’s pathname.

The following example executes the FIND_LARGE_FILES asynchronous rule:EXECUTE RULE=FIND_LARGE_FILES



EXECUTE_SQL

DescriptionExecutes a specified SQL statement.

CLI syntaxEXECUTE_SQL [COMPUTER=computer_name,][DATA_SOURCE=data_source_name,][OPTIONS=connection_options,][PASSWORD=password,] [USER_ID=user_id,] SQL=″;SQL_statement″;

where:

COMPUTER=computer_nameSpecifies the computer on which the SQL statement is executed. Thiscorresponds to the ODBC HOST attribute. If the COMPUTER specificationis not specified, the local host is used.

DATA_SOURCE=data_source_nameSpecifies the ODBC data source to be operated on. This must be a systemdata source name. The data source is opened if necessary and remainsopen until closed with the CLOSE action or until there has been no activitywith the data source for a period of more than 12-hours. If thisspecification is not specified, the data source specified with the SETDATA_SOURCE definition is used. If there is not a SET definition, theEXECUTE_SQL action fails.

OPTIONS=connection_optionsSpecifies the ODBC attribute and value pairs that are required to properlyaccess and process the database.

PASSWORD=passwordSpecifies the password associated with the user ID being used to log intothe database. This specification corresponds to the ODBC PWD attribute. Ifomitted, the value from the registry entry for the database is used.

SQL=″;SQL_statement″;Specifies the SQL statement to be executed. You must contain the SQLstatement in quotes and the SQL statement must be the last specificationspecified. When the SQL keyword is detected, the rest of the line isinterpreted as the SQL statement to execute.

USER_ID=user_idSpecifies the user identification string to use to log into the database. Thiskeyword corresponds to the ODBC UID attribute. If omitted, the valuefrom the registry entry for the database is used.

SymbolsSymbol substitution is supported in the DATA_SOURCE, COMPUTER, USER_ID,PASSWORD, OPTIONS, and SQL keyword values.

CLI exampleEXECUTE_SQL DATA_SOURCE=Inventory, SQL=";INSERT Parts (Part, Inventory, Price)\VALUES (’132N’;, 1000, 9.95)";



EXIT

DescriptionExit the rule engine process with the specified exit status.

CLI syntaxEXIT STATUS=value

where:

STATUS=valueUses the specified value as the exit status. The value can be an expressionthat is converted to a longword before using the value as the exit status ofthe rule engine process. The expression syntax is the same as thatsupported in a calculate expression. This specification is required.

SymbolsAll items in the expression are assumed to be statistics, user-defined statistics,variables, or constants. The operands must be statistic names, user-defined statisticnames, variable names, numeric constants, or string constants which are containedin quotes. You must not enclose the statistic and variable names in braces ({}).

Variable values are retrieved from the rule engine memory structures; if thevariable does not exist in these structures, it is looked for in the default variablefile. If it is not in the default file, a value of zero is used.

CLI exampleThe following example causes the process to terminate with the exit status of thestatus of the previously executed action:EXIT STATUS=$ACTION_STATUS



EXPORT

DescriptionWrites to a binary data file, an ODBC data source, or a jet database. Binary datafiles are organized into records containing one or more fields. Each time anEXPORT statement executes, a new record is written to the specified file ordatabase. For entity-level rules, one record is written for each entity that meets therule condition.

CLI syntaxExporting to an ODBC data source:

EXPORT DATA_SOURCE=data_source_name [,COMPUTER=computer-name][,OPTIONS=connection_options] [,PASSWORD=password][,TABLE_NAME=table_name] [,USER_ID=user_id],STATISTICS=(statistic[=column_name[:length]][,...])

where::

COMPUTER=computer-nameSpecifies the computer on which the export action is performed.

When exporting data to an ODBC data source, the action is alwaysexecuted on the local computer, even if a remote computer name isspecified. This computer name is passed to ODBC, which writes the datato the remote computer. However, this mechanism requires ODBC to beinstalled locally as well as on the remote computer.

DATA_SOURCE=data_source_nameSpecifies the ODBC data source to be written to. This must be a systemdata source name. The data source is opened if necessary and remainsopen until closed with the CLOSE action or until there has been no activitywith the data source for a period of more than twelve hours.

OPTIONS=connection_optionsUsed to specify ODBC attribute and value pairs that are required toproperly access and process the database.

PASSWORD=passwordSpecifies the password associated with the user ID being used to log intothe database. This keyword corresponds to the ODBC PWD attribute. Ifomitted, the value from the registry entry for the database is used.

STATISTICS=(statistic[=column_name[:length]][,...])Specifies the statistics whose values are to be written to the specifieddatabase. Statistic names can be followed by an optional =column_name oran optional :length.

The column_name corresponds to the column name specified in the table ofthe database. If the column_name is the same as the statistic name, you donot need to specify column_name.

The length is ignored on all but string statistics and defines how manycharacters to write out for string statistic values. If no length is specified,the length of the field in the output is the length of the statistic value.

TABLE_NAME=table_nameSpecifies the table name in the ODBC data source.


USER_ID=user_idSpecifies the user identification string to use to log into the database. Thiskeyword corresponds to the ODBC UID attribute. If omitted, the valuefrom the registry entry for the database is used.

Exporting to a jet database:

EXPORT DATABASE=database_name [,TABLE_NAME=table_name],STATISTICS=(statistic[=column_name[:length]][,...])

where:

DATABASE=database_nameSpecifies the name of the jet database. The database is opened if necessaryand remains open until closed with the CLOSE action or until there hasbeen no activity with the database for a period of more than 12-hours.

STATISTICS=(statistic[=column_name[:length]][,...])Specifies the statistics whose values are to be written to the specifieddatabase. Statistic names can be followed by an optional =column_name oran optional :length.

The column_name corresponds to the column name specified in the table ofthe database. If the column_name is the same as the statistic name, you donot need to specify the column_name.

The length is ignored on all but string statistics and defines how manycharacters to write out for string statistic values. If no length is specified,the length of the field in the output is the length of the statistic value.

Note: The first two columns written to a jet database are alwaysRecordNumber and DateTime. The first statistic specified in this listis written to the third column of the database. When exporting to anexisting database, these two columns must already be defined in thedatabase.

TABLE_NAME=table_nameSpecifies the table name in the database.

Exporting to a binary data file:

EXPORT FILE=filename [,COMPUTER=computer-name],STATISTICS=(statistic[:length][,...])

where:

COMPUTER=computer-nameSpecifies the computer on which the export action is performed.

FILE=filenameSpecifies the file to be written. The file is opened if necessary and remainsopen until closed with the CLOSE action or until there has been no activitywith the file for a period of more than twelve hours.

STATISTICS=(statistic[:length][,...])Specifies the statistics whose values are written to the specified file.Statistic names can be followed by an optional :length specification. This isignored on all but string statistics and defines how many characters towrite out for string statistic values. If no length is specified, the length ofthe field in the output is the length of the statistic value, resulting in


records having varying lengths. You must always specify a length to insurethat you get fixed length records in the output file, resulting in valuesbeing space padded or truncated.

SymbolsNone.

CLI exampleThe following example writes to the c:\TEMS\user\binary_data.dat file. There is arecord written for each process that contains an 8-byte float for the DATEspecification, an 8-byte float for the TIME specification, a 4-byte integer for thePROCESS_ID specification, and a 4-byte integer for thePROCESS_BASE_PRIORITY_CLASS specification:EXPORT FILE=c:\TEMS\user\binary_data.dat,-STATISTCS=(DATE,TIME,PROCESS_ID, PROCESS_BASE_PRIORITY_CLASS)

The following example writes to the c:\TEMS\user\disk_system_data.dat file. Eachrecord contains a 20-character field with the disk ID, followed by a floating pointfield containing the value of the DISK_SIZE statistic:EXPORT FILE=c:\TEMS\user\disk_system_data.dat, -STATISTICS=(DISK_ID:20,DISK_SIZE)



IF

DescriptionEnables conditional execution of actions and must appear after one of the ACTIONstatements in a rule. The IF statement can be expressed in two different forms: asingle line if there is only one action to be taken based on the value of theexpression, or a multi-line format if there are multiple actions to be taken.

In both forms of the IF statement, the expression is evaluated. If it is non-zero, theactions following the THEN statement are executed. In the multi-line form, theactions following the optional ELSE statement are executed if the expressionevaluates to zero.

Additionally, the multi-line form enables the use of the ELSE_IF statements. Theseare evaluated if the result of the expression in the IF statement is zero. Theexpression in the ELSE_IF statement is evaluated and treated in a similar way asthe IF statement. If the value is non-zero, the THEN statements are executed;otherwise the ELSE statements are evaluated.

CLI syntaxIF expression THEN action [ELSE action]

or

IF expression THEN

action

...

[[ELSE_IF expression THEN

action

......]

[ELSE

action

... ...]

END_IF

where:

action A valid Tivoli action statement.

expressionA valid Tivoli expression.

SymbolsAll items in the expression are assumed to be statistics, user-defined statistics,variables, or constants. The operands must be statistic names, user-defined statistic


names, variable names, numeric constants, or string constants that are contained inquotes. You must not enclose the statistic and variable names in braces ({}).

Variable values are retrieved from the rule engine memory structures. If thevariable does not exist in these structures, the default variable file is searched. If itis not in the default file, a value of zero is used.

CLI exampleThe following example logs a message if the value of the DISK_FREE_PCT statisticis less than 10 and logs a different message if the value is less than 20. Otherwise,there is a third message that is written to the log.IF DISK_FREE_PCT < 10 THEN

LOG FILE=c:\TEMS\user\information.log, -

TEXT= "Space % is extremely low {DISK_FREE_PCT} on {DISK_ID}"

ELSE_IF DISK_FREE_PCT < 20 THEN


TEXT="Space % is very low -{DISK_FREE_PCT} on {DISK_ID}"

ELSE


TEXT="Space % -is OK {DISK_FREE_PCT} on {DISK_ID}"

END_IF

The following example sends a mail message if the value of the TOTAL_COUNTstatistic is greater than five. Since only one action is taken, the single-line form ofthe IF statement can be used:IF TOTAL_COUNT>5 THEN MAIL USER=Admin, -

TEXT="5 iterations - have occurred"



INCREMENT

DescriptionIncrements the value of one or more variables by 1. The value of the variable isupdated in memory; if the variable is read in from disk, the on-disk value is notchanged.

CLI syntaxINCREMENT variable[,...]

where:

variableA comma-separated list of the names of the variables to be incremented.The value of the variable that is stored in memory is incremented by one.Variables are not loaded from a disk or written to a disk. If a specific levelis specified for the variable through the VARIABLE statement, it isreferenced for that particular context level. If no level is specified, thecurrent lowest context level applies.

If the variable does not currently exist in memory, it is created with a valueof 1.

SymbolsNone.

CLI exampleThe following example increments the in-memory value of the COUNTER variableby one:INCREMENT COUNTER



LOG

DescriptionLogs a message to a file.

CLI syntaxLOG FILE=filename, [COMPUTER=computer-name], TEXT=text

where:

COMPUTER=computer-nameSpecifies the name of the computer on which the log action is performed.

FILE=filenameSpecifies the file name or terminal of the log file. The file is opened ifnecessary and remains open until closed with the CLOSE action or untilthere has been no activity with the file for a period of more than twelvehours.

TEXT=textSpecifies what to log to the file. The text can be specified using one ofthree methods:v A quoted line of text. This text can include a new line <NL> to specify


SymbolsSymbol substitution is supported in the FILE, COMPUTER, and TEXTspecifications. However, a symbol cannot be used for the TEXT_BLOCK name or inthe external file specification but symbols can be used within the contents of thesespecifications.

CLI exampleThe following are legal examples of TEXT=message:TEXT="This is a quoted line with a symbol {STATISTIC_1}"


TEXT=BLOCK_A

[email protected]


The following example logs a message to the c:\TEMS\log\user_information.logfile. The contents of the message are the contents of the PROCESS_MESSAGE textblock:LOG FILE=c:\TEMS\log\user_information.log, -

TEXT=PROCESS_MESSAGE

The following message logs a message to the c:\TEMS\logs\process_info.log file.The message text has the value of the process ID substituted before the text iswritten:


LOG FILE=c:\TEMS\logs\process_info.log, -

TEXT="Process {PROCESS_NAME} is an idle process"

The following message logs a message to the c:\TEMS\logs\process_info.log file.Each line has the same length, 12-characters for the process name followed by aspace, and the CPU percentage formatted to a length of 6 with 2 decimal places:LOG FILE=c:\TEMS\logs\process_info.log, -

TEXT="{PROCESS_NAME:12} {PROCESS_CPU_PCT:6.2}%"



MAIL

DescriptionSends a mail message to a user or a list of users.

The MAIL action is initiated asynchronously by the rule engine and cannot be usedin one-shot rules. Depending on how you configured IBM Tivoli ManagementSolution for Exchange using the Tivoli configuration wizard, the MAIL action isimplemented using SMTP, Microsoft Exchange, or CC Mail. You must configure thespecified mail software properly for the MAIL action to execute successfully.

CLI syntaxMAIL [COMPUTER=computer-name], [SUBJECT=text], TEXT=text,USER=(name[,...])

where:

COMPUTER=computer-nameSpecifies the name of the computer on which the mail action is performed.

SUBJECT=textSpecifies the text that is used as the subject for the mail message. This canbe a quoted string of text only, although the text can contain symbolreferences.

TEXT=textSpecifies what to log to the file. The text can be specified using one ofthree methods:v A quoted line of text. This text can include a new line <NL> to specify


USER=(name[,...])Specifies the user to receive the mail message. This can be a single user ormultiple users.

SymbolsSymbol substitution is supported in the COMPUTER, SUBJECT, TEXT, and USERspecifications. However, a symbol cannot be used for the TEXT_BLOCK name or inthe external file specification but symbols can be used within the contents of these.



TEXT=BLOCK_A

[email protected]


The following example sends a mail message to the Admin user, with the subjectof DISK low on space, and the contents of the mail message is the contents of the


c:\TEMS\user\disk_low_space.txt file. Any symbols contained within the text ofthis file is substituted before the message is sent:MAIL USER=Admin, SUBJECT="{DISK low on space",-TEXT=@c:\TEMS\user\disk_low_space.txt



MODIFY

DescriptionModifies a schedule. Any components that are not specified are left unchanged.

CLI syntaxMODIFY [SCHEDULE= schedule name], [DATES=(date[-date][,...])],[DAYS=(number[number][,...])],

[HOURS=(number[-number][,...])], [INTERVAL=interval],

[MONTHS=(month[-month][,...])], [SCHEDULE=name],

[TIMES=(time[-time][,...])], [WEEKDAYS=(weekday[weekday][,...])],

[WEEKS=(number[-number][,...])]

where:

DATES=(date[-date][,...])Specifies the newly scheduled dates to execute. If not specified, the datesin the selected schedule are used.

DAYS=(number[number][,...])Specifies the newly scheduled days of the month to execute. If notspecified, the days in the selected schedule are used.

HOURS=(number[-number][,...])Specifies the newly scheduled hours of the day to execute. If not specified,the hours in the selected schedule are used.

INTERVAL=intervalSpecifies the newly scheduled interval. If not specified, the interval in theselected schedule are used.

MONTHS=(month[-month][,...])Specifies the newly scheduled months of the year to execute. If notspecified, the months in the selected schedule are used.

SCHEDULE=nameSpecifies the name of the schedule to be modified. If not specified, theschedule of the current rule is modified.

If a schedule is not defined with the specified name, but there is a rulewith the specified name, the schedule for that rule is potentially modified.If the rule is written with a USE SCHEDULE statement, the schedule forthe rule is modified. If the rule is written with a SCHEDULE statement, theschedule of the rule is modified according to the specified changes.

SCHEDULE= schedule nameSpecifies the schedule to modify. If the SCHEDULE= specification is notspecified, the schedule for the current rule is modified.

TIMES=(time[-time][,...])Specifies the newly scheduled times of day to execute. If not specified, thetimes in the selected schedule are used.


WEEKDAYS=(weekday[weekday][,...])Specifies the newly scheduled days of the week to execute. If not specified,the weekdays in the selected schedule are used. The days are numbered 1through 7 beginning with Monday.

WEEKS=(number[-number][,...])Specifies the newly scheduled weeks of the month to execute. If notspecified, the weeks in the selected schedule are used.

SymbolsSymbol substitution is supported in the DATES, DAYS, HOURS, INTERVAL,MONTHS, TIMES, WEEKDAYS, and WEEKS specifications.

CLI exampleThe following example modifies the schedule of the current rule to have aten-minute interval:MODIFY INTERVAL=00:10:00

The following example modifies the LARGE_FILES schedule to execute during theperiod of 8 AM through 5 PM:MODIFY SCHEDULE=LARGE_FILES,TIMES=(8:00-17:00)

The following example modifies the PRIME_HOURLY schedule to execute only onMonday through Friday during the hours of 8 AM to 5:59:59 PM:MODIFY SCHEDULE=PRIME_HOURLY,WEEKDAYS=1-5,HOURS=8-17



PRIORITY

DescriptionAlters the scheduling priority of a running process. The PRIORITY action isinitiated asynchronously by the rule engine and cannot be used in one-shot rules.

CLI syntaxPRIORITY [COMPUTER=computer-name], PROCESS_ID=process-id,[CLASS=priority class]

where:

CLASS=priority classSpecifies the intended priority change for the REALTIME, HIGH,NORMAL, or IDLE process. This specification is required.

COMPUTER=computer-nameSpecifies the computer on which to perform the priority change operation.

PROCESS_ID=process-idSpecifies the process ID whose priority is to be changed. This specificationis required and you must have security access to the process to change it.For example, the Tivoli rule server must be running from the systemaccount to change the priority of certain system processes.

SymbolsSymbol substitution is supported in the COMPUTER, PROCESS_ID, and CLASS,specifications. The value of the PROCESS_ID is typically the same as thePROCESS_ID statistic.

CLI exampleThe following example changes the scheduling priority of the process whoseprocess ID is the value of the PROCESS_ID statistic to NORMAL:PRIORITY CLASS=NORMAL, PROCESS_ID={PROCESS_ID}



READ

DescriptionReads one or more variables from a file or the Windows NT registry, and saves thevalue in the rule engine memory structures.

CLI syntaxREAD [FILE=filename], [COMPUTER=computer-name], [HIVE=hive name], [KEY=keyname], [VALUE_ENTRY=value entry name], VARIABLE=(variable[,...])

where:

COMPUTER=computer-nameSpecifies to execute the read operation on another computer.

FILE=filenameSpecifies the file from which to read the specified variable. If this is notspecified, the default variable file is used. If there is no default variablefile, the READ action is not performed.

If the FILE specification is specified, the HIVE specification cannot bespecified. The file is opened if necessary and remains open until closedwith the CLOSE action or until there has been no activity with the file fora period of more than 12-hours.

HIVE=hive nameSpecifies the hive to access. If the HIVE specification is present, it impliesthat you are accessing the Windows NT registry rather than a variable file.If the HIVE specification is specified, the FILE specification cannot bespecified. One of the HKEY_LOCAL_MACHINE, HKEY_USERS, orHKEY_CLASSES_ROOT hives are accessed.

KEY=key nameSpecifies the key to access for the Windows NT Registry only. If the HIVEspecification is specified, this keyword is required.

VALUE_ENTRY=value entry nameSpecifies the value entry from which to read for the Windows NT Registryonly. The value entry can be of any data type except the REG_MULTI_SZand REG_EXPAND_SZ data types. If the HIVE specification is specified,this keyword is required.

VARIABLE=(variable[,...])Specifies the list of variables to read from a file. This specification isrequired.

SymbolsSymbol substitution is supported in the COMPUTER, FILE, HIVE, KEY, andVALUE_ENTRY specifications.

CLI exampleThe following example reads the ORACLE_PROCESS_EXISTS_STATUS variablefrom the default variable file:READ VARIABLE=ORACLE_PROCESS_EXISTS_STATUS


The following example reads the LARGE_FILES_ACTION_STATUS andLARGE_DIRECTORIES_ACTION_STATUS variables from thec:\TEMS\config\automation.var variable file:READ FILE=c:\TEMS\config\automation.var,-

VARIABLE=(large_files_action_status,large_directories_action_status)

In the following example, the value of the ComputerName value entry in theSYSTEM\CurrentControlSet\Control\ActiveComputerName key on theHKEY_LOCAL_MACHINE hive reads into the SYSTEM_NAME variable:READ HIVE=HKEY_LOCAL_MACHINE, -KEY=SYSTEM\CurrentControlSet\Control\ActiveComputerName, -VALUE_ENTRY=ComputerName,-

VARIABLE=SYSTEM_NAME



REMOVE

DescriptionRemoves a file.

CLI syntaxREMOVE FILE=filename, [COMPUTER=computer_name]

where:

COMPUTER=computer_nameSpecifies the computer on which to perform the remove operation.

FILE=file_nameThe file name to be removed. This specification is required.

SymbolsSymbol substitution is supported in the FILE specification.

CLI exampleThe following example removes the c:\temp\error_log.backup file:REMOVE FILE=c:\temp\error_log.backup



SNMP_SET

DescriptionSets the value of an SNMP variable.

CLI syntaxSNMP_SET STATISTIC=statistic, VALUE=value, AGENT=agent_ip_address orSNMP_SET [COMMUNITY=community,] [DATA_TYPE=data_type,} OID=oid[,TIMEOUT=timeout], VALUE=value, AGENT=agent_ip_address

where:

AGENT=agent_ip_addressSpecifies the IP address of the agent.

COMMUNITY=communitySpecifies the SNMP community. If not specified, the public value is used.

DATA_TYPE=data_typeSpecifies the data type of the variable, which can be the STRING,INTEGER, or FLOAT data type. If not specified, the STRING data type isused.

OID=oidSpecifies the object identifier of the SNMP variable. This specification isrequired.

STATISTIC=statisticSpecifies the name of the Tivoli statistics associated with the SNMPvariable.

TIMEOUT=timeoutSpecifies the number of milliseconds used as a timeout value when settingthe SNMP variable. If not specified, a value of 2000 (2 seconds) is used.

VALUE=valueSpecifies the value of the SNMP variable to set. This specification isrequired.

If you are setting an SNMP variable defined by a Tivoli statistic, use the first formof the syntax, specifying the statistic name. Otherwise, use the second form of thesyntax, specifying the variable definition.

SymbolsSymbol substitution is supported in the AGENT, COMMUNITY, OID, STATISTIC,TIMEOUT, and VALUE specifications.

CLI exampleThe following example sets the value of the integer SNMP variable defined by the1.2.3.4 OID in the public community with a value of 0 on the agent with an IPaddress of 100.60.50.1. A timeout of 3 seconds is used:SNMP_SET OID=1.2.3.4, COMMUNITY=public, DATA_TYPE=INTEGER, TIMEOUT=3000,\VALUE=0, AGENT=100.60.50.1



SNMP_TRAP

DescriptionGenerates an SNMP Trap.

CLI syntaxSNMP_TRAP [CLASS=class,] [FULL_TEXT=text,] NUMBER=number,[SEVERITY=severity,] [SUBCLASS=subclass,] TEXT=message [,VAR1=variable1 text][,VAR2=variable 2 text] [,VAR3= variable 3 text] [,VAR4= variable 4 text] [,VAR5=variable 5 text]

where:

CLASS=classSpecifies the class of the SNMP trap. This specification is optional and ismapped into the 1.3.6.1.4.1.1339.2 Tivoli OID.

FULL_TEXT=textSpecifies the full text of the SNMP trap. This text is optional and ismapped into the 1.3.6.1.4.1.1339.5 Tivoli OID.

NUMBER=numberSpecifies the SNMP trap specific number.

SEVERITY=severitySpecifies the severity of the SNMP trap. This is optional and is mappedinto the 1.3.6.1.4.1.1339.1 Tivoli OID. The severity value can be a number inthe range of 1 to 9 or one of the following strings:

S Success

I Information

MW Minor Warning

W Warning

E Error


AS Audit Success

AF Audit Failure

CR Critical

MA Major

MI Minor

WA Warning

CL Cleared

IN Indeterminate

SUBCLASS=subclassSpecifies the subclass of the SNMP trap. This is optional and is mappedinto the 1.3.6.1.4.1.1339.3 Tivoli OID.

TEXT=messageSpecifies the SNMP trap brief text. This text is required and is mapped intothe 1.3.6.1.4.1.1339.4 Tivoli OID.


VAR1=variable1_textOptionally specifies the text that is mapped into the 1 Tivoli variable. TheOID for this text is 1.3.6.1.4.1.1339.6.





The TEXT, FULL_TEXT, and VARIABLE specifications can be specified using oneof the following three methods:v A quoted line of text. This text can include a new line <NL> to specify multiple

lines of text.v An external text file, using @filespec.v A TEXT_BLOCK name.

SymbolsSymbol substitution is supported in the NUMBER, CLASS, SUBCLASS, SEVERITY,TEXT, FULL_TEXT, VAR1, VAR2, VAR3, VAR4, and VAR5 specifications. However,a symbol cannot be used for the TEXT_BLOCK name or in the external filespecification, but symbols can be used within the contents of these specifications.



TEXT=BLOCK_A

[email protected]


The following example generates an SNMP trap with a specific trap number of 1.The SNMP trap text is contained in the PROCESS_PROBLEM text block. The textfor the 1 Tivoli variable is Problem reported by Tivoli:SNMP_TRAP TEXT=PROCESS_PROBLEM, VAR1=";Problem reported by Tivoli";, NUMBER = 1



TERMINATE

DescriptionTerminates the specified process. The TERMINATE action is initiatedasynchronously by the rule engine and cannot be used in one-shot rules.

CLI syntaxTERMINATE [COMPUTER=computer_name], PROCESS_ID=process_id

where:

COMPUTER=computer_nameSpecifies that the process has stopped on another computer.

PROCESS_ID=process_idSpecifies the process ID of the process to be stopped. This specification isrequired.

You must have security access to the process to terminate. For example, theTivoli rule server must be running from the system account to terminatecertain system processes.

SymbolsSymbol substitution is supported in the COMPUTER and PROCESS_IDspecifications. The value of the PROCESS_ID specification is the PROCESS_IDstatistic as shown in the example.

CLI exampleThe following example stops the process with the PROCESS_ID specification asdefined by the value of the PROCESS_ID statistic:TERMINATE PROCESS_ID={PROCESS_ID}



WAIT

DescriptionCauses execution of the rule engine process to stop until the value of a particularvariable satisfies a specified conditional expression. The variable value is read froma specified file, or the default variable file if none is specified, every second untilthe condition is met.

This action provides a mechanism to synchronize one rule process with another.Use of the WAIT action is dependent on another rule process to modify the valueof the specified variable. If there is no other process to modify the value, the ruleengine hangs while executing the WAIT action. If a file is not specified and there isno default variable file, no waiting occurs.

If the variable is not found in the file, the action continues to try until it is foundand the condition is true. It is important to note that no rules execute until thiscondition is true. The rule engine reads the variable once every second until thecondition is true. While this is happening, the rule engine does not perform anyother functions.

CLI syntaxWAIT [FILE=filename], VARIABLE=name, conditional_expression

where:

conditional_expressionThe format of the conditional_expression specification is operator value,where the value can be a constant or an expression.

The conditional_expression specification must include one of the followingvalid relational operators:v =v <>v <v >v <=v >=

The following is an example of a valid conditional expression:=VARIABLE_1

or>3

The value expression can include other variables or statistics. Variablesincluded in the value expression are evaluated as follows:v If in memory, that value is used.v If not in memory, the value is retrieved from the default file.v If not in this file, zero is used.

FILE=file_nameSpecifies the name of the file from which to read the variable. If this optionis not specified, the default variable file is used. The file is opened if


necessary and remains open until closed with the CLOSE action or untilthere has been no activity with the file for a period of more than twelvehours.

VARIABLE=nameSpecifies the name of the variable to read and test.

SymbolsSymbol substitution is supported in the FILE specification. Symbols which arevariables or statistics can be included in the conditional expression. You must notuse the braces ({}) notation in the expression.

CLI exampleThe following example causes the rule process to stop and wait until the value ofthe TOTAL_COUNT variable in the default variable file is greater than 30:WAIT VARIABLE=TOTAL_COUNT, >30



WORKING_SET

DescriptionModifies the working set of a process.

CLI syntaxWORKING_SET [MINIMUM_SIZE=minsize,]

[MINIMUM_CHANGE=minchange,] [MAXIMUM_SIZE=maxsize,]

[MAXIMUM_CHANGE=maxchange,] PROCESS_ID=pid

where:

MAXIMUM_CHANGE=maxchangeSpecifies the amount to change the maximum working set for the process.This value can be positive or negative, and can include a percent sign toindicate a percentage change. The Windows NT virtual memory managerattempts to keep no more than this much memory resident in the process.The MAXIMUM_CHANGE specification cannot be specified with theMAXIMUM_SIZE specification.

MAXIMUM_SIZE=maxsizeSpecifies the new value, in bytes, for the maximum working set for theprocess. The Windows NT virtual memory manager attempts to keep nomore than this much memory resident in the process. A 1 value means toset the maximum working set to its default value. To empty the workingset of a process, set both the MINIMUM_SIZE and MAXIMUM_SIZEspecifications to 0. The MAXIMUM_SIZE specification cannot be specifiedwith the MAXIMUM_CHANGE specification.

MINIMUM_CHANGE=minchangeSpecifies the amount to change the minimum working set for the process.This value can be positive or negative, and can include a percent sign toindicate a percentage change. The Windows NT virtual memory managerattempts to keep at least this much memory resident in the process. TheMINIMUM_CHANGE specification cannot be specified with theMINIMUM_SIZE specification.

MINIMUM_SIZE=minsizeSpecifies the new value, in bytes, for the minimum working set for theprocess. The Windows NT virtual memory manager attempts to keep atleast this much memory resident in the process. A –1 value means to setthe minimum working set to its default value. To empty the working set ofa process, set both the MINIMUM_SIZE and MAXIMUM_SIZEspecifications to 0. The MINIMUM_SIZE specification can not be specifiedwith the MINIMUM_CHANGE specification.

PROCESS_ID=pidSpecifies the process ID of the process to modify. You must have securityaccess to the process to change its working set. For example, the Tivoli ruleserver must be running from the system account to modify the working setof certain system processes.

SymbolsNone.


CLI exampleThe following example sets both the minimum and maximum working sets of thecurrent process to 0 to empty its working set:WORKING_SET MINIMUM_SIZE=0, MAXIMUM_SIZE=0, PROCESS_ID={PROCESS_ID}

The following example reduces the minimum working set of the current process by30%, and reduces the maximum working set of the current process by 50%:WORKING_SET MINIMUM_CHANGE=-30%, MAXIMUM_CHANGE=-50%, PROCESS_ID={PROCESS_ID}



WRITE

DescriptionWrites one or more variables to a file or to the Windows NT registry.

CLI syntaxWRITE [FILE=file_name], [COMPUTER=computer_name], [HIVE=hive_name][KEY=key_name], [VALUE_ENTRY=value_entry_name], VARIABLE=(variable[,...])

where:

COMPUTER=computer_nameSpecifies to execute the operation on another computer.

FILE=file_nameSpecifies the file which to write the specified variable. If this option is notspecified, the default variable file is used. If there is no default variablefile, the action is not performed. The file is opened if necessary andremains open until closed with the CLOSE action or until there has beenno activity with the file for a period of more than twelve hours.

HIVE=hive_nameSpecifies the hive to access. If this the HIVE specification is present, itimplies that you are accessing the Windows NT registry rather than avariable file. If the HIVE specification is specified, the FILE specificationcannot be specified. One of the HKEY_LOCAL_MACHINE, HKEY_USERS,or HKEY_CLASSES_ROOT hives is accessed.

KEY=key_nameSpecifies the key to access for the Windows NT Registry only. If the HIVEspecification is specified, then this keyword is required.

VALUE_ENTRY=value_entry_nameSpecifies the value entry to write to for the Windows NT Registry only.The value entry can be of any data type except the REG_MULTI_SZ andREG_EXPAND_SZ data types. If the HIVE specification is specified, thiskeyword is required.

VARIABLE=(variable[,...])Specifies the list of variables which to write the file. The currentin-memory value of each specified variable is written out.

When writing a variable to a file, the context of the variable in the file isalways set to the current context of the executing rule. This behavior isindependent of how the variable might have been declared in the rule. Tocreate a variable in a file with a different context from that of the executingrule, use the CREATE action.

SymbolsSymbol substitution is supported in the COMPUTER, FILE, HIVE, KEY, andVALUE_ENTRY specifications.

CLI exampleThe following example writes out the value of the TOTAL_ERRORS variable forthe current context to the c:\TEMS\user\variables.dat file:WRITE FILE=c:\TEMS\user\variables.dat, -VARIABLE=TOTAL_ERRORS


In the following example, the ComputerName value entry in theSYSTEM\CurrentControlSet\Control\ActiveComputerName key on theHKEY_LOCAL_MACHINE hive is set to the value of the SYSTEM_NAMEspecification:WRITE HIVE=HKEY_LOCAL_MACHINE, -KEY=SYSTEM\CurrentControlSet\Control\ActiveComputerName\,-VALUE_ENTRY=ComputerName, -

VARIABLE=SYSTEM_NAME



ZERO

DescriptionSets the value of one or more variables to zero.

CLI syntaxZERO variable[,...]

where:

variable[,...]Specifies the variable whose value is set to zero.

The value of the variable that is stored in memory is set to zero or anempty string. Variables are not loaded from disk or written to disk.

If the variable does not currently exist in memory, it is created with a valueof zero.

SymbolsNone.

CLI exampleThe following example initializes the value of the COUNTER variable to zero:ZERO COUNTER



Glossary

Glossary

AAccount Information tab. Configures IBM TivoliManagement Solution for Exchange to use the accountspecified by the Domain and Account fields in theTivoli Configuration Manager. You must create thisaccount using the User Manager window in theAdministrative Tools (Common) menu and you mustcreate a password.

Asynchronous rules. An asynchronous rule is a rulethat is not executed until it is explicitly requested to befired by an external agent. The agent can be anotherrule that fires the asynchronous rule or a user that firesthe asynchronous rule from the Tivoli user interface.

Auto clean filter. Filter specification used toautomatically remove events from the local eventdatabase. The filter thread runs once a day at midnightto remove events from the local event database thatmatch the filter specification. The filter specificationnormally includes an event age filter so that events areremoved based on age.

Available. A domain or computer that exists but is notmanaged by the Tivoli Enterprise Manager isconsidered available.

BBrowsing. Dynamically consulting the network for alist of domains and computers in each domain. It canalso involve checking the state of IBM TivoliManagement Solution for Exchange on each computer.The length of time to browse depends on the size andspeed of the network and the number of computerswithin the network on which IBM Tivoli ManagementSolution for Exchange is installed.

Set the browsing level by clicking the Options menuitem from the View menu in the main window of theTivoli Enterprise Manager.

CClass. Identification generated by the IBM TivoliManagement Solution for Exchange rule. Make theClass an alphanumeric string that is no longer than 32characters.

Computer pop-up menu. The menu that is displayedwhen you position the pointer over a computer icon in

the network display pane of the main window of theTivoli Enterprise Manager and click the right mousebutton.

Configuration settings. Configuration Settings are allof the general, account, mail, rule, and collectionsettings used in the Tivoli Configuration Manager forIBM Tivoli Management Solution for Exchange.

Context statistic. Uniquely identifies the instance ofan enumerated statistic domain. For example, processID is the context statistic for the process statisticdomain because process ID is unique across allprocesses on your computer.

Control. An individual component of a window towhich the user can input data. Depending on thecontrol, input can be in the form of key presses ormouse clicks. An example of a control is a text box,which allows a user to type text. Another commoncontrol is an OK button, which the user can click withthe left mouse button.

Counter. A counter is a numeric value stored in theWindows NT® Performance Monitor. Counters can bemapped to Tivoli statistics, so that the value of thestatistic is equal to the value of the counter.

DDate format. Insert the date format for the TivoliConfiguration Manager by selecting United States orEuropean.

Debug mode. Debugging information is written to adaily log file in the IBM Tivoli Management Solutionfor Exchange \logs directory. The file is namedEvent_server_yyyy_mm_dd.LOG, where yyyy is the year,mm is the month and, dd is the day. The levels ofdebugging range from 0 (no debugging) to 4 (fulldebugging). Level 1 is the normal level for debugging.Debugging levels are synonymous with logging levels.

Default data source. The default data source specifiesthe ODBC data source name to use in the Execute SQLaction when a data source name is not specified in theTivoli Rule Designer. The default data source must be asystem data source name.

Default variable file. The default variable file is thefile that is used in actions that read and write variablesto files when a file name is not specified in the TivoliRule Designer. It is also the file that is read to get avariable’s value when the variable is referenced but hasnot been explicitly read or defined.

319

Development View. One of two views or modes ofoperation provided by Tivoli Enterprise Manager.Development View is used to construct and modifyTivoli rule processes. Development View provides aview of all existing rule processes, right down to therule level on the left side of the main window. Theright side of the main window displays rules writtenwith the Tivoli Rule Designer. These rules are stored insource rule directories and are available for deploymentin Tivoli rule processes. In Development View, Tivolirule processes can be created, modified, or augmentedby dragging and dropping source rules on the rightside onto rules, processes, computers, domains, or theenterprise on the left side of the main window. Theactive view can be switched by selecting the desiredview from the View pull-down menu.

Disabling a rule. Disabling a rule means that the ruleis not allowed to execute. When the schedule of adisabled rule indicates that it is time to run, the TivoliRule Engine skips the execution of the rule if it isdisabled.

Disabling a rule affects only the rule while in thecurrently running rule process. If the process is stoppedand restarted for any reason, disabled rules areenabled. Additionally, if a process with disabled rules iscopied to another computer and started, all disabledrules are enabled in the process on the other computer.

Domain. On Windows NT® based computers, adomain represents an enterprise of computers thatshare common account administration and security. Anindividual computer is a member of a domain. IBMTivoli Management Solution for Exchange also usesVirtual Domains. A virtual domain is a named group ofcomputers that has no relationship to real Windows NTdomains. Virtual domains exist to provide for a moreflexible way of grouping computers. For example, avirtual domain could be named Exchange and thecomputers added to the Exchange domain could be thecomputers in the network that are Exchange severs.The computers could be in different Windows NTdomains. Within the Tivoli Event ConfigurationManager, virtual domains have the same status asphysical domains. The Tivoli Event ConfigurationManager can manage domains that are completelyphysical, completely virtual, or a combination of both.Additionally, a computer can be a member of morethan one domain.

Domain pop-up menu. The menu that is displayedwhen you position the pointer over a domain icon inthe network display pane of the main window of theTivoli Enterprise Manager and click the right mousebutton.

Drop-down list. Drop-down list refers to the menuitems that are displayed as a single line with a downarrow to the right. Clicking on the down arrow resultsin all of the possible choices being listed. To change thechoice, click the item on the list that you want. When

the item is selected, the list disappears and the newchoice is displayed on the single line.

Within the Tivoli Enterprise Manager, drop-down listsare typically used for domain, computer, directory, orprocess selection.

EEmail delivery timeout. Email delivery timeout is thenumber of seconds it takes for an email, sent by IBMTivoli Management Solution for Exchange, to return adelivery receipt. Rules can be written, using domainMSExchangeEmail, to send an email to a specifiedaddress and perform an action if a delivery receipt isnot returned in the amount of time specified by theEmail delivery timeout.

Enabling a rule. The rule is allowed to executeaccording to its defined schedule. This is the normalstate for a rule.

Enterprise. An Enterprise is a named cluster ofdomains and computers that has no relationship to realWindows NT® domains.

Entity. Entity refers to a component of your computerfor which there can be many occurrences. Examples ofentities are disks, processes, services, databases,enterprises, domains, and computers..

EntityContext. Identification generated by the IBMTivoli Management Solution for Exchange rule.

Enumerated. Having an array of values, each onecorresponding to an instance of a statistic domain. Forexample, a process statistic or variable is enumeratedbecause it has a value for each process on thecomputer.

EventSubType. The EventSubType filter furthernarrows the EventType filter.

EventType. A filter used only for Problem or Messageevents.

Expression. An expression is a mathematical formulamade up of values, functions, operators, andparentheses. Operators can be arithmetic (such as + and-), logical (such as OR and NOT), and relational (suchas < or =).

FFiring a rule. Executing the code of the ruleimmediately. Rules consist of conditions that arechecked and actions that are potentially taken. Onlyrules with asynchronous schedules can be fired.

Frame. A rectangular section of a window thatcontains a label in the upper left corner and one ormore controls that are logically related to the label.


HHandle. Specifies the name associated with a problemto identify the problem. If the handle name is notspecified, a default is formed by the rule engine. Thedefault handle name is the rule name, followed by thecontext, followed by the creation date and time of theevent.

IInbox timer. The amount of time that the Event Serverwaits, in seconds, before polling the Inbox for newevents.

Instance. An instance is one occurrence in anenumerated statistic domain. For example, the processexecuting the Tivoli Event Monitor is an instance in theprocess statistic domain.

Interval. The interval of a rule is the period of timefrom the previous execution, or initialization, of a ruleto the current execution of the rule. The value of astatistic is based either on the activity during theinterval or a status or level at the end of the interval.

LLeft and right mouse buttons. The properterminology for the mouse buttons is primary andsecondary. The default mouse button configurationassigns the left mouse button as the primary mousebutton and the right mouse button as the secondary.Because of this setup, the common terminology is leftand right mouse button rather than primary andsecondary mouse button.

If the mouse button configuration is changed using theControl Panel, such that the left mouse button is thesecondary and the right mouse button is the primary,then references to the left mouse button are reallyreferences to the right mouse button.

Log file age. Number of days to retain Event Serverdaily log files.

MMail Information tab. Defines how IBM TivoliManagement Solution for Exchange sends mail with theMAIL action. This tab is located in the Tivoli EventConfiguration Manager.

Main window. The main window is the window thatthe Tivoli Enterprise Manager displays when firstinvoked. In Management View, the main windowshows the network display on the left and the contentsof the selected item in the network display on the right.

The network display shows the domains, computers,and processes that are managed by the TivoliEnterprise Manager.

In the Development View, the source rule display is onthe right. The network display shows the domains,computers, processes, and rules that are managed bythe Tivoli Enterprise Manager. The source rule displayshows the rules that are available for constructingTivoli processes from the specified computer anddirectory.

Managed. If the Tivoli Enterprise Manager displays adomain or computer in its network display pane, thedomain or computer is considered to be managed bythe Tivoli Enterprise Manager.

If a domain is managed, it means that some or all ofthe individual computers in the domain can bemanaged. Managing a computer means the TivoliEnterprise Manager is capable of creating, controlling,modifying, and deleting Tivoli processes on thatcomputer.

Management View. One of two views or modes ofoperation provided by Tivoli Enterprise Manager. Thedefault view is the Management View. ManagementView uses the Explorer paradigm with containers inthe left pane (the enterprise, domains, computers, andprocesses) and the contents of the containers in theright pane. The Management View is used to controlIBM Tivoli Management Solution for Exchangethroughout the network. The active view can beswitched by selecting the desired view from the Viewpull down menu.

Maximum hops. Maximum number of times an eventcan be forwarded from computer to computer before itis discarded.

Maximum items. Limits the number of entities that asingle IBM Tivoli Management Solution for Exchangerule collects. You must set this number large enough tohandle the largest collection of your rules. If thisnumber is not large enough, IBM Tivoli ManagementSolution for Exchange can be prevented fromdiagnosing potential problems. IBM Tivoli ManagementSolution for Exchange allocates memory for everyentity collected, so the greater this number, the greaterthe potential memory usage.

NNetwork display. The network display is the windowdisplay pane on the left side of the main TivoliEnterprise Manager display. The label above thenetwork display reads Managed Network View. Thenetwork display contains a tree-like presentation of theenterprise, along with the domains, computers, andprocesses that are managed by the Tivoli EnterpriseManager. The network display displays the rules withina process when in the Development View.

Glossary 321

Network Display pop-up menu. The menu that isdisplayed when you position the pointer over whitespace in the network display pane in the main windowof the Tivoli Enterprise Manager and click the rightmouse button.

OObject. An object refers to the enterprise, domain,category, computer, process, setting, display, status bar,tool bar, process rule, or source rule.

Outbox timer. The amount of time the Event Serverwaits, in seconds, before retrying the sending ofundeliverable remote events.

PPerformance data retention age. Filter specificationused to automatically remove performance data fromthe Performance database. The filter thread runs once aday at midnight to remove events from thePerformance database that match the filter specification.

Performance routing timer. The amount of time theEvent Server waits, in seconds, before retrying thesending of remote performance data.

Performance rules. The Performance rules are a groupof rules that are part of both IBM Tivoli ManagementSolution for Exchange and Tivoli Management Solutionfor SQL. These rules archive performance data atregular intervals to a database, and must be running tocreate that data necessary for reporting and graphing.

Pop-up menu. The menu that is displayed when youposition the pointer over an icon or over white space inthe network display pane or source rule pane and clickthe right mouse button.

Predefined symbol. A predefined symbol is one of agroup of symbols whose value is always known by theexecuting rule. Examples of predefined symbols are thedate and time strings and the computer name.

Predefined variable. A predefined variable is one of agroup of variables that contains information maintainedby the executing rule. Examples of predefined symbolsare the status of the last action executed and thenumber of times the rule detected a problem.

Process pop-up menu. The menu that is displayedwhen you position the pointer over a process icon inthe network display pane of the main window of theTivoli Enterprise Manager and click the right mousebutton.

Pull-down menu. Pull-down menu refers to the menunames listed horizontally in the Tivoli EnterpriseManager main window, just under the window titlebar. This list of names is commonly referred to as the

menu bar. When the primary mouse button is clickedon one of these items, a secondary list of menu items isdisplayed for subsequent selection. The pull-downmenu names in the Tivoli Enterprise Manager mainwindow include the following:

v File

v Edit

v View

v Manage

v Help

RRule. A Tivoli rule is a named entity that is used tomonitor a specific situation and if appropriate, takecorrective action or perform external notification. ATivoli rule consists of four major components:

v The schedule that defines when the rule executes.

v The selections that define which entities the ruleexamines.

v The condition for which to search.

v The action to take if the condition is found to be trueor false.

Within each component there is considerable powerand flexibility that can be explored by running theTivoli Rule Designer.

Rule code. Rule code consists of the actual statementsthat are executed by the Tivoli Rule Engine. The rulecode is in ASCII. Rule code defines the rule name aswell as the schedule, selection, condition, and actionthat define the mission of the rule. Rule code can bewritten directly by users. It is also written by the TivoliRule Designer in response to choices that are made tothe Rule Designer’s graphical user interface.

Rule Information tab. Automatically starts rules forthe Tivoli Event Configuration Manager. Check the boxof an item when you want its rules to begin monitoringyour computer. This must be done each time that yourestart your computer.

Rule name. The name of the IBM Tivoli ManagementSolution for Exchange rule that captures an event.

Rule pop-up menu. The menu that is displayed whenyou position the pointer over a rule icon within aprocess in the network display pane of the mainwindow of the Tivoli Enterprise Manager and click theright mouse button.

Rule process. A rule process is a set of Tivoli rulesthat is executed by the Tivoli Rule Engine. Each ruleperforms a specific monitoring task. The Tivoli RuleEngine runs as a background process on a WindowsNT computer.


SScalar. Having a single value. A scalar statistic orvariable has only one value.

Solution. A solution is a pre-built rule processdesigned to monitor a specific application. IBM TivoliManagement Solution for Exchange provides manysolutions as part of a standard IBM Tivoli ManagementSolution for Exchange installation. Examples aresolutions for Exchange and SQL Server. The Tivolisolutions architecture is easily extensible. For example,you can create your own solutions to monitor criticalin-house applications.

Solutions differ from ordinary rule processes in thattheir behavior can be easily tailored while the solutionis running. For example, one of the things the solutionfor NT server monitors is available disk space. You cancontrol the alert threshold for the depletion of availablespace by modifying a parameter in the graphicalinterface.

IBM Tivoli Management Solution for Exchangeprovides many solutions. It is unlikely you will use allof them. Consequently you might want to reduce theset of solutions that are visible to the Tivoli EnterpriseManager for actual management. This is done by aprocess known as removing solutions. Solutions thatare removed are not deleted. They can easily be addedback for management at any time. The process ofadding and removing solutions is also known asmanaging the visibility of solutions to the TivoliEnterprise Manager.

Source. The process from which an event is captured.

Source rule. A source rule is a rule that is written bythe Tivoli Rule Designer and is available for inclusionwhen constructing Tivoli processes using the TivoliEnterprise Manager.

A rule is used to monitor specific situations and ifappropriate, take corrective actions or perform externalnotification.

Source rule computer. The name of the computer thatis currently providing Tivoli source rules to the TivoliEnterprise Manager. This computer is listed in thecontrol above the source rule display in the mainwindow of the Tivoli Enterprise Manager. The formatof the text in the control is\\domain\computer\directory.

Source rule directory. The name of the directory onthe source rule computer that is currently providingTivoli source rules to the Tivoli Enterprise Manager.Different directories can provide different types ofrules. For example, one directory can provide rules foran NT Server. Another might provide rules forExchange or for an SQL Server.

The set of directories that are available for source rulestorage on a given computer is the set of subdirectories

under the C:\Program Files\TEMS\Rules directory,assuming IBM Tivoli Management Solution forExchange is installed in the C:\Program Files\TEMSdefault directory.

This directory is listed in the control above the sourcerule display in the main window of the TivoliEnterprise Manager. The format of the text in thecontrol is \\domain\computer\directory.

Source rule display. The source rule display is thewindow display pane on the right side of the TivoliEnterprise Manager main window when you are inDevelopment View. The control above the source ruledisplay indicates the domain, computer, and directoryproviding the rules used in the display. This control canalso be used to change the computer and directoryproviding source rules.

The source rule display contains the actual rules, whichcan be presented in one of four different views: largeicon view, small icon view, list view, and detail view.

Source Rule Display pop-up menu. The menu that isdisplayed when you position the pointer over whitespace in the source rule display pane in the mainwindow of the Tivoli Enterprise Manager and click theright mouse button.

Source Rule pop-up menu. The menu that isdisplayed when you position the pointer over a sourcerule icon in the source rule display pane of the mainwindow of the Tivoli Enterprise Manager and click theright mouse button.

Splitter bar. The splitter bar is a graphical control thatis used to control the width of the network displayrelative to the right side of the display in the mainwindow in the Tivoli Enterprise Manager. The splitterbar manifests itself as a vertical line between thenetwork display on the left side and the right sidedisplay. The splitter bar can be dragged to change thewidth of the network relative to the right-side display.

Start up state. Determines whether a Tivoli process isautomatically started at system boot time. If thestart-up state box is checked, the process isautomatically started at system boot time. If the box isnot checked, you must manually start the Tivoli ruleprocess to execute it.

If the process is successfully started at system boot timeand is still running, the process icon is green in thenetwork display. If the process is not running for anyreason, the process icon is white.

Statistic. A Tivoli statistic is a value or a set of valuescollected from your computer. A value of a statisticremains unchanged during the execution of a rule.

Status bar. The status bar is on the bottom of themain window. The status bar describes the current stateof the drag and drop operation. The status bar alsocommunicates information on the operation in process

Glossary 323

when the operation can take a measurable amount oftime to complete. The right side of the status bardisplays the current system date and time.

The status bar can be made invisible by removing thecheck from the Status Bar menu option under the Viewmenu.

String. A string is a fundamental data type that holdscharacter information. A string variable can containapproximately 65,535 bytes (64KB), is eitherfixed-length or variable-length, and contains onecharacter for each byte. Fixed-length strings aredeclared to be a specific length. Variable-length stringscan be any length up to 64KB, less a small amount ofstorage overhead.

SubClass. An identification generated by the IBMTivoli Management Solution for Exchange rule. Analphanumeric string that is no longer than 32characters.

Symbol. A symbol is a Tivoli statistic, a user-definedstatistic, a variable, or one of a set of pre-defined Tivolisymbols or variables. Symbol substitution occurs whenIBM Tivoli Management Solution for Exchangeevaluates the value of a symbol or an expression madeup of symbols, constants, and arithmetic operators, andsubstitutes the symbol expression with the value. Thesymbol expression is enclosed in braces ({}).

TTime format. For the Tivoli Configuration Manager,insert the time format by selecting 12 Hour or 24 Hour.The 1:00:00 PM in the 12-hour time format correspondsto 13:00:00 in the 24-hour time format.

Tivoli Performance Database. The Tivoli PerformanceDatabase is the database that contains the performancedata used for reporting and graphing. This database ispopulated by the IBM Tivoli Management Solution forExchange performance rules.

Tivoli Rule Process. A Tivoli process is a backgroundprocess that runs on a Windows NT computer. Theprocess executes the Tivoli Rule Engine, which in turnexecutes a defined set of Tivoli rules. Each ruleperforms a specific monitoring task and can takeactions appropriate to the condition being monitored.

Tivoli Rule Engine. The Tivoli Rule Engine is aWindows NT® process that runs in the background. Itsmission is to execute a Tivoli rule file, which consists ofone or more Tivoli rules. Each Tivoli rule performs awell-defined monitoring function coupled with apowerful action capability.

Toolbar. The toolbar is a horizontal strip of icons thatis displayed under the menu names in the TivoliEnterprise Manager main display. Clicking the iconresults in the associated function being performed. If

you hold the pointer over an icon for a short period oftime, a toolbar tip is displayed, indicating the functionassociated with the icon. Toolbars are convenient foraccelerating frequently performed operations.

The toolbar can be made invisible by removing thecheck from the Toolbar menu option under the Viewmenu.

Types of schedules. A rule can have one of thefollowing schedule types:

Interval basedRuns at regular intervals (e.g. once per hour).

Time of day basedRuns at specific times of day.

One ShotRuns once when the Tivoli Process starts.

AsynchronousRuns only when explicitly requested by anexternal agent.

UUnits. Text that describes the units associated with thevalue. For example, megabytes or transactions persecond.

Universe string. Comma-separated lists used to selector exclude items.

User defined statistic. A user-defined statistic is astatistic defined by the user based on the value ofTivoli statistics, constants, and operators. The value of auser-defined statistic remains unchanged during theexecution of a rule.

User names. The account used to log into thenetwork.

VVariable. A variable is a placeholder for a value or aset of values that can be changed by the actions of arule.

Virtual domain. A virtual domain is a named groupof computers that has no relationship to real WindowsNT® domains. Virtual domains exist to provide for amore flexible way of grouping computers. For example,a virtual domain can be named Exchange and thecomputers added to the Exchange domain can be thecomputers in the network that are Exchange severs.These computers can be in different Windows NTdomains.

Within the Tivoli Enterprise Manager, virtual domainshave the same status as physical domains. In fact, theTivoli Enterprise Manager can manage domains thatare completely physical, completely virtual, or a


combination of both. Additionally, a computer can be amember of more than one domain.

Glossary 325

Index

Special Characters.BRG files for batch reports and graphs 191.GDF graph definition files 191.RDF report definition files 191.RPT file, for use by Crystal Reports 191.UDF user-defined files 191.View files 191$ACTION_RESULT

predefined rule syntax variable 247$ACTION_STATUS

predefined rule syntax variable 247$CLOSE_CONDITION_COUNT

predefined rule syntax variable 248$FALSE_CONDITION_COUNT

predefined rule syntax variable 248$NEW_CONDITION_COUNT

predefined rule syntax variable 248$PROBLEM_COUNT

predefined rule syntax variable 248$PROBLEM_STATE

predefined rule syntax variable 247$TRUE_CONDITION_COUNT

predefined rule syntax variable 248$UPDATE_CONDITION_COUNT

predefined rule syntax variable 248

Numerics2D Gallery tab, using to customize graphs in Tivoli Reporting

and Graphing 1873D Gallery tab, using to customize graphs in Tivoli Reporting

and Graphing 187

AAccess database 150Access database, Microsoft 130access violations, troubleshooting in Tivoli Statistics

Builder 222access, restricting for RoboMon_Emgr.exe, RoboMon_esrv.exe,

and RoboMon_rulsrv.exe files 224accessibility features

about ixaccount information configuration settings

changing in Tivoli Configuration Manager 52Acknowledge All option in Tivoli Event Monitor Monitor and

View menus 133action blocks, defined 236action categories, rule

defined 96ACTION statements

using ACTION types with 237using CLOSE_ACTION types with 237using EPILOGUE_ACTION types with 237using FALSE_ACTION types with 237using NEW_ACTION types with 237using PROLOGUE_ACTION types with 237using TRUE_ACTION types with 237using UPDATE_ACTION types with 237

ACTION statements, defined 237

action typesclose 98epilogue 98false 97new 97prologue 98true 97update 97

ACTION typesrequirements for 238requirements for creating 238using with rule ACTION statements 237using with rule CONDITION statements 228

action types ,ruleadding 99

action types, rulechanging 100defined 97inserting into an existing action list 99

actionsAPPEND 264as components of rules 81CALCULATE 265CHECK_BOUNDS 266CLOSE 267COPY 268CREATE 269DECREMENT 270DELETE 271DISABLE 272ENABLE 274EVENT TYPE=MESSAGE 276EVENT TYPE=PROBLEM 279EVENT TYPE=TEXT 283EVENT TYPE=WINDOWS 285EXECUTE 287EXECUTE_SQL 289EXIT 290EXPORT 291for rule action categories 97IF 294INCREMENT 296LOG 297MAIL 299MODIFY 301PRIORITY 303READ 304REMOVE 306SNMP_SET 307SNMP_TRAP 308TERMINATE 310using the COMPUTER option in 260WAIT 311WORKING_SET 313WRITE 315ZERO 317

actions and action types, about 236actions in rules syntax, EVENT 261actions, default IBM Tivoli Management Solution for

Exchange 263

327

actions, ruleactivating inactive 100changing computers in 102defining an expression for 102formatting symbolss across rules for 101inactivating 100modifying 100removing 100setting values across rules 101specifying 96

adapters, troubleshooting TCP/IP network 220Admin solutions, defined 73Advanced tab

in EventType/Class filterTivoli Event Configuration Manager 158

Advanced tab of Filter option in Tivoli Event Monitor Viewmenu 141

alert severitiessetting for events in Tivoli Event Monitor 146

alert severity icon 146alert severity icons for events, choosing 148alert severity sounds for events, choosing 147APPEND action 264Application Views icons

for configuring Tivoli Web Event Monitor 167architecture

about IBM Tivoli Management Solution for Exchange 1ASCII file statistic domains

about 118adding 119modifying 120removing 121

ASCII File tab, Tivoli Statistics Builderdefined 112

ASCII$(string) expression functions 230asynchronous rules

troubleshooting variable usage in 221AVG$(statistic) expression functions 230

Bbatch folders

for running reports and graphs 190batch folders, managing

in Tivoli Reporting and Graphing 191batch graphs

Admin rules for creating batch reports and graphs 190creating to run automatically 190

batch reporting and graphing, interactive 2batch reports

Admin rules for creating batch reports and graphs 190creating to run automatically 190

Batch, Manage option in Edit menuTivoli Reporting and Graphing 192

booksfeedback viiionline viiiordering viii

BPS Graphic control, Pinnacle 2braces

using for command line interface parameters 195brackets

using for command line interface parameters 195Browse, Cache, Confirmation, and Process Start options

in Tivoli Enterprise Manager 42Builder, Tivoli Statistics

about 3

CCache, Confirmation, , Browse, and Process Start options

in Tivoli Enterprise Manager 42CALCULATE action 265CALCULATE statements, using expressions in 229case-sensitivity in rule syntax 241central processing unit (CPU) usage statistics,

troubleshooting 223CHAR$(integer-value) expression functions 230CHECK_BOUNDS action 266CIO view, Tivoli Reporting and Graphing 174

reports and graphs in 174Class option


Class: option in EventType/Class tab of Filter option in TivoliEvent Monitor View menu 138

CLOSE action 267CLOSE_ACTION types

using with rule ACTION statements 237using with rule CONDITION statements 228

Closed problem View icon in Tivoli Event Monitor 131collection information configuration settings

changing in Tivoli Configuration Manager 53COM statistic domains

about 125adding 126modifying 127removing 127

COM tab, Tivoli Statistics Builderdefined 112

command failure, about 196command line interface

adding \bin to Windows NT® directory search path 195return values 195

command line interface executableRoboMon.exe file 195

command line interface parametersusing braces in 195using double quotes in 195

command line interface parameters and syntaxabout 195

command line interface syntaxusing pipes in 195

command line parametersusing brackets in 195

command line, IBM Tivoli Management Solution for Exchangeabout 3

commandsorganization of 196RoboMon /Ps 212RoboMon /Ra 197RoboMon /Rd 198RoboMon /Re 199RoboMon /Rk 200RoboMon /Rl 201RoboMon /Rp 202RoboMon /Rr 203RoboMon /Rs 204RoboMon /Rv 205RoboMon /Sk 206RoboMon /Sp 207RoboMon /Ss 208RoboMon /Vd 209RoboMon /Vp 210RoboMon /Vw 211


commands (continued)RoboMon_compact /P, using to run database compaction

program that converts and compacts performancedatabases 224

comments, rule file syntax for 240compactions, troubleshooting Jet event and performance

database 220components, IBM Tivoli Management Solution for

Exchange 2COMPUTER

predefined rule syntax symbol 246computer bar graphs 174COMPUTER option in rules syntax for actions 260computers

using Tivoli Enterprise Manager to manage 49CONDITION statements

syntax for 229using ACTION types with 228using CLOSE_ACTION types with 228using EPILOGUE_ACTION types with 228using FALSE_ACTION types with 228using NEW_ACTION types with 229using PROLOGUE_ACTION types with 229using TRUE_ACTION types with 229using UPDATE_ACTION types with 229using with rules 228

CONDITION statements, rule 227CONDITION statements, using expressions in 229conditions

as components of rules 81using statistics to test for rules 227

conditions, ruleexamples of 93managing 92using constants in 92using functions in 92using operators in 92using predefined variables in 92using statistics in 92using the Expression field to create 94using user-defined statistics in 92using variables in 92

Configuration Manager, Tivoliabout 3

Configuration Manager, Tivoli Eventabout 1, 2

configuration screenSQL Server DSN

for configuring Tivoli Web Event Monitor 166configuration settings

changing for collection information in Tivoli ConfigurationManager 53

changing in Tivoli Configuration Manager 52displaying in Tivoli Configuration Manager 52for Event Server in Tivoli Event Configuration Manager

Manage menu 152confirmation options

setting in Tivoli Solutions Manager 76Confirmation, Process Start, Browse, and Cache options

in Tivoli Enterprise Manager 42Connectivity database, Microsoft Jet Open DataBase

about 129constants

examples of 96using in rule conditions 92

CONTEXTpredefined rule syntax symbol 246

continuation charactersrule file syntax for 240

Control Panel menuusing to add databases in Tivoli Event Monitor 131

conventionscomputer naming 225defining community names and timeout values for DHCP

statistics 225typeface x

conversions, troubleshooting database 219, 220COPY action 268corrective actions

rule actions category defined 97CPU

See central processing unit 223CREATE action 269creating rule processes

in Tivoli Enterprise Manager 62Crystal Reports 2

reports, exporting to Crystal Report format in TivoliReporting and Graphing 183

Crystal Reports .RPT files 191CUM$(statistic) expression functions 230CUR_DATE$(component) expression functions 230Customer Support

contacting ixCVTFI$(number) expression functions 231CVTFS$(number) expression functions 231CVTIF$(number) expression functions 231CVTIS$ expression functions 231CVTSF$(string) expression functions 231CVTSI$(string) expression functions 231

Ddata store

about 1data types

floating point 229integer 229string 229using in expressions 229

data types for DHCPCommunity registry values 225data types for DHCPTimeout registry values 225DataBase Connectivity database, Microsoft Jet Open

about 129database, Access 130database, Microsoft Jet Open DataBase Connectivity

about 129database, ODBC-compliant

using with Tivoli Event Configuration Manager 1databases 130

about data stored in Event Database and in Tivoli EventMonitor 134

Access 150adding columns or tables to performance 224Jet

troubleshooting 216local inbox 150Microsoft Access 97

troubleshooting 216Microsoft Jet Open DataBase Connectivity (ODBC) 129modifying PerformanceEmpty.mdb file when adding

columns or tables to performance 224Open DataBase Connectivity event 150RoboMon Event 129, 213RoboMon Event Database 166

Index 329

databases (continued)SQL Server 129Tivoli performance 173troubleshooting converting IBM Tivoli Management

Solution for Exchange databases to SQL servers 219troubleshooting converting Jet to SQL Server 219using RoboMon_compact /P command to run database

compaction program that converts and compactsperformance 224

using the Control Panel menu to add databases in TivoliEvent Monitor 131

databases, large eventtroubleshooting 216

databases, Tivoli eventusing with Tivoli Event Monitor 130

databases, using RoboMon_compact.exe utility program totroubleshoot compacting Jet event and performance 220

DATE_STRpredefined rule syntax symbol 246

DATE$(number) expression functions 232Days/Time tab of Filter option in Tivoli Event Monitor View

menu 137debug levels for processes

setting in Tivoli Enterprise Manager 59DECREMENT action 270DELETE action 271deleting processes

in Tivoli Enterprise Manager 59Description tab


Description tab of Filter option in Tivoli Event Monitor Viewmenu 139

Designer, Tivoli Ruleabout 3

detail reportsin Tivoli Reporting and Graphing Sysadmin view 174

development view modeusing in Tivoli Enterprise Manager 41

DHCP statistics, defining community names and timeoutvalues 225

DHCPCommunity data types 225DHCPCommunity registry values 225DHCPTimeout data types 225DHCPTimeout registry values 225DISABLE action 272DISK_READ_PCT and DISK_WRITE_PCT statistic values,

troubleshooting 224DISK_WRITE_PCT and DISK_READ_PCT statistic values,

troubleshooting 224domains

using Tivoli Enterprise Manager to manage 47domains, statistic

about 112about ASCII file 118about COM 125about importing and exporting 115about ODBC Database 121about peformance monitor 117about SNMP 124adding ASCII file 119adding COM 126adding ODBC Database 121adding peformance monitor 117adding SNMP 124automatically fixing mismatches of 113copying 116

domains, statistic (continued)definition for 112description of 113importing and exporting 115managing peformance monitor 117mismatches defined 113modifying 113modifying ASCII file 120modifying COM 127modifying ODBC Database 123modifying peformance monitor 118modifying SNMP 125name for 112removing 113removing ASCII file 121removing COM 127removing ODBC Database 123removing peformance monitor 118removing SNMP 125restoring to original definition 113type of 113

domains, virtualdefined 47

DSN, Open menuin Tivoli Event Monitor 131

dynamic link library loading errors, troubleshooting 224

EEdit menu

in Tivoli Reporting and Graphing 190EDIT$(string, edit-options) expression functions 232ENABLE action 274enabling rules

about 68Enterprise Manager, Tivoli

about 1, 2Enterprise Service port numbers, using to troubleshoot

TCP/IP port numbers 221Enterprise Views icons

for configuring Tivoli Web Event Monitor 167entity bar graphs 174ENVIRONMENT$(name) expression functions 232EPILOGUE_ACTION types


error messagestroubleshooting remote installation 215

error trackingfor Tivoli Event Service 214

errors, troubleshooting Unknown MAPI 223EVENT action in rules syntax 261event alert severity icon 146event alert severity icons, choosing 148event alert severity sounds, choosing 147Event Configuration Manager, Tivoli

about 1, 2event correlations

using with rules 227Event Database

and Tivoli Event Monitor 134event databases, Tivoli

using with Tivoli Event Monitor 130event databases, using RoboMon_compact.exe utility program

to troubleshoot compacting Jet 220event filter, Windows NT

in Tivoli Event Configuration Manager 153


event filters, localusing in Tivoli Event Configuration Manager 155

event forwarding architecture, Event Serverabout 150

event forwarding in one-way trust relationships,troubleshooting 219

event forwarding, troubleshooting 218Event menu options in Tivoli Event Monitor

Update Progress 133Event Monitor View, Tivoli

icons 131Event Monitor, Tivoli

about 2Event Server

about 130controlling from the Tivoli Event Configuration

Manager 150using event forwarding architecture 150using Open DataBase Connectivity 150

Event Server configuration settingsin Tivoli Event Configuration Manager Manage menu 152

Event Server optionin Tivoli Event Configuration Manager Manage menu 152

Event Server, Tivoliconfiguration option

Tivoli Event Configuration Manager View menu 158Event Service, using to troubleshoot TCP/IP port

numbers 221EVENT TYPE=MESSAGE action 276EVENT TYPE=PROBLEM action 279EVENT TYPE=TEXT action 283EVENT TYPE=WINDOWS action 285Event_Server_1999_01_15.log file 214

using to troubleshoot Tivoli Event Service 217events

about 129about configuring settings and filters in the Tivoli Event

Configuration Manager 150about Event Database and Tivoli Event Monitor 134about filtering in Tivoli Event Monitor 134about managing 129about monitor and view filters in Tivoli Event

Monitor 134about unacknowledged 133sending and receiving between computers

in Tivoli Event Configuration Manager 159setting alert severities for in Tivoli Event Monitor 146troubleshooting management functions in Tivoli Event

Configuration Manager 218troubleshooting routing across the network 216updating as complete fix 133using the Application Views icon to configure Tivoli Web

Event Monitor 167using the Enterprise Views icon to configure Tivoli Web

Event Monitor 167using the Filtering icon to configure Tivoli Web Event

Monitor 168using the Security Settings icon to configure Tivoli Web

Event Monitor 169using the Server Health icon to configure Tivoli Web Event

Monitor 167using Tivoli Web Event Monitor to manage events from a

browser 166using Tivoli Web Event Monitor to manage from an

Internet Explorer 4.0 Web browser 166events, troubleshooting forwarding between a workgroup and

a domain 219

events, troubleshooting forwarding in workgroups 219EventSubType: option


EventSubType: option in EventType/Class tab of Filter optionin Tivoli Event Monitor View menu 138

EventType: optionin EventType/Class filter

Tivoli Event Configuration Manager 156EventType: option in EventType/Class tab of Filter option in

Tivoli Event Monitor View menu 138EventType/Class filter

Advanced tabTivoli Event Configuration Manager 158

Class optionTivoli Event Configuration Manager 156

Description tabTivoli Event Configuration Manager 157

EventSubType: optionTivoli Event Configuration Manager 156

EventType: optionTivoli Event Configuration Manager 156

Severity tabTivoli Event Configuration Manager 157

SubClass optionTivoli Event Configuration Manager 156

EventType/Class Filter option in Tivoli Event ConfigurationManager 155

EventType/Class tab of Filter option in Tivoli Event MonitorView menu 138

EVT_DATE and EVT_TIME statistic values,troubleshooting 224

EVT_TIME and EVT_DATE statistic values,troubleshooting 224

exceptionsusing in rule selection types 90

Exchange 2000 solutions, defined 73Exchange command line, IBM Tivoli Management Solution for

about 3Exchange components, IBM Tivoli Management Solution

for 2Exchange mail actions, troubleshooting 223Exchange solutions, defined 73Exchange, Microsoft

troubleshooting setting up for mail actions 215Exchange, Version 5.5, Service Pack 1, troubleshooting mail

actions using Microsoft 223executables

RoboMon.exe 3EXECUTE action 287EXECUTE_SQL action 289EXISTS

predefined rule syntax symbol 246EXIT action 290expiration warning, show key

changing settings in Tivoli Configuration Manager 52EXPORT action 291Export Report icon 183exporting graphs

to HTML format for Web use in Tivoli Reporting andGraphing 188

exporting reportsin Tivoli Reporting and Graphing 183to HTML format for Web use in Tivoli Reporting and

Graphing 182exporting reports to rich text format

in Tivoli Reporting and Graphing 183

Index 331

exporting, graphsto JPEG format for Web use in Tivoli Reporting and

Graphing 189Expression field

using to define rule conditions 94expression functions

ASCII$(string) 230AVG$(statistic) 230CHAR$(integer-value) 230CUM$(statistic) 230CUR_DATE$(component) 230CVTFI$(number) 231CVTFS$(number) 231CVTIF$(number) 231CVTIS$ 231CVTSF$(string) 231CVTSI$(string) 231DATE$(number) 232EDIT$(string, edit-options) 232ENVIRONMENT$(name) 232FIELD_COUNT$(string, delimiter) 232FIELD_POSITION$(string, delimiter, number) 233FIELD$(string, delimiter, number) 232FIND$(string, substring) 233FINDB$(string, substring) 233FINDE$(string, substring) 233LENGTH$(string) 233MAX$(statistic [,context]) 233MIN$(statistic [,context]) 233PADL$(string, padchars, length) 234PADR$(string, padchars, length) 234REMOVE$(string, remove-string) 234REPLACE$(string, remove-string) 234ROUND$(number, precision) 234SEG$(string, start-position, length) 235SEG1$(string, position) 235SEGL$(string, length) 235SEGR$(string, start-position) 235STRING$(string, count) 235SUM$(statistic, context) 235TRUNC$(number, precision) 236

expression operators 236expressions, using in CONDITION, CALCULATE, IF, and

STATISTIC statements 229external definition files (.edf)

about 115

FFALSE_ACTION types


FIELD_COUNT$(string, delimiter) expression functions 232FIELD_POSITION$(string, delimiter, number) expression

functions 233FIELD$(string, delimiter, number) expression functions 232File menu in Tivoli Event Monitor 131files

.BRG for batch reports and graphs 191

.GDF graph definition files 191

.RDF report definition files 191

.RPT for use by Crystal Reports 191

.UDF user-defined files 191

.View, stored in product directory and user profile 191Event_Server_1999_01_15.log 214

using to troubleshoot Tivoli Event Service 217external definition (.edf) 115

files (continued)Msinfo32.exe 213MSJTER40.DLL, troubleshooting errors when loading 224PerformanceEmpty.mdb, modifying when adding columns

or tables to performance databases 224RoboMon_compact.exe 220RoboMon_Emgr.exe, restricting access to 224RoboMon_esrv.exe, restricting access to 224RoboMon_EventDatabase_CreateTables.SQL 219RoboMon_evtsrv_ErrorTracking.log 214

using to troubleshoot Tivoli Event Service 217RoboMon_PerformanceDatabase_CreateTables.SQL 220RoboMon_revtsrv_ErrorTracking.log

using to troubleshoot Tivoli Event Service 217RoboMon_rulsrv.exe, restricting access to 224RoboMon_SQL7_EventDB_CreateTables.SQL 220RoboMon.exe 195solution set driver 74solution.var 75SQLCTR60.DLL, using to troubleshoot Tivoli Statistics

Builder 222TivoliInstallLog.txt 213

Filter option in Tivoli Event Monitor Monitor menu 135Filter option in Tivoli Event Monitor View menu 135, 136filter, EventType/Class

Advanced tabTivoli Event Configuration Manager 158

Class optionTivoli Event Configuration Manager 156

Description tabTivoli Event Configuration Manager 157

EventSubType: optionTivoli Event Configuration Manager 156

EventType: optionTivoli Event Configuration Manager 156

Severity tabTivoli Event Configuration Manager 157

SubClass optionTivoli Event Configuration Manager 156

Filtering iconsfor configuring Tivoli Web Event Monitor 168

filters, eventabout monitor and view in Tivoli Event Monitor 134

filters, local eventusing in Tivoli Event Configuration Manager 155

filters, SNMP trapusing in Tivoli Event Configuration Manager 154

Find Tivoli in Networkcompared to Refresh Network View in Tivoli Enterprise

Manager 46, 47FIND$(string, substring) expression functions 233FINDB$(string, substring) expression functions 233FINDE$(string, substring) expression functions 233finding

IBM Tivoli Management Solution for Exchange computersin the network 46

firing rulesabout 67using Tivoli Rule Engine 67

Fix/Acknowledge tab of Filter option in Tivoli Event MonitorView menu 140

forwarding events between a workgroup and a domain,troubleshooting 219

forwarding events in a workgroup, troubleshooting 219functions

using in rule conditions 92using with rules 227


Ggraph definition files (.GDF) 191Graphic control, Pinnacle BPS 2graphing and reporting, about 173graphing, interactive batch reporting and 2Graphing, Tivoli Reporting and 2

about 2graphs

about 173creatingto run automatically in batch 190customizing views of 193source of input data 173using batch folders for running automatically 190

graphs and reportsin Tivoli Reporting and Graphing CIO, Management, and

Sysadmin views 174graphs and reports in Sysadmin view

Tivoli Reporting and Graphing views 174graphs and reports, creating

in Tivoli Reporting and Graphing 179graphs, batch

Admin rules for creating batch reports and graphs 190graphs, computer bar 174graphs, creating 183graphs, customizing

in Tivoli Reporting and Graphing 186using 2D Gallery tab in Tivoli Reporting and

Graphing 187using 3D Gallery tab in Tivoli Reporting and

Graphing 187graphs, entity bar 174graphs, exporting

to HTML format for Web use in Tivoli Reporting andGraphing 188

to JPEG format for Web use in Tivoli Reporting andGraphing 189

graphs, hourly summary bar 174graphs, summary pie 174graphs, timeline

in Tivoli Reporting and Graphing Sysadmin view 174

HHKEY_LOCAL_MACHINE\SOFTWARE\TEMS registry

key 213HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Config

registry key 221, 225HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Config

registry keys, using to troubleshoot Exchange mailactions 223

HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Debugregistry editor

using to troubleshoot Tivoli Remote Event Service 216,217

HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Debugregistry key 214

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer\Performance registry key, using totroubleshoot Tivoli Statistics Builder 222

HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_esrvregistry key 213

HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_evtsrvregistry key 213

HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_licsrvregistry key 213

HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_Ruleregistry key 213

HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_Tcpregistry key 213

HKEY_PERFORMANCE_DATA registry key, using totroubleshoot Tivoli Statistics Builder 222

host names, troubleshooting TCP/IP 220hourly summary bar graphs 174Hourly_Reports Admin rule

for creating batch reports and graphs 190HTML format

exporting graphs for Web use in Tivoli Reporting andGraphing 189

exporting reports for Web use in Tivoli Reporting andGraphing 182

IIBM Tivoli Management Solution for Exchange

finding computers, rules, and processes in the network 46IBM Tivoli Management Solution for Exchange command line

about 3IBM Tivoli Management Solution for Exchange components 2IBM Tivoli Management Solution for Exchange product

architecture 1IBM Tivoli Management Solution for Exchange, product

overview 1icons

Application Viewsfor configuring Tivoli Web Event Monitor 167

choosing event alert severity 148Enterprise Views

for configuring Tivoli Web Event Monitor 167event alert severity 146Export Report 183Filtering

for configuring Tivoli Web Event Monitor 168Run Tivoli Reporting and Graphing 179

in Tivoli Reporting and Graphing 183Security Settings

for configuring Tivoli Web Event Monitor 169Server Health

for configuring Tivoli Web Event Monitor 167Tivoli Event Configuration Manager 151, 159Tivoli Event Monitor View 131using large icon view for source rule display in Tivoli

Enterprise Manager main window 225IF action 294IF statements, using expressions in 229INCLUDE statements

in rule file syntax 242INCREMENT action 296installation errors

troubleshooting 213using registry keys to troubleshoot 213

installations, remotetroubleshooting error messages during 215

installing to computers in a workgroup, troubleshooting 219instrumentation

for Tivoli Event Service 214Intelligent Solution Sets (ISS)

defined 1interactive batch reporting and graphing 2Internet Explorer 4.0 Web browser

using to manage events in Tivoli Web Event Monitor 166Internet Information Server, troubleshooting in Tivoli Statistics

Builder 223

Index 333

intervalscheduling option 84

IP addresses, using for computer names 225IP_REACHABLE statistic, defining timeout values for 225IPTimeToReach registry value 225

JJet database

troubleshooting 216Jet database, using

RoboMon_EventDatabase_CreateTables.SQL script totroubleshoot converting to SQL Server 6.5 219

Jet database, usingRoboMon_SQL7_EventDB_CreateTables.SQL script totroubleshoot converting to SQL Server 7.0 220

Jet databases, troubleshooting converting to SQL Server 219Jet event and performance databases, using

RoboMon_compact.exe utility program to troubleshootcompacting 220

Jet Open DataBase Connectivity database, Microsoftabout 129

JPEG formatexporting graphs for Web use in Tivoli Reporting and

Graphing 189

Kkey expiration warning, show

changing settings in Tivoli Configuration Manager 52

LLENGTH$(string) expression functions 233literal characters

rule file syntax for 240local event filter

in Tivoli Event Configuration Manager 155local inbox database in the Event Server 150LOG action 297

MMACRO statements

in rule file syntax 242MAIL action 299mail actions

troubleshooting setting up in Microsoft Exchange 215MAIL actions

using to specify Microsoft profile names in TivoliConfiguration Manager 51

mail actions, troubleshooting Microsoft Exchange 223mail information configuration settings

changing in Tivoli Configuration Manager 52mailboxes, Tivoli

creating in Tivoli Configuration Manager 51Manage Batch option in Edit menu

Tivoli Reporting and Graphing 192Manage menu in Tivoli Event Configuration Manager 151Manage menu option in Tivoli Event Configuration Manager

Event Server 152Maximum hops: Event Server configuration setting 152

Managed Network viewusing to change solutions 75

Managed Network Viewusing to manage computers in Tivoli Enterprise

Manager 49Management Solution for Exchange command line, IBM Tivoli

about 3Management Solution for Exchange components, IBM

Tivoli 2management view mode

using in Tivoli Enterprise Manager 41Management view, Tivoli Reporting and Graphing 174

reports and graphs in 174Manager, Tivoli Configuration

about 3Manager, Tivoli Enterprise

about 1, 2Manager, Tivoli Event Configuration

about 1, 2Manager, Tivoli Solutions

about 2managing computers

using Managed Network View in Tivoli EnterpriseManager 49

managing domainsusing Tivoli Enterprise Manager 47

managing processesabout 55

managing rulesabout 65

manualsfeedback viiionline viiiordering viii

Mark All As Read option in Tivoli Event Monitor Monitor andView menus 133

Mark All As Read option in Tivoli Event Monitor ViewMenu 132

Mark All As Unread option in Tivoli Event Monitor Viewmenu 132

MAX$(statistic [,context]) expression functions 233menus

Control Panel for adding databases in Tivoli EventMonitor 131

Edit in Tivoli Reporting and Graphing 190, 192File in Tivoli Event Monitor 131Manage in Tivoli Event Configuration Manager 151Monitor for viewing monitors in Tivoli Event Monitor 131Open DSN in Tivoli Event Monitor 131Run in Tivoli Event Monitor 130Send/Receive

in Tivoli Event Configuration Manager Managemenu 160

Severity tab View filter options in Tivoli EventMonitor 139

Tivoli Event Configuration Manager Manage 152Tivoli Event Configuration Manager Manage menu 159Tivoli Event Monitor Advanced tab View filter

options 141Tivoli Event Monitor Description tab View filter

options 139Tivoli Event Monitor Event 133Tivoli Event Monitor EventType/Class tab View filter

optionsClass: 138EventSubType: 138EventType: 138SubClass: 138


menus (continued)Tivoli Event Monitor Fix/Acknowledge tab View filter

options 140Tivoli Event Monitor Monitor 133, 134, 135Tivoli Event Monitor View 132, 133, 135, 136Tivoli Event Monitor View filter options

Days/Time tab 137EventType/Class tab 138

View for viewing events in Tivoli Event Monitor 131MESSAGE, type of EVENT action in rules syntax 261Microsoft Access 130Microsoft Access 97 database

troubleshooting 216Microsoft Access database

using with the Event Server 130Microsoft Exchange

troubleshooting setting up for mail actions 215Microsoft Exchange mail actions, troubleshooting 223Microsoft Exchange, Version 5.5, Service Pack 1,

troubleshooting mail actions using 223Microsoft Internet Information Server, troubleshooting in

Tivoli Statistics Builder 223Microsoft Internet Information Services server

domain name system (DNS) 166Microsoft Jet Open DataBase Connectivity database

about 129Microsoft profile names

specifying in Tivoli Configuration Manager MAILactions 51

Microsoft RegQueryValueEx function, using to troubleshootTivoli Statistics Builder 222

Microsoft SQL Server DSN Configuration screenfor configuring Tivoli Web Event Monitor 166

MIN$(statistic [,context]) expression functions 233MODIFY action 301Monitor menu for viewing monitors in Tivoli Event

Monitor 131Monitor menu options in Tivoli Event Monitor

Acknowledge All 133Filter 135Mark All As Read 133Open 134

Monitor, Tivoli Eventabout 2

Monthly_Reports Admin rulefor creating batch reports and graphs 190

moving processesin Tivoli Enterprise Manager 59

Msinfo32.exe fileusing to troubleshoot 213

MSJTER40.DLL file, troubleshooting errors when loading 224

Nnetwork services, troubleshooting TCP/IP 220Network view, Managed

using to change solutions 75Network View, Managed

using to manage computers in Tivoli EnterpriseManager 49

New Rule Wizardusing to create new rules 82

NEW_ACTION typesusing with rule ACTION statements 237using with rule CONDITION statements 229

Nightly_Reports Admin rulefor creating batch reports and graphs 190

notification actionsrule actions category defined 96

Oobject definitions in rules syntax

RULE 257SCHEDULE 251SELECT 255SET 248TEXT_BLOCK 251VARIABLE 249

ODBCSee Open Database Connectivity 214

ODBC Data Sources on Windows 2000 Control PanelSystem DSN tab

configuring Tivoli Web Event Monitor 166ODBC Data Sources on Windows NT Control Panel

System DSN tabconfiguring Tivoli Web Event Monitor 166

ODBC Database statistic domainsabout 121adding 121modifying 123removing 123

ODBC Database tab, Tivoli Statistics Builderdefined 112

ODBC-compliant databaseusing with Tivoli Event Configuration Manager 1

ODBC, using RoboMon_EventDatabase_CreateTables.SQLscript to troubleshoot converting Jet to SQL Server 6.5database 219

ODBC, usingRoboMon_PerformanceDatabase_CreateTables.SQL script totroubleshoot converting performance database to SQL Server7.0 220

ODBC, using RoboMon_SQL7_EventDB_CreateTables.SQLscript to troubleshoot converting Jet to SQL Server 7.0database 220

ODBC. See Microsoft Jet Open DataBase Connectivity 129one-shot rules

troubleshooting execution of multiple 221one-way trust relationships, troubleshooting 218one-way trust relationships, troubleshooting event and

performance data forwarding in 219one-way trust relationships, troubleshooting management

functions in 218online publications

viewing viiiOPCOM security messages View icon in Tivoli Event

Monitor 132OPCOM system messages View icon in Tivoli Event

Monitor 132Open DataBase Connectivity

using with the Event Server 150Open Database Connectivity (ODBC) 213

troubleshooting 214Open Database Connectivity (ODBC), as source of data source

names (DSN) for Tivoli Performance Database 173Open DataBase Connectivity database, Microsoft Jet

about 129Open DataBase Connectivity event database 150Open DSN menu

in Tivoli Event Monitor 131Open option in Tivoli Event Monitor Monitor menu 134Open problems View icon in Tivoli Event Monitor 131

Index 335

operatorsusing with rules 227

operators, expression 236options

Class in EventType/Class filterTivoli Event Configuration Manager 156

Event Server in Tivoli Event Configuration ManagerManage menu 152

EventSubType: in EventType/Class filterTivoli Event Configuration Manager 156

EventType: in EventType/Class filterTivoli Event Configuration Manager 156

Manage Batch in Edit menu, Tivoli Reporting andGraphing 192

SubClass in EventType/Class filterTivoli Event Configuration Manager 156

Tivoli Event Server configurationTivoli Event Configuration Manager View menu 158

ordering publications viiiOther SNMP traps View icon in Tivoli Event Monitor 132

PPADL$(string, padchars, length) expression functions 234PADR$(string, padchars, length) expression functions 234parameters

using braces in command line interface 195using brackets in the command line interface 195using double quotes in command line interface 195using in the command line interface 195

performance datacreating graphs for viewing 183

performance data between a workgroup and a domain,troubleshooting forwarding 219

performance data forwarding in one-way trust relationships,troubleshooting 219

performance data forwarding, troubleshooting 218performance data in workgroups, troubleshooting

forwarding 219performance database, Tivoli

as source of data for graphics and reports 173performance database, using

RoboMon_PerformanceDatabase_CreateTables.SQL script totroubleshoot converting to SQL Server 7.0 220

performance databases, adding columns or tables to 224performance databases, using RoboMon_compact.exe utility

program to troubleshoot compacting Jet 220performance monitor statistic domains

about 117adding 117managing 117modifying 118removing 118

Performance Monitor tab, Tivoli Statistics Builderdefined 112

performance rulesas source of data for reports and graphs 173

PerformanceEmpty.mdb file, modifying when adding columnsor tables to performance databases 224

PIDpredefined rule syntax symbol 246

Pinnacle BPS Graphic control 2pipes

using in command line interface syntax 195port numbers, troubleshooting TCP/IP 221PRIORITY action 303PROBLEM, type of EVENT action in rules syntax 261

process schedulesviewing in Tivoli Enterprise Manager 57

Process Start, Browse, Cache, and Confirmation optionsin Tivoli Enterprise Manager 42

process statusviewing in Tivoli Enterprise Manager 57

processesabout managing in Tivoli Enterprise Manager 55changing startup state for in Tivoli Enterprise Manager 59copying in Tivoli Enterprise Manager 58creating rule in Tivoli Enterprise Manager 62defining rules for 70deleting in Tivoli Enterprise Manager 59moving in Tivoli Enterprise Manager 59performing operations on in Tivoli Enterprise Manager 58renaming in Tivoli Enterprise Manager 59setting debug levels for in Tivoli Enterprise Manager 59starting and stopping in Tivoli Enterprise Manager 58using Tivoli Enterprise Manager to refresh network view

of 46profile names, Microsoft

specifying in Tivoli Configuration Manager MAILactions 51

PROLOGUE_ACTION typesusing with rule ACTION statements 237using with rule CONDITION statements 229

publicationsfeedback viiionline viiiordering viii, ixproviding comments on ixrelated viiiviewing online viii

Qquotation characters

rule file syntax for 240, 241quotes, double

using in command line interface syntax 195

Rrate statistics exceeding 100%, troubleshooting 223reachable statistics 225READ action 304Refresh Network View

compared to Find Tivoli in Network in Tivoli EnterpriseManager 46, 47

Refresh_solution _Variables rule 75refreshing the network view

in Tivoli Enterprise Manager 46registry editor

HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Debug 216,217

registry entriesROBOMON_DATE_FORMAT 246ROBOMON_DIGIT_SEPARATOR 245ROBOMON_RADIX_POINT 245ROBOMON_TIME_FORMAT 246

registry keysHKEY_LOCAL_MACHINE\SOFTWARE\TEMS 213HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Config 221,

225HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Config,

using to troubleshoot Exchange mail actions 223


registry keys (continued)HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Debug 214HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet

\Services\MSSQLServer\Performance, using totroubleshoot Tivoli Statistics Builder 222

HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_esrv 213

HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_evtsrv 213

HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_licsrv 213

HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_Rule 213

HKEY_LOCAL_MACHINE\SYSTEM\Services\RoboMon_Tcp 213

HKEY_PERFORMANCE_DATA, using to troubleshootTivoli Statistics Builder 222

RoboMon_evtsrv 214using to troubleshoot Tivoli Event Service 217

RoboMon_revtsrvusing to troubleshoot Tivoli Event Service 217

using to troubleshoot installation errors 213registry values

DHCPCommunity 225DHCPTimeout 225IPTimeToReach 225

registry values, TcpIpForRpcusing to troubleshoot forcing remote procedure call

connections to use TCP/IP 221RegQueryValueEx function, using to troubleshoot Tivoli

Statistics Builder 222remote computers in a workgroup, troubleshooting managing

of 219Remote Event Service and the Rule Service, using to

troubleshoot TCP/IP port numbers 221remote installation error messages

troubleshooting 215remote procedure call (RPC)

defined 130remote procedure call connections, troubleshooting forcing to

use TCP/IP 221REMOVE action 306REMOVE$(string, remove-string) expression functions 234renaming processes

in Tivoli Enterprise Manager 59REPLACE$(string, remove-string) expression functions 234report definition files (.RDF) 191reporting and graphing, about 173reporting and graphing, interactive batch 2Reporting and Graphing, Tivoli 2

about 2reports

about 173creating to run automatically in batch 190customizing views of 193source of input data 173using batch folders for running automatically 190

reports and graphsin Tivoli Reporting and Graphing CIO, Management, and

Sysadmin views 174reports and graphs in Sysadmin view

Tivoli Reporting and Graphing views 174reports and graphs, creating

in Tivoli Reporting and Graphing 179reports, batch

Admin rules for creating batch reports and graphs 190Reports, Crystal 2

reports, detailin Tivoli Reporting and Graphing Sysadmin view 174

reports, exportingin Tivoli Reporting and Graphing 183to HTML format for Web use in Tivoli Reporting and

Graphing 182reports, exporting to rich text format

in Tivoli Reporting and Graphing 183reports, summary 174return values

in the command line interface 195RoboMon /Ps command 212RoboMon /Ra command 197RoboMon /Rd command 198RoboMon /Re command 199RoboMon /Rk command 200RoboMon /Rl command 201RoboMon /Rp command 202RoboMon /Rr command 203RoboMon /Rs command 204RoboMon /Rv command 205RoboMon /Sk command 206RoboMon /Sp command 207RoboMon /Ss command 208RoboMon /Vd command 209RoboMon /Vp command 210RoboMon /Vw command 211RoboMon Event database 129RoboMon Event Database 166, 213RoboMon Event Database option

in System Data Sources listfor configuring Tivoli Web Event Monitor 166

RoboMon Performance ReportingSee Tivoli Performance Database 173

RoboMon_compact /P command, modifying when addingcolumns or tables to performance databases 224

RoboMon_compact.exe utility program, using to troubleshootcompacting Jet event and performance databases 220

ROBOMON_DATE_FORMAT registry entry 246ROBOMON_DIGIT_SEPARATOR registry entry 245RoboMon_Emgr.exe file, restricting access to 224RoboMon_esrv.exe files, restricting access to 224RoboMon_EventDatabase_CreateTables.SQL script, using to

troubleshoot converting Jet to SQL Server 6.5 database 219RoboMon_evtsrv registry key 214, 217RoboMon_evtsrv_ErrorTracking.log file 214

using to troubleshoot Tivoli Event Service 217RoboMon_PerformanceDatabase_CreateTables.SQL script,

using to troubleshoot converting performance database toSQL Server 7.0 database 220

ROBOMON_RADIX_POINT registry entry 245RoboMon_revtsrv registry key 217RoboMon_revtsrv_ErrorTracking.log file

using to troubleshoot Tivoli Event Service 217RoboMon_rulsrv.exe files, restricting access to 224RoboMon_SQL7_EventDB_CreateTables.SQL script, using to

troubleshoot converting Jet to SQL Server 7.0 database 220ROBOMON_TIME_FORMAT registry entry 246RoboMon.exe executable 3RoboMon.exe file 195ROUND$(number, precision) expression functions 234RULE

object definitions in rules syntax 257predefined rule syntax symbol 246

rule action categoriesactions for 97corrective actions 97

Index 337

rule action categories (continued)defined 96notification actions 96rule control actions 97variable management actions 97

rule action typeschanging 100close 98defined 97epilogue 98false 97inserting into an existing action list 99new 97prologue 98true 97update 97

rule action types, adding 99rule actions

activating inactive 100changing computers in 102defined 81defining an expression for 102formatting symbols for 101inactivating 100modifying 100removing 100setting values across rules 101specifying 96

rule codeabout 57about creating and editing in Tivoli Rule Designer 82about creating and editing in Tivoli Rule Editor 82about using Tivoli Rule Designer to write 57about using Tivoli Rule Engine to execute 57defined 82

rule code process statusviewing in Tivoli Enterprise Manager 57

rule conditionsdefined 81examples of 93managing 92using constants in 92using functions in 92using operators in 92using predefined variables in 92using statistics in 92using statistics to test 227using the Expression field to create 94using user-defined statistics in 92using variables in 92

rule control actionsrule actions category defined 97

Rule Designer, Tivoliabout 3

rule file syntaxfor comments 240for continuation characters 240for literal characters 240for quotation characters 240, 241for statement delimiters 240for white space 240using general file statements 242using INCLUDE statements to include statements from

other files 242using MACRO statements 242using symbol substitution 244

rule information configuration settingschanging in Tivoli Configuration Manager 53

rule processdefined 41

rule process thresholdsediting 77

rule processesmaximum number for IBM Tivoli Management Solution for

Exchange 225rule processes, default

defined as solutions 73rule processes, Tivoli

creating and managing with Tivoli Enterprise Manager 55rule schedules

about specifying restrictions for 85date restriction options for 85days of the month restriction options for 85days of the week restriction options for 85defined 81part of the day restriction options for 85restriction options for 85setting days, weeks, and months restriction options for 89setting part of the day and dates restriction options for 88setting up 85specifying restrictions for interval-based 85specifying restrictions for time of day 85weeks of the month restriction options for 85

rule scheduling optionsinterval 84Run manually (from the user interface or from an action of

another rule) 84Run only once when the Tivoli rule process is started 84time of day 84

rule selection typessimple 89using exceptions in 90using wildcards in 90

rule selectionsdefined 81formats for 89managing 89types of 89using Statistics drop-down list to create 91

rule syntaxcase-sensitivity in 241

Rule Wizard, Newusing to create new rules 82

rulesabout 1about actions for 65about components of 65about conditions for 65about documenting 103about enabling in Tivoli Enterprise Manager 68about firing in Tivoli Enterprise Manager 67about managing in Tivoli Enterprise Manager 65about managing within a process 69about schedules for 65, 239about selections for 65, 240about viewing status, code, and scheduling in Tivoli

Enterprise Manager 69about writing, testing, and editing with Tivoli Rule

Designer 65components of 1conditions for 227copying 70


rules (continued)creating manually using the Tivoli Rule Editor’s internal

rule language 105creating with the New Rule Wizard 82defined 1defining the processes of 70directories for storing source 45editing manually using the Tivoli Rule Editor’s internal

rule language 107file syntax for 240functions and restrictions for defining schedules 239Refresh_solution _Variables rule 75specifying schedules for 84specifying statistic domains for 84structure of 227troubleshooting execution of multiple one-shot 221troubleshooting variable usage in asynchronous 221using ACTION types with rule ACTION statements 237using ACTION types with rule CONDITION

statements 228using CLOSE_ACTION types with rule ACTION

statements 237using CLOSE_ACTION types with rule CONDITION

statements 228using CONDITION statements in 228using EPILOGUE_ACTION types with rule ACTION

statements 237using EPILOGUE_ACTION types with rule CONDITION

statements 228using event correlations in 227using FALSE_ACTION types with rule ACTION

statements 237using FALSE_ACTION types with rule CONDITION

statements 228using functions in 227using NEW_ACTION types with rule ACTION

statements 237using NEW_ACTION types with rule CONDITION

statements 229using operators in 227using PROLOGUE_ACTION types with rule ACTION

statements 237using PROLOGUE_ACTION types with rule CONDITION

statements 229using the source rule computer to manage 45using the Tivoli Rule Designer to edit graphically 104using Tivoli Enterprise Manager to refresh network view

of 46using Tivoli Rule Engine to enable 68using Tivoli Rule Engine to fire 67using TRUE_ACTION types with rule ACTION

statements 237using TRUE_ACTION types with rule CONDITION

statements 229using UPDATE_ACTION types with rule ACTION

statements 237using UPDATE_ACTION types with rule CONDITION

statements 229using variables in 227viewing available source 46viewing code for available source 46

rules syntaxCOMPUTER option in actions 260EVENT action in 261MESSAGE as type of EVENT action 261object definitions

RULE 257

rules syntax (continued)object definitions (continued)

SCHEDULE 251SELECT 255SET 248TEXT_BLOCK 251VARIABLE 249

predefined symbolsCOMPUTER 246CONTEXT 246DATE_STR 246EXISTS 246PID 246RULE 246TIME_STR 246USERNAME 246

predefined variables$ACTION_RESULT 247$ACTION_STATUS 247$CLOSE_CONDITION_COUNT 248$FALSE_CONDITION_COUNT 248$NEW_CONDITION_COUNT 248$PROBLEM_COUNT 248$PROBLEM_STATE 247$TRUE_CONDITION_COUNT 248$UPDATE_CONDITION_COUNT 248

PROBLEM as type of EVENT action 261TEXT as type of EVENT action 261WINDOWS as type of EVENT action 261

rules, sourcedefined 70modifying 70

rules, targetdefined 70modifying 70

rules, Tivolicomponents of 81defined 81

Run manually (from the user interface or from an action ofanother rule)

scheduling option 84Run menu in Tivoli Event Monitor 130Run only once when the Tivoli rule process is started

scheduling option 84Run Tivoli Reporting and Graphing icon 179

in Tivoli Reporting and Graphing 183

SSCHEDULE

object definitions in rules syntax 251schedule tab window

using the 86schedules

about rule 239as components of rules 81functions and restrictions for defining for rules 239setting up for rules 85specifying for rules 84viewing for processes in Tivoli Enterprise Manager 57

schedules, ruleabout specifying restrictions for 85date restriction options for 85days of the month restriction options for 85days of the week restriction options for 85part of the day restriction options for 85restriction options for 85

Index 339

schedules, rule (continued)setting days, weeks, and months restriction options for 89setting part of the day and dates restriction options for 88specifying restrictions for interval-based 85specifying restrictions for time of day 85weeks of the month restriction options for 85

scheduling optionsinterval 84time of day 84

scheduling options, ruleRun manually (from the user interface or from an action of

another rule) 84Run only once when the Tivoli rule process is started 84

SCL Server 7 solutions, defined 73scripts

RoboMon_EventDatabase_CreateTables.SQL 219RoboMon_PerformanceDatabase_CreateTables.SQL 220RoboMon_SQL7_EventDB_CreateTables.SQL 220

security issues, restricting access to IBM Tivoli ManagementSolution for Exchange files 224

Security Settings iconfor configuring Tivoli Web Event Monitor 169

SEG$(string, start-position, length) expression functions 235SEG1$(string, position) expression functions 235SEGL$(string, length) expression functions 235SEGR$(string, start-position) expression functions 235SELECT

object definitions in rules syntax 255selection types, rule

simple 89using exceptions in 90using wildcards in 90

selectionsabout rule 240as components of rules 81

selections, ruleformats for 89managing 89types of 89using Statistics drop-down list to create 91

Server Health iconsfor configuring Tivoli Web Event Monitor 167

servicesdefined 221Enterprise Manager, troubleshooting 222Event, troubleshooting 222Remote Event, troubleshooting 222Rule, troubleshooting 222TCP/IP, troubleshooting 222

SETobject definitions in rules syntax 248

settings and filtersabout configuring for events in the Tivoli Event

Configuration Manager 150Severity tab


Severity tab on Filter option in Tivoli Event Monitor Viewmenu 139

show key expiration warning configuration settingschanging in Tivoli Configuration Manager 52

Simple Network Management Protocol (SNMP)troubleshooting 214

simple rule selection types 89SNMP

See Simple Network Management Protocol 214

SNMP statistic domainsabout 124adding 124modifying 125removing 125

SNMP tab, Tivoli Statistics Builderdefined 112

SNMP trap filterin Tivoli Event Configuration Manager 154

SNMP traps View icon in Tivoli Event Monitor 132SNMP_SET action 307SNMP_TRAP action 308Solution for Exchange command line, IBM Tivoli Management

about 3Solution for Exchange components, IBM Tivoli

Management 2solution set driver files 74

creating and updating 75solution sets

variable parts in 77solution variables

editing 77solution.var files 75solutions

solution set driver file requirement for 74using Managed Network view to change 75viewing and managing in Tivoli Solutions Manager 74

Solutions Manager, Tivoliabout 2

solutions, defined 73source rule

defined 45source rule computer

changing in Tivoli Enterprise Manager 45source rule display

in the Tivoli Enterprise Manager main window 45using large icon view in Tivoli Enterprise Manager main

window 225source rules

defined 70directories for storing 45modifying 70viewing available 46viewing code for available 46

SQL Server 2000 solutions, defined 73SQL Server 6.5 database, using

RoboMon_EventDatabase_CreateTables.SQL script totroubleshoot converting Jet to 219

SQL Server 6.5 solutions, defined 73SQL Server 7.0 database, using

RoboMon_PerformanceDatabase_CreateTables.SQL script totroubleshoot converting performance database to 220

SQL Server 7.0 database, usingRoboMon_SQL7_EventDB_CreateTables.SQL script totroubleshoot converting Jet to 220

SQL Server database 129SQL Server databases, troubleshooting converting Jet to 219SQL Server DSN Configuration screen

for configuring Tivoli Web Event Monitor 166SQLCTR60.DLL file, using to troubleshoot Tivoli Statistics

Builder 222startup state

changing for processes in Tivoli Enterprise Manager 59statement delimiters

rule file syntax for 240statistic domains

about 112


statistic domains (continued)about ASCII file 118about COM 125about importing and exporting 115about ODBC Database 121about performance monitor 117about SNMP 124adding ASCII file 119adding COM 126adding ODBC Database 121adding performance monitor 117adding SNMP 124automatically fixing mismatches of 113copying 116definition for 112description of 113importing and exporting 115managing performance monitor 117mismatches defined 113modifying 113modifying ASCII file 120modifying COM 127modifying ODBC Database 123modifying performance monitor 118modifying SNMP 125name for 112removing 113removing ASCII file 121removing COM 127removing ODBC Database 123removing performance monitor 118removing SNMP 125restoring to original definition 113specifying for rules 84type of 113

Statistic drop-down listusing to create rule selections 91

STATISTIC statements, using expressions in 229statistics

defined 111using in rule conditions 92using to test rule conditions 227

Statistics Builder, Tivoliabout 3

statistics, defining timeout values for IP_REACHABLE 225statistics, user-defined

using in rule conditions 92storage

directories for source rule 45STRING$(string, count) expression functions 235SubClass: option in EventType/Class tab of Filter option in

Tivoli Event Monitor View menu 138SubClasss option


SUM$(statistic, context) expression functions 235summary pie graphs 174summary reports 174symbol names, valid

predefined 245Statistics 245user-defined statistics 245variables 245

symbols, list of valid justification options for 244symbols, predefined

COMPUTER 246CONTEXT 246

symbols, predefined (continued)DATE_STR 246

symbols, predefined rule syntaxEXISTS 246PID 246RULE 246TIME_STR 246USERNAME 246

symbols, substituting for text expansion in rule filesyntax 244

syntaxusing the command line interface 195

syntax for CONDITION statements 229syntax, command line interface

using braces in 195using double quotes in 195using pipes in 195

syntax, rule file 240Sysadmin view, Tivoli Reporting and Graphing 174

reports and graphs in 174System Data Sources list

RoboMon Event Database option infor configuring Tivoli Web Event Monitor 166

System DSN tabODBC Data Sources on Windows 2000 Control Panel

configuring Tivoli Web Event Monitor 166ODBC Data Sources on Windows NT Control Panel

configuring Tivoli Web Event Monitor 166

Ttabs

Advanced in EventType/Class filterTivoli Event Configuration Manager 158

Description in EventType/Class filterTivoli Event Configuration Manager 157

Severity in EventType/Class filterTivoli Event Configuration Manager 157

System DSN in ODBC Data Sources on Windows 2000Control Panel

configuring Tivoli Web Event Monitor 166System DSN in ODBC Data Sources on Windows NT

Control Panelconfiguring Tivoli Web Event Monitor 166

target rulesdefined 70modifying 70

TCP/IP host names, troubleshooting 220TCP/IP network services and adapters, troubleshooting 220TCP/IP port numbers, troubleshooting 221TCP/IP protocol DNS configuration screen, using to

troubleshoot host names 220TCP/IP Service and the Rule Service, using to troubleshoot

TCP/IP port numbers 221TCP/IP, troubleshooting forcing remote procedure call

connections to use 221TcpIpForRpc registry value, using to troubleshoot forcing

remote procedure call connections to use TCP/IP 221technical support

contacting ixTERMINATE action 310TEXT_BLOCK

object definitions in rules syntax 251TEXT, type of EVENT action in rules syntax 261threshold variables

updating 75

Index 341

thresholdsediting in a rule process 77

tier oneabout rules in 1

tier threeabout data store in 2

tier twoabout data store in 1

time of dayscheduling option 84

TIME_STRpredefined rule syntax symbol 246

timeline graphsin Tivoli Reporting and Graphing Sysadmin view 174

timeout values and community names, defining for DHCPstatistics 225

timeout values, defining for IP_REACHABLE statistic 225Tivoli Configuration Manager

about 3, 51specifying Microsoft profile names in MAIL actions 51using to change account information configuration

settings 52using to change collection information configuration

settings 53using to change configuration settings 52using to change mail information configuration

settings 52using to change rule information configuration settings 53using to change show key expiration warning

configuration settings 52using to create Tivoli mailboxes 51using to display configuration settings 52

Tivoli Customer Supportcontacting ix

Tivoli Enterprise Managerabout 1, 2, 41about enabling rules in 68about firing rules in 67about managing rules in 65about rule code in 57about viewing rule status, code, and scheduling in 69accessing view modes in 41as hierarchical representation of the network 42Browse options 42changing startup state for processes in 59changing the source rule computer in 45Confirmation options 42copying processes in 58creating rule processes in 62customizing behavior options 42deleting processes in 59moving processes in 59performing operations on processes in 58Process start options 42Refresh Network View compared to Find Tivoli in

Network 46, 47renaming processes in 59service, troubleshooting 222setting debug levels for processes in 59starting and stopping processes in 58using large icon in source rule display in main

window 225using to control the Tivoli Rule Engine 41using to create and manage Tivoli rule processes 55using to find IBM Tivoli Management Solution for

Exchange computers, rules, and processes in thenetwork 46

Tivoli Enterprise Manager (continued)using to manage computers 49using to manage domains 47using to manage processes 55using to refresh network view of rules and processes 46using to refresh the network view 46using to view process schedules 57using to view process status 57using to view rule code process status 57

Tivoli Event Configuration Managerabout 1, 2about using to configure event settings and filters 150controlling the Event Server 150EventType/Class filter option 155

Advanced tab 158Class 156Description tab 157EventSubType: 156EventType: 156Severity tab 157

sending and receiving events between computers 159using to access the local event filter 155using to access the SNMP trap filter 154using to access the Windows NT event filter 153

Tivoli Event Configuration Manager icon 151, 159Tivoli Event Configuration Manager Manage menu 151, 159Tivoli Event Configuration Manager Manage menu Event

Server configuration settings 152Tivoli Event Configuration Manager Manage menu Event

Server option 152Tivoli Event Configuration Manager Send/Receive menu

in Tivoli Event Configuration Manager Manage menu 160Tivoli Event Configuration Manager View menu

Tivoli Event Server configuration option 158Tivoli Event Configuration Manager, troubleshooting

management functions in 218Tivoli Event Database

about 129Tivoli event databases

using with Tivoli Event Monitor 130Tivoli Event Monitor

about 2, 129about filtering events 134Event menu options

Update Progress 133Monitor and View menu options

Acknowledge All 133Mark All As Read 133

Monitor menu for viewing monitors 131Monitor menu options

Filter 135Open 134

setting alert severities for events 146using to view and monitor events 130View icons

Closed problem 131OPCOM security messages 132OPCOM system messages 132Open problems 131Other SNMP traps 132Tivoli messages 131Tivoli SNMP traps 132Windows NT application messages 132Windows NT security messages 132Windows NT system messages 132Work in progress 131


Tivoli Event Monitor (continued)View menu filter options

Advanced tab 141Days/Time tab 137Description tab 139EventType/Class tab 138Fix/Acknowledge tab 140Severity tab 139

View menu filter options, EventType/Class tabClass: 138EventSubType: 138EventType: 138SubClass: 138

View menu for viewing events 131View menu options

Filter 135, 136Mark All As Read 132Mark All As Unread 132

Tivoli Event Monitor View iconsicons 131

Tivoli Event Server configuration optionTivoli Event Configuration Manager View menu 158

Tivoli Event Serviceerror tracking 214instrumentation 214troubleshooting

using Event_Server_1999_01_15.log 214using RoboMon_evtsrv_ErrorTracking.log 214

troubleshooting excessive CPU capacity 216troubleshooting starting of 213troubleshooting the Jet database 216

Tivoli mailboxescreating in Tivoli Configuration Manager 51

Tivoli Management Solution for Exchange command line, IBMabout 3

Tivoli Management Solution for Exchange components,IBM 2

Tivoli messages View icon in Tivoli Event Monitor 131Tivoli Performance Database, as source of data for graphics

and reports 173Tivoli process

defined 55using to start the Tivoli Rule Engine 55

Tivoli Remote Event Servicetroubleshooting 216using

HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Debugto troubleshoot 216, 217

Tivoli reporting and graphingabout 2

Tivoli Reporting and Graphing 2.GDF graph definition files in 191.RDF report definition files in 191.RPT files for use by Crystal Reports 191about 2, 173creating reports and graphs 179customizing graphs 186Edit menu 192exporting graphs to HTML format for Web use 188exporting graphs to JPEG format for Web use 189exporting reports 183exporting reports to HTML format for Web use 182exporting reports using rich text format 183Run Tivoli Reporting and Graphing icon 183using 2D Gallery tab to customize graphs 187using 3D Gallery tab to customize graphs 187using to manage batch folders 191

Tivoli Reporting and Graphing CIO, Management, andSysadmin views

reports and graphs in 174Tivoli Reporting and Graphing detail reports

in Sysadmin view 174Tivoli Reporting and Graphing Edit menu 190Tivoli Reporting and Graphing timeline graphs

in Sysadmin view 174Tivoli Reporting and Graphing views 174

reports and graphs in Sysadmin view 174Tivoli Rule Designer

about 1, 3, 81about using to write rule code 57about writing, testing, and editing rules using 65

Tivoli Rule Engineabout using to execute rule code 57starting with the Tivoli process 55using to enable rules 68using to fire rules 67using with the Tivoli Enterprise Manager 41

Tivoli rule processesand source rule display icons 45creating and managing with Tivoli Enterprise Manager 55

Tivoli rulesabout using Tivoli Rule Designer to create and modify 81components of 81defined 81

Tivoli servicestroubleshooting starting of 213

Tivoli SNMP traps View icon in Tivoli Event Monitor 132Tivoli Solutions Manager

about 2, 73setting confirmation options in 76using variables to update computers in 73viewing 73viewing and managing solutions in 74

Tivoli Statistics Builderabout 3, 111troubleshooting 222using HKEY_PERFORMANCE_DATA registry key to

troubleshoot 222Tivoli Statistics Builder access violations, troubleshooting 222Tivoli Statistics Builder ASCII File tab

defined 112Tivoli Statistics Builder COM tab

defined 112Tivoli Statistics Builder ODBC Database tab

defined 112Tivoli Statistics Builder Performance Monitor tab

defined 112Tivoli Statistics Builder SNMP tab

defined 112Tivoli Statistics Builder, troubleshooting Microsoft Internet

Information Server in 223Tivoli Web Event Monitor

SQL Server DSN configuration screen 166using Application Views icons to configure 167using Enterprise Views icons to configure 167using Server Health icons to configure 167using System DSN tab in ODBC Data Sources to configure

in Windows NT Control Panel 166using the Filtering icon to configure 168using the Security Settings icon to configure 169using to manage events from a browser 166

Tivoli, contacting ixTivoliInstallLog.txt file 213

Index 343

troubleshootingaccess violations 222adding columns or tables to performance databases 224central processing unit (CPU) usage statistics 223converting IBM Tivoli Management Solution for Exchange

databases to SQL Servers 219DISK_READ_PCT and DISK_WRITE_PCT statistic

values 224error messages during remote installation 215event and performance data forwarding 218event and performance data forwarding in one-way trust

relationships 219EVT_DATE and EVT_TIME statistic values 224Exchange mail actions using the

HKEY_LOCAL_MACHINE\SOFTWARE\TEMS\Configregistry key 223

execution of multiple one-shot rules 221forcing remote procedure call connections to use

TCP/IP 221forwarding events and performance data in

workgroups 219installation errors 213installing to computers in a workgroup 219large event database 216loading a dynamic link library during an upgrade

installation 224management functions in one-way trust relationships 218management functions in untrusting domains 218managing event and performance data forwarding between

a workgroup and a domain 219managing remote computers in a workgroup 219Microsoft Exchange mail actions 223Microsoft Internet Information Server in Tivoli Statistics

Builder 223one-way trust relationships 218Open Database Connectivity (ODBC) 214rate statistics exceeding 100% 223routing events across the network 216services 222setup of Microsoft Exchange for mail actions 215Simple Network Management Protocol (SNMP) 214starting Tivoli Event Service 213starting Tivoli services 213TCP/IP adapter and network services 220TCP/IP host names 220TCP/IP port numbers 221Tivoli Enterprise Manager service 222Tivoli Event Configuration Manager 218Tivoli Event Service

using Event_Server_1999_01_15.log 214using RoboMon_evtsrv_ErrorTracking.log 214using the Event_Server_1999_01_15.log file 217using the RoboMon_evtsrv registry key 217using the RoboMon_evtsrv_ErrorTracking.log file 217using the RoboMon_revtsrv registry key 217using the RoboMon_revtsrv_ErrorTracking.log file 217

Tivoli Event Service - Jet database 216Tivoli Event Service using excessive CPU capacity 216Tivoli Remote Event Service 216Tivoli Statistics Builder 222Tivoli Statistics Builder using the

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer\Performance registry key 222

Tivoli Statistics Builder using theHKEY_PERFORMANCE_DATA registry key 222

Tivoli Statistics Builder using the SQLCTR60.DLL file 222untrusting domains 218

troubleshooting (continued)using RoboMon Event Database 213using the Msinfo32.exe file 213using the TivoliInstallLog.txt file 213variable usage in asynchronous rules 221Windows NT errors 224

TRUE_ACTION typesusing with rule ACTION statements 237using with rule CONDITION statements 229

TRUNC$(number, precision) expression functions 236trust relationships, troubleshooting event and performance

data forwarding in one-way 219trust relationships, troubleshooting management functions in

one-way 218trust relationships, troubleshooting one-way 218typeface conventions x

Uuninstalling IBM Tivoli Management Solution for

Exchange 222Unknown MAPI errors, troubleshooting 223untrusting domains

troubleshooting 218troubleshooting management functions in 218

UPDATE_ACTION typesusing with rule ACTION statements 237using with rule CONDITION statements 229

USERNAMEpredefined rule syntax symbol 246

using with the Event Server 130utility programs, RoboMon_compact.exe 220

Vvalues, return

in the command line interface 195VARIABLE

object definitions in rules syntax 249variable management actions

rule actions category defined 97variable parts

in solution sets 77variable usage, troubleshooting in asynchronous rules 221variables

defined 73using in rule conditions 92using to update computers in Tivoli Solutions Manager 73using with rules 227

variables, as predefined rule syntax$ACTION_RESULT 247$ACTION_STATUS 247$CLOSE_CONDITION_COUNT 248$FALSE_CONDITION_COUNT 248$NEW_CONDITION_COUNT 248$PROBLEM_COUNT 248$PROBLEM_STATE 247$TRUE_CONDITION_COUNT 248$UPDATE_CONDITION_COUNT 248

variables, predefinedusing in rule conditions 92

variables, solutionediting 77

variables, thresholdupdating 75

View menu in Tivoli Event Monitor for viewing events 131


View menu options in Tivoli Event MonitorAcknowledge All 133Filter 135, 136

Days/Time tab 137EventType/Class tab 138

Filter, EventType/Class tab optionsClass: 138EventSubType: 138EventType: 138SubClass: 138

Mark All As Read 132, 133Mark All As Unread 132

view modesaccessing in Tivoli Enterprise Manager 41

viewingavailable source rules 46

viewing rule status, code, and schedulingabout 69

viewslarge icon in source rule display of Tivoli Enterprise

Manager main window 225views, Tivoli Reporting and Graphing

CIO, Management, and Sysadmin 174virtual domains

defined 47

WWAIT action 311Web HTML format

exporting graphs for Web use in Tivoli Reporting andGraphing 189

exporting reports for Web use in Tivoli Reporting andGraphing 182

Weekly_Reports Admin rulefor creating batch reports and graphs 190

white spacerule file syntax for 240

wildcard rule selection types 90Windows 2000 Control Panel

System DSN tab in ODBC Data Sourcesconfiguring Tivoli Web Event Monitor 166

Windows NT application messages View icon in Tivoli EventMonitor 132

Windows NT Control PanelSystem DSN tab in ODBC Data Sources

configuring Tivoli Web Event Monitor 166Windows NT errors, troubleshooting 224Windows NT event filter

in Tivoli Event Configuration Manager 153Windows NT security messages View icon in Tivoli Event

Monitor 132Windows NT system messages View icon in Tivoli Event

Monitor 132WINDOWS, type of EVENT action in rules syntax 261Wizard, New Rule

using to create new rules 82Work in progress View icon in Tivoli Event Monitor 131workgroups, troubleshooting forwarding events and

performance data in 219workgroups, troubleshooting installing to computers in 219workgroups, troubleshooting managing event and

performance data forwarding between a workgroup and adomain 219

workgroups, troubleshooting managing remote computersin 219

WORKING_SET action 313

WRITE action 315

ZZERO action 317

Index 345

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC23-4721-00

ibm ® tivoli ® management solution for excha nge: user's...

Documents