IBM Tivoli Decision Support for OS/390 Version 1.6 (RACF)

Warehouse Enablement Pack, Version 1.2.0

Implementation Guide

 

for Tivoli Data Warehouse, Version 1.2

 

Template Version 3.8

 

 

 

 

 

Date of Last Update: October 24, 2003

 

NOTE:  The printed version of this document is FOR REFERENCE ONLY. The online version is the master copy. 

It is the responsibility of the users to ensure that they have the current version. Any outdated printed copy is not valid and must be removed from possible use. It is also the responsibility of the users to ensure the completeness of this document prior to use.

Document Location: This document can be found online in the Tivoli Data Warehouse Lotus Notes database on the server ATE08DB/D/ATE in the directory t_dir\twhdp.nsf.


 


 

DEVELOPERS: Do not modify this copyright information. It changes constantly and has legal implications. Your ID team maintains it.

Note:

Before using this information and the product it supports, read the information in Notices on page 22.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

First Edition (February 2004)

This edition applies to IBM Tivoli Decision Support for OS/390 Version 1.6 and to all subsequent releases and modifications until otherwise indicated in new editions.

 

© Copyright International Business Machines Corporation 2004. All rights reserved.

WRITERS: Make sure that you put the first copyright year followed by the last copyright year.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

 


Contents

To update the table of contents and cross-references to pick up text changes and to update page numbers:

1. Turn off tracked changes (Tools -> tracked changes -> Highlight changes, then deselect Track changes while editing).

2. Select the entire document using Control-A or Edit -> Select All.

3. Right-click anywhere in the document.

4. Click Update Field.

5. Word will ask how you want to update the table of contents. Select Update entire table and then click OK.

1 About this guide. 1

1.1 Who should read this guide. 1

1.2 Publications. 1

1.2.1 IBM Tivoli Decision Support for OS/390 library. 1

1.2.2 Tivoli Data Warehouse library. 2

1.2.3 Related publications 2

1.2.3.1 IBM DB2, DB2 Data Warehouse Center, and DB2 Warehouse Manager library. 2

1.2.3.2 IBM Redbooks. 3

1.2.4 Accessing publications online. 4

1.2.5 Ordering publications 4

1.3 Accessibility. 4

1.4 Contacting software support 4

1.5 Participating in newsgroups. 5

1.6 Typeface conventions. 5

2 Overview. 6

2.1 Overview of Tivoli Data Warehouse. 6

2.2 Overview of the warehouse pack for Tivoli Decision Support for OS/390. 7

2.3 Data source and targets for Tivoli Decision Support for OS/390 (RACF) 8

3 Installing and configuring the warehouse pack. 9

3.1 Prerequisite hardware and software. 9

3.2 Product notes and limitations. 9

3.3 Database-sizing considerations. 9

3.4 Pre-installation procedures. 9

3.5 Installation of the warehouse pack.. 9

3.6 Post-installation procedures. 10

3.6.1 How to change the default schema name of Tivoli Decision Support for OS/390. 10

3.6.2 How to schedule ETL processes 10

3.7 Migration from a previous release of the warehouse pack.. 11

3.8 Uninstallation of the warehouse pack.. 11

3.9 Multiple data centers. 11

3.10 Multiple customer environments. 11

4 Maintenance and problem determination. 13

4.1 Backing up and restoring. 13

4.2 Deleting data in the central data warehouse. 13

4.2.1 Deleting measurement data (table Prune_Msmt_Control) 13

4.3 Maintenance of customized environments. 13

4.4 Problem determination. 13

5 ETL process 14

5.1 D09_c05_RACF_Process. 14

6 Central data warehouse information. 15

6.1 Component configuration. 15

6.1.1 Component type (table CompTyp) 15

6.1.2 Component extension (table Comp_ext) 15

6.1.3 Component (table Comp) 15

6.1.4 Component relationship type (table RelnTyp) 16

6.1.5 Component relationship rule (table RelnRul) 16

6.1.6 Component relationship (table CompReln) 16

6.1.7 Component type keyword (table CompTyp_Keyword) 16

6.1.8 Attribute type (table AttrTyp) 16

6.1.9 Attribute rule (table AttrRul) 16

6.1.10 Attribute domain (table AttrDom) 16

6.1.11 Component attribute (table CompAttr) 17

6.1.12 Component type relationship (table CTypReln) 17

6.1.13 Component attribute type relationship (table ATypReln) 17

6.2 Component measurement 18

6.2.1 Measurement group type (table MGrpTyp) 18

6.2.2 Measurement group (table MGrp) 18

6.2.3 Measurement group member (table MGrpMbr) 18

6.2.4 Measurement unit category (table MUnitCat) 18

6.2.5 Measurement unit (table MUnit) 18

6.2.6 Measurement alias names (table MTypReln) 19

6.2.7 Time summary (table TmSum) 19

6.2.8 Measurement source (table MSrc) 19

6.2.9 Measurement source history (table MSrcHistory) 19

6.2.10 Measurement type (table MsmtTyp) 19

6.2.11 Component measurement rule (table MsmtRul) 20

6.2.12 Measurement (table Msmt) 20

6.2.13 Threshold measurement objective (table Mobj) 20

6.2.14 Threshold measurement objective range (table MobjRng) 20

6.2.15 Threshold severity level (table SevLvl) 20

6.3 Component events. 21

6.4 Helper tables. 21

6.5 Exception tables. 21

6.6 Incremental extraction. 21

Notices 22


1 About this guide

Mark all trademarks at the first occurrence as appropriate. To mark a trademark, use Insert -> Symbol, (normal text).

This document describes the warehouse enablement pack, Version 1.2.0 for IBM Tivoliâ Decision Support for OS/390 âVersion 1.6 (RACF)â. This warehouse enablement pack (hereafter referred to as warehouse pack) is created for Tivoli Data Warehouse, Version 1.2 and it is used to load RACF data for IBM Tivoli Decision Support for OS/390 into a central data warehouse.

With this implementation guide, you can install and configure the warehouse pack and analyze the data structures it uses.

1.1 Who should read this guide

This guide is for people who do any of the following activities:

·         Plan for and install the warehouse pack

·         Use and maintain the warehouse pack

·         Create new reports

·         Create additional warehouse packs that use data from this warehouse pack

Administrators and installers should have the following knowledge or experience:

·         Basic system administration and file management of the operating systems on which the components of Tivoli Data Warehouse are installed

·         An understanding of the basic concepts of relational database management

·         Experience administering IBM DB2 Universal Database

Additionally, report designers and warehouse pack creators should have the following knowledge or experience:

·         An understanding of the source data and application

·         Data warehouse information and design, extract, transform, and load (ETL) processes, and online analytical processing (OLAP)

1.2 Publications

Do not change the information about TEDW & DB2 documents. Add information about documents that are important to understanding your warehouse pack, such as product documentation that defines the schema of the operational data.

This section lists publications in the Tivoli Data Warehouse library and other related documents. It also describes how to access Tivoli publications online and how to order Tivoli publications.

The following sets of documentation are available to help you understand, install, and manage this warehouse pack:

·         IBM Tivoli Decision Support for OS/390

·         IBM Tivoli Data Warehouse

·         Crystal Enterprise

·         IBM DB2, DB2 Data Warehouse Center, and DB2 Warehouse Manager

·         IBM Redbooks

 

Note: The documentation for Crystal Enterprise is available on the Crystal Enterprise CD, which is distributed with Tivoli Data Warehouse.

 

1.2.1 IBM Tivoli Decision Support for OS/390 library

<Describe your library if appropriate. Otherwise, delete this section. Follow the format and structure of the typical preface information.>

The following documents are available in the IBM Tivoli Decision Support for OS/390 library:

·         Tivoli Decision Support for OS/390,System Performance Feature Reference, Version 1.6 (vol. II), SH19-4494

Provides reference information for the System Performance feature, describes the component tables and look up tables associated with the feature, and provides a detailed explanation of how the feature processes each type of system performance data.

·         Tivoli Decision Support for OS/390, Administration Guide, Version 1.6, SH19-6816

Provides information about customizing Tivoli Decision Support for OS/390.

1.2.2 Tivoli Data Warehouse library

The following documents are available in the Tivoli Data Warehouse library. The library is available on the Tivoli Data Warehouse Documentation CD as well as online, as described in “Accessing publications online” on page 4.

·         Tivoli Data Warehouse Release Notes, SC32-1399

Provides late-breaking information about Tivoli Data Warehouse and lists hardware requirements and software prerequisites.

·         Installing and Configuring Tivoli Data Warehouse, GC32-0744

Describes how Tivoli Data Warehouse fits into your enterprise, explains how to plan for its deployment, and gives installation and configuration instructions. It contains maintenance procedures and troubleshooting information.

·         Enabling an Application for Tivoli Data Warehouse, GC32-0745

Provides information about connecting an application to Tivoli Data Warehouse. This book is for application programmers who use Tivoli Data Warehouse to store and report on their application data, data warehousing experts who import Tivoli Data Warehouse data into business intelligence applications, and customers who put their local data in Tivoli Data Warehouse. This document is available only from the IBM Web site.

·         Tivoli Data Warehouse Messages, SC09-7776

Lists the messages generated by Tivoli Data Warehouse, and describes the corrective actions you should take.

1.2.3 Related publications

The following sections describe additional publications to help you understand and use Tivoli Data Warehouse.

1.2.3.1 IBM DB2, DB2 Data Warehouse Center, and DB2 Warehouse Manager library

The DB2 library contains important information about the database and data warehousing technology provided by IBM DB2, DB2 Data Warehouse Center, and DB2 Warehouse Manager. Refer to the DB2 library for help in installing, configuring, administering, and troubleshooting DB2, which is available on the IBM Web site:

http://www-3.ibm.com/software/data/db2/library/

After you install DB2, its library is also available on your system.

The following DB2 documents are particularly relevant for people working with Tivoli Data Warehouse:

·         IBM DB2 Universal Database for Windows Quick Beginnings, GC09-2971

Guides you through the planning, installation, migration (if necessary), and setup of a partitioned database system using the IBM DB2 product on Microsoft Windows.

·         IBM DB2 Universal Database for UNIX Quick Beginnings, GC09-2970

Guides you through the planning, installation, migration (if necessary), and setup of a partitioned database system using the IBM DB2 product on UNIX.

·         IBM DB2 Universal Database Administration Guide: Implementation, SC09-2944

Covers the details of implementing your database design. Topics include creating and altering a database, database security, database recovery, and administration using the Control Center, which is a DB2 graphical user interface.

·         IBM DB2 Universal Database Data Warehouse Center Administration Guide, SC26-9993

Provides information on how to build and maintain a data warehouse using the DB2 Data Warehouse Center.

·         IBM DB2 Warehouse Manager Installation Guide, GC26-9998

Provides information on how to install the following Warehouse Manager components: Information Catalog Manager, warehouse agents, and warehouse transformers.

·         IBM DB2 Universal Database and DB2 Connect Installation and Configuration Supplement, GC09-2957

Provides advanced installation considerations, and guides you through the planning, installation, migration (if necessary), and set up of a platform-specific DB2 client. This supplement also contains information on binding, setting up communications on the server, the DB2 GUI tools, DRDA® AS, distributed installation, the configuration of distributed requests, and accessing heterogeneous data sources.

·         IBM DB2 Universal Database Message Reference Volume 1, GC09-2978 and IBM DB2 Universal Database Message Reference Volume 2, GC09-2979

Lists the messages and codes issued by DB2, the Information Catalog Manager, and the DB2 Data Warehouse Center, and describes the actions you should take.

·         IBM DB2 UDB for z/OS and OS/390 Administration Guide, SC26-9931

Provides information on how to administer DB2 UDB on z/OS and OS/390 systems.

·         IBM DB2 UDB for z/OS and OS/390 An introduction to DB2 for OS/390, SC26-9937

Provides start-up information for DB2 for OS/390 users.

·         IBM DB2 UDB for z/OS and OS/390 Messages and codes, GC26-9940

Lists the messages and codes issued by DB2 on z/OS and OS/390 systems.

·         IBM DB2 UDB for z/OS and OS/390 Installation Guide, GC26-9936

Provides information on how to install DB2 UDB on z/OS and OS/390 systems.

·         IBM DB2 UDB for z/OS and OS/390 Diagnosis Guide and Reference, LY37-3740

Provides information on how to understand DB2 errors and instruct corrective actions that should be taken.

1.2.3.2 IBM Redbooks

IBM Redbooks are developed and published by the IBM International Technical Support Organization, the ITSO. They explore integration, implementation, and operation of realistic customer scenarios. The following Redbooks contain information about Tivoli Data Warehouse:

·         Introduction to Tivoli Enterprise Data Warehouse, SG24-6607

Provides a broad understanding of Tivoli Data Warehouse. Some of the topics that are covered are concepts, architecture, writing your own extract, transform, and load processes (ETLs), and best practices in creating data marts.

·         Planning a Tivoli Enterprise Data Warehouse Project, SG24-6608

Describes the necessary planning you must complete before you can deploy Tivoli Data Warehouse. The guide shows how to apply these planning steps in a real-life deployment of a warehouse pack using IBM Tivoli Monitoring. It also contains frequently used Tivoli and DB2 commands and lists troubleshooting tips for Tivoli Data Warehouse.

1.2.4 Accessing publications online

The publications CD or product CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both.

IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli Software Information Center Web site. The Tivoli Software Information Center is located at the following Web address:

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Note: If you print PDF documents on other than letter-sized paper, select the Fit to page check box in the Adobe Acrobat Print dialog. This option is available when you click File " Print. Fit to page ensures that the full dimensions of a letter-sized page print on the paper that you are using.

1.2.5 Ordering publications

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

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

·         In the United States: 800-879-2755

·         In Canada: 800-426-4968

·         In other countries, for a list of telephone numbers, see the following Web site:

http://www.ibm.com/software/tivoli/order-lit/

1.3 Accessibility

Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. For the warehouse pack, you use the interfaces of IBM DB2 and the Crystal Enterprise. See those documentation sets for accessibility information.

1.4 Contacting software support

If you have a problem with a Tivoli product, refer to the following IBM Software Support Web site:

http://www.ibm.com/software/sysmgmt/products/support/

If you want to contact customer support, see the IBM Software Support Guide at the following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support, depending on the severity of your problem, and the following information:

·         Registration and eligibility

·         Telephone numbers, depending on the country in which you are located

·         Information you must have before contacting IBM Software Support

1.5 Participating in newsgroups

User groups provide software professionals with a forum for communicating ideas, technical expertise, and experiences related to the product. They are located on the Internet, and are available using standard newsreader programs. These groups are primarily intended for user-to-user communication, and are not a replacement for formal support. You can use Web browsers like Netscape Navigator or Microsoft Internet Explorer to view these newsgroups:

Tivoli Data Warehouse

news://news.software.ibm.com/ibm.software.tivoli.enterprise-data-warehouse

Add your product newsgroup here, if you have one.

1.6 Typeface conventions

This guide uses the following typeface conventions:

Bold

·         Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text

·         Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip and Operating system considerations)

·         Column headings in a table

·         Keywords and parameters in text

Italic

·         Citations (titles of books, diskettes, and CDs)

·         Words defined in text

·         Emphasis of words (words as words)

·         Letters as letters

·         New terms in text (except in a definition list)

·         Variables and values you must provide

Monospace

·         Examples and code examples

·         File names, programming keywords, and other elements that are difficult to distinguish from surrounding text

·         Message text and prompts addressed to the user

·         Text that the user must type

·         Values for arguments or command options

2 Overview

The following sections provide an overview of Tivoli Data Warehouse and the warehouse pack for Tivoli Decision Support for OS/390 RACF Component.

2.1 Overview of Tivoli Data Warehouse

The TEDW ID team maintains this overview. Please contact us before changing it.

Tivoli Data Warehouse provides the infrastructure for the following:

·         Extract, transform, and load (ETL) processes through the IBM DB2 Data Warehouse Center tool

·         Schema generation of the central data warehouse

·         Historical reports

As shown in Figure 1, Tivoli Data Warehouse consists of a centralized data store where historical data from many management applications can be stored, aggregated, and correlated.

 

Figure 1. Tivoli Data Warehouse basic architecture

The central data warehouse uses a generic schema that is the same for all applications. As new components or new applications are added, more data is added to the database; however, no new database objects are added in the schema.

A data mart is a subset of a data warehouse that contains data that is tailored and optimized for the specific reporting needs of a department or team.

The central data warehouse ETL reads the data from the operational data stores of the application that collects it, verifies the data, makes the data conform to the schema, and places the data into the central data warehouse.

The data mart ETL extracts a subset of data from the central data warehouse, transforms it, and loads it into one or more star schemas, which can be included in data marts to answer specific business questions.

A program that provides these ETLs is called a warehouse pack.

The ETLs are typically scheduled to run periodically, usually during non-peak hours.

 

2.2 Overview of the warehouse pack for Tivoli Decision Support for OS/390

Tivoli Decision Support for OS/390 is structured with several components relative to the different applications where it collects data. Consequently also the Extract Transform and Load processes will be defined as different “subject areas” according to each Tivoli Decision Support component. For instance in the “DB2 Warehouse Center” one can find as subject areas, if the corresponding warehouse enablement packs were installed, as follows:Tivoli Decision Support for OS/390 is structured with several components relative to the different applications where it collects data. Consequently also the Extract Transform and Load processes will be defined as different “subject areas” according to each Tivoli Decision Support component. For instance in the “DB2 Warehouse Center” one can find as subject areas, if the corresponding warehouse enablement packs were installed, as follows:Give an overview of your warehouse pack. Include information that would be helpful for understanding the overall flow of application-specific data in and out of the central data warehouse and data marts. Data flow diagrams worked well for some products.

Provide customer-centric rationale on what benefit customers obtain from installing the warehouse pack. Discuss report capabilities generically and insert a cross reference to the reports section.

If the warehouse pack does not provide reports, describe how other Tivoli applications provide value to your product data. Here is an example statement for warehouse packs that are to be used by Tivoli Service Level Advisor: The warehouse pack for Tivoli SAN Manager extracts data from the Tivoli SAN Manager Enterprise Repository database. The warehouse pack then loads that data into the central data warehouse. The collection of data from Tivoli products into one central data warehouse lets you see trends in operation, resource usage, and cross-product interoperability. The historical data from Tivoli SAN Manager is provided to use by Tivoli Service Level Advisor and Tivoli Storage Manager.

Tivoli Decision Support for OS/390 is structured with several components relative to the different applications where it collects data. Consequently  the extract transform and load processes are also defined as different Subject Areas according to each Tivoli Decision Support component. For instance in the “DB2 Warehouse Center” you can find the following Subject Areas, if the corresponding warehouse packs were installed:

·   D01_TDS/390-MVS_v1.6.0_Subject_Area (ETLs for Tivoli Decision Support for OS/390 System performance feature MVS component)

·   D07_TDS/390-OPC_v1.6.0_Subject_Area (ETLs for Tivoli Decision Support for OS/390 System performance feature OPC component)

·   D09_TDS/390-RACF_v1.6.0_Subject_Area (ETLs for Tivoli Decision Support for OS/390 System performance feature RACF component)

The relationship between Tivoli Decision Support and Tivoli Data Warehouse through the ETL processes varies according to the different tasks they perform. The graph below shows what has been just stated:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Figure 2. Overview of the warehouse pack for Tivoli Decision Support for OS/390

This figure refers only to the central data warehouse loading, because this warehouse pack does not provide either data marts or reports.

To understand how Tivoli Decision Support for OS/390 interacts with Tivoli Data Warehouse, see that topic in Installing and Configuring Tivoli Data Warehouse.

2.3 Data source and targets for Tivoli Decision Support for OS/390 (RACF)

The following table shows the corresponding Tivoli Decision Support for OS/390 source locations for the   central data warehouse OS/390 component types and measurement types managed by the warehouse pack.

Tivoli Decision Support for OS/390 source

Table name

Tivoli Decision Support for OS/390 Source

Field or Source formula

Tivoli Data Warehouse

CompTyp_Cd  (C)

MsmtTyp_Nm (M) 

AttrTyp_Cd(A)

RACF_COMMAND_T

SYSTEM_ID

(C) 'MVS_SYSTEM'

'RACF'

(C) ‘MVS_SYSAPPL’

‘RACF’

(A) ’MVS_SYSAPPL_TYPE’

Count(SPECIAL=’Y’)

(M) 'RACF Commands By SPECIAL Users'

Count(AUDITOR=’Y’)

(M) 'RACF Commands By AUDITOR Users'

Count(FAILED=’Y’)

(M) 'RACF Insufficient Authority Failures’'

RACF_LOGON_T

SYSTEM_ID

(C) ‘MVS_SYSTEM’

'RACF'

(C) ‘MVS_SYSAPPL’

‘RACF’

(A) ‘MVS_SYSAPPL_TYPE’

Count(EVENT_QUAL>0) 

      when (event ='INIT/LOGON')

(M) 'RACF Logon Violations'

Count (EVENT_QUAL=9)

      when (event ='INIT/LOGON')

(M) 'RACF Logon Violations - Undefined user'

Count(EVENT_QUAL=1)

      when (event ='INIT/LOGON')

(M) 'RACF Logon Violations - Invalid Password'

RACF_OPERATION_T

SYSTEM_ID

(C) ‘MVS_SYSTEM’

'RACF'

(C) ‘MVS_SYSAPPL’

‘RACF’

(A) ‘MVS_SYSAPPL_TYPE’

Count(EVENT_CODE=2)

(M) 'RACF Resource Access OPERATIONS Users'

RACF_RESOURCE_T

SYSTEM_ID

(C) ‘MVS_SYSTEM’

'RACF'

(C) ‘MVS_SYSAPPL’

‘RACF’

(A) ‘MVS_SYSAPPL_TYPE’

Count(EVENT_QUAL=0)

(M) 'RACF Resource Access Successes'

Count(EVENT_QUAL=3,5,8,9,10,13)

(M) 'RACF Resource Access Warnings'

Count(EVENT_QUAL=1,2,4,6,7,11,12)

(M) 'RACF Resource Access Violations'

 

.

WRITERS: Optionally, provide a screen shot of the final report. If you put several graphics in Word, eventually Word will crash. So you can put some representative report screen shots instead of every one.

DEVELOPERS: To send your report requirements to the report vendor, be sure to include a graphic representation of each report that you would like the report vendor to create. If Word starts to crash because you have 10 or more graphics imported into the template, put the graphics in a separate document so that they can be sent with the template to the enabling team.

 

3 Installing and configuring the warehouse pack

This section describes the installation and configuration of the warehouse pack.

3.1 Prerequisite hardware and software

Every prerequisite application and version number must be listed either below or in your product document that contains the full list of software/hardware prerequisites. This list must include version numbers for supported databases, fix packs for databases, version of Tivoli Data Warehouse, fix packs/interim fixes for Tivoli Data Warehouse, and fix packs for your product.

Before installing the warehouse pack for Tivoli Decision Support for OS/390 RACF component, you must install the following software:

·         IBM Tivoli Decision Support for OS/390 Version 1.6 System performance feature with the following component:

Ø       RACF Component

·         IBM DB2 Universal Database, Version 7.2

·         IBM DB2 Universal Database for z/OS and OS/390, Version 7 (If your app works on 390, you need this. Otherwise delete.)

·         Tivoli Data Warehouse, Version 1.2 and its prerequisites

·         Crystal Enterprise and its prerequisites

 (If your application requires another warehouse pack to make your application function correctly with TDW, you need this. Otherwise delete.)

If your product specifies in the twh_install_props.cfg file whether each central data warehouse or data mart can be specifically on z/OS, distributed or both, document the number of systems and locations for the data marts and central data warehouses.

This warehouse pack supports central data warehouses on DB2 UDB for z/OS and OS/390.

Refer to the Tivoli Data Warehouse Release Notes and Tivoli Decision Support for OS/390 Administration Guide for specific information about hardware prerequisites, database and operating system support, and product prerequisites. For late-breaking news about prerequisites, refer to the following IBM Software Support Web site:

http://www.ibm.com/software/sysmgmt/products/support/

 

3.2 Product notes and limitations

For performance and disk capacity reasons, data from Tivoli Decision Support for OS/390 can only be stored in the central data warehouse database on OS/390 system.

In addition, place Tivoli Decision Support for OS/390 in the same DB2 subsystem as   central data warehouse.

To avoid resource contention, warehouse packs on OS/390 must be run in sequence. See the following sections for instructions on how to install and schedule multiple Tivoli Decision Support for OS/390 warehouse packs.

Describe restrictions, limitations, known bugs, etc. in this section. Use section heads to indicate each item, product note, or limitation.

3.3 Database-sizing considerations

Refer to the “Estimating the size of your Tivoli Data Warehouse deployment” in Installing and Configuring Tivoli Data Warehouse manual.

Accurate database sizings are important for capacity planning purposes. Customers need to know the number of rows inserted into key tables to calculate throughput and determine how long the ETLs will run. Customers also need the base size and daily growth size to calculate the amount of disk space required for their databases.

Describe the database-sizing considerations, which include:

In summary what is really needed for each database (TWH_CDW, TWH_MART and TWH_MD) is:

.

This is just a sample of how to approach this. Create worksheets that work for your product's components.

<Here is an example for an imaginary warehouse pack. Delete this after reviewing.>

3.4 Pre-installation procedures

There are no pre-installation procedures for this warehouse pack.

List any steps the customer must do before running the warehouse pack installation program. For example, this might include tasks such as creating additional tables in an existing database or establishing an ODBC connection.

If there are none, say: This warehouse pack requires no pre-installation procedures.

3.5 Installation of the warehouse pack

To install this warehouse pack, perform the following steps:

1.        Make sure that Tivoli Decision Support for OS/390 is installed and the data source is available.

2.        Make sure that all prerequisite product patches are applied.

3.        Make sure that Tivoli Data Warehouse is installed. For instructions about installing Tivoli Data Warehouse, refer to Installing and Configuring Tivoli Data Warehouse.

 

4.        Record the following information that will be used during the installation:

ODBC source

User ID

Password

Database type

Database alias

TDS390

Customer fills this in.

Your DB2 UDB for z/OS and OS/390 User ID

Customer fills this in.

Your DB2 UDB for z/OS and OS/390 Password

DB2 UDB for z/OS and OS/390

The ODBC data source used for CDW (for example TCDW1)

 Customer fills this in.

 

5.        Install the warehouse pack as described in Installing and Configuring Tivoli Data Warehouse, using the installation properties file (twh_install_props.cfg) located in the tdw_weps\d09\ v1200 directory.

6.        If you want to run multiple warehouse packs on OS/390 select “Do not schedule the data extraction, transformation and loading”, when the ETL configuration window is displayed.  In this way you are able to manually schedule ETLs in sequence as explained in the following Post-installation procedures section.

7.        Perform the post-installation steps described in Post-installation procedures.

 

The ODBC source is the data source name you put in the twh_install_props.cfg file. If your warehouse pack is capable of having multiple sources of data, then add a line for each data source below. State that they have to specify the ODBC connection information for each additional data source while installing the warehouse pack.

Provide the location of the installation media. You do not need to explain how to install Tivoli Data Warehouse.

 

3.6 Post-installation procedures

Complete the following post-installation procedures.

3.6.1 How to change the default schema name of Tivoli Decision Support for OS/390

Before running any ETL process, if this is the first Tivoli Decision Support for OS/390 warehouse pack that you are installing and you have installed Tivoli Decision Support for OS/390 using a schema (Tivoli Decision Support for OS/390 table prefix) name different from DRL (which is the default name), you must customize the db2os390.translate file, as described in Installing and Configuring Tivoli Data Warehouse.  For instance, if your schema name is DRLxxx, you must change the following:

 __TDS390_SCHEMA     DRL

into:

__TDS390_SCHEMA     DRLxxx

3.6.2 How to schedule ETL processes

If you are installing this warehouse pack as the only OS/390 warehouse pack, you can schedule it using the ETL configuration window during the installation steps. On the contrary, if you are installing multiple OS/390 warehouse packs, you must ensure that their ETLs must be run in sequence. During the installation process, you selected “Do not schedule data extraction, transformation and loading”. Now you must create shortcuts in the Data Warehouse Interface to link the ETL processes in sequence. With shortcuts you specify only the first ETL process runs. All the other processes run automatically because they are linked to that process. For details see “Scheduling warehouse pack ETL processes” in Installing and Configuring Tivoli Data Warehouse manual.

If there are none, say: This warehouse pack requires no post-installation procedures.

 

If your warehouse pack doesn't have any dependencies between processes, delete that part of the step.

3.7 Migration from a previous release of the warehouse pack

This warehouse pack has no migration from previous release.

3.8 Uninstallation of the warehouse pack

To uninstall the warehouse pack on your computer select Start> Programs> Tivoli Data Warehouse> Uninstall a Warehouse Pack. For further information see Installing and Configuring Tivoli Data Warehouse, “Uninstalling warehouse pack” chapter. Before uninstalling the warehouse pack, you can delete the related data from the central data warehouse by running a specific SQL script. A sample of it can be found in the twh\apps\d09\v1200\misc directory, the name is d09_data_delete.sql. The sample deletes both the static data and the instances loaded in the central data warehouse by this warehouse pack. Before running this script make sure you do not need those data anymore and make sure you are connected to the central data warehouse Database on host.

To uninstall the Warehouse pack using this script open a DB2 Command Window and enter the following command from the twh\apps\d09\v1200\misc directory:

db2 –z <your logfile name> -tvf d09_data_delete.sql

The sample provided is deleting both the static data and all the instances loaded in the CDW by the ETLs.If your warehouse pack requires the user to perform additional steps beyond what is documented in the Installing and Configuring Tivoli Data Warehouse guide, then list them in order. If your warehouse pack requires a different uninstall order, reflect that here. If there are no additional steps, delete the steps.

3.9 Multiple data centers

If your application and warehouse pack do not use fully qualified host names and Centr_Cd, then you need to provide examples and description of how the customer will create the lookup table for multiple data centers.

After you install the warehouse pack, you can configure Tivoli Data Warehouse to separate data for multiple data centers. To set this up, you must create SQL scripts with the following values:

Information for scripts

Value or location

Field in source data

MVS System IS

Name of lookup table

D09.Centr_lookup table

Name of center list

TWG.Centr

For the procedural instructions and example of  SQL statements, see the information about warehouse pack installation in the Installing and Configuring Tivoli Data Warehouse guide.

After the configuration for multiple data centers, you must modify the tables when data centers are added and removed.

3.10 Multiple customer environments

If your application and warehouse pack do not use fully qualified host names or the customer account code/customer ID, then you need to provide examples and description of how the customer will create the lookup table for multiple customer environments.

After you install the warehouse pack, you can configure Tivoli Data Warehouse to separate data for the multiple customer environments. To set this up, you must create SQL scripts with the following values:

Information for scripts

Value or location

Field in source data

MVS System ID

Name of lookup table

D09.Cust_lookup  table

Name of customer list

TWG.Cust

For the procedural instructions and example of  SQL statements, see the information about warehouse pack installation in the Installing and Configuring Tivoli Data Warehouse guide.

After your configuration of the multiple customer environments, you must modify the tables when customers are added and removed.

 

4 Maintenance and problem determination

Describe any maintenance tasks required for this warehouse pack.

This section describes maintenance tasks for the warehouse pack.

4.1 Backing up and restoring

Together with the procedures describing maintenance tasks in Installing and Configuring Tivoli Data Warehouse, it is recommended that you back up your data on a regular basis. Ensure you have sufficient back up to restore as much event data as you need to store in the central data warehouse.

For further information refer to the section about backing up and restoring in Installing and Configuring Tivoli Data Warehouse.

Describe any special backup and restoration considerations. For example, if the warehouse pack requires that additional tables be created in the operational data store, these tables must be backed up.

4.2 Deleting data in the central data warehouse

To manage the high volume of measurement data, use the Prune_Msmt_Control table where the deletion criteria are specified. The Prune_Msmt_Log table keeps a history of all data deletion activity.

For further information refer to “Pruning data from the central data warehouse” in Enabling an Application.Describe any special data pruning considerations. For example, if the warehouse pack requires that additional tables be created in the operational data store, these tables may need to be pruned.

By default the data older than the deletion criteria specified in the Prune_Msmt_Control table is deleted when the CDW_c05_Prune_and_Mark_Active process runs. This process is within the CDW_Tivoli_Data_Warehouse_v1.2.0_Subject_Area. By default, this process runs daily at 6:00 a.m..

4.2.1 Deleting measurement data (table Prune_Msmt_Control)

Include this optional statement if your warehouse pack uses measurement data. Otherwise, delete this section.

This table provides the deletion criteria for the data in the Msmt table

MSrc_Cd CHAR (6)

Tmsum_Cd CHAR (1)

PMsmtC_Age_In_Days DECIMAL(8,0)

D09

H

100

D09

D

300

D09

W

10000

D09

M

10000

 

Note: PMsmtC_Age_In_Days column contains the "Prune Measurement Control Age in Days”. This is the age at which measurements are deleted (day duration yyyymmdd).

4.3 Maintenance of customized environments

For successful Tivoli Data Warehouse maintenance do not change the Tivoli Data Warehouse ETLs, but rather create new ETLs in another subdirectory of the apps directory. At the same time define your process in the Data Warehouse Center.  Tivoli Data Warehouse provides standard maintenance of its subdirectories and processes, if not modified. Refer to Enabling an Application for details on how to create your ETLs.

If you have additional maintenance tasks, describe them in additional sections. Please notify the TDW ID team so that they can consider whether that new maintenance task is common enough to be added to this template.

4.4 Problem determination

If you have any additional troubleshooting information, describe it here. Before documenting a problem/solution, check the Installing and Configuring Tivoli Data Warehouse guide to see if the topic is already documented there.

For common problems and solutions, see the Installing and Configuring Tivoli Data Warehouse guide.

 

5 ETL process

The warehouse pack has the following process:

·         D09_c05_RACF _Process

5.1 D09_c05_RACF_Process

Repeat this section for each process.

Explain the function of the process, list its process steps, and describe the function of each step. If steps need to be linked together, explain how they connect. Installing and Configuring Tivoli Data Warehouse has instructions for linking steps together. You need to tell them if they need to do that and what links are needed.

State whether the process is run once or repeatedly. Explain the circumstances in which it runs, for example, a process might be run once immediately after installing the warehouse pack to configure it. A repeated process might run nightly to extract data from an operational data store or periodically to delete data from the warehouse. If the process is specific to the central data warehouse ETL or the data mart ETL, explain that.

Explain how to recognize when the process fails, and what to do if that happens. A common cause of errors is nonvalid data in the source database. The ETL process creates exception tables.  Explain the corrective action to take for common errors.

This process is used to load component and measurement tables from source data into the   central data warehouse database.

The process has the following steps:

·         D09_c05_s010_processRACF

This step populates the component table (Comp table),the component attribute table (CompAttr table) and the component relationship table (CompReln table).

·         D09_c05_s020_processRACF

This step populates the measurement table (Msmt table).

 


6  Central data warehouse information

This section is in landscape mode on purpose. The tables are too wide for portrait presentation.

This section provides the heart of the application integration information-how the application's operational data maps to the data being stored in the central data warehouse. Information developers should work closely with developers to provide complete and meaningful information. Detailed data descriptions are crucial to effective data sharing.

Information that is saved in the central data warehouse will be visible to the customer in reports, in the Tivoli Service Level Advisor (TSLA) GUI, and other tools. The customer should be able to look at a component name (Comp_Nm) and have some clue what resource is being measured.

While the content of the tables changes from application to application, most applications will have data in all of the tables shown in this section. All columns might not be used and therefore do not contain any information.

Before reading this section, read about the generic schema for the   central data warehouse, which is described in Enabling an Application for Tivoli Data Warehouse. That document defines the content of each table and explains the relationships between the tables in this document.

Describe how you came about the data values you put in the tables in this section. The following is an example from NetView. Modify it so that it applies to your product.

This section provides an example of how information is stored in Tivoli Data Warehouse. The data values shown in the following tables come from a generic installation.

Shaded central data warehouse columns indicate values that source applications must translate and deliver corresponding Java resource bundles. Internationalization of data is described in Enabling an Application for Tivoli Data Warehouse.

Note to writers:

If you are documenting one of the IBM Tivoli Monitoring PACs, ask your developers whether they had to edit the resource bundle. If they did, that means that they didn't use translatable words in the MsmtTyp_Nm field (and possibly others), but it wasn't noticed until after testing was too far along to change the value. They "fixed" this for translation by hand editing the resource bundle files that are sent to translation, without changing the scripts that created the untranslatable strings in the database.

That means that the database contains one value (usually a camel case abbreviation like PctCPUBusy), but the report interface will show a different, human-readable value (for example, Percent CPU Busy).  If this happened, you need to add info in the section describing that column to explain it and to help them map the database value to the translated string. Some of the strings will be translatable if you ignore the underscores (Percent_CPU_Busy). This is important for people writing reports to know the values they will see in the database.  You have to do this for each item they hand-edited.

A table showing the corresponding values might be a good idea. For example, something like this:

The values for MsmtTyp_Nm are stored in the central data warehouse as a short string, but are displayed in reports as descriptive phrases.  The following table shows how the values of MsmtTyp_Nm in the database correspond to the values displayed in reports.

PctCPUWait

Percent_CPU_Wait

Shaded columns in the following tables are translated. These columns are also marked with an asterisk (*) after the column name.

6.1 Component configuration

Some of the commonly used static data is listed below. Remove any that you are not using. Also, depending on your application you will add additional static data types.

The following sections describe the component configuration.

6.1.1 Component type (table CompTyp)

CompTyp_Cd CHAR (17)

CompTyp_Parent_Cd CHAR (17)

CompTyp_Nm * VARCHAR (120)

CompTyp_Strt_DtTm TIMESTAMP

CompTyp_End_DtTm TIMESTAMP

MSrc_Corr_Cd CHAR (6)

MVS_SYSTEM

 

MVS System

2002-01-01-00.00.00.000000

9999-01-01-00.00.00.000000

MODEL1

MVS_SYSAPPL

 

MVS System Application

2002-01-01-

00.00.00.000000

9999-01-01-00.00.00.000000

MODEL1

*This column is translated.

Most products collect IP host information, and therefore need an IP_HOST component type. If your application doesn't record IP information, you can delete that row from the table.

6.1.2 Component extension (table Comp_ext)

This table is not used by this warehouse pack.

6.1.3 Component (table Comp)

Comp_ID INTEGER

CompTyp_Cd CHAR  (17)

Centr_Cd CHAR (6)

Cust_ID INTEGER

Comp_Corr_ID INTEGER

Comp_Nm VARCHAR  (254)

Comp_Corr_Val VARCHAR  (254)

Comp_Strt_DtTm TIMESTAMP

Comp_End_DtTm TIMESTAMP

Comp_Ds VARCHAR  (254)

MSrc_Corr_Cd CHAR (6)

1

MVS_SYSTEM

CDW

1

 

ES38

 

2002-01-01-00.00.00.000000

9999-01-01-00.00.00.000000

 

SHARED

2

MVS_SYSAPPL

CDW

1

 

RACF

 

2002-01-01-00.00.00.000000

9999-01-01-00.00.00.000000

 

SHARED

 

Note1: The Comp_Corr_Val column is used to correlate the component instance to its parents. In the above Comp table sample this column was left empty for better readability. However in a real case, for this warehouse pack, it is built using the following structure:

 

CompType_Cd                           Component instance                      Comp_Corr_Val

         MVS_SYSTEM                          mvs_system_id                               ----

         MVS_SYSAPPL                        sysappl_name                                "MVS - mvs_system_id"

 

Note2: The Component Name (Comp_Nm column) , for components of type MVS_SYSTEM, contains the MVS System Identifier (SID) as specified  in the SMFPRM00 member in the SYS1.PARMLIB. The SID is 1 to 4 characters long.

Note that an alternative MVS identifier is the SYSNAME which is 1-8 characters long and could also be used in the future.

6.1.4 Component relationship type (table RelnTyp)

RelnTyp_Cd CHAR (6)

RelnTyp_Nm * VARCHAR (120)

MSrc_Corr_Cd CHAR (6)

PCHILD

Parent Child Relation

MODEL1

* This column is translated.

If your application does not need the type, delete that row from the table.

6.1.5 Component relationship rule (table RelnRul)

CompTyp_Source_Cd CHAR (17)

CompTyp_Target_Cd CHAR (17)

RelnTyp_Cd CHAR (6)

RelnRul_Strt_DtTm TIMESTAMP

RelnRul_End_DtTm TIMESTAMP

MVS_SYSTEM

MVS_SYSAPPL

PCHILD

2002-01-01-

00.00.00.000000

9999-01-01-00.00.00.000000

 

6.1.6 Component relationship (table CompReln)

CompReln_ID INTEGER

Comp_Source_ID INTEGER

Comp_Target_ID INTEGER

RelnTyp_Cd CHAR (6)

CompReln_Strt_DtTm TIMESTAMP

CompReln_End_DtTm TIMESTAMP

MSrc_Corr_Cd CHAR (6)

1

1

2

PCHILD

2002-01-01-

00.00.00.000000

9999-01-01-00.00.00.000000

SHARED

 

6.1.7 Component type keyword (table CompTyp_Keyword)

This table is not used by this warehouse pack.

6.1.8 Attribute type (table AttrTyp)

AttrTyp_Cd CHAR (17)

AttrTyp_Nm * VARCHAR (120)

MSrc_Corr_Cd CHAR (6)

MVS_SYSAPPL_TYPE

MVS System Application Type

MODEL1

* This column is translated.

If your application does not need the attribute type, delete that row from the table.

If you need to enumerate the valid values for an attribute, add a third column to the table.

If the attributes can be separated into groups, subdivide the table into groups, putting a single row (with merged cells) in between groups, and put the label for that group in the single separator row.

6.1.9 Attribute rule (table AttrRul)

CompTyp_Cd CHAR (17)

AttrTyp_Cd CHAR (17)

AttrRul_Strt_DtTm TIMESTAMP

AttrRul_End_DtTm TIMESTAMP

AttrTyp_Multi_Val CHAR (1)

AttrRul_Dom_Ind CHAR (1)

MVS_SYSAPPL

MVS_SYSAPPL_TYPE

2002-01-01-00.00.00.000000

9999-01-01-00.00.00.000000

N

N

If your application does not have the IP_HOST attribute, delete its rule from the table.

6.1.10 Attribute domain (table AttrDom)

This table is not used by this warehouse pack.

6.1.11 Component attribute (table CompAttr)

CompAttr_ID INTEGER

Comp_ID INTEGER

AttrTyp_Cd CHAR (17)

CompAttr_Strt_DtTm TIMESTAMP

CompAttr_End_DtTm TIMESTAMP

CompAttr_Val VARCHAR (254)

MSrc_Corr_Cd CHAR (6)

1

      2

 

MVS_SYSAPPL_TYPE

2002-01-01

00.00.00.000000

9999-01-01

00.00.00.000000

RACF

SHARED

6.1.12 Component type relationship (table CTypReln)

This table is not used by this warehouse pack.

6.1.13 Component attribute type relationship (table ATypReln)

This table is not used by this warehouse pack.

 


6.2 Component measurement

The component measurement tables are strictly for applications that want to store measurement data. These tables are not for event data. If you do not use the component measurement tables, delete these tables.

The following sections describe the component measurement.

6.2.1 Measurement group type (table MGrpTyp)

MGrpTyp_Cd CHAR (6)

MGrpTyp_Nm * VARCHAR (120)

CATEG

Category

GROUP

Aggregate Types or Group Functions

*This column is translated.

6.2.2 Measurement group (table MGrp)

MGrp_Cd CHAR (6)

MGrpTyp_Cd CHAR (6)

MGrp_Parent_Cd CHAR (6)

MGrp_Nm * VARCHAR (120)

UTIL

CATEG

 

Utilization

TOT_E

GROUP

 

Total Value Exists

*This column is translated.

Delete measurement groups that your application does not use.

6.2.3 Measurement group member (table MGrpMbr)

MGrp_Cd CHAR (6)

MGrpTyp_Cd CHAR (6)

MsmtTyp_ID INTEGER

UTIL

CATEG

1-10

TOT_E

GROUP

1-10

 

Delete measurement group members that your application does not use. Consolidate group type values by using this example text: "The following metrics: 12, 17, 26, 30" or "All metrics except the following: 23, 29, 45". This reduces the amount of rows in the table.

6.2.4 Measurement unit category (table MUnitCat)

MunitCat_Cd CHAR (6)

MunitCat_Nm * VARCHAR (120)

QTY

Quantity

*This column is translated.

Delete measurement unit categories that your application does not use.

6.2.5 Measurement unit (table MUnit)

MUnit_Cd CHAR (6)

MUnitCat_Cd CHAR (6)

Munit_Nm * VARCHAR (120)

QTY

QTY

Quantity

*This column is translated.

 

 

 

Delete measurement units that your application does not use.

6.2.6 Measurement alias names (table MTypReln)

This table is not used by this warehouse pack.

6.2.7 Time summary (table TmSum)

Delete time summary values that your application does not use.

The period over which a measurement may be summarized.

TmSum_Cd CHAR (1)

TmSum_Nm * VARCHAR (120)

H

Hourly

*This column is translated.

6.2.8 Measurement source (table MSrc)

MSrc_Cd CHAR (6)

MSrc_Parent_Cd CHAR (6)

MSrc_Nm  VARCHAR (120)

SHARED

 

Shared

MODEL1

 

Tivoli Common Data Model V1

Tivoli

 

Tivoli Application

DRL

Tivoli

Tivoli Decision Support for OS/390

D09

DRL

Tivoli Decision Support for OS/390 (RACF component)

6.2.9 Measurement source history (table MSrcHistory)

This table is not used by this warehouse pack.

6.2.10 Measurement type (table MsmtTyp)

 

MsmtTyp_ID INTEGER

MUnit_Cd CHAR (6)

MSrc_Cd CHAR  (6)

MsmtTyp_Nm * VARCHAR (120)

MsmtTyp_Ds * VARCHAR (254)

1

QTY

D09

RACF Logon Violations

Total user logon violations

2

QTY

D09

RACF Logon Violations - Undefined User

Total user logon violations, undefined user

3

QTY

D09

RACF Logon Violations - Invalid Password

Total user logon violations, invalid password

4

QTY

D09

RACF Resource Access Successes

Total resource access successes

5

QTY

D09

RACF Resource Access Warnings

Total resource access warnings

6

QTY

D09

RACF Resource Access Violations

Total resource access violations

7

QTY

D09

RACF Resource Access OPERATIONS users

Total resource accesses by user with OPERATIONS attribute

8

QTY

D09

RACF Commands By SPECIAL Users

 

Total RACF commands issued by user with SPECIAL attribute

9

QTY

D09

RACF Commands By AUDITOR Users

Total RACF commands issued by user with AUDITOR attribute

 

10

QTY

D09

RACF Insufficient Authority Failures

Total RACF Insufficient Authority Failures because of insufficient authority

*This column is translated.

Refer to Measurement unit (table MUnit) for the values of the MUnit_Cd column.

6.2.11 Component measurement rule (table MsmtRul)

CompTyp_Cd CHAR (17)

MsmtTyp_ID INTEGER

MVS_SYSTEM

1-10

MVS_SYSAPPL

1-10

 

6.2.12 Measurement (table Msmt)

Msmt_ID BIGINT

Comp_ID INTEGER

MsmtTyp_ID INTEGER

TmSum_Cd CHAR (1)

Msmt_Strt_Dt DATE

Msmt_Strt_Tm TIME

Msmt_Min_Val FLOAT

Msmt_Max_Val FLOAT

Msmt_Avg_Val FLOAT

Msmt_Tot_Val FLOAT

Msmt_Smpl_Cnt INTEGER

Msmt_Err_Cnt INTEGER

Msmt_stddev_Val DOUBLE

MSrc_Corr_Cd CHAR (6)

1

1

3

H

2002-02-05

09.00.00

 

 

 

5

 

 

 

D09

2

2

4

H

2002-02-05

09.00.00

 

 

 

4

 

 

 

D09

3

1

6

H

2002-02-05

09.00.00

 

 

 

1

 

 

 

D09

 

 

 

 

 

 

 

 

 

 

 

 

 

 

6.2.13 Threshold measurement objective (table Mobj)

This table is not used by this warehouse pack.

6.2.14 Threshold measurement objective range (table MobjRng)

This table is not used by this warehouse pack.

6.2.15 Threshold severity level (table SevLvl)

This table is not used by this warehouse pack.

 


6.3 Component events

The component event tables are strictly for applications that want to store event data. These tables are not for measurement data. If you do not use the component event tables, delete these tables.

There are no component events for this warehouse pack.

6.4 Helper tables

These tables are not used by this warehouse pack.

Helper tables are unique to each application. If helper tables are being utilized, descriptive information should be provided. If not part of the warehouse pack, state “This warehouse pack does not have helper tables.”

6.5 Exception tables

These tables are not used by this warehouse pack.

Include descriptive information for all possible exceptions to assist with debugging and serviceability. If not part of the warehouse pack, state “This warehouse pack does not have exception tables.”

6.6 Incremental extraction

Data extraction into Tivoli Data Warehouse is done in an incremental way.

New data from the source database is loaded into the data warehouse by checking that the existing measurements for a component are older than the new available ones.

The following columns d09.stage_cntl table store this information:

·         cntl_comp_id (INTEGER)

·         cntl_dttm (TIMESTAMP)

 

When loading measurements, this control table checks each comp_id, and accepts only those with a newer timestamp.

After successful loading of the measurement data, this control table is updated with the last timestamp present in the twg.msmt table for each comp_id.

Applications should describe their design for incremental extracts in this section. If not part of the warehouse pack, state “This warehouse pack does not have incremental extraction.”

For example, you could state something like: “This warehouse pack uses incremental extraction to extract data from the central data warehouse and store it into the data mart tables. The data in the TWG.Extract_Control table controls this process.” Then you can provide what the entries would be in the TWG.Extract_Control table. Here is an example from WebLogic:

 

.

 

 

 

 


Notices

DEVELOPERS: Do not change this information.

WRITERS: Verify that these notices are up to date.

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX  78758        U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

Add or delete entries from these lists as appropriate for how you have included trademarks in your document. Also, remove special statements if they trademarks are not used (SET, for example).

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, DB2, DRDA, Informix, OS/2, OS/400, Tivoli Enterprise Console, RACF and TME are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both.

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

 

 Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

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


 

 

Printed in U.S.A.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

SH19-8512-00