tds for event management 1.0.1 release notes

TDS for ERelease Version 1.1July 1999

vent Management 1.0.1Notes

TDS for Event Management 1.0.1 (July 1999)

Copyright Notice

Copyright © 1999 by Tivoli Systems Inc., an IBM Company, including this documentation and all software. Allrights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for TivoliProducts to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted,transcribed, stored in a retrieval system, 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 TivoliSystems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the Tivoli Systemscopyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. Thedocument is not intended for production and is furnished “as is” without warranty of any kind. All warranties onthis document are hereby disclaimed including the warranties of merchantability and fitness for aparticular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subjectto restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

Trademarks

The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, CICS, IBM, MVS,NetView, Tivoli, Tivoli Change Management, Tivoli Enterprise Console, Tivoli Decision Support 2.0, TivoliManagement Environment, TME 10, OS/2, O/S390, and RS/6000.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks ofMicrosoft Corporation.

Java and all Java-based trademarks or logos are trademarks of Sun Microsystems, Inc.

UNIX is a registered trademark in the United States and other countries licensed exclusively through X/OpenCompany Limited.

Other company, product, and service names mentioned in this document may be trademarks or servicemarksof others.

Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will beavailable 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 Tivoli System’s or IBM’s valid intellectual property or other legally protectable right, 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 patent applications covering subject matter in this document. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries, in writing,to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

Tivoli Decision Support Guide Documentation

Each Tivoli Discovery Guide is delivered with on-line documentation. During the installation process, the applicabledocumentation is copied to the Tds\Guide docs installation directory on your system.

TDS for Event Management 1.0.1Release Notes Version 1.1

i

Table of Contents

Revision History................................................................................................ iv

Preface ................................................................................................................ v

Who Should Read This Book.................................................................................... v

TDS and EVM Guide Documentation ...................................................................... vi

Contacting Customer Support .............................................................................. viii

Introduction ........................................................................................................ 1

Product Summary ..................................................................................................... 1

Supported Databases............................................................................................................... 2

Installation .......................................................................................................... 3

Overview .................................................................................................................... 3

Requirements ............................................................................................................ 4

General ..................................................................................................................................... 4

ODBC Drivers ........................................................................................................................... 5

Oracle and Sybase ................................................................................................................... 6

DB2........................................................................................................................................... 6

Supported Languages .............................................................................................................. 7

Installing the Event Management Guide.................................................................. 7

Preparing to Work with the TEC Database............................................................................... 7

Setting Up an Oracle, Sybase, or DB2 Client ....................................................................... 7

Preparing the TEC Database ................................................................................................... 7

Installing an ODBC Driver ..................................................................................................... 8For Oracle and Sybase Databases ................................................................................... 8For DB2 Databases ........................................................................................................... 8

Setting Up an ODBC Data Source Connection..................................................................... 8Verifying the ODBC Driver Installation........................................................................... 9Registering the DB2 Database .................................................................................... 10Configuring the DB2 CLI/ODBC Driver Using CCA..................................................... 11Accessing DB2 Data Using ODBC Applications.......................................................... 11

Creating the Archive Table and Trigger in the TEC Database ........................................... 12Creating Views in a Sybase TEC Database ....................................................................... 12


ii

After Installing TDS................................................................................................................. 13

Configuring the Shared Source File Path ........................................................................... 13Installing and Importing the Event Management Guide...................................................... 14Assigning and Verifying a Data Source .............................................................................. 16Setting the Date Range Parameter in the Cube ................................................................. 17Building the Cubes .............................................................................................................. 17

Reinstalling a Discovery Guide .............................................................................. 18

Operating Procedures ..................................................................................... 18

Scheduling the Cube Build Task............................................................................ 18

Scheduling the Cube Build Task ............................................................................................ 18

Backing Up the Archive and Trigger Data .............................................................................. 20

Using the Event Management Guide...................................................................... 20

Specifying the Database Logon for Crystal Reports .............................................................. 20

Troubleshooting............................................................................................... 21

ODBC Driver Problems ........................................................................................... 21

Cube Building.......................................................................................................... 21

Report Problems ..................................................................................................... 23

Year 2000 (Y2K) Compliance .................................................................................. 25

Microsoft Y2K Service Packs ................................................................................................. 25

TEC Database ........................................................................................................................ 25

Seagate Crystal Reports Version 6 ........................................................................................ 26

Software Defects, Limitations, and Workarounds......................................... 26

Defects ..................................................................................................................... 26

Limitations............................................................................................................... 27

Workarounds ........................................................................................................... 27

Functional Description .................................................................................... 28

Data Sources ........................................................................................................... 28

Event Management Database Schema.................................................................................. 28

tds_tec_t_archive Table ...................................................................................................... 28

Event Management Database Triggers.................................................................................. 29

Database Trigger for Sybase Databases............................................................................ 29Database Trigger for Oracle Databases ............................................................................. 30Database Trigger for DB2 Databases................................................................................. 31


iii

Managing the Event Management Archive Table.................................................. 33

Sizing the TEC Database for the Archive Table..................................................................... 33

Deleting Records from the Archive Table............................................................................... 33

Deleting Records from the Archive Table in a Oracle Database ........................................ 33Deleting Records from the Archive Table in a Sybase Database....................................... 34Deleting Records from the Archive Table in a DB2 Database............................................ 34

Cubes (Tivoli Discovery Administrator) ................................................................ 36

Closed TEC Events ................................................................................................................ 36

Queries Used to Build the Cube ......................................................................................... 36TEC Class Hierarchy....................................................................................................... 36TEC Date Info.................................................................................................................. 36TEC Historical Archive..................................................................................................... 37TEC System Info ............................................................................................................. 38

Parameters Used to Build Cube ......................................................................................... 39Dimensions ......................................................................................................................... 40

By Date ............................................................................................................................ 40By Day of Week............................................................................................................... 40By Time of Day ................................................................................................................ 41By Day and Time............................................................................................................. 41By Entire Network............................................................................................................ 41By Hostname ................................................................................................................... 42By Class........................................................................................................................... 42By Severity....................................................................................................................... 43By Source ........................................................................................................................ 43By Duration...................................................................................................................... 43By SLA............................................................................................................................. 44

Measures............................................................................................................................. 44Check of the Allowed Measures and Dimensions Combination...................................... 45

Topics and Views (Tivoli Discovery Interface) ...................................................... 47

Am I meeting expectations for resolving events? ........................................................ 47Could I be more effective at resolving events?............................................................ 47What are my trends?.................................................................................................... 48What types of events am I seeing?.............................................................................. 48When are my peak days for event volume? ................................................................ 49When are my peak times for event volume? ............................................................... 49Where are events coming from?.................................................................................. 49

Related Views and Roles ........................................................................................ 50

Report Definitions ................................................................................................... 55

APPENDIX A ..................................................................................................... 58

DB2 Crystal Reports Filename Changes ............................................................... 58


iv

Revision HistoryDocument Version & Date

Release Note Version 1.1 for TDS for Event Management Release 1.0.1 (July 1999)

Incorporated changes to this release note for the Tivoli Decision Support for EventManagement (DB2 Only) Version 1.0.1.

The guide installation option for Tivoli Decision Support for Event Managementrelease 1.0, for use with Sybase and Oracle TEC databases, is also included on theCD-ROM. This version of the guide has not changed from the March 1999 release (1.0).


v

PrefaceThis document describes the Tivoli Decision Support (TDS) for Event Managementproduct. The Event Management guide is designed to augment the Tivoli EnterpriseConsole (TEC) product. This discovery guide lets you strategically manage yourenterprise network. Where the TEC provides a powerful, rule-based event managementapplication that integrates network, systems, database and application management, theEvent Management guide provides the IT managers of the business enterprise anoverview of how events are being handled.

Note: The Tivoli guides as a group are called discovery guides. The TDS for EventManagement product is a discovery guide that is also called the EventManagement guide or the EVM guide.

Who Should Read This BookThis document is intended for the users of the Event Management guide and anyoneresponsible for the administration of Tivoli Decision Support.

Before using the Event Management guide, you should be familiar with the following:

• The operating system on your computer• The basic use of discovery guides and the Tivoli Discovery Interface

To set up the Event Management guide, your system administrator should be familiarwith the following:

• The Tivoli Discovery Administrator• The basic use of Crystal Reports and Cognos PowerPlay• The TEC database• The Open Database Connectivity (ODBC) for your database


vi

TDS and EVM Guide DocumentationTo install and use the Event Management (EVM) guide, you should be familiar with thefollowing Tivoli Decision Support publications:

DescriptionDocument

Location

Review this document before installing TDS for Event Management. It contains the latestinformation about the TDS product. This document also describes the features of the TivoliDiscovery Interface that are not documented in version 2.0. These features are found in theTivoli Discovery Interface, and not in the Tivoli Discovery Administrator. The TivoliDecision Support 2.0 User Online Help system provides detailed information andprocedures for using the undocumented features.

Tivoli Decision Support

(TDS) 2.0 Readme0799.txt

Filename on the CD-ROM: d:\Readme0799.txt(where d: is the drive letter for your CD-ROM Drive)

Filename on your system: Tds\Docs\Readme0799.txt

Provides a description of the product documentation, the initial installation instructions, andthe contact information for Tivoli Customer Support.TDS for Event Management

Readme.txtFilename on the CD-ROM:

For the Sybase and Oracle version of the guide: d:\Tivoli Decision Supportfor Event Management\NTimage\Readme.txt(where d: is the drive letter for your CD-ROM Drive)

For the DB2 version of the guide: d:\Tivoli Decision Support for EventManagement (DB2 Only)\NTimage\Readme.txt(where d: is the drive letter for your CD-ROM Drive)

Filename on your system:

For the Sybase and Oracle version of the guide: TDS\Guide docs\TivoliDecision Support for Event Management\Readme.txt

For the DB2 version of the guide: TDS\Guide docs\Tivoli DecisionSupport for Event Management (DB2 Only)\Readme.txt

Provides copyright, prerequisite, installation procedures, and trouble shooting for theEvent Management guide.TDS for Event Management

Release NotesFilename on the CD-ROM:

For the Sybase and Oracle version of the guide: d:\Tivoli Decision Supportfor Event Management\NTimage\TDS_EVM_Rel_Notes.pdf(where d: is the drive letter for your CD-ROM Drive)

For the DB2 version of the guide: d:\Tivoli Decision Support for EventManagement (DB2 Only)\NTimage\TDS_EVM_Rel_Notes.pdf(where d: is the drive letter for your CD-ROM Drive)

Filename on your system:

For the Sybase and Oracle version of the guide: TDS\Guide docs\TivoliDecision Support for Event Management\Tds_EVM_Rel_Notes.pdf

For the DB2 version of the guide: TDS\Guide docs\Tivoli DecisionSupport for Event Management (DB2 Only)\Tds_EVM_Rel_Notes.pdf


vii

DescriptionDocument

Location

Provides an overview of the TDS Guides, cube dimensions and measures, and detailedprocedures for using the Tivoli Decision Support discovery guides.Using Decision Support

GuidesFilename on your system: TDS\Docs\Pdf\dg.pdf

Installation GuideProvides installation procedures for TDS and its components in stand-alone andnetwork mode.

Filename on your system: TDS\Docs\Pdf\install.pdf

Describes TDS features, concepts, and provides procedures for using the Tivoli DiscoveryInterface.Decision Support User’s

GuideFilename on your system: TDS\Docs\Pdf\user-gd.pdf

Explains the features of the Tivoli Discovery Administrator.Administrator Guide

Filename on your system: TDS\Docs\Pdf\admin-gd.pdf

Each Tivoli discovery guide is delivered with online documentation. During theinstallation process for each discovery guide, the applicable discovery guide documentationis copied to the Tds\Guide docs (where Tds\ is the TDS installation directory)installation directory on your system.

Other Guides

Directory on your system: Tds\Guide docs


viii

Contacting Customer SupportTo contact Tivoli Customer Support:

Note: Whenever contacting Tivoli Customer Support, please have your customeridentification information available.

• Access the Tivoli Customer Support home page at http://www.support.tivoli.com.After you link to and submit the customer registration form, you can access manycustomer support services on the World Wide Web. Refer to the Customer SupportHandbook for a listing of Tivoli Customer Support services, hours of operation, andcontact numbers. This handbook is available online at http://www.support.tivoli.com.

• Send an e-mail to [email protected].• In the United States, call Tivoli Customer Support at 1-800-TIVOLI-8.• Outside the United States, refer to your Customer Support Handbook for a list of

support numbers in your country. This handbook is available online athttp://www.support.tivoli.com.

To provide comments and suggestions about our documentation:

• We at Tivoli are very interested in hearing from you about your experience withTivoli products, documentation, and services. We welcome your suggestions forimprovements. If you have comments or suggestions about our documentation,please send e-mail to [email protected].

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


mailto:[email protected]



TDS for Event Management 1.0.1 1Release Notes Version 1.1

IntroductionImportant: The Tivoli Decision Support for Event Management (DB2 Only) guide release

1.0.1 supports TEC databases running on DB2. The guide installation optionfor Tivoli Decision Support for Event Management release 1.0, for use withSybase and Oracle TEC databases, is also included on the CD-ROM. Thisversion of the guide has not changed from the March 1999 release (1.0).

Product SummaryTivoli Decision Support for Event Management (Event Management guide), version 1.0,provides a strategic view of network activity as recorded in TEC events and informationabout the response time for these events. Two versions of the Event Management guide aresupplied on the 1.0.1 release CD-ROM:

Title GuideVersion Number

DatabasesSupported

Tivoli Decision Support for Event Management 1.0 SybaseOracle

Tivoli Decision Support for Event Management(DB2 Only)

1.0.1 DB2

TDS for Event Management version 1.0 supports Sybase or Oracle versions of the TECdatabase. TDS for Event Management version 1.0.1 supports DB2 versions of the TECdatabase. The following modifications were made to the Tivoli Decision Support for EventManagement Guide (DB2 Only) version 1.0.1:

• The trigger used in the TEC database• Five Crystal reports (See Appendix A).• A new DB2 database schema

The Event Management guide provides information about areas of high activity or recurringpatterns of system activity. The combination of the Tivoli Discovery Administrator and theTivoli Discovery Interface with Tivoli Decision Support for Event Management providesyou with the following powerful analysis and reporting capabilities:


• Gathers and reviews information based on a set of powerful questions and reports thataddress success rates, effectiveness, trends, peak volume, and sources of events

• Presents event management information as charts and tabular reports• Automates data acquisition – cube building

Tivoli Discovery Interface uses a multidimensional cube. The cube is based on closed TECevents that have been archived from the TEC database event repository. A new archivetable and trigger for the TEC database are provided with this discovery guide so that as eachTEC event is closed, it is archived for later inclusion in the TDS multidimensional cube.Each TDS installation site can control when the multidimensional cube is refreshed.

Supported DatabasesThe Event Management guide supports the following databases:

• Oracle 7.x• Sybase 10.x or 11.x• DB2 5.2


InstallationOverviewThe following table lists the sequence of activities required to install the Event Managementguide. The shaded activities are only performed if your are first installing TDS on yoursystem. If TDS is already installed on your system, skip the shaded steps (Steps 2, 4-6).

How to… See section…1. Determine the software requirements Requirements

2. Set up an Oracle, Sybase, or DB2 client Setting Up an Oracle, Sybase, or DB2 Client

3. Size the TEC database Sizing the TEC Database for the Archive Table

4. Install TDS

5. Install Cognos

6. Install the ODBC drivers

See the TDS Installation Guide documentdescribed in the section TDS and EVM GuideDocumentation.

7. Set Up an ODBC data source connection Setting Up an ODBC Data Source

Creating the Archive Table and Trigger in theTEC Database

8. Create the SQL table, trigger, and views

Creating Views in a Sybase TEC Database

9. Configure the shared source file path Configuring the Shared Source File Path

10. Install the discovery guide

11. Import the discovery guide

Installing and Importing the EventManagement Guide

12. Assign the ODBC data source

13. Test the connectivity with the data source

Assigning and Verifying a Data Source

14. Set the date range parameter in the cube Setting the Date Range Parameter in the Cube

15. Build the cube Building the Cubes

16. Schedule the cube build task Scheduling the Cube Build Task


RequirementsThis section lists the products that are prerequisites for the Event Management guide. Referto the appropriate product documentation for installation procedures.

GeneralThe following requirments apply to all configurations of the Event Management guide.

• Microsoft Windows 95 and Windows NT 3.51 or later

• Tivoli Decision Support 2.0 with the following components:

• Tivoli Discovery Interface• Tivoli Discover Administrator ( to build cubes)• Cognos PowerPlay (Administrator)• Seagate Crystal Reports (only required when creating new reports)

• Tivoli TEC 3.6 on your network

• Access to the TEC database

• Access to the cube built by the administrator


ODBC DriversThe Event Manager guide uses ODBC Drivers to communicate with the TEC database, noRIM support is required.

DB2 users need to use the IBM DB2 ODBC drivers that is automatically installed with theDB2 client. Check with your system administrator about setting up your DB2 client

Oracle and Sybase ODBC drivers are included on the TDS 2.0 CD-ROM. The followingODBC drivers are provided on the TDS 2.0 CD-ROM.

Database Version Database Version Database VersionDatabaseType ODBC Version ODBC Version ODBC Version

10.X all tier 1 11.0.1.X all tier 1 11.0.3.X all tier 1SybaseINTERSOLV Inc.ODBC 3.01(10.03 client or higher)

INTERSOLV Inc.ODBC 3.01

INTERSOLV Inc.ODBC 3.01

7.2.X all tier 1 7.3.X all tier1OracleMicrosoft ODBC Driver for Oracle2.00.006325

Microsoft ODBC for Oracle2.573.292700

Microsoft ODBC Driver for Oracle2.00.006325

Microsoft ODBC for Oracle2.573.292700

Note: If you experience problems with the INTERSOLV ODBC driver version 3.01 forSybases, contact Tivoli Customer Support, and request the updated INTERSOLVODBC driver version 3.01 for Sybase. For more information about this issue,please contact Tivoli Customer Support by sending an email [email protected] or by visiting the Tivoli Customer Support web site athttp://www.support.tivoli.com. Please be sure to include your customeridentification information.

• The Microsoft Access ODBC driver must be installed on your system before you canuse an ED Drill Through data source with Seagate Crystal Reports.

• Installation of Microsoft Access is also recommended though not required.




Oracle and SybaseImportant: The Event Management guide that supports Sybase and Oracle has not

changed from the 1.0 release of this guide. The only change for the 1.0.1release of the Event Management guide was the addition of a DB2 version ofthe guide.

If you are an Oracle or Sybase user, you will also need the following:

• The appropriate Oracle or Sybase client and server

• Oracle 7.x• Sybase 10.x or 11.x

• The appropriate Oracle or Sybase ODBC driver (see the section ODBC Drivers)

DB2Note: A list of the report filenames that were modified for the DB2 version of the guide

is provided in Appendix A.

If you are a DB2 UDB user, you will also need the following:

• DB2 UDB 5.2 Server

• DB2 UDB 5.2 Client Application Enabler (CAE)

The Client Application Enabler is contained on the DB2 Client Application EnablersCD-ROM or can be downloaded from the Web page athttp://www.software.ibm.com/data/db2.

• IBM DB2 ODBC drivers (delivered with DB2)

• If you are using Tivoli Management Framework you will need to install two patches.The following Tivoli Management Framework patches (patches can be downloadedfrom the Tivoli Software Fixes Web Page: http://w3.support.tivoli.com/patches/ )

• 361-TMF-0002• 361-TMF-0032

http://w3.support.tivoli.com/patches/


Supported LanguagesThis version of TDS for Decision Support only supports the English language.

Installing the Event Management GuideBefore using the Event Management guide, complete the installation procedures describedin the following sections.

Preparing to Work with the TEC DatabaseUse the following procedures to create the network identification required by Sybase orOracle to access the TEC database from the systems running TDS.

Setting Up an Oracle, Sybase, or DB2 Client

Consult your database administrator for the appropriate client configuration. Your systemmust have a valid client configuration for the ODBC connection that TDS uses to accessyour database.

Preparing the TEC DatabaseInstall the appropriate database client before setting up the ODBC data source. Theprocedure for setting up the ODBC data source is described in the next section.


Installing an ODBC Driver

For Oracle and Sybase Databases

1. Insert the Tivoli Decision Support 2.0 CD-ROM in the CD-ROM drive for your TDSserver, and from the Start menu, choose Run.

The Run dialog box appears.

2. In the Run dialog box, type d:\setup.exe (where d: is the drive letter for your CD-ROMdrive), and click OK.

The Tivoli Decision Support Discovery Guide Installation window appears.

3. Click on Install Microsoft 32-bit ODBC

4. Follow the prompts and install appropriate drivers for your database platform.

For DB2 DatabasesThe ODBC drivers for DB2 databases are included with the DB2 Client ApplicationEnabler. This is contained on the DB2 Client Application Enablers CD-ROM or can bedownloaded from the Web page at http://www.software.ibm.com/data/db2. The DB2CLI/ODBC driver is automatically installed when the DB2 Client Application Enabler isinstalled.

Setting Up an ODBC Data Source Connection

Before creating an ODBC connection, you must install and configure your database client.This section describes how to set up an ODBC connection to an Oracle or Sybase database.

If you are using a DB2 database, the ODBC connection is created while completing theprocedure described in the section Registering the DB2 Database.

During the database client configuration, you will need to create a database alias (Oracle) ora server entry (Sybase) for the TEC database. Specify this alias or entry in Step 7 of thefollowing procedure.

Note: Contact your system administrator for specific information concerning how to setup your database client.

http://www.software.ibm.com/data/db2


Use the following procedure to connect to an ODBC data source for TEC.

1. On the Control Panel, select the ODBC icon

2. Select the System DSN tab.

3. Click Add.

4. Select the appropriate ODBC driver for your database, and click Finish.

5. Type a meaningful name for this ODBC data source in the Data Source text box.

Note: Record the data source name. Use this data source name when adding a datasource for the guide in TDS Administrator.

6. Type a description for the data source in the Description text box.

7. Type the data source server name in the Sever Name text box.

8. If you are installing a Sybase ODBC driver, type the TEC database, in the DatabaseName text box.

Verifying the ODBC Driver Installation

Verify that the Microsoft ODBC Driver Manager, which is accessed through the ControlPanel, and the DB2 CLI/ODBC driver are installed. On Windows 95 and Windows NT theyare both installed with DB2 unless the ODBC component is manually unselected during theinstall.

To verify that they both exist on the machine:

1. Run the Microsoft ODBC Administrator from the icon in the Control Panel, or issue theappropriate command from the command line:

odbcad32.exe for Windows 95 or Windows NT

2. Click on the Drivers push button, or the ODBC Drivers tab (depending on the platform).

3. Verify that "IBM DB2 ODBC Driver" is shown in the list.

4. If either the Microsoft ODBC Driver Manager or the IBM DB2 CLI/ODBC driver is notinstalled, then rerun the DB2 install and select the ODBC component in Windows 95 orWindows NT.


Registering the DB2 Database

Register the DB2 database with the ODBC driver manager as a data source. On Windows95 and Windows NT you can make the data source available to all users of the system (asystem data source), or only the current user (a user data source). You can use any of thesemethods to add the data source but using the Client Configuration Assistant (CCA) is theeasiest:

1. Using the CCA:

a) Select the DB2 database alias that you want to add as a datasource.

b) Click on the Properties push button. The Database Properties window opens

c) Select the Register this database for ODBC check box.

d) On Windows 95 and Windows NT you can use the radio buttons to add the datasource as either a user or system data source.

2. Using the Microsoft 32bit ODBC Administration tool, which you can access from theicon in the Control Panel or by running odbcad32.exe from the command line:

a) On Windows 95 and Windows NT the list of user data sources appears by default. Ifyou want to add a system data source click on the System DSN button, or theSystem DSN tab (depending on the platform).

b) Click on the Add push button.

c) Double-click on the IBM DB2 ODBC Driver in the list.

d) Select the DB2 database to add and click on OK.

3. On Windows 95 and Windows NT there is a command that can be issued in thecommand line processor to register the DB2 database with the ODBC driver manager asa datasource. An administrator could create a command line processor script to registerthe required databases. This script could then be run on all of the machines that requireaccess to the DB2 databases through ODBC.

See the CATALOG [ user | system ] ODBC DATA SOURCE command in theCommand Reference for more information.


Configuring the DB2 CLI/ODBC Driver Using CCA

The following is an optional procedure:

1. Select the DB2 database alias you want to configure.

2. Click on the Properties push button, and the Database Properties window opens.

3. Click on the Settings push button, and the CLI/ODBC Settings window opens.

4. Click on the Advanced push button. You can set the configuration keywords in thewindow that opens. These keywords are associated with the database alias name, andaffect all DB2 CLI/ODBC applications that access the database. The online helpexplains all of the keywords, as does Configuration Keywords. For information onmanually editing this file (db2cli.ini), see Configuring db2cli.ini.

Accessing DB2 Data Using ODBC Applications

If you have correctly configured your system to use ODBC, you can now access DB2 datausing ODBC applications. Start the ODBC application and go to the Open window. Selectthe ODBC databases file type. The DB2 databases that you added as ODBC data sourceswill be selectable from the list. Many ODBC applications will open the table as read-onlyunless a unique index exists. To test an ODBC connection, refer to this manual’s section onAssigning and Verifying a Data Source under After Installing TDS.


Creating the Archive Table and Trigger in theTEC Database

Before creating the Archive table and trigger, read the section Sizing the TEC Database forthe Archive Table, and make sure that your database is sized correctly to accommodate theincreased volume of data. Complete the following procedure to create the Archive tableand the trigger for Sybase and Oracle databases. Your database name, user, and passwordmay be different from those shown in the following examples. Contact your systemadministrator for additional information.

• For Oracle, enter the following:sqlplus tec@<oracle alias> @ tds_tec_t_archive.ora.sql

OR

plus33.exe tec@<oracle alias> @ tds_tec_t_archive.ora.sql

• For Sybase, enter the following:isql –Utec –Ptectec –itds_tec_t_archive.syb.sql

• For DB2, enter the following:db2 –td~ -f tds_tec_t_archive.DB2.sql

Creating Views in a Sybase TEC Database

Views are only required when running Crystal Reports with a Sybase database. The viewsallow Crystal Reports to access data from the lowercase TEC table names in a Sybasedatabase.

• For Sybase, enter the following:isql –Utec –Ptectec –itds_tec_views.syb.sql

mailto:tec@<oracle

mailto:tec@<oracle


After Installing TDSAfter installing TDS, complete the procedures described in this section to finish the EventManagement guide installation process.

Configuring the Shared Source File Path

Before using the Tivoli Discovery Administrator or the Tivoli Discovery Interface, theymust be configured to locate certain files (called source files) that are stored on your system(the local system) or on the network. If you installed TDS using the stand-alone installationoption, your source files are on your system. For other installations, the source files usuallyreside on a network server. Specify the path to the source files when you start the TivoliDiscovery Administrator for the first time.

To set the shared source file path:

1. On the View menu, select Options.

The Options dialog box appears.

2. On the General tab, in the Network box, type the name of the drive (and folder, ifappropriate) that contains the following folders:

• Cubes• Data• Reports

3. Click OK.


Installing and Importing theEvent Management Guide

Use the following procedure to install and import the Event Management guide:

1. Insert the Tivoli Decision Support for Event Management CD-ROM in the CD-ROMdrive for your TDS server, and from the Start menu, choose Run.

The Run dialog box appears.

2. In the Run dialog box, type d:\setup.exe (where d: is the drive letter for your CD-ROM drive), and click OK.

The Tivoli Decision Support Discovery Guide Installation window appears.

3. If you are using Sybase or Oracle, select

Tivoli Decision Support for Event Management

-OR-

If you are using DB2, select

Tivoli Decision Support for Event Management (DB2 Only)

The discovery guide files are placed in the following Tds\ installation directories:cubes, models, reports, and install (where Tds\ is the TDS installation directory).

For the Oracle and Sybase installation, the online documentation is installed in thefollowing directory:Tds\Guide docs\Tivoli Decision Support for Event Management

For the DB2 installation, the online documentation is installed in the followingdirectory:

Tds\Guide docs\Tivoli Decision Support for Software Deployment Analysis(DB2 Only)

The updated TDS readme is installed in the following directory:Tds\Docs\Readme0799.txt

Note: For more information, see the section TDS and EVM Guide Documentation.


The SQL scripts to build the table, trigger, and views are installed in thefollowing directory:Tds\Util\Tivoli Decision Support for Event Management

4. Start the Tivoli Discovery Administrator.

5. On the Decision Support Guides menu, click Import.

-OR-

If a discovery guide has not been installed on your system, you are prompted to importan installed discovery guide, and to connect to a data source.

Note: For a step-by-step procedure, see Running the Tivoli DiscoveryAdministrator for the First Time in the Administrator Guide document.

a. A dialog box appears prompting you to import and to install the decision supportguide, select the Tivoli Decision Support for Event Management guide, click Yes.

b. When prompted to add a data source, click Yes.

c. Select your configured data source.

d. Enter the database userid and password.

e. Enter the database qualifier:

• For Sybase, enter tec• For Oracle, enter TEC• For DB2, enter DB2ADMIN

Note: Your database qualifier may be different. Contact the database administratorfor additional information.

6. Select Event Management on the Import Decision Support Guides dialog box, andclick OK.


Assigning and Verifying a Data Source

Use the following procedure to assign and verify a data source for the Event Managementguide:

1. Using the Tivoli Discovery Administrator, select the Closed TEC Events cube.

2. On the Data Sources menu, click Assign Data Sources.

3. Select the data source from the dropdown list.

4. Select the following queries, and click OK:

• TEC Class Hierarchy• TEC Date Info• TEC Historical Archive• TEC System Info

5. Click the Data Sources folder.

6. Right click on the data source you just assigned, and select Test Connectivity

If the Tivoli Discovery Administrator message dialog box appears with the messageError connecting to Data Source – DataSourceName, click Details to display moreinformation about the connection error. Click OK, and verify the data source definition,userid, password, and qualifier.

If the connection is successful, the Test Data Source dialog box appears with themessage Connection Successful. Click OK.


Setting the Date Range Parameter in the Cube

TEC sets the current period by the most recent date in the records that are returned by thequery. You can use the Date range parameter to select a specific range of records.

Building the Cubes

Schedule cube builds on a regular basis and during periods of decreased database activity.Adjust your cube date range to optimize the time required to build a cube. Use the followingprocedure to build a cube:

1. From the Administrator pane in the Tivoli Discovery Administrator window,double-click Cubes.

2. Right-click on the Closed TEC Events cube, and select Build.

The Confirm Cube Build dialog box appears. The date ranges appear in the dialog box.

3. Click Yes.

TDS connects to your database and retrieves the records specified in your query. Thesize of your data and the network speed affect the time required to retrieve all records.Use the status bar to check the status of the processing.

The Cube Transform Status dialog box appears.Processing messages appear in the dialog box.

4. Review the processing messages for any errors.

If an error generates an error dialog box, review the error, and click OK.

5. Click Close.

6. Start the Tivoli Discovery Interface

7. Use the discovery guide to review the views for each topic (a topic is presented as aquestion).

For more information about how to use the Tivoli Decision Support DiscoveryInterface, see the TDS User’s Guide, and the TDS Using Decision Support Guidesdocuments described in the section Required Documentation.


Reinstalling a Discovery GuideTo reinstall a discovery guide, you must first uninstall all the discovery guides on yoursystem, and then uninstall TDS. You must now reinstall TDS and then reinstall thediscovery guides.

Operating ProceduresThe following sections describe the operating procedures for the Event Management guide.

Scheduling the Cube Build TaskYou must periodically rebuild the cube to update your cube data. The build process can bescheduled to build automatically at regular intervals (for example, schedule nightly cubebuilds). Stagger the start times for your cube builds for improved performance.

Scheduling the Cube Build TaskThe following procedure uses the Tivoli Discovery Administrator to create a cube buildingschedule and to determine the schedule TaskID. The cube build is then scheduled using theCognos Scheduler. Use the following procedure to define a cube building schedule:

1. Start the Tivoli Discovery Administrator.

2. On the Scheduled Task menu, point to Add, and click Cube Build.

The Add Schedule Wizard appears.

3. Type a name for the schedule you are creating in the Schedule Name box, andclick Next.

4. Continue to click Next until you are prompted for the date range for the schedule.

5. In the Effective from date box, type or select a date that is prior to the current date.

6. Select the To checkbox to display the ending date box.

7. In the ending date box, type or select the date that you entered in the Effective from datebox, and click Next.


8. Click Finish.

9. In the Tivoli Discovery Administrator pane, click on Scheduled Tasks.

10. In the Properties pane, right click on the scheduled task you created, and click Edit.

The Edit Schedule dialog box appears.

11. On the Task tab, record the schedule Task ID for use in Step 15.

12. Click OK.

13. On the Start menu, under Programs, choose Cognos, and click Scheduler to start theCognos Scheduler.

14. On the Insert menu, click Recurring task.

The Insert Task dialog box appears.

15. On the Identification tab, type the following command string in the File name box:

“<directory path>\edamin.exe” /TaskID=X

(where <directory path> is the installation directory path for TDS and X is the schedule Task ID from Step 11)

Note: Enclose the directory path and the edamin.exe in quotes as shown in thefollowing example: “c:\Program Files\TDS\edamin.exe” /TaskID=1

16. Type a brief description of the cube and the schedule in the Description box.

17. On the Timetable tab, specify the cube building frequency, run time, and duration.

18. Repeat this procedure for each cube.

19. Minimize Cognos Scheduler.

Note: Cognos Scheduler must be running for the cube to build at the scheduled time.


Backing Up the Archive and Trigger DataBefore dropping your database, use the following procedure to archive your database:

1. Export and archive reporting data. For example, export your data to a flat file format.

2. Drop the TEC database schema.

3. Run the script that recreates the TEC database schema.

4. Run the script that recreates the TEC Archive table and trigger.

See the section Creating the Archive Table in the TEC Database.

5. If you are using a Sybase database, run the script that creates the views.

See the section Creating Views in a Sybase TEC Database.

6. Import archived data back into the TEC Archive table

Using the Event Management GuideAfter your system administrator has built the Closed Event Management cube using theTivoli Discovery Administrator, start the Tivoli Discovery Interfaces. Select the EventManagement guide, and view a report or chart.

Specifying the Database Logon for CrystalReportsThe first time you run a Crystal Report using the Discovery Interface, you must set the datasource using the Event Management Database Logon dialog box. Specify the DSN, theQualifier, and the Database name and type for the data source you defined.


Enter the following values for the qualifier:

• For Sybase, enter tec• For Oracle, enter TEC• For DB2, enter DB2ADMIN

Note: Your database qualifier may be different. Contact the database administrator foradditional information.

TroubleshootingODBC Driver ProblemsIf you experience problems with the INTERSOLV ODBC driver version 3.01 for Sybases,contact Tivoli Customer Support, and request the updated INTERSOLV ODBC driverversion 3.01 for Sybase. For more information about this issue, please contact TivoliCustomer Support by sending an email to [email protected] or by visiting the TivoliCustomer Support web site at http://www.support.tivoli.com. Please be sure to include yourcustomer identification information.

Cube Building• In the Tivoli Discovery Administrator the following message appears: Error

building cube. If you click Details on the message dialog box, the following messageappears: Error 91 – Error getting query parameters; object variable or with blockvariable not set.

The data sources have not been assigned to the cube queries. Assign the data sources tothe queries.

• While using the Tivoli Discovery Interface, a Cognos PowerPlay report iconappears with the X symbol (a circle bisected by a diagonal line), and you cannotopen the report. What does this indicate?

This symbol indicates that the cube is unavailable. Contact your TDS administrator, andrequest that the cube be rebuilt.




• Why does the Tivoli Discovery Administrator report that a cube could not bebuilt?

The cube you are attempting to rebuild is currently in use, and TDS cannot overwritethis cube with the new cube data. Close all copies of the Tivoli Discovery Interface thatare running. Copy the <CubeName>.mdc file from the Tds\Cubes\Temp directoryto Tds\cubes directory (where Tds\ is the TDS installation directory), replacing theexisting cube.

The queries returned insufficient data to build a cube. Verify your queries.

• You closed all the Tivoli Discovery Interface processes, and the cube still does notbuild.

A copy of Cognos PowerPlay may still be running in the background. This can alsoprevent cube builds from succeeding. Open the Task manager, and look for the processpplay.exe. If you find it, end the process, and rebuild the cube.

• Your cubes do not automatically build overnight.

For scheduled cube builds to occur, the Cognos Scheduler must be running. StartCognos Scheduler. Review the schedule definitions in Cognos Scheduler and the TivoliDiscovery Administrator.

You may have to redefine the cube building schedule definitions if the followingconditions exist:

• You have defined a cube building schedule• One or more scheduled cube builds was not executed because the Cognos Scheduler

was not running

• How are relative dates calculated in a report?

The Date Range parameter for a cube determines the time period that you want toexamine. This parameter uses explicit values, a start date and end date, or a calculatedvalue (for example, the last three months and the last six months). The calculatedvalues are relative to the current date. The current period for a TDS cube is set using oneof the following methods:

• Use the Date Range parameter and the <CubeName>_dt.txt to set thecurrent period as shown in the following table:

If the Date Range parameter is

defined for a query using…

then the resulting date in the <CubeName>_dt.txt1 is the…

Explicit Date Range End Date


If the Date Range parameter is

defined for a query using…

then the resulting date in the <CubeName>_dt.txt1 is the…

Calculated Values Calculated End Date

No Date Range Parameter in the Cube Date the Cube is Built1 where <CubeName> is the name of the cube that is being built

• If you want to use the date in the <CubeName>_dt.txt as the current period, thenyou must create a new query in the cube model. This query must use the<CubeName>_dt.txt as a local data file. Also, the Set the current period optionmust be set only for this query.

• Use the Date Range parameter, but do not use the <CubeName>_dt.txt. Thisselects only records between the specific start date and end date, and sets thecurrent period to the most recent date in the data.

• Do not use either the Date Range parameter or the <CubeName>_dt.txt. Thisselects all the records, and sets the current period to the most recent date inthe data.

• Use the <CubeName>_dt.txt, but do not use the Date Range parameter. Thisselects all the records, and sets the current period to the date of the current cubebuild.

• For more information on how to set the current period and select records, see theTDS Administrator Guide document.

Report Problems• The All Closed Event report does not sort correctly when using the Tivoli Decision

Support for Event Management (DB2 Only) version of the guide.

Due to a limitation in DB2, this report must sort the host names using only the first fiftycharacters of the Hostname field. If your database contains hostnames that haveidentical characters in the first fifty positions, the records in the report may not sortproperly.

• The following error message appears: load_graph_from_powercube.

This indicates that the cube has not been built. Build the cube.


• You tried to open a report, and the Tivoli Discovery Interface gets stuck at the waitcursor.

The Tivoli Discovery Interface may have lost its connection to the Cognos PowerPlaytask. Close the Tivoli Discovery Interface and PowerPlay. Restart the Tivoli DiscoveryInterface, and your reports should open.

• You opened a report, and it contained no data.

There may be data in the report, but there is no data in drill down. The report may befiltered on a dimension. Look at the dimension bar and check if any of the values(especially the date dimension) are drilled down.

• The Crystal Reports do not have a left margin.

The type of printer attached to a workstation influences the alignment of crystal reports.Try disconnecting the printer and restarting TDS.

• You cannot open a Crystal Report using the Discovery Interface.

You may be addressing the wrong database. The first time you open a Crystal report, alogon dialog box appears. Verify that the User ID and the Password are correct. Clickthe Options button on this dialog box, and verify that you are using the correct ODBCconnection and that the connection information is correct.


Year 2000 (Y2K) ComplianceTHIS INFORMATION DOES NOT CONSTITUTE A CERTIFICATION ORWARRANTY, EXPRESS OR IMPLIED, OF ANY KIND.

Microsoft Y2K Service Packs• I installed a Microsoft service pack for Y2K, and TDS no longer works correctly?

The installation of certain service packs for Y2K can alter the system registry. Tocorrect this problem, complete the following procedure:

1. Save your customizations to TDS by making copies of the following TDSdirectories: \cubes, \data, \models, and \reports.

2. Reinstall TDS, any TDS patches, and the Microsoft ODBC Driver 2.6.5. Note,install TDS in the same directory as the previous installation.

3. After installing TDS and the patches, overwrite the new TDS data andconfiguration files with your original files by copying the directories you savedearlier into the TDS installation directory.

TEC Database• How do you ensure that the database that TDS accesses is Y2K compliant?

To help ensure that TDS continues to select data correctly after January 1, 2000, thedatabase used to store historical data must be Y2K certified. Please contact your systemadministrator and your database vendor if you have any questions concerning the Y2Kcompliance of your database.


Seagate Crystal Reports Version 6• How do you ensure that Seagate Crystal Reports is Y2K compliant?

Seagate Crystal Reports version 6 is Y2K ready if you download the required patches.Seagate Software considers a product Year 2000 ready if the product performance andfunctionality are unaffected by processing of dates prior to, during and after the Year2000, but only if all products (for example hardware, software and firmware) used withthe product properly exchange accurate date data with it.

Based on testing to date the following versions (in all available languages) of SeagateCrystal Reports, Seagate Crystal Info and Seagate Info are currently Year 2000 ready:1

Product Name and Version - All Versions, STANDARD & PRO

Seagate Crystal Reports 7 - Shipped Year 2000 Ready

Seagate Crystal Reports 62

Software Defects, Limitations,and WorkaroundsDefectsThe following is a list of some of the more important software defects. Workarounds areprovided when applicable.

• None.

1 For the compiled report option of Seagate Crystal Reports 6 to be Year 2000 ready, the appropriate versionupdate must be downloaded from the Seagate Software Website.

2 If using a native connection to Xbase (.dbf) database files, a patch must be downloaded from the SeagateSoftware Website. Please refer to the attached FAQ for more information. The official disclosure is posted onSeagate Software’s Year 2000 Readiness page at http://www.seagatesoftware.com/y2k.


LimitationsThe following is a list of known software limitations for the 3.6.1 release of TEC.Workarounds are provided when applicable.

• Manage the size of the Archive table in the TEC database. This will optimize the cubebuilding process.

• Measures on simple bar graphs appear twice – centered on the graph and over theY-axis. On low resolution monitors, the measure names may overlap.

Workaround:

The recommend minimum resolution for your monitor is 800 x 600 pixels.

WorkaroundsThe following is a list of workarounds for this release:

• <Process_Name.exe> Application Error message dialog box appears with the followingmessage: The instruction at “<memory address>” referenced memory at “<memoryaddress>”. The could not be “read”.

Workaround:

Occasionally, when the cubes are built or their queries are exported, an application errormessage appears when TDS is used in combination with the Sybase INTERSOLV IncODBC driver Version 3.01. This error message can appear frequently for a time andthen suddenly cease to appear. If you experience this problem during cube build, waituntil the transformation process has completed before clicking OK or Cancel on theerror message dialog box. By waiting, you allow the cube to finish building. After thebuild process has completed, click OK on the error message dialog box. The TivoliDiscovery Administrator will close. Start the Tivoli Discovery Administrator andcontinue building any remaining cubes.


Functional DescriptionData SourcesThe source of data for TDS for Event Management is the TEC database. As each eventreceived by the TEC is closed, it is copied to the tds_tec_t_archive table. A database triggerwill be used to copy each event as it is closed in the TEC event repository into the archivetable. The new table and trigger are created in the TEC database. This database table andtrigger do not affect the functionality of the TEC product.

The trigger also manages removing an event from the archive which has had its statuschanged from closed.

You will be adding this new table to the existing TEC database, and it will be necessary foryou to identify how much space this new table will require. The amount of space requiredby this table is based on the amount of event data you want to store in the archive table.

Event Management Database SchemaA new table is provided to hold TEC events as they are closed.

tds_tec_t_archive Table

Element Name Datatype NULLAccepted

Field Description

server_hndl integer NOT NULLdate_reception integer NOT NULLevent_hndl integer NOT NULLtime_opened datetime* NOT NULLtime_closed datetime* NOT NULLclass Varchar(64) NOT NULLsource Varchar(64) NULLsub_source Varchar(64) NULLorigin Varchar(32) NULLsub_origin Varchar(64) NULLhostname Varchar(128) NULLadapter_host Varchar(128) NULL

* For DB2 databases these elements are type “timestamp”


Element Name Datatype NULLAccepted

Field Description

status integer NULLadministrator Varchar(64) NULLseverity integer NULL

duration integer NULL

msg Varchar(255) NULL

cause_date_recptn integer NULL

cause_event_handleinteger NULL

credibility integer NULLnum_actions integer NULL repeat_count integer NULL

Event Management Database Triggers

Database Trigger for Sybase DatabasesCREATE TRIGGER tds_tec_close_triggeron tec_t_evt_repFOR UPDATE ASIF UPDATE (status)BEGINinsert into tds_tec_t_archiveselectinserted.server_hndl,inserted.date_reception,inserted.event_hndl,dateadd(second, inserted.date_reception, ’1970/01/01’),getdate(),inserted.class,inserted.source,inserted.sub_source,inserted.origin,inserted.sub_origin,inserted.hostname,inserted.adapter_host,inserted.status,inserted.administrator,inserted.severity,inserted.duration,inserted.msg,inserted.cause_date_receptn,


inserted.cause_event_handle,inserted.credibility,inserted.num_actions,inserted.repeat_countfrom inserted, deletedwhere inserted.status = 30and deleted.status != 30and inserted.server_hndl = deleted.server_hndland inserted.date_reception = deleted.date_receptionand inserted.event_hndl = deleted.event_hndldelete from tec_t_archive where exists(select * from inserted, deletedwhere inserted.status != 30and deleted.status = 30and inserted.server_hndl = deleted.server_hndland inserted.date_reception = deleted.date_receptionand inserted.event_hndl = deleted.event_hndland tec_t_archive.server_hndl = deleted.server_hndland tec_t_archive.date_reception = deleted.date_receptionand tec_t_archive.event_hndl = deleted.event_hndl)

END

Database Trigger for Oracle DatabasesCREATE OR REPLACE TRIGGER tec_close_triggerAFTER UPDATE OF statusON tec_t_evt_repFOR EACH ROWBEGIN

if :new.status = 30 and :old.status <> 30 then insert into tec_t_archive values ( :new.server_hndl, :new.date_reception, :new.event_hndl, sysdate - (:new.duration / 86400), sysdate, :new.class, :new.source, :new.sub_source, :new.origin, :new.sub_origin, :new.hostname, :new.adapter_host, :new.status, :new.administrator, :new.severity,


:new.duration, :new.msg, :new.cause_date_receptn, :new.cause_event_handle, :new.credibility, :new.num_actions, :new.repeat_count); end if; if :new.status <> 30 and :old.status = 30 then delete from tec_t_archive where tec_t_archive.server_hndl = :old.server_hndl and tec_t_archive.date_reception = :old.date_reception and tec_t_archive.event_hndl = :old.event_hndl;

end if;

END;/

Database Trigger for DB2 DatabasesLines that are different from the Oracle and Sybase Database trigger are marked in bold.

CREATE TRIGGER TEC_CLOSE_TRIGGER AFTER UPDATE OF STATUS ON TEC_T_EVT_REP

REFERENCING NEW_TABLE AS INSERTED OLD_TABLE ASDELETED FOR EACH ROW MODE DB2SQL

BEGIN ATOMIC

insert into tec_t_archive ( SELECT inserted.server_hndl, inserted.date_reception, inserted.event_hndl, (CURRENT TIMESTAMP -(INSERTED.DURATION SECONDS)), CURRENT TIMESTAMP, inserted.class, inserted.source, inserted.sub_source, inserted.origin, inserted.sub_origin, inserted.hostname, inserted.adapter_host, inserted.status, inserted.administrator, inserted.severity,


inserted.duration, inserted.msg, inserted.cause_date_receptn, inserted.cause_event_handle, inserted.credibility, inserted.num_actions, inserted.repeat_count date(CURRENT TIMESTAMP – (INSERTED.DURATION SECONDS)) from inserted, deleted

where inserted.status = 30 and deleted.status != 30 and inserted.server_hndl = deleted.server_hndl and inserted.date_reception = deleted.date_reception and inserted.event_hndl = deleted.event_hndl);

delete from tec_t_archive where exists (select t.* from inserted, deleted,tec_t_archive t where inserted.status != 30 and deleted.status = 30 and inserted.server_hndl = deleted.server_hndl and inserted.date_reception = deleted.date_reception and inserted.event_hndl = deleted.event_hndl and tec_t_archive.server_hndl = deleted.server_hndl and tec_t_archive.date_reception = deleted.date_reception and tec_t_archive.event_hndl = deleted.event_hndl);

END~


Managing the Event ManagementArchive Table

Sizing the TEC Database for the Archive TableThe existing TEC database must be sized to accommodate the new archive table used byTDS for Event Management. You must determine the average volume of events that youreceive per day, and specify the number of days you want to retain as archive data. Basedon this estimate, size your database accordingly before using this guide.

Additionally, verify that you have adequate disk space available to accommodate the .csvfiles created during the process of building the cube. The flat files (.csv) are created withthe data from the tds_tec_t_archive table when a cube build is initiated, these files are usedto build the actual cube.

Deleting Records from the Archive TableThe archive table used by TDS for Event Management needs to be purged on a periodicbasis. This manages the database resource and improves cube building performance. It isrecommended that you back up the Archive table before deleting records. Procedures areprovided for Oracle, Sybase, and DB2 databases.

Deleting Records from the Archive Table in aOracle Database1. At the DOS prompt, type the following to connect to the Oracle database server:

sqlplus tec@<tnsnames alias>

2. When prompted, enter your password.

3. At the SQL> prompt, type the following to delete the specified records from the archivetable:

SQL>delete tec_t_archive where time_closed < ‘dd-Mon-yy’;

for example, to delete all records prior to July 1,1999 enter:

SQL>delete tec_t_archive where time_closed < ‘01-JUL-99’

4. At the SQL> prompt, type the following to display that status of autocommit:

mailto:tec@tnsnames


SQL>show autocommit

The autocommit status appears. If the feature is on, you do not need to commit yourdelete because Oracle automatically commits your work.

5. If autocommit is off, at the SQL> prompt, type the following to commit the deletion ofthe archive table entries:

SQL>commit;

6. At the SQL> prompt, type the following to exit SQL:

SQL>exit;

Deleting Records from the Archive Table in aSybase Database1. At the DOS prompt, type the following to connect to the Sybase database server:

isql –Utec –Ptectec (where tectec is your password)

2. At the isql> prompt, type the following to delete the specified records from the archivetable:

isql> delete tec_t_archive where time_closed < ‘mm/dd/yy’

isql> go

isql> exit

For example, to delete all records prior to July 1, 1999 the first line would be:

isql> delete tec_t_archive where time_closed < ‘07/01/99’

Deleting Records from the Archive Table in aDB2 Database1. Open a DB2 Command Line Processor session.

2. Type the following command to connect to the DB2 database:

connect to <database name> user <userid> using <password>

3. Type the following command to delete the rows from the archive table:

delete from tec_t_archive where date_ opened < ' yyyy-mm-dd'


for example, to delete all records prior to July 1,1999 enter:

delete from tec_t_archive where date_opened < ’1999-07-01’

4. Type the following command to disconnect from the database:

terminate

Notes: The DB2 UDB Command Line Processor automatically commits all commands.This feature can be overridden using the UPDATE COMMAND OPTIONScommand. This command is documented in the DB2 UDB Command Reference.To access help while using the DB2 UDB Command Line Processor, enter aquestion mark (?) at the DB2 prompt.


Cubes (Tivoli Discovery Administrator)

Closed TEC EventsThe Closed TEC Events multidimensional cube contains information from several of theTEC database tables and the new archive table in order to provide metrics about eventresponse performance.

Queries Used to Build the Cube

The following sql queries are used to create the flat files in comma separated value (csv)format. These files are used to create the multidimensional cube.

TEC Class Hierarchy

Contains relationship information about TEC classes from the tec_t_isa table.

QUERYSELECT min({fn ifnull(T2.parent, ’EVENT’)}) as grandparent_class,min({fn ifnull(T1.parent, ’EVENT’)}) as parent,T1.child as classfrom {oj ?[DB Qualifier].tec_t_isa T1 LEFT OUTER JOIN?[DB Qualifier].tec_t_isa T2 ON T1.parent = T2.child}group by T1.child

CALCULATED COLUMNSCalculated Column Data TypePARENT_CLASS string

TEC Date Info

Contains information on when the archived event was opened within a given start andend date.

QUERYSELECT DISTINCT

{fn year(time_opened)} as year_opened, {fn month(time_opened)} as month_opened, {fn dayofmonth(time_opened)} as day_opened, 1 as num_days, 1440 as num_minutes

FROM ?[DB Qualifier].tec_t_archive T1

WHERE time_opened Between ?[Date Range].[Start Date] AND

?[Date Range].[End Date]


CALCULATED COLUMNSCalculated Column Data TypeDATE_OPENED string

TEC Historical Archive

Contains the details of each closed event.

QUERYselect {fn year(time_opened)} as year_opened, {fn month(time_opened)} as month_opened, {fn dayofmonth(time_opened)} as day_opened, {fn hour(time_opened)} as hour_opened,

T1.class,T1.source,T1.sub_source,T1.origin,T1.sub_origin,T1.hostname as event_hostname,T1.adapter_host,T1.severity as severity_value,

T2.description as severity, T1.administrator, 1 as num_events, (duration / 60) as duration, num_actions, (1 + repeat_count) as num_occurrences

from ?[DB Qualifier].tec_t_archive T1, ?[DB Qualifier].tec_t_severity T2where T1.severity = T2.codeand time_opened Between ?[Date Range].[Start Date] AND ?[Date Range].[End Date]


CALCULATED COLUMNSCalculated Column Data TypeDATE_OPENED stringIP_A_NETWORK stringIP_B_NETWORK stringIP_C_NETWORK stringHOSTNAME stringHOSTNAME_ORIGIN stringSEVERITY_WEIGHT integerWEIGHTED_DURATION integerSOURCE_SUBSOURCE stringORIGIN_SUBORIGIN stringALTERNATE_SEVERITY stringALTERNATE_CLASS stringALTERNATE_SOURCE stringDURATION_RANGE stringTIME_OR_DAY stringWEEKDAY stringWEEKDAY_NAME stringDAY_TIME_SORT integerDAY_AND_TIME stringWEEKDAY_OR_WEEKEND stringDAY_OR_NIGHT stringSLA_STATUS stringMET_SLA integerMISSED_SLA integerNEAR_MISSED_SLA integer

TEC System Info

Contains information about network addresses and hostnames for closed events.

QUERYselect distinct origin, hostname as event_hostname, 1 as num_systemsfrom ?[DB Qualifier].tec_t_archive

CALCULATED COLUMNSCalculated Column Data TypeHOSTNAME stringHOSTNAME_ORIGIN stringIP_B_NETWORK stringIP_C_NETWORK stringIP_A_NETWORK string


Parameters Used to Build CubeParameter Name Type Default ValuesDate range Range Start Date

End DateCalculated on Rolling 6 months

Alternate class Terminology 1500 TEC ClassesAlternate severity Terminology Serious Problem (Fatal, Critical)

Minor Problem (Minor, Warning)Informational(Harmless, Unknown)SourceClassification

Tec Event Sources

NETWORK NV6KHPOVSNMSNMPSPECTRUMOPENVIEW

SYSTEM SENTRYLOGFILENTAS400_ALERTAS400_MSGQOS2

HOST NV390ALTNV390MSG

INTERNAL TEC

Alternate source Terminology

TECNT AdapterSeverity Weight Terminology Fatal=100

Critical=75Minor=50Warning=25Harmless=0Unknown=0

Day or Night Categorization 1– 6 (1AM to 6AM) is Night7 – 17 (7AM to 5PM) is Day18 – 24 (6PM to 12AM) is Night

Duration range Categorization 0 less than 15 minutes15 15-30 minutes30 30-60 minutes60 1-2 hours120 2-4 hours240 4-8 hours480 8-24 hours1440 greater than 24 hours

CRITICAL SLA Categorization 30-60 minutes duration period for closeFATAL SLA Categorization 15-30 minutes duration period for closeMINOR SLA Categorization 420-480 minutes duration period for closeWARNING SLA Categorization 1320-1440 minutes duration period for close


Dimensions

The dimensions defined for the Event Management guide determine the types of questionsthat can be answered by the application.

By Date

The time dimension associated with the model.

By Date

Month Week

Day

By Day of Week

Permits categorization on Days of the Week

By Day of Week

WEEKDAY_OR_WEEKEND

WEEKDAY_NAME

DATE_OPENED


By Time of Day

Permits categorization by Day and Night and Time of Day

By Time of Day

DAY_OR_NIGHT

TIME_OF_DAY

By Day and Time

Permits Categorization by a concatenated field of date and time

By Day and Time

DAY_AND_TIME

By Entire Network

Breaks down the IP address by the 4 parts of the IP address. Hostname_origin is aconcatenation of the ip address and hostname.

By Entire Network

IP_A_NETWORK

IP_B_NETWORK

IP_C_NETWORK

ORIGIN


HOSTNAME_ORIGIN

By Hostname

Hostname comes with the event. Hostname_origin is a concatenation of the ip address andhostname.

By Hostname

HOSTNAME

HOSTNAME_ORIGIN

By Class

Classification of Events by class with determination of parent and grandparent classgenerated when cube is built.

By Class

GRANDPARENT_CLASS

PARENT_CLASS

ALTERNATE_CLASS

CLASS


By Severity

Severity of event comes with the event data.

By Severity

ALTERNATE_SEVERITY

SEVERITY

By Source

Source of the event comes with event data.

By Source

ALTERNATE_SOURCE

SOURCE

SOURCE_SUBSOURCE

By Duration

Duration time of event, calculated value.

By Duration

DURATION_RANGE


By SLA

Status of event in regard to service level agreement parameters, calculated value.

By SLA

SLA_STATUS

Measures

The measures defined for the Event Management guide determine key performanceindicators using qualitative data.

Measure Name Purpose Calculation Included

Total Number of Events Sum column Column = NUM_EVENTS yes

Events per system “Total number of events”/ “Number of systems” yes

Events per system per day “Events per system”/ ”Number of days” yes

Total event duration (minutes) Sum column Column = DURATION yes

Weighted down time (minutes) DMIN (“Weighted event duration”,

“Number of systems” * “Number of minutes”)

yes

Mean Time to Repair (minutes) Average column Column = DURATION yes

Number of times met SLA Sum column Column = MET_SLA yes

Number of times missed SLA Sum column Column = MISSED_SLA yes

Near Misses on SLA Sum column Column = NEAR_MISSED_SLA yes

Percent met SLA DPERCENT ( “ Number of times met SLA”, “Total

number of events” )

yes

Percent missed SLA DPERCENT ( “ Number of times missed SLA”,

“Total number of events” )

yes

Percent near misses DPERCENT ( “ Near misses on SLA”,

“Total number of events” )

yes

Total number of occurrences Sum column Column = NUM_OCCURRENCES yes

Number of Systems Sum column Column = NUM_SYSTEMS yes

Number of days Sum column Column = NUM_DAYS no

Number of minutes Sum column Column = NUM_MINUTES no

Weighted event duration Sum column Column = WEIGHTED_DURATION no


Check of the Allowed Measures and Dimensions Combination

The following table lists the measures of the cube and if they are in scope for thedimensions. Measures out of scope for a certain dimension produce invalid information orno data.

Table Legendy = In scope

g = Out of scope

gx = Out of scope, measure allocated to the dimension

TDS for Event Management 1.0.1Release Notes 1.1

46

Measure By Date By Day of

Week

By Time of

Day

By Day

and Time

Entire

Network

By

Hostname

By Class By

Severity

By Source By

Duration

By

SLA

Total Number of Events y y y y y y y y y y y

Events per system g g g g y y g g g g g

Events per system per day g g g g g g g g g g g

Total event duration (minutes) y y y y y y y y y y y

Weighted down time (minutes) g g g g g g g g g g g

Mean Time to Repair (minutes) y y y y y y y y y y y

Number of times met SLA y y y y y y y y y y y

Number of times missed SLA y y y y y y y y y y y

Near Misses on SLA y y y y y y y y y y y

Percent met SLA y y y y y y y y y y y

Percent missed SLA y y y y y y y y y y y

Percent near misses y y y y y y y y y y y

Total number of occurrences y y y y y y y y y y y

Number of Systems gx gx gx gx y y gx gx gx gx gx

Number of days y y gx gx gx gx gx gx gx gx gx

Number of minutes y y gx gx gx gx gx gx gx gx gx

Weighted event duration y y y y y y y y y y y


47

Topics and Views (Tivoli DiscoveryInterface)The TDS Guide for Event Management pose the following questions to be answered bydata collected from the TEC event repository.

Am I meeting expectations for resolving events?

This topic helps you assess and improve your event handling process based upon howwell you are meeting your users’ expectations.

View Title Filename Data Source

Event classes most frequently missing SLA tec_007.ppr tec_history cube

How often am I missing my SLA? tec_017.ppr tec_history cube

Could I be more effective at resolving events?

This topic helps you assess the time it takes you to close out events and make adjustmentsto improve the repair time. Since availability is a function of reducing the number ofproblems and reducing the time it takes to repair a problem, this is an importantcontributor to your overall system availability.


Events by severity and duration tec_006.ppr tec_history cube

General summary of open events tec_GenSumOpenEvts.rpt

(Oracle and Sybase)

or

tec_GenSumOpenEvts_DB

2.rpt (DB2)

Tivoli Event

Console (TEC)

Database

Which events take the longest to fix? tec_014.ppr tec_history cube


48

What are my trends?This topic helps you to spot trends in the volume of events being generated, the time ittakes to fix them and the overall impact of these events within your environment.


All closed events tec_AllClosedEvts.rpt

(Oracle and Sybase)

or

tec_AllClosedEvts_DB2.rp

t (DB2)

Tivoli Event

Console (TEC)

Database

Archived events – in date range tec_ClosedEvtsInDateRang

e.rpt (Oracle and Sybase)

or

tec_ClosedEvtsInDateRang

e_DB2.rpt (DB2)

Tivoli Event

Console (TEC)

Database

Event imapct by date and severity Tec_016.ppr tec_history cube

What types of events am I seeing?

This topic helps you analyze the most frequently occurring types of events.


Event volume by date and severity Tec_015.ppr tec_history cube

All open events – by severity Tec_AllOpenEvts.rpt

(Oracle and Sybase)

or

Tec_AllOpenEvts_DB2.rpt

(DB2)

Tivoli Event

Console (TEC)

Database

Open events – with filters Tec_OpenWithFilters.rpt

(Oracle and Sybase)

Or

Tec_OpenWithFilters_DB

2.rpt (DB2)

Tivoli Event

Console (TEC)

Database

Top 10 event classes –serious problems Tec_008.ppr tec_history cube


49

When are my peak days for event volume?

This topic will help you detect patterns in event volume that are sensitive to the day ofthe week. This is important for establishing staffing plans and shift schedules for supportpersonnel.


Average daily event volume tec_005.ppr tec_history cube

Event histogram by day tec_002.ppr tec_history cube

This week vs. last week vs. average tec_003.ppr tec_history cube

When are my peak times for event volume?

Event volume is frequently tied to the activity taking place on your systems. This activitytends to be time of day and day of week sensitive in many businesses. This topic willhelp you understand the patterns of event generation for your enterprise so that you canmake adjustments to reduce the volume and/or reduce the time it takes to fix the events.


Event histogram by day and hour tec_001.ppr tec_history cube

Event source volume by hour tec_004.ppr tec_history cube

Where are events coming from?

This topic will help you identify the systems and networks that are causing the bulk ofyour events. This can help to identify corrective actions that might prevent futureproblems.


Event rate by network address tec_026.ppr tec_history cube

Event rate by network and duration tec_025.ppr tec_history cube

Event rate by network address and source tec_024.ppr tec_history cube

Top 100 systems by serious events tec_010.ppr tec_history cube

Top 100 systems by events per system tec_009.ppr tec_history cube

Top 100 systems by weighted down-time tec_011.ppr tec_history cube


50

Related Views and RolesFilename View Title View Description Related Views Roles

Assigned

tec_007 Event classes mostfrequently missingSLA

This view ranks the different types of events that you have handledaccording to which ones have most often not been resolved within thebounds of the Service Level Agreement. Using this information youcan identify potential areas requiring additional tools and training.

tec_008

tec_OpenWithFilters

standard

tec_017 How often am Imissing my SLA?

This view gives you a quick look at how you are doing at meeting yourSLA for resolving events as well as your trends for performance in thisarea.

tec_008 standard

tec_006 Events by severity andduration

This view gives you a snapshot of the average duration (mean time torepair) for events of different severities by grouping them into rangesof repair time.

tec_017

tec_007

tec_003

standard

tec_GenSumOpenEvts

(Oracle and Sybase)

tec_GenSumOpenEvts_

DB2 (DB2)

General Summary ofOpen Events

This tabular report provides a list of events that are currently open inthe database table Event Repository. Events are grouped by date andtime starting with the most recent open event. Within the date-timegrouping records are sorted by severity and hostname.

All open events are selected for this report. This may impact theperformance of your TEC database depending on the volume of openevents in the table.

tec_AllOpenEvts

tec_OpenWithFilters

standard

tec_014 Which events take thelongest to fix?

This view gives you a snapshot of the average duration (mean time torepair) for events of different classes and highlights the ones that takethe longest to fix.

tec_007

tec_008

tec_011

standard


51

Filename View Title View Description Related Views Roles

Assigned

tec_AllClosedEvts

(Oracle and Sybase)

tec_AllClosedEvts

(DB2)

All Closed events This tabular report presents information about all recently closed TECevents grouped by severity from the Event Repository table. Theentries in this report will only reflect closed events not yet timed outbased on the Event Server parameters. Use the Archived Events reportto see all closed events in the history file.

A report parameter entry field is provided to filter events by severity.Leaving the parameter entry field blank displays all closed events forall severities. For Oracle and Sybase databases, within each severitygrouping, events are sorted by hostname, class, and source. For DB2databases, within each severity grouping, events are sorted by the first50 letters of hostname, class, source and date (the 50 letter restriction isdue to a DB2 limitation where the total length of an “Order By” clausecannot exceed 254 bytes). To minimize the impact to your databasesperformance, use the filters to limit record selection.

Entry of the severity parameter is case sensitive (i.e. to match FATALyou must type FATAL.)

tec_025.ppr

tec_006.ppr

standard

tec_ClosedEvtsInDateR

ange (Oracle and

Sybase)

tec_ClosedEvtsInDateR

ange_DB2 (DB2)

Archived Events – indate range

This tabular report provides a list of closed TEC events from thedatabase Archive table. A filter is provided to request events within aspecified date range. The report is sorted by severity, hostname, anddate event opened.

Specify either the explicit begin and end date or one of the caluclatedtime periods provided in the drop down list. Click on the icon to theleft of the entry field to toggle between filters for explict date rangeinput and calculated time periods. To minimize the impact to yourdatabases performance, use the filter to limit record selection.

tec_003.ppr standard

tec_016 Event impact by dateand severity

This view gives you a quick look at the overall trend in event impact asmeasured by the weighted down-time and also highlights any trendsbased on the severity of the events.

tec_011

tec_AllOpenEvts

standard


52


Assigned

tec_AllOpenEvts

(Oracle and Sybase)

tec_AllOpenEvts_DB2

(DB2)

All open events – byseverity

This tabular report presents information about all open TEC events inthe the Event Repository table. Events in the report are grouped byseverity and then sorted by source and hostname. A parameter entryfield is provided to filter events by severity. Leaving the parameterentry field blank displays all open events for all severities. Tominimize the impact to your databases performance, use the filter tolimit record selection.

Entry of the severity parameter is case sensitive (i.e. to match FATALyou must type FATAL.)

tec_AllClosedEvts

tec_GenSumOpenEvts

standard

tec_015 Event volume by dateand severity

This view gives you a quick look at the overall trend in event volumeand also highlights any trends based on the severity of the events.Double click on the week date and view information about each daythat week, or double click on a severity bar in the week and viewvolume of events for that severity.

tec_005

tec_AllOpenEvts

standard

tec_OpenWithFilters

(Oracle and Sybase)

tec_OpenWithFilters_D

B2 (DB2)

Open Events – withfilters

This report presents a tabular view of open events with calculated openduration from the database table Event Repository. Events are groupedby date and time starting with the most recent event received. A filteris provided so events can be selected by hostname, class, and source.To minimize the impact to your database performance, use the filters tolimit record selection.

Within each time group, events are grouped by severity.

Entry of the filter parameters is case sensitive (i.e to matchPrinter_offline you must enter Printer_offline.)

tec_AllClosedEvts

tec_GenSumOpenEvts

standard

tec_008 Top 10 event classes –serious problems

This view shows you the types of events that you are most frequentlyreceiving. It is restricted to only those events that are classified withthe fatal or critical severity.

tec_014

tec_010

standard

tec_005 Average daily eventvolume

This view gives you the average daily number of events received byday of week based on the previous 4 weeks.

tec_004

tec_015

tec_016

standard


53


Assigned

tec_002 Event histogram byday

This view shows you the event volume by day of week for the previous4 weeks.

Use the 3-D Rotate tool to realign graph for better viewing from otherangles. Right click on the graph and select Display Options.

tec_001

tec_015

tec_016

tec_ClosedEvtsInDateRange

standard

tec_003 This week vs. lastweek vs. average

This report lets you look at the day by day event volume of the last 2weeks against an average week (based on the last 4 weeks and/or thelast 13 weeks).

Use the 3-D Rotate tool to realign graph for better viewing from otherangles. Right click on the graph and select Display Options.

tec_ClosedEvtsInDateRange standard

tec_001 Event histogram byday and hour

This view lets you quickly detect patterns in the event arrival based onboth day of week and time of day. This could indicate a problem thatis triggered by some regularly scheduled activity that you were notaware of.

tec_002

tec_003

tec_009

tec_011

standard

tec_004 Event source volumeby hour

This view shows you the average number of events by event source foreach hour of the day. This average is based on the previous 30 daysworth of events. This can be helpful in establishing the shift schedulesand staffing levels for your service center or in isolating a scheduledactivity that is causing problems.

tec_005

tec_GenSumOpenEvts

standard

tec_026 Event rate by NetworkAddress

This view helps to isolate portions of the network that are having adisproportionate number of events. Double Click on the network id toexplore the subnets and reach individual nodes. The machinehostnames can be seen at the lowest level.

tec_014

tec_016

standard

tec_024 Event rate by Networkaddress and Source

This view helps you see what type of events are coming from differentlocations in your network. Double Click on the network id to explorethe subnets and reach individual nodes. The machine hostnames can beseen at the lowest level.

tec_014

tec_016

standard


54


Assigned

tec_025 Event rate by Networkand Duration

This view helps you see if events from one portion of your networkseem to take a disproportionately long time to close out.

Double Click on the network id to explore the subnets and reachindividual nodes. The machine hostnames can be seen at the lowestlevel.

tec_014

tec_016

standard

tec_010 Top 100 systems byevents per system

This view shows you the systems that are generating the most events. tec_008

tec_016

standard

tec_009 Top 100 systems bytotal number of events

This view shows you the systems that are generating the most seriousevents.

tec_001

tec_016

standard

tec_011 Top 100 systems byweighted down-time

This view shows you the systems that are having the highest weighteddown-time. Weighted down-time is the fundamental measurementused for calculating system availability (Percent up-time).

tec_001

tec_016

standard


55

Report DefinitionsFilename View Title Rank Report

Type

Period Measure Row Column Other Information

tec_007 Event classes most frequently

missing SLA

YES Explorer Rolling 30 days Total Number of

Events

Business Day By Class Filter by Severity

Rank by Severity

tec_017 How often am I missing my

SLA?

Explorer Rolling 30 days Number of times

missed SLA

By Severity Rolling 30 days

tec_006 Events by severity and duration Explorer Rolling 30 days Total Number of

Events

By Severity By Duration

tec_GenSumOpenEvt

s (Oracle and Sybase)

tec_GenSumOpenEvt

s_DB2 (DB2)

General Summary of Open

Events

CrystalReport

tec_014 Which events take the longest

to fix?

YES Explorer Rolling 30 days Mean time to repair

(minutes)

30 day

average per

class

By Event Class Rank by Class

Ascending

Filter by Alternate

Severity

tec_AllClosedEvts

(Oracle and Sybase)

tec_AllClosedEvts_D

B2 (DB2)

All Closed events CrystalReport


56

Filename View Title Rank Report

Type


tec_ClosedEvtsInDate

Range (Oracle and

Sybase)

tec_ClosedEvtsInDate

Range_DB2 (DB2)

Archived Events – in date

range

CrystalReport

tec_016 Event imapct by date and

severity

Explorer Rolling 30 daysWeighted down time

(minutes)

By Severity Rolling 30 Days

tec_015 Event volume by date and

severity

Explorer Rolling 13weeks

Total Number of

Events

By Severity Rolling 13 weeks

tec_AllOpenEvts

(Oracle and Sybase)

tec_AllOpenEvts_DB

2 (DB2)

All open events CrystalReport

tec_OpenWithFilters

(Oracle and Sybase)

tec_OpenWithFilters_

DB2 (DB2)

Open Events – with filters CrystalReport

tec_008 Top 10 event classes –serious

problems

YES Explorer Rolling 30 daysTotal Number of

Events

Serious

Problems

By Class Rank Class Top 10

Descending

tec_005 Average daily event volume Reporter By Date Total Number of

Events

Average day

over 4 weeks

By Day of the

week


57

Filename View Title Rank Report

Type


tec_002 Event histogram by day Explorer Rolling 4 weeks Total Number of

Events

rolling 4

weeks

By day of the

week

tec_003 This week vs. last week vs.

average

Reporter By Date Total Number of

Events

This week to

date / Average

over last 13

weeks

By day of the

week

tec_004 Event source volume by hour Reporter Rolling 30 days Total Number of

Events

By source By Time of day

tec_001 Event histogram by day and

hour

Explorer Rolling 4 weeks Total Number of events Rolling 4

Weeks

By day and time

tec_026 Event rate by Network Address YES Explorer Rolling 13weeks

Events per system per

day

Rolling 13weeks

Entire Network Rank Hostname

Descending

tec_025 Event rate by Network and

Duration

YES Explorer Rolling 13weeks


day

By Duration Entire Network Rank Network Address

Descending

tec_024 Event rate by Network Address

and Source

YES Explorer Rolling 13weeks


day

By Alternate

Source

Entire Network Cant Rank because of

Average

tec_010 Top 100 systems by serious

events


Events

By Serious

Problems

By Hostname Rank top 100

hostnames

tec_009 Top 100 systems by events per

system


Events

Serious

Events

By Hostname Rank top 100

hostnames

tec_011 Top 100 systems by weighted

down-time

YES Explorer Rolling 30 days Weighted down time

(minutes)

By Severity By Hostname Can’t Rank because of

Average


58

APPENDIX ADB2 Crystal Reports Filename ChangesOracle and Sybase File Name DB2 File Nametec_AllClosedEvts.rpt tec_AllClosedEvts_DB2.rpttec_AllOpenEvts.rpt tec_AllOpenEvts_DB2.rpttec_ClosedEvtsInDateRange.rpt tec_ClosedEvtsInDateRange_DB2.rpttec_GenSumOpenEvts.rpt tec_GenSumOpenEvts_DB2.rpttec_OpenWithFilters.rpt tec_OpenWithFilters_DB2.rpt

tds for event management 1.0.1 release notes

Documents