TDS for Event Management 1.0.1 Release Notes Version 1.1 July 1999

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. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products 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 Tivoli Systems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machinereadable documentation for your own use, provided that each such reproduction shall carry the Tivoli Systems copyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. The document is not intended for production and is furnished “as is” without warranty of any kind. All warranties on

this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to 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, Tivoli Management Environment, TME 10, OS/2, O/S390, and RS/6000. Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft 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/Open Company Limited. Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.

Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services 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 functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli 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. The furnishing 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 applicable documentation is copied to the Tds\Guide docs installation directory on your system.

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 ..................................................................................................... 8 For Oracle and Sybase Databases ................................................................................... 8 For DB2 Databases ........................................................................................................... 8 Setting Up an ODBC Data Source Connection..................................................................... 8 Verifying the ODBC Driver Installation........................................................................... 9 Registering the DB2 Database .................................................................................... 10 Configuring the DB2 CLI/ODBC Driver Using CCA..................................................... 11 Accessing DB2 Data Using ODBC Applications.......................................................... 11 Creating the Archive Table and Trigger in the TEC Database ........................................... 12 Creating Views in a Sybase TEC Database ....................................................................... 12

TDS for Event Management 1.0.1 Release Notes Version 1.1

i

After Installing TDS................................................................................................................. 13 Configuring the Shared Source File Path ........................................................................... 13 Installing and Importing the Event Management Guide...................................................... 14 Assigning and Verifying a Data Source .............................................................................. 16 Setting the Date Range Parameter in the Cube ................................................................. 17 Building 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............................................................................ 29 Database Trigger for Oracle Databases ............................................................................. 30 Database Trigger for DB2 Databases................................................................................. 31

TDS for Event Management 1.0.1 Release Notes Version 1.1

ii

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 ........................................ 33 Deleting Records from the Archive Table in a Sybase Database....................................... 34 Deleting 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 ......................................................................................... 36 TEC Class Hierarchy ....................................................................................................... 36 TEC Date Info.................................................................................................................. 36 TEC Historical Archive..................................................................................................... 37 TEC System Info ............................................................................................................. 38 Parameters Used to Build Cube ......................................................................................... 39 Dimensions ......................................................................................................................... 40 By Date ............................................................................................................................ 40 By Day of Week............................................................................................................... 40 By Time of Day ................................................................................................................ 41 By Day and Time ............................................................................................................. 41 By Entire Network............................................................................................................ 41 By Hostname ................................................................................................................... 42 By Class........................................................................................................................... 42 By Severity....................................................................................................................... 43 By Source ........................................................................................................................ 43 By Duration ...................................................................................................................... 43 By SLA............................................................................................................................. 44 Measures............................................................................................................................. 44 Check of the Allowed Measures and Dimensions Combination...................................... 45

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

Related Views and Roles ........................................................................................ 50 Report Definitions ................................................................................................... 55

APPENDIX A ..................................................................................................... 58 DB2 Crystal Reports Filename Changes ............................................................... 58

TDS for Event Management 1.0.1 Release Notes Version 1.1

iii

Revision History Document 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 Event Management (DB2 Only) Version 1.0.1. The guide installation option for Tivoli Decision Support for Event Management release 1.0, for use with Sybase and Oracle TEC databases, is also included on the CD-ROM. This version of the guide has not changed from the March 1999 release (1.0).

TDS for Event Management 1.0.1 Release Notes Version 1.1

iv

Preface This document describes the Tivoli Decision Support (TDS) for Event Management product. The Event Management guide is designed to augment the Tivoli Enterprise Console (TEC) product. This discovery guide lets you strategically manage your enterprise network. Where the TEC provides a powerful, rule-based event management application that integrates network, systems, database and application management, the Event Management guide provides the IT managers of the business enterprise an overview of how events are being handled. Note:

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

Who Should Read This Book This document is intended for the users of the Event Management guide and anyone responsible 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 familiar with 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

TDS for Event Management 1.0.1 Release Notes Version 1.1

v

TDS and EVM Guide Documentation To install and use the Event Management (EVM) guide, you should be familiar with the following Tivoli Decision Support publications: Document

Description Location

Tivoli Decision Support (TDS) 2.0 Readme0799.txt

Review this document before installing TDS for Event Management. It contains the latest information about the TDS product. This document also describes the features of the Tivoli Discovery Interface that are not documented in version 2.0. These features are found in the Tivoli Discovery Interface, and not in the Tivoli Discovery Administrator. The Tivoli Decision Support 2.0 User Online Help system provides detailed information and procedures for using the undocumented features. 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

TDS for Event Management Readme.txt

Provides a description of the product documentation, the initial installation instructions, and the contact information for Tivoli Customer Support. Filename on the CD-ROM: For the Sybase and Oracle version of the guide: d:\Tivoli Decision Support for 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 Event Management (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\Tivoli Decision Support for Event Management\Readme.txt For the DB2 version of the guide: TDS\Guide docs\Tivoli Decision Support for Event Management (DB2 Only)\Readme.txt

TDS for Event Management Release Notes

Provides copyright, prerequisite, installation procedures, and trouble shooting for the Event Management guide. Filename on the CD-ROM: For the Sybase and Oracle version of the guide: d:\Tivoli Decision Support for 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 Event Management (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\Tivoli Decision Support for Event Management\Tds_EVM_Rel_Notes.pdf For the DB2 version of the guide: TDS\Guide docs\Tivoli Decision Support for Event Management (DB2 Only)\Tds_EVM_Rel_Notes.pdf

TDS for Event Management 1.0.1 Release Notes Version 1.1

vi

Document

Description Location

Using Decision Support Guides Installation Guide

Provides an overview of the TDS Guides, cube dimensions and measures, and detailed procedures for using the Tivoli Decision Support discovery guides. Filename on your system: TDS\Docs\Pdf\dg.pdf Provides installation procedures for TDS and its components in stand-alone and network mode. Filename on your system: TDS\Docs\Pdf\install.pdf

Decision Support User’s Guide Administrator Guide

Describes TDS features, concepts, and provides procedures for using the Tivoli Discovery Interface. Filename on your system: TDS\Docs\Pdf\user-gd.pdf Explains the features of the Tivoli Discovery Administrator. Filename on your system: TDS\Docs\Pdf\admin-gd.pdf

Other Guides

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

TDS for Event Management 1.0.1 Release Notes Version 1.1

vii

Contacting Customer Support To contact Tivoli Customer Support: Note: Whenever contacting Tivoli Customer Support, please have your customer identification 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 many customer support services on the World Wide Web. Refer to the Customer Support Handbook for a listing of Tivoli Customer Support services, hours of operation, and contact 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 at http://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 with Tivoli products, documentation, and services. We welcome your suggestions for improvements. If you have comments or suggestions about our documentation, please send e-mail to [email protected].

TDS for Event Management 1.0.1 Release Notes Version 1.1

viii

Introduction Important: The Tivoli Decision Support for Event Management (DB2 Only) guide release 1.0.1 supports TEC databases running on DB2. The guide installation option for Tivoli Decision Support for Event Management release 1.0, for use with Sybase and Oracle TEC databases, is also included on the CD-ROM. This version of the guide has not changed from the March 1999 release (1.0).

Product Summary Tivoli Decision Support for Event Management (Event Management guide), version 1.0, provides a strategic view of network activity as recorded in TEC events and information about the response time for these events. Two versions of the Event Management guide are supplied on the 1.0.1 release CD-ROM: Title

Guide Version Number

Tivoli Decision Support for Event Management

1.0

Tivoli Decision Support for Event Management (DB2 Only)

1.0.1

Databases Supported Sybase Oracle DB2

TDS for Event Management version 1.0 supports Sybase or Oracle versions of the TEC database. TDS for Event Management version 1.0.1 supports DB2 versions of the TEC database. The following modifications were made to the Tivoli Decision Support for Event Management 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 recurring patterns of system activity. The combination of the Tivoli Discovery Administrator and the Tivoli Discovery Interface with Tivoli Decision Support for Event Management provides you with the following powerful analysis and reporting capabilities:

TDS for Event Management 1.0.1 Release Notes Version 1.1

1

• • •

Gathers and reviews information based on a set of powerful questions and reports that address 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 TEC events that have been archived from the TEC database event repository. A new archive table and trigger for the TEC database are provided with this discovery guide so that as each TEC 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 Databases The Event Management guide supports the following databases: • • •

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

TDS for Event Management 1.0.1 Release Notes Version 1.1

2

Installation Overview The following table lists the sequence of activities required to install the Event Management guide. The shaded activities are only performed if your are first installing TDS on your system. 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 2. Set up an Oracle, Sybase, or DB2 client 3. Size the TEC database

Requirements Setting Up an Oracle, Sybase, or DB2 Client Sizing the TEC Database for the Archive Table See the TDS Installation Guide document described in the section TDS and EVM Guide Documentation.

4. Install TDS 5. 6. 7. 8.

Install Cognos Install the ODBC drivers Set Up an ODBC data source connection Create the SQL table, trigger, and views

9. 10. 11. 12. 13. 14.

Configure the shared source file path Install the discovery guide Import the discovery guide Assign the ODBC data source Test the connectivity with the data source Set the date range parameter in the cube

15. Build the cube 16. Schedule the cube build task

TDS for Event Management 1.0.1 Release Notes Version 1.1

Setting Up an ODBC Data Source Creating the Archive Table and Trigger in the TEC Database Creating Views in a Sybase TEC Database Configuring the Shared Source File Path Installing and Importing the Event Management Guide Assigning and Verifying a Data Source Setting the Date Range Parameter in the Cube Building the Cubes Scheduling the Cube Build Task

3

Requirements This section lists the products that are prerequisites for the Event Management guide. Refer to the appropriate product documentation for installation procedures.

General The 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

TDS for Event Management 1.0.1 Release Notes Version 1.1

4

ODBC Drivers The Event Manager guide uses ODBC Drivers to communicate with the TEC database, no RIM support is required. DB2 users need to use the IBM DB2 ODBC drivers that is automatically installed with the DB2 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 following ODBC drivers are provided on the TDS 2.0 CD-ROM. Database Type Sybase

Oracle

Note:

• •

Database Version ODBC Version 10.X all tier 1

Database Version ODBC Version 11.0.1.X all tier 1

Database Version ODBC Version 11.0.3.X all tier 1

INTERSOLV 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 tier1

Microsoft ODBC Driver for Oracle 2.00.006325

Microsoft ODBC Driver for Oracle 2.00.006325

Microsoft ODBC for Oracle 2.573.292700

Microsoft ODBC for Oracle 2.573.292700

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

The Microsoft Access ODBC driver must be installed on your system before you can use an ED Drill Through data source with Seagate Crystal Reports. Installation of Microsoft Access is also recommended though not required.

TDS for Event Management 1.0.1 Release Notes Version 1.1

5

Oracle and Sybase Important: 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.1 release of the Event Management guide was the addition of a DB2 version of the 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)

DB2 Note:

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 Enablers CD-ROM or can be downloaded from the Web page at http://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 downloaded from the Tivoli Software Fixes Web Page: http://w3.support.tivoli.com/patches/ ) • •

361-TMF-0002 361-TMF-0032

TDS for Event Management 1.0.1 Release Notes Version 1.1

6

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

Installing the Event Management Guide Before using the Event Management guide, complete the installation procedures described in the following sections.

Preparing to Work with the TEC Database Use the following procedures to create the network identification required by Sybase or Oracle 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 system must have a valid client configuration for the ODBC connection that TDS uses to access your database.

Preparing the TEC Database Install the appropriate database client before setting up the ODBC data source. The procedure for setting up the ODBC data source is described in the next section.

TDS for Event Management 1.0.1 Release Notes Version 1.1

7

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 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. Click on Install Microsoft 32-bit ODBC 4. Follow the prompts and install appropriate drivers for your database platform.

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

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 the procedure described in the section Registering the DB2 Database. During the database client configuration, you will need to create a database alias (Oracle) or a server entry (Sybase) for the TEC database. Specify this alias or entry in Step 7 of the following procedure. Note:

Contact your system administrator for specific information concerning how to set up your database client.

TDS for Event Management 1.0.1 Release Notes Version 1.1

8

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 data source 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 Database Name text box.

Verifying the ODBC Driver Installation Verify that the Microsoft ODBC Driver Manager, which is accessed through the Control Panel, and the DB2 CLI/ODBC driver are installed. On Windows 95 and Windows NT they are both installed with DB2 unless the ODBC component is manually unselected during the install. To verify that they both exist on the machine: 1. Run the Microsoft ODBC Administrator from the icon in the Control Panel, or issue the appropriate 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 not installed, then rerun the DB2 install and select the ODBC component in Windows 95 or Windows NT.

TDS for Event Management 1.0.1 Release Notes Version 1.1

9

Registering the DB2 Database Register the DB2 database with the ODBC driver manager as a data source. On Windows 95 and Windows NT you can make the data source available to all users of the system (a system data source), or only the current user (a user data source). You can use any of these methods to add the data source but using the Client Configuration Assistant (CCA) is the easiest: 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 data source as either a user or system data source. 2. Using the Microsoft 32bit ODBC Administration tool, which you can access from the icon 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. If you want to add a system data source click on the System DSN button, or the System 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 the command line processor to register the DB2 database with the ODBC driver manager as a datasource. An administrator could create a command line processor script to register the required databases. This script could then be run on all of the machines that require access to the DB2 databases through ODBC. See the CATALOG [ user | system ] ODBC DATA SOURCE command in the Command Reference for more information.

TDS for Event Management 1.0.1 Release Notes Version 1.1

10

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 the window that opens. These keywords are associated with the database alias name, and affect all DB2 CLI/ODBC applications that access the database. The online help explains all of the keywords, as does Configuration Keywords. For information on manually 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 data using ODBC applications. Start the ODBC application and go to the Open window. Select the ODBC databases file type. The DB2 databases that you added as ODBC data sources will be selectable from the list. Many ODBC applications will open the table as read-only unless a unique index exists. To test an ODBC connection, refer to this manual’s section on Assigning and Verifying a Data Source under After Installing TDS.

TDS for Event Management 1.0.1 Release Notes Version 1.1

11

Creating the Archive Table and Trigger in the TEC Database Before creating the Archive table and trigger, read the section Sizing the TEC Database for the Archive Table, and make sure that your database is sized correctly to accommodate the increased volume of data. Complete the following procedure to create the Archive table and the trigger for Sybase and Oracle databases. Your database name, user, and password may be different from those shown in the following examples. Contact your system administrator for additional information. •

For Oracle, enter the following: sqlplus tec@ @ tds_tec_t_archive.ora.sql OR plus33.exe tec@ @ 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 views allow Crystal Reports to access data from the lowercase TEC table names in a Sybase database. •

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

TDS for Event Management 1.0.1 Release Notes Version 1.1

12

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

Configuring the Shared Source File Path Before using the Tivoli Discovery Administrator or the Tivoli Discovery Interface, they must 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 installation option, your source files are on your system. For other installations, the source files usually reside on a network server. Specify the path to the source files when you start the Tivoli Discovery 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, if appropriate) that contains the following folders: • • •

Cubes Data Reports

3. Click OK.

TDS for Event Management 1.0.1 Release Notes Version 1.1

13

Installing and Importing the Event 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-ROM drive 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 CDROM 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

-ORIf 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 the following directory: Tds\Guide docs\Tivoli Decision Support for Event Management

For the DB2 installation, the online documentation is installed in the following directory: 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.

TDS for Event Management 1.0.1 Release Notes Version 1.1

14

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

4. Start the Tivoli Discovery Administrator. 5. On the Decision Support Guides menu, click Import. -ORIf a discovery guide has not been installed on your system, you are prompted to import an installed discovery guide, and to connect to a data source. Note: For a step-by-step procedure, see Running the Tivoli Discovery Administrator for the First Time in the Administrator Guide document. a. A dialog box appears prompting you to import and to install the decision support guide, 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 administrator for additional information. 6. Select Event Management on the Import Decision Support Guides dialog box, and click OK.

TDS for Event Management 1.0.1 Release Notes Version 1.1

15

Assigning and Verifying a Data Source Use the following procedure to assign and verify a data source for the Event Management guide: 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: • • • • 5.

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

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 message Error connecting to Data Source – DataSourceName, click Details to display more information 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 the message Connection Successful. Click OK.

TDS for Event Management 1.0.1 Release Notes Version 1.1

16

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 the query. 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 following procedure 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. The size 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 a question). For more information about how to use the Tivoli Decision Support Discovery Interface, see the TDS User’s Guide, and the TDS Using Decision Support Guides documents described in the section Required Documentation.

TDS for Event Management 1.0.1 Release Notes Version 1.1

17

Reinstalling a Discovery Guide To reinstall a discovery guide, you must first uninstall all the discovery guides on your system, and then uninstall TDS. You must now reinstall TDS and then reinstall the discovery guides.

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

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

Scheduling the Cube Build Task The following procedure uses the Tivoli Discovery Administrator to create a cube building schedule and to determine the schedule TaskID. The cube build is then scheduled using the Cognos 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, and click 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 date box, and click Next.

TDS for Event Management 1.0.1 Release Notes Version 1.1

18

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 the Cognos 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: “\edamin.exe” /TaskID=X (where 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 the following 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.

TDS for Event Management 1.0.1 Release Notes Version 1.1

19

Backing Up the Archive and Trigger Data Before 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 Guide After your system administrator has built the Closed Event Management cube using the Tivoli Discovery Administrator, start the Tivoli Discovery Interfaces. Select the Event Management guide, and view a report or chart.

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

TDS for Event Management 1.0.1 Release Notes Version 1.1

20

Enter the following values for the qualifier: • • • Note:

For Sybase, enter tec For Oracle, enter TEC For DB2, enter DB2ADMIN Your database qualifier may be different. Contact the database administrator for additional information.

Troubleshooting ODBC Driver Problems If you experience problems with the INTERSOLV ODBC driver version 3.01 for Sybases, contact Tivoli Customer Support, and request the updated INTERSOLV ODBC driver version 3.01 for Sybase. For more information about this issue, please contact Tivoli Customer Support by sending an email to [email protected] or by visiting the Tivoli Customer Support web site at http://www.support.tivoli.com. Please be sure to include your customer 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 message appears: Error 91 – Error getting query parameters; object variable or with block variable not set. The data sources have not been assigned to the cube queries. Assign the data sources to the queries.

•

While using the Tivoli Discovery Interface, a Cognos PowerPlay report icon appears with the X symbol (a circle bisected by a diagonal line), and you cannot open the report. What does this indicate? This symbol indicates that the cube is unavailable. Contact your TDS administrator, and request that the cube be rebuilt.

TDS for Event Management 1.0.1 Release Notes Version 1.1

21

•

Why does the Tivoli Discovery Administrator report that a cube could not be built? The cube you are attempting to rebuild is currently in use, and TDS cannot overwrite this cube with the new cube data. Close all copies of the Tivoli Discovery Interface that are running. Copy the .mdc file from the Tds\Cubes\Temp directory to Tds\cubes directory (where Tds\ is the TDS installation directory), replacing the existing 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 not build. A copy of Cognos PowerPlay may still be running in the background. This can also prevent cube builds from succeeding. Open the Task manager, and look for the process pplay.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. Start Cognos Scheduler. Review the schedule definitions in Cognos Scheduler and the Tivoli Discovery Administrator. You may have to redefine the cube building schedule definitions if the following conditions 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 to examine. This parameter uses explicit values, a start date and end date, or a calculated value (for example, the last three months and the last six months). The calculated values are relative to the current date. The current period for a TDS cube is set using one of the following methods: •

Use the Date Range parameter and the _dt.txt to set the current period as shown in the following table: If the Date Range parameter is

then the resulting date in the _dt.txt1 is the…

defined for a query using… Explicit Date Range

TDS for Event Management 1.0.1 Release Notes Version 1.1

End Date

22

If the Date Range parameter is

then the resulting date in the _dt.txt1 is the…

defined for a query using… Calculated Values

Calculated End Date

No Date Range Parameter in the Cube

Date the Cube is Built

1

where is the name of the cube that is being built

•

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

•

Use the Date Range parameter, but do not use the _dt.txt. This selects only records between the specific start date and end date, and sets the current period to the most recent date in the data.

•

Do not use either the Date Range parameter or the _dt.txt. This selects all the records, and sets the current period to the most recent date in the data.

•

Use the _dt.txt, but do not use the Date Range parameter. This selects all the records, and sets the current period to the date of the current cube build.

•

For more information on how to set the current period and select records, see the TDS 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 fifty characters of the Hostname field. If your database contains hostnames that have identical characters in the first fifty positions, the records in the report may not sort properly.

•

The following error message appears: load_graph_from_powercube. This indicates that the cube has not been built. Build the cube.

TDS for Event Management 1.0.1 Release Notes Version 1.1

23

•

You tried to open a report, and the Tivoli Discovery Interface gets stuck at the wait cursor. The Tivoli Discovery Interface may have lost its connection to the Cognos PowerPlay task. Close the Tivoli Discovery Interface and PowerPlay. Restart the Tivoli Discovery Interface, 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 be filtered 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, a logon dialog box appears. Verify that the User ID and the Password are correct. Click the Options button on this dialog box, and verify that you are using the correct ODBC connection and that the connection information is correct.

TDS for Event Management 1.0.1 Release Notes Version 1.1

24

Year 2000 (Y2K) Compliance THIS INFORMATION DOES NOT CONSTITUTE A CERTIFICATION OR WARRANTY, 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. To correct this problem, complete the following procedure: 1. Save your customizations to TDS by making copies of the following TDS directories: \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 and configuration files with your original files by copying the directories you saved earlier 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, the database used to store historical data must be Y2K certified. Please contact your system administrator and your database vendor if you have any questions concerning the Y2K compliance of your database.

TDS for Event Management 1.0.1 Release Notes Version 1.1

25

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 and functionality are unaffected by processing of dates prior to, during and after the Year 2000, but only if all products (for example hardware, software and firmware) used with the product properly exchange accurate date data with it. Based on testing to date the following versions (in all available languages) of Seagate Crystal 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 Workarounds Defects The following is a list of some of the more important software defects. Workarounds are provided when applicable.

•

None.

1

For the compiled report option of Seagate Crystal Reports 6 to be Year 2000 ready, the appropriate version update 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 Seagate Software Website. Please refer to the attached FAQ for more information. The official disclosure is posted on Seagate Software’s Year 2000 Readiness page at http://www.seagatesoftware.com/y2k.

TDS for Event Management 1.0.1 Release Notes Version 1.1

26

Limitations The 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 cube building process. Measures on simple bar graphs appear twice – centered on the graph and over the Y-axis. On low resolution monitors, the measure names may overlap. Workaround: The recommend minimum resolution for your monitor is 800 x 600 pixels.

Workarounds The following is a list of workarounds for this release:

•

Application Error message dialog box appears with the following message: The instruction at “” referenced memory at “”. The could not be “read”. Workaround: Occasionally, when the cubes are built or their queries are exported, an application error message appears when TDS is used in combination with the Sybase INTERSOLV Inc ODBC driver Version 3.01. This error message can appear frequently for a time and then suddenly cease to appear. If you experience this problem during cube build, wait until the transformation process has completed before clicking OK or Cancel on the error message dialog box. By waiting, you allow the cube to finish building. After the build process has completed, click OK on the error message dialog box. The Tivoli Discovery Administrator will close. Start the Tivoli Discovery Administrator and continue building any remaining cubes.

TDS for Event Management 1.0.1 Release Notes Version 1.1

27

Functional Description Data Sources The source of data for TDS for Event Management is the TEC database. As each event received by the TEC is closed, it is copied to the tds_tec_t_archive table. A database trigger will be used to copy each event as it is closed in the TEC event repository into the archive table. The new table and trigger are created in the TEC database. This database table and trigger do not affect the functionality of the TEC product. The trigger also manages removing an event from the archive which has had its status changed from closed. You will be adding this new table to the existing TEC database, and it will be necessary for you to identify how much space this new table will require. The amount of space required by this table is based on the amount of event data you want to store in the archive table.

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

tds_tec_t_archive Table Element Name

Datatype

server_hndl date_reception event_hndl time_opened time_closed class source sub_source origin sub_origin hostname adapter_host

integer integer integer datetime* datetime* Varchar(64) Varchar(64) Varchar(64) Varchar(32) Varchar(64) Varchar(128) Varchar(128)

*

NULL Accepted NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NULL NULL NULL NULL NULL NULL

Field Description

For DB2 databases these elements are type “timestamp”

TDS for Event Management 1.0.1 Release Notes Version 1.1

28

Element Name status administrator severity duration msg cause_date_recptn cause_event_handle credibility num_actions repeat_count

Datatype integer Varchar(64) integer

NULL Accepted NULL NULL NULL

integer

NULL

Varchar(255)

NULL

integer integer

NULL NULL

integer integer integer

NULL NULL NULL

Field Description

Event Management Database Triggers Database Trigger for Sybase Databases CREATE TRIGGER tds_tec_close_trigger on tec_t_evt_rep FOR UPDATE AS IF UPDATE (status) BEGIN insert into tds_tec_t_archive select inserted.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, TDS for Event Management 1.0.1 Release Notes Version 1.1

29

inserted.cause_event_handle, inserted.credibility, inserted.num_actions, inserted.repeat_count 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 * 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 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

Database Trigger for Oracle Databases CREATE OR REPLACE TRIGGER tec_close_trigger AFTER UPDATE OF status ON tec_t_evt_rep FOR EACH ROW BEGIN 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,

TDS for Event Management 1.0.1 Release Notes Version 1.1

30

: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 Databases Lines 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 AS DELETED 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, TDS for Event Management 1.0.1 Release Notes Version 1.1

31

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~

TDS for Event Management 1.0.1 Release Notes Version 1.1

32

Managing the Event Management Archive Table Sizing the TEC Database for the Archive Table The existing TEC database must be sized to accommodate the new archive table used by TDS for Event Management. You must determine the average volume of events that you receive per day, and specify the number of days you want to retain as archive data. Based on this estimate, size your database accordingly before using this guide. Additionally, verify that you have adequate disk space available to accommodate the .csv files created during the process of building the cube. The flat files (.csv) are created with the data from the tds_tec_t_archive table when a cube build is initiated, these files are used to build the actual cube.

Deleting Records from the Archive Table The archive table used by TDS for Event Management needs to be purged on a periodic basis. This manages the database resource and improves cube building performance. It is recommended that you back up the Archive table before deleting records. Procedures are provided for Oracle, Sybase, and DB2 databases.

Deleting Records from the Archive Table in a Oracle Database 1. At the DOS prompt, type the following to connect to the Oracle database server: sqlplus tec@

2. When prompted, enter your password. 3. At the SQL> prompt, type the following to delete the specified records from the archive table: 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:

TDS for Event Management 1.0.1 Release Notes Version 1.1

33

SQL>show autocommit

The autocommit status appears. If the feature is on, you do not need to commit your delete because Oracle automatically commits your work. 5. If autocommit is off, at the SQL> prompt, type the following to commit the deletion of the 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 a Sybase Database 1. 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 archive table: 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 a DB2 Database 1. Open a DB2 Command Line Processor session. 2. Type the following command to connect to the DB2 database: connect to user using

3. Type the following command to delete the rows from the archive table: delete from tec_t_archive where date_opened < 'yyyy-mm-dd'

TDS for Event Management 1.0.1 Release Notes Version 1.1

34

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 OPTIONS command. This command is documented in the DB2 UDB Command Reference. To access help while using the DB2 UDB Command Line Processor, enter a question mark (?) at the DB2 prompt.

TDS for Event Management 1.0.1 Release Notes Version 1.1

35

Cubes (Tivoli Discovery Administrator) Closed TEC Events The Closed TEC Events multidimensional cube contains information from several of the TEC database tables and the new archive table in order to provide metrics about event response 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. QUERY SELECT min({fn ifnull(T2.parent, ’EVENT’)}) as grandparent_class, min({fn ifnull(T1.parent, ’EVENT’)}) as parent, T1.child as class from {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 COLUMNS Calculated Column PARENT_CLASS

Data Type string

TEC Date Info Contains information on when the archived event was opened within a given start and end date. QUERY SELECT 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]

TDS for Event Management 1.0.1 Release Notes Version 1.1

36

CALCULATED COLUMNS Calculated Column DATE_OPENED

Data Type string

TEC Historical Archive Contains the details of each closed event. QUERY select {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 T2 where T1.severity = T2.code and time_opened Between ?[Date Range].[Start Date] AND ?[Date Range].[End Date]

TDS for Event Management 1.0.1 Release Notes Version 1.1

37

CALCULATED COLUMNS Calculated Column DATE_OPENED IP_A_NETWORK IP_B_NETWORK IP_C_NETWORK HOSTNAME HOSTNAME_ORIGIN SEVERITY_WEIGHT WEIGHTED_DURATION SOURCE_SUBSOURCE ORIGIN_SUBORIGIN ALTERNATE_SEVERITY ALTERNATE_CLASS ALTERNATE_SOURCE DURATION_RANGE TIME_OR_DAY WEEKDAY WEEKDAY_NAME DAY_TIME_SORT DAY_AND_TIME WEEKDAY_OR_WEEKEND DAY_OR_NIGHT SLA_STATUS MET_SLA MISSED_SLA NEAR_MISSED_SLA

Data Type string string string string string string integer integer string string string string string string string string string integer string string string string integer integer integer

TEC System Info Contains information about network addresses and hostnames for closed events. QUERY select distinct origin, hostname as event_hostname, 1 as num_systems from ?[DB Qualifier].tec_t_archive CALCULATED COLUMNS Calculated Column HOSTNAME HOSTNAME_ORIGIN IP_B_NETWORK IP_C_NETWORK IP_A_NETWORK

TDS for Event Management 1.0.1 Release Notes Version 1.1

Data Type string string string string string

38

Parameters Used to Build Cube Parameter Name Date range

Type Range

Alternate class Alternate severity

Terminology Terminology

Alternate source

Terminology

Severity Weight

Terminology

Day or Night

Categorization

Duration range

Categorization

CRITICAL SLA FATAL SLA MINOR SLA WARNING SLA

Categorization Categorization Categorization Categorization

TDS for Event Management 1.0.1 Release Notes Version 1.1

Default Values Start Date End Date Calculated on Rolling 6 months 1500 TEC Classes Serious Problem (Fatal, Critical) Minor Problem (Minor, Warning) Informational(Harmless, Unknown) Source Tec Event Sources Classification NV6K NETWORK HPOV SNM SNMP SPECTRUM OPENVIEW SENTRY SYSTEM LOGFILE NT AS400_ALERT AS400_MSGQ OS2 NV390ALT HOST NV390MSG TEC INTERNAL TECNT Adapter Fatal=100 Critical=75 Minor=50 Warning=25 Harmless=0 Unknown=0 1– 6 (1AM to 6AM) is Night 7 – 17 (7AM to 5PM) is Day 18 – 24 (6PM to 12AM) is Night 0 less than 15 minutes 15 15-30 minutes 30 30-60 minutes 60 1-2 hours 120 2-4 hours 240 4-8 hours 480 8-24 hours 1440 greater than 24 hours 30-60 minutes duration period for close 15-30 minutes duration period for close 420-480 minutes duration period for close 1320-1440 minutes duration period for close

39

Dimensions The dimensions defined for the Event Management guide determine the types of questions that 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

TDS for Event Management 1.0.1 Release Notes Version 1.1

40

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 a concatenation of the ip address and hostname. By Entire Network IP_A_NETWORK IP_B_NETWORK IP_C_NETWORK ORIGIN

TDS for Event Management 1.0.1 Release Notes Version 1.1

41

HOSTNAME_ORIGIN

By Hostname Hostname comes with the event. Hostname_origin is a concatenation of the ip address and hostname. By Hostname HOSTNAME HOSTNAME_ORIGIN

By Class Classification of Events by class with determination of parent and grandparent class generated when cube is built. By Class GRANDPARENT_CLASS

ALTERNATE_CLASS

PARENT_CLASS CLASS

TDS for Event Management 1.0.1 Release Notes Version 1.1

42

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

TDS for Event Management 1.0.1 Release Notes Version 1.1

43

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 performance indicators using qualitative data. Measure Name Total Number of Events

Purpose

Included

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

Column = DURATION

yes

DMIN (“Weighted event duration”,

yes

Total event duration (minutes)

Sum column

Calculation

Sum column

Weighted down time (minutes)

“Number of systems” * “Number of minutes”) 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

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

yes

Percent met SLA

number of events” ) Percent missed SLA

DPERCENT ( “ Number of times missed SLA”,

yes

“Total number of events” ) Percent near misses

DPERCENT ( “ Near misses on SLA”,

yes

“Total number of events” ) 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

TDS for Event Management 1.0.1 Release Notes Version 1.1

44

Check of the Allowed Measures and Dimensions Combination The following table lists the measures of the cube and if they are in scope for the dimensions. Measures out of scope for a certain dimension produce invalid information or no data. Table Legend y = In scope g = Out of scope gx = Out of scope, measure allocated to the dimension

TDS for Event Management 1.0.1 Release Notes Version 1.1

45

Measure

Total Number of Events Events per system Events per system per day Total event duration (minutes) Weighted down time (minutes) Mean Time to Repair (minutes) Number of times met SLA Number of times missed SLA Near Misses on SLA Percent met SLA Percent missed SLA Percent near misses Total number of occurrences Number of Systems Number of days Number of minutes Weighted event duration

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

y

y

y

y

y

y

y

y

y

y

y

g

g

g

g

y

y

g

g

g

g

g

g

g

g

g

g

g

g

g

g

g

g

y

y

y

y

y

y

y

y

y

y

y

g

g

g

g

g

g

g

g

g

g

g

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

y

gx

gx

gx

gx

y

y

gx

gx

gx

gx

gx

y

y

gx

gx

gx

gx

gx

gx

gx

gx

gx

y

y

gx

gx

gx

gx

gx

gx

gx

gx

gx

y

y

y

y

y

y

y

y

y

y

y

TDS for Event Management 1.0.1 Release Notes 1.1

46

Topics and Views (Tivoli Discovery Interface) The TDS Guide for Event Management pose the following questions to be answered by data 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 how well 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 adjustments to improve the repair time. Since availability is a function of reducing the number of problems and reducing the time it takes to repair a problem, this is an important contributor to your overall system availability. View Title

Filename

Data Source

Events by severity and duration

tec_006.ppr

tec_history cube

General summary of open events

tec_GenSumOpenEvts.rpt

Tivoli Event

(Oracle and Sybase)

Console (TEC) Database

or tec_GenSumOpenEvts_DB 2.rpt (DB2) Which events take the longest to fix?

TDS for Event Management 1.0.1 Release Notes 1.1

tec_014.ppr

tec_history cube

47

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

Filename

Data Source

All closed events

tec_AllClosedEvts.rpt

Tivoli Event

(Oracle and Sybase)

Console (TEC) Database

or tec_AllClosedEvts_DB2.rp t (DB2) Archived events – in date range

tec_ClosedEvtsInDateRang

Tivoli Event

e.rpt (Oracle and Sybase)

Console (TEC) Database

or tec_ClosedEvtsInDateRang e_DB2.rpt (DB2) 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. View Title

Filename

Data Source

Event volume by date and severity

Tec_015.ppr

tec_history cube

All open events – by severity

Tec_AllOpenEvts.rpt

Tivoli Event

(Oracle and Sybase)

Console (TEC)

or

Database

Tec_AllOpenEvts_DB2.rpt (DB2) Open events – with filters

Tec_OpenWithFilters.rpt

Tivoli Event

(Oracle and Sybase)

Console (TEC) Database

Or Tec_OpenWithFilters_DB 2.rpt (DB2) Top 10 event classes –serious problems

TDS for Event Management 1.0.1 Release Notes 1.1

Tec_008.ppr

tec_history cube

48

When are my peak days for event volume? This topic will help you detect patterns in event volume that are sensitive to the day of the week. This is important for establishing staffing plans and shift schedules for support personnel. View Title

Filename

Data Source

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 activity tends to be time of day and day of week sensitive in many businesses. This topic will help you understand the patterns of event generation for your enterprise so that you can make adjustments to reduce the volume and/or reduce the time it takes to fix the events. View Title

Filename

Data Source

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 of your events. This can help to identify corrective actions that might prevent future problems. View Title

Filename

Data Source

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

TDS for Event Management 1.0.1 Release Notes 1.1

49

Related Views and Roles Filename

View Title

View Description

Related Views

Roles Assigned

tec_007

tec_017

tec_006

This view ranks the different types of events that you have handled according to which ones have most often not been resolved within the bounds of the Service Level Agreement. Using this information you can identify potential areas requiring additional tools and training. How often am I This view gives you a quick look at how you are doing at meeting your missing my SLA? SLA for resolving events as well as your trends for performance in this area. Events by severity and This view gives you a snapshot of the average duration (mean time to duration repair) for events of different severities by grouping them into ranges of repair time. Event classes most frequently missing SLA

tec_008

standard

tec_OpenWithFilters tec_008

standard

tec_017

standard

tec_007 tec_003

tec_GenSumOpenEvts General Summary of Open Events (Oracle and Sybase) tec_GenSumOpenEvts_ DB2 (DB2) tec_014

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

tec_AllOpenEvts tec_OpenWithFilters

All open events are selected for this report. This may impact the performance of your TEC database depending on the volume of open events in the table. Which events take the This view gives you a snapshot of the average duration (mean time to tec_007 longest to fix? repair) for events of different classes and highlights the ones that take tec_008 the longest to fix. tec_011

TDS for Event Management 1.0.1 Release Notes 1.1

standard

standard

50

Filename

View Title

View Description

Related Views

Roles Assigned

tec_AllClosedEvts

All Closed events

(Oracle and Sybase) tec_AllClosedEvts (DB2)

This tabular report presents information about all recently closed TEC tec_025.ppr events grouped by severity from the Event Repository table. The entries in this report will only reflect closed events not yet timed out tec_006.ppr based on the Event Server parameters. Use the Archived Events report to see all closed events in the history file.

standard

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

Entry of the severity parameter is case sensitive (i.e. to match FATAL you must type FATAL.) Archived Events – in This tabular report provides a list of closed TEC events from the tec_ClosedEvtsInDateR tec_003.ppr date range database Archive table. A filter is provided to request events within a ange (Oracle and specified date range. The report is sorted by severity, hostname, and date event opened. Sybase) tec_ClosedEvtsInDateR ange_DB2 (DB2)

tec_016

Event impact by date and severity

TDS for Event Management 1.0.1 Release Notes 1.1

Specify either the explicit begin and end date or one of the caluclated time periods provided in the drop down list. Click on the icon to the left of the entry field to toggle between filters for explict date range input and calculated time periods. To minimize the impact to your databases performance, use the filter to limit record selection. This view gives you a quick look at the overall trend in event impact as tec_011 measured by the weighted down-time and also highlights any trends tec_AllOpenEvts based on the severity of the events.

standard

standard

51

Filename

View Title

View Description

Related Views

Roles Assigned

tec_AllOpenEvts

All open events – by severity

(Oracle and Sybase) tec_AllOpenEvts_DB2 (DB2)

This tabular report presents information about all open TEC events in tec_AllClosedEvts the the Event Repository table. Events in the report are grouped by severity and then sorted by source and hostname. A parameter entry tec_GenSumOpenEvts field is provided to filter events by severity. Leaving the parameter entry field blank displays all open events for all severities. To minimize the impact to your databases performance, use the filter to limit record selection.

Entry of the severity parameter is case sensitive (i.e. to match FATAL you must type FATAL.) Event volume by date This view gives you a quick look at the overall trend in event volume tec_005 tec_015 and severity and also highlights any trends based on the severity of the events. tec_AllOpenEvts Double click on the week date and view information about each day that week, or double click on a severity bar in the week and view volume of events for that severity. Open Events – with This report presents a tabular view of open events with calculated open tec_AllClosedEvts tec_OpenWithFilters filters duration from the database table Event Repository. Events are grouped (Oracle and Sybase) by date and time starting with the most recent event received. A filter tec_GenSumOpenEvts is provided so events can be selected by hostname, class, and source. To minimize the impact to your database performance, use the filters to tec_OpenWithFilters_D limit record selection. B2 (DB2) Within each time group, events are grouped by severity.

tec_008

tec_005

Entry of the filter parameters is case sensitive (i.e to match Printer_offline you must enter Printer_offline.) Top 10 event classes – This view shows you the types of events that you are most frequently serious problems receiving. It is restricted to only those events that are classified with the fatal or critical severity. Average daily event This view gives you the average daily number of events received by volume day of week based on the previous 4 weeks.

tec_014

standard

standard

standard

standard

tec_010 tec_004

standard

tec_015 tec_016

TDS for Event Management 1.0.1 Release Notes 1.1

52

Filename

View Title

View Description

Related Views

Roles Assigned

tec_002

Event histogram by day

tec_003

This week vs. last week vs. average

tec_001

Event histogram by day and hour

tec_004

Event source volume by hour

tec_026

tec_024

This view shows you the event volume by day of week for the previous tec_001 4 weeks. tec_015 Use the 3-D Rotate tool to realign graph for better viewing from other tec_016 angles. Right click on the graph and select Display Options. tec_ClosedEvtsInDateRange This report lets you look at the day by day event volume of the last 2 tec_ClosedEvtsInDateRange weeks against an average week (based on the last 4 weeks and/or the last 13 weeks). Use the 3-D Rotate tool to realign graph for better viewing from other angles. Right click on the graph and select Display Options. This view lets you quickly detect patterns in the event arrival based on tec_002 both day of week and time of day. This could indicate a problem that tec_003 is triggered by some regularly scheduled activity that you were not aware of. tec_009

tec_011 This view shows you the average number of events by event source for tec_005 each hour of the day. This average is based on the previous 30 days worth of events. This can be helpful in establishing the shift schedules tec_GenSumOpenEvts and staffing levels for your service center or in isolating a scheduled activity that is causing problems. Event rate by Network This view helps to isolate portions of the network that are having a tec_014 Address disproportionate number of events. Double Click on the network id to tec_016 explore the subnets and reach individual nodes. The machine hostnames can be seen at the lowest level. Event rate by Network This view helps you see what type of events are coming from different tec_014 address and Source locations in your network. Double Click on the network id to explore the subnets and reach individual nodes. The machine hostnames can be tec_016 seen at the lowest level.

TDS for Event Management 1.0.1 Release Notes 1.1

standard

standard

standard

standard

standard

standard

53

Filename

View Title

View Description

Related Views

Roles Assigned

tec_025

Event rate by Network This view helps you see if events from one portion of your network and Duration seem to take a disproportionately long time to close out.

tec_014

standard

tec_016

tec_010

Top 100 systems by events per system

Double Click on the network id to explore the subnets and reach individual nodes. The machine hostnames can be seen at the lowest level. This view shows you the systems that are generating the most events.

tec_008

standard

tec_016 tec_009

Top 100 systems by This view shows you the systems that are generating the most serious total number of events events.

tec_011

Top 100 systems by weighted down-time

TDS for Event Management 1.0.1 Release Notes 1.1

tec_001

standard

tec_016 This view shows you the systems that are having the highest weighted tec_001 down-time. Weighted down-time is the fundamental measurement tec_016 used for calculating system availability (Percent up-time).

standard

54

Report Definitions Filename tec_007

View Title

Rank Report

Event classes most frequently YES missing SLA

tec_017

How often am I missing my SLA?

tec_006

Events by severity and duration

Period

Measure

Type Explorer Rolling 30 days Total Number of

Row

Column

Business Day By Class

Events Explorer Rolling 30 days Number of times

By Severity

Rolling 30 days

missed SLA Explorer Rolling 30 days Total Number of

By Severity

By Duration

30 day

By Event Class

Other Information Filter by Severity Rank by Severity

Events tec_GenSumOpenEvt General Summary of Open

Crystal Report

s (Oracle and Sybase) Events tec_GenSumOpenEvt s_DB2 (DB2) tec_014

Which events take the longest YES

Explorer Rolling 30 days Mean time to repair

to fix?

(minutes)

Rank by Class

average per

Ascending

class

Filter by Alternate Severity

tec_AllClosedEvts

All Closed events

Crystal Report

(Oracle and Sybase) tec_AllClosedEvts_D B2 (DB2)

TDS for Event Management 1.0.1 Release Notes 1.1

55

Filename

View Title

Rank Report

tec_ClosedEvtsInDate Archived Events – in date Range (Oracle and

Period

Measure

Row

Column

Other Information

Type Crystal Report

range

Sybase) tec_ClosedEvtsInDate Range_DB2 (DB2) tec_016

Event imapct by date and

Explorer Rolling 30 days Weighted down time

severity tec_015

Event volume by date and All open events

Rolling 30 Days

By Severity

Rolling 13 weeks

Serious

By Class

(minutes) Explorer Rolling 13 weeks

severity tec_AllOpenEvts

By Severity

Total Number of Events

Crystal Report

(Oracle and Sybase) tec_AllOpenEvts_DB 2 (DB2) tec_OpenWithFilters Open Events – with filters

Crystal Report

(Oracle and Sybase) tec_OpenWithFilters_ DB2 (DB2) tec_008

Top 10 event classes –serious YES

Explorer Rolling 30 days Total Number of

problems tec_005

Average daily event volume

TDS for Event Management 1.0.1 Release Notes 1.1

Reporter By Date

Events

Problems

Total Number of

Average day By Day of the

Events

over 4 weeks week

Rank Class Top 10 Descending

56

Filename tec_002 tec_003

View Title

Rank Report

Period

Measure

Event histogram by day

Type Explorer Rolling 4 weeks Total Number of

This week vs. last week vs.

Reporter By Date

average

Row

Column

rolling 4

By day of the

Events

weeks

week

Total Number of

This week to By day of the

Events

date / Average week

Other Information

over last 13 weeks tec_004 tec_001

Event source volume by hour

Reporter Rolling 30 days Total Number of

By source

By Time of day

Event histogram by day and

Events Explorer Rolling 4 weeks Total Number of events Rolling 4

By day and time

hour tec_026 tec_025

tec_010

Entire Network

YES

Event rate by Network Address YES

Explorer Rolling 13 weeks

and Source

Source

YES

day Explorer Rolling 30 days Total Number of

Problems

Top 100 systems by events per YES

Events Explorer Rolling 30 days Total Number of Events Explorer Rolling 30 days Weighted down time

Events

Top 100 systems by serious

system tec_011

Events per system per By Duration

Event rate by Network and

Explorer Rolling 13 weeks

events tec_009

Entire Network

Event rate by Network Address YES

Duration tec_024

Weeks Events per system per Rolling 13 weeks day

Explorer Rolling 13 weeks

Top 100 systems by weighted YES down-time

TDS for Event Management 1.0.1 Release Notes 1.1

Rank Hostname Descending Rank Network Address

day

Descending

Events per system per By Alternate Entire Network

Cant Rank because of

(minutes)

By Serious Serious By Severity

Average By Hostname

Rank top 100 hostnames

By Hostname

Rank top 100 hostnames

By Hostname

Can’t Rank because of Average

57

APPENDIX A DB2 Crystal Reports Filename Changes Oracle and Sybase File Name tec_AllClosedEvts.rpt tec_AllOpenEvts.rpt tec_ClosedEvtsInDateRange.rpt tec_GenSumOpenEvts.rpt tec_OpenWithFilters.rpt

TDS for Event Management 1.0.1 Release Notes 1.1

DB2 File Name tec_AllClosedEvts_DB2.rpt tec_AllOpenEvts_DB2.rpt tec_ClosedEvtsInDateRange_DB2.rpt tec_GenSumOpenEvts_DB2.rpt tec_OpenWithFilters_DB2.rpt

58