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 (DB2)â. 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 DB2 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.
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)
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.
<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, (vol.
I),Version 1., SH19-6819
Provides reference
information for the System Performance feature, describes the component tables
and lookup tables associated with the feature, and provides a detailed
explanation of how the feature process 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.
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.
The following sections describe additional publications to help you
understand and use Tivoli Data Warehouse.
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.
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.
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.
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/
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.
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
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.
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
The following sections provide an
overview of Tivoli Data Warehouse and the warehouse pack for Tivoli Decision
Support for OS/390 DB2 Component.
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.
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 also 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.
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
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)
|
|
DB2_SYSTEM_T
|
MVS_SYSTEM_ID
|
(C) ‘MVS_SYSTEM’
|
|
DB2_SYSTEM_ID
|
(C)
‘MVS_SUBSYSTEM’
|
|
‘DB2’
|
(A)
‘MVS_SUBSYS_TYPE’
|
|
SRB_TIME_DBM1+SRB_TIME_DIST+
SRB_TIME_IRLM+SRB_TIME_MSTR+
TCB_TIME_DBM1+TCB_TIME_DIST+
TCB_TIME_IRLM+TCB_TIME_MSTR
|
(M) 'DB2 CPU
Time'
|
|
(TCB_TIME_DBM1+SRB_TIME_DBM1)*100
/(TCB_TIME_DBM1+TCB_TIME_MSTR+
TCB_TIME_DIST+TCB_TIME_IRLM+
SRB_TIME_DBM1+SRB_TIME_MSTR+
SRB_TIME_DIST+SRB_TIME_IRLM)
|
(M) 'DB2 CPU
Utilization (DBM1 Address Space)'
|
|
(TCB_TIME_MSTR+SRB_TIME_MSTR)*100/(
TCB_TIME_DBM1+TCB_TIME_MSTR
+TCB_TIME_DIST+TCB_TIME_IRLM
+SRB_TIME_DBM1+SRB_TIME_MSTR
+SRB_TIME_DIST+SRB_TIME_IRLM)
|
(M) 'DB2 CPU
Utilization (MSTR Address Space)'
|
|
(TCB_TIME_DIST+SRB_TIME_DIST)*100/
(TCB_TIME_DBM1+TCB_TIME_MSTR+
TCB_TIME_DIST+TCB_TIME_IRLM+
SRB_TIME_DBM1+SRB_TIME_MSTR+
SRB_TIME_DIST+SRB_TIME_IRLM)
|
(M) 'DB2 CPU
Utilization (DIST Address Space)'
|
|
(TCB_TIME_IRLM+SRB_TIME_IRLM)*100/
(TCB_TIME_DBM1+TCB_TIME_MSTR+
TCB_TIME_DIST+TCB_TIME_IRLM+
SRB_TIME_DBM1+SRB_TIME_MSTR+
SRB_TIME_DIST+SRB_TIME_IRLM)
|
(M) 'DB2 CPU
Utilization (IRLM Address Space)'
|
|
IDENTIFY
|
(M) 'DB2
Successful Identify Requests'
|
|
SIGNON
|
(M) 'DB2
Successful Sign-On Requests'
|
|
CREATE_THREAD
|
(M) 'DB2 User
Threads'
|
|
WRITES_NOWAIT+WRITES_FORCE
|
(M) 'DB2 Log
Writes'
|
|
COMMAND_COUNT
|
(M) 'DB2
Commands'
|
|
DB2_DATABASE_T
|
MVS_SYSTEM_ID
|
(C) ‘MVS_SYSTEM’
|
|
DB2_SYSTEM_ID
|
(C)
‘MVS_SUBSYSTEM’
|
|
‘DB2’
|
(A)
‘MVS_SUBSYS_TYPE’
|
|
(EDM_REQ_DBD-EDM_LOAD_DBD)*100/
EDM_REQ_DBD
|
(M) 'DB2
Database Descriptors Read Efficiency'
|
|
(EDM_REQ_CT_SECT-EDM_LOAD_CT_SECT)*100/
EDM_REQ_CT_SECT
|
(M) 'DB2 Cursor
Table Read Efficiency'
|
|
(EDM_REQ_PT_SECT-EDM_LOAD_PT_SECT)*100/
EDM_REQ_PT_SECT
|
(M) 'DB2 Package
Table Read_Efficiency'
|
|
(EDM_POOL_SIZE-EDM_PAGES_FREE)*100/
EDM_POOL_SIZE
|
(M) 'DB2 EDM
Pool Utilization Percentage'
|
|
SQL_CLOSE+
SQL_DELETE+
SQL_DESCRIBE+SQL_DESCRIBE_TABLE+
SQL_FETCH+SQL_INSERT+
SQL_OPEN+SQL_PREPARE+
SQL_SELECT+SQL_UPDATE
|
(M) 'DB2 DML
Type SQL Statements'
|
|
SQL_ALTER_DATABASE+SQL_ALTER_INDEX+
SQL_ALTER_STOGROUP+SQL_ALTER_TABLE+
SQL_ALTER_TS+SQL_ALTER_FUNCTION+
SQL_ALTER_PROC+SQL_COMMENT_ON+
SQL_CREATE_ALIAS+SQL_CREATE_DATABAS+
SQL_CREATE_INDEX+SQL_CREATE_STG+
SQL_CREATE_SYNONYM+SQL_CREATE_VIEW+
SQL_CREATE_AUX_TAB+SQL_CRT_DIST_TYPE+
SQL_CREATE_FUNCT+SQL_CRT_PROCEDURE+
SQL_CREATE_TRIGGER+SQL_DROP_ALIAS+
SQL_DROP_DATABASE+SQL_DROP_INDEX+
SQL_DROP_PACKAGE+SQL_DROP_STOGROUP+
SQL_DROP_SYNONYM+SQL_DROP_TABLE+
SQL_DROP_TS+SQL_DROP_VIEW+
SQL_DROP_DIST_TYPE+SQL_DROP_FUNCTION+
SQL_DROP_PROCEDURE+SQL_DROP_TRIGGER+
SQL_LABEL_ON
|
(M) 'DB2 DDL Type SQL Statements'
|
|
DB2_US_TRAN_SHAR_H
|
SQL_GRANT+SQL_REVOKE+SQL_LOCK_TABLE
|
(M) 'DB2 Control
Type SQL Statements'
|
|
PLAN_ALLOC_SUCC
|
(M) 'DB2 Plan
Allocations'
|
|
PLANS_BOUND+PKG_BOUND
|
(M) 'DB2 Plans
And Packages Bound'
|
|
PLANS_REBOUND+PKG_REBOUND
|
(M) 'DB2 Plan
And Packages Rebound'
|
|
LOCK_REQUESTS
|
(M) 'DB2 IRLM
Lock Requests'
|
|
DEADLOCKS
|
(M) 'DB2 Deadlocks'
|
|
LOCK_SUSPENDS
|
(M) 'DB2 Lock
Suspends'
|
|
LOCK_TIMEOUTS
|
(M) 'DB2 Lock
Timeouts'
|
|
LOCK_ESCAL_SHARED+LOCK_ESCAL_EXCL
|
(M) 'DB2 Lock
Escalations'
|
|
MVS_SYSTEM_ID
|
(C) ‘MVS_SYSTEM’
|
|
DB2_SYSTEM_ID
|
(C)
‘MVS_SUBSYSTEM’
|
|
‘DB2’
|
(A)
‘MVS_SUBSYS_TYPE’
|
|
SH_LOCK_REQS
|
(M) 'DB2 Lock
Requests'
|
|
SH_UNLOCK_REQS
|
(M) 'DB2 Unlock
Requests'
|
|
SH_CHANGE_REQS
|
(M) 'DB2 Change
Requests'
|
|
DB2_SYS_PARAMETER
|
MVS_SYSTEM_ID
|
(C) ‘MVS_SYSTEM’
|
|
DB2_SYSTEM_ID
|
(C)
‘MVS_SUBSYSTEM’
|
|
‘DB2’
|
(A)
‘MVS_SUBSYS_TYPE’
|
|
SERVICE_UNIT_LIMIT
|
(M) 'DB2 Service
Units Limit'
|
|
MONITOR_BFR_SIZE
|
(M) 'DB2 Monitor
Buffer Size'
|
|
LOG_OPUT_BFR_SIZE
|
(M) 'DB2 Log
Output Buffer Pool Size'
|
|
LOG_INPUT_BFR_SIZE
|
(M) 'DB2 Log
Input Buffer Pool Size '
|
|
DB2_USER_TRAN_H
|
MVS_SYSTEM_ID
|
(C) ‘MVS_SYSTEM’
|
|
DB2_SYSTEM_ID
|
(C)
‘MVS_SUBSYSTEM’
|
|
‘DB2’
|
(A)
‘MVS_SUBSYS_TYPE’
|
|
APPLICATION_NAME
|
(C) ‘D05_APPL’
|
|
ELAPSED_SEC/(COMMIT_COUNT+ABORT_COUNT)
|
(M) 'DB2 Elapsed
Time'
|
|
COMMIT_COUNT
|
(M) 'DB2 Commit
Count'
|
|
ABORT_COUNT
|
(M) 'DB2 Abort
Count'
|
|
(IO_WAIT_SEC+OTHER_READ_SEC+OTHER_WRITE_SEC)/(COMMIT_COUNT+ABORT_COUNT)
|
(M) 'DB2 Other
I/O Wait Time '
|
|
SERVICE_TASK_SEC/(COMMIT_COUNT+ABORT_COUNT)
|
(M) 'DB2 Service
Wait Time'
|
|
TCB_SEC/(COMMIT_COUNT+ABORT_COUNT)
|
(M) 'DB2 Average
TCB Seconds'
|
|
SRB_SEC/(COMMIT_COUNT+ABORT_COUNT)
|
(M) 'DB2 Average
SRB Seconds'
|
|
LOCK_LATCH_SEC/(COMMIT_COUNT+
ABORT_COUNT)
|
(M) 'DB2
Lock/Latch Time’
|
|
ARC_LOGWAIT_SEC/(COMMIT_COUNT+
ABORT_COUNT)
|
(M) 'DB2 Archive
Log Wait Time'
|
|
ARC_LOGREAD_SEC/(COMMIT_COUNT+
ABORT_COUNT)
|
(M) 'DB2 Archive
Log Read Time'
|
|
(DRAIN_LOCK_SEC
+ DRAIN_WAIT_SEC)
/(COMMIT_COUNT+B.ABORT_COUNT)
|
(M) 'DB2 Drain
Time'
|
|
UDF_EXECUTED
|
(M) 'DB2 User
Defined Functions Executed'
|
|
UDF_ABENDED
|
(M) 'DB2 User
defined Functions Abended'
|
|
UDF_TIMED_OUT
|
(M) 'DB2 User
Defined Functions Timed out'
|
|
UDF_REJECTED
|
(M) 'DB2 User
Defined Functions Rejected'
|
|
ACTIV_SQL_TRIGGER
|
(M) 'DB2
Statement Triggers Activated'
|
|
ACTIV_ROW_TRIGGER
|
(M) 'DB2 Row
Triggers Activated'
|
|
TRIGGER_ERRORS
|
(M) 'DB2 Trigger
Errors'
|
|
IO_WAIT_LOGWRT_SEC
/(COMMIT_COUNT+ABORT_COUNT)
|
(M) 'DB2 Log Write I/O Time'
|
|
DB2_BUFFER_POOL_T
|
IO_WAIT_DB_SEC
/(COMMIT_COUNT+ABORT_COUNT)
|
(M) 'DB2
Database I/O Wait Time'
|
|
MVS_SYSTEM_ID
|
(C) ‘MVS_SYSTEM’
|
|
DB2_SYSTEM_ID
|
(C)
‘MVS_SUBSYSTEM’
|
|
'BP'!!CHAR(BUFFER_POOL_ID)
|
(C)
‘D05_BF_POOL’
|
|
‘DB2’
|
(A)
‘MVS_SUBSYS_TYPE’
|
|
SYNC_READ_IO
|
(M) 'DB2
Synchronous Reads'
|
|
SEQ_PREFETCH_REQ
|
(M) 'DB2
Sequential Prefetch Requests'
|
|
LIST_PREFETCH
|
(M) 'DB2 List
Prefetch Requests'
|
|
BUFFER_UPDATES
|
(M) 'DB2 Buffer
Updates'
|
|
PAGES_WRITTEN
|
(M) 'DB2 Pages
Written'
|
|
ASYNC_WRITE_IO
|
(M) 'DB2
Asynchronous Writes'
|
|
DATASET_OPENS
|
(M) 'DB2 Data
Set OPENs Performed'
|
|
(GETPAGE-SYNC_READ_IO)*100
/GETPAGE
|
(M) 'DB2 Buffer
Pool Read Efficiency'
|
|
(1-(SPTH_REACHED+NO_READ_ENGINE))
/SEQ_PREFETCH_REQ*100
|
(M) 'DB2
Prefetch Availability'
|
|
(1-(SYNC_WRITE_IO+ASYNC_WRITE_IO))
/PAGES_WRITTEN*100
|
(M) 'DB2 DASD
Write Efficiency'
|
|
(1-PAGES_WRITTEN)
/BUFFER_UPDATES*100
|
(M) 'DB2 Buffer
Update Efficiency'
|
|
DB2_BP_SHARING_T
|
MVS_SYSTEM_ID
|
(C) ‘MVS_SYSTEM’
|
|
DB2_SYSTEM_ID
|
(C)
‘MVS_SUBSYSTEM’
|
|
‘DB2’
|
(A)
‘MVS_SUBSYS_TYPE’
|
|
'BP'!!CHAR(BUFFER_POOL_ID)
|
(C)
‘D05_BF_POOL’
|
|
CHG_PGS_SYN_WRTN
|
(M) 'DB2 Changed
Pages Synchronously Written'
|
|
CHG_PGS_ASYN_WRTN
|
(M) 'DB2 Changed
Pages Asynchronously Written'
|
|
CLEAN_PGS_SYN_WRTN
|
(M) 'DB2 Clean
Pages Synchronously Written'
|
|
CLEAN_PGS_ASYN_WRT
|
(M) 'DB2 Clean
Pages Asynchronously Written'
|
|
READ_FAILED_NOSTOR
|
(M) 'DB2 Read
Failed No Storage'
|
|
WRIT_FAILED_NOSTOR
|
(M) 'DB2 Write
Failed No Storage'
|
|
REG_PG_LIST_RPL
|
(M) 'DB2
Requests To Register A Page List '
|
|
DB2_PACKAGE_H (1)
|
MVS_SYSTEM_ID
|
(C) ‘MVS_SYSTEM’
|
|
DB2_SYSTEM_ID
|
(C)
‘MVS_SUBSYSTEM’
|
|
‘DB2’
|
(A)
‘MVS_SUBSYS_TYPE’
|
|
DB2_PACKAGE
|
(C) ‘D05_PKG’
|
|
PACKAGE_SQL
|
(M) 'DB2 SQL
Statements'
|
|
AVAILABILITY_T (2)
|
Count(Substr(INTERVAL_TYPE,1,1)
= '|’)
|
(M) ‘DB2
Resource Starts’
|
|
Count(Substr(INTERVAL_TYPE,3,1)
= '|’)
|
(M) ‘DB2
Resource Stops’
|
|
((DAYS(END_TIME)*60*24)+(MIDNIGHT_SECONDS(END_TIME)/60))- ((DAYS(START_TIME)*60*24)+(MIDNIGHT_SECONDS(.START_TIME)/60))
(where INTERVAL_TYPE IN
('===','==|','|=|'))
|
(M) 'Available'
|
|
((DAYS(END_TIME)*60*24)+(MIDNIGHT_SECONDS(END_TIME)/60))-
((DAYS(START_TIME)*60*24)+(MIDNIGHT_SECONDS(.START_TIME)/60))
(where
INTERVAL_TYPE = (' ') and previous recorded
INTERVAL_TYPE = ('==!'))
|
(M) 'Unavailable’
|
|
((DAYS(END_TIME)*60*24)+(MIDNIGHT_SECONDS(END_TIME)/60))-
((DAYS(START_TIME)*60*24)+(MIDNIGHT_SECONDS(.START_TIME)/60))
(where INTERVAL_TYPE = (' ‘))
|
(M) 'Unknown'
|
Note
(1): Defining the D05_PKG component and every
measurement related to it, we use the
DB2_PACKAGE_H table joined with the DB2_USER_TRAN_H table.
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.
This section describes the installation
and configuration of the warehouse pack.
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 DB2 component, you must install the
following software:
·
IBM Tivoli Decision Support for OS/390
Version 1.6 System performance feature with the following component:
Ø
DB2 component
Ø
MVS availability 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/
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.
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 the central data warehouse, space for the
historical data. See below for an example showing how the user calculates that
value.
· In the data mart, space for summarized data.
· In the control database on the control server,
space for metadata defining data marts and reports.
· In your application's operational data sources,
space for tables that are created by the warehouse pack. (Not all applications
do this.)
· In <specify database>, space for staging
tables. The staging tables usually are approximately equivalent to 1 day’s
worth of database space.
· Any other space requirements you have.
· If possible, provide formulas and worksheets.
In summary what is
really needed for each database (TWH_CDW, TWH_MART and TWH_MD) is:
· An estimate of the number of rows of data in
key tables based on size of the environment (Comp, Comptyp, Msmtyp)
· A formula to calculate the base database size.
· An estimate of the number of rows of data
inserted into key tables based on the number of Measurements per day (i.e Msmt)
· A formula for calculating the daily size growth
of the database.
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.>
To collect MVS availability data for DB2
into Tivoli Decision support for OS/390 you must configure the MVS_AVAIL_RESOURCE
lookup table. The following can be used as a sample:
|
MVS_SYSTEM_ID
|
SUBSYSTEM_ID
|
JOB_NAME
|
RESOURCE_TYPE
|
RESOURCE_NAME
|
|
|
%
|
%
|
OTHER
|
OTHER
|
|
ESJ4
|
STC
|
DSN%
|
SUBSYS
|
DB2G
|
|
ESJ4
|
DB2
|
%
|
SUBSYS
|
DB2G
|
Where:
·
MVS_SYSTEM_ID: Name of your MVS system
(% can be used as a wildcard).
·
SUBSYSTEM_ID: Subsystem type or name
(% can be used as a wildcard) as defined in SYS1.PARMLIB(IEAICSxx) member. For
subsystems not explicitly defined in this member, the STC type is used, leaving
the details in the JOB_NAME column.
·
JOB_NAME: Name of the job for which you would measure
availability (% can be used as a wildcard).
·
RESOURCE_TYPE: In this field you must
specify “SUBSYS” for the MVS resources
for which you want to collect availability data.
·
RESOURCE_NAME: The name used as a
component name in Tivoli Data Warehouse for MVS data. For correlation purposes
with other measurements, ensure that this name is a subsystem identifier.
Note: to have availability
data for the DB2 MVS Subsystem loaded into the
central data warehouse you need to specify a RESOURCE_NAME in the
MVS_AVAIL_RESOURCE table that refer to the subsystem names of your MVS
Subsystem.
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.
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 central data warehouse (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\d05\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.
Complete the following post-installation
procedures.
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
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.
This
warehouse pack has no migration from previous release.
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 packs” 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\d05\v1200\misc directory, the name is d05_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 you must open a DB2 Command Window and
enter the following command from the twh\apps\d05\v1200\misc directory:
db2 –z
<your logfile name> -tvf d05_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.
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 ID
|
|
Name of lookup
table
|
D05.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.
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
|
D05.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.
Describe any maintenance tasks required
for this warehouse pack.
This section describes maintenance tasks
for the warehouse pack.
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 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.
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..
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)
|
|
D05
|
P
|
100
|
|
D05
|
H
|
100
|
|
D05
|
D
|
300
|
|
D05
|
W
|
10000
|
|
D05
|
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).
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 they define your process in the Data Warehouse
Center. Tivoli Data Warehouse provides
standard maintenance to its subdirectories and processes, if not modified.
Refer 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.
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.
The warehouse pack has the following
process:
·
D05_c05_DB2 _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:
·
D05_c05_s010_processDB2
This step
populates the component table (Comp table), the component attribute table
(CompAttr table) and the component relationship table (CompReln table).
·
D05_c05_s020_processDB2
This step
populates the measurement table (Msmt table).
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.
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.
|
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_SUBSYSTEM
|
|
MVS Subsystem
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
MODEL1
|
|
D05_APPL
|
|
Application Name
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
|
D05_BF_POOL
|
|
Buffer Pool
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
|
D05_PKG
|
|
Package Name
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
|
* 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.
This
table is not used by this warehouse pack.
|
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
|
|
SY4B
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
SHARED
|
|
2
|
MVS_SYSTEM
|
CDW
|
1
|
|
ESJ4
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
SHARED
|
|
3
|
MVS_SUBSYSTEM
|
CDW
|
1
|
|
DSN7
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
SHARED
|
|
4
|
MVS_SUBSYSTEM
|
CDW
|
1
|
|
DB2G
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
SHARED
|
|
5
|
D05_APPL
|
CDW
|
1
|
|
SPUFI RR
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D05
|
|
6
|
D05_APPL
|
CDW
|
1
|
|
DIST SERVER
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D05
|
|
7
|
D05_APPL
|
CDW
|
1
|
|
OTHER
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D05
|
|
8
|
D05_BF_POOL
|
CDW
|
1
|
|
BP0
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D05
|
|
9
|
D05_BF_POOL
|
CDW
|
1
|
|
BP1
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D05
|
|
12
|
D05_PKG
|
CDW
|
1
|
|
JEEPONE
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D05
|
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 Wep, it is built using
the following structure:
CompType_Cd Component
instance Comp_Corr_Val
MVS_SYSTEM mvs_system_id ----
MVS_SUBSYSTEM subsystem_id "MVS - mvs_system_id"
D05_APPL appl_name "MVS - mvs_system_id - SUBS - db2_subsystem_id"
D05_PKG pkg_name "MVS - mvs_system_id
- SUBS - db2_subsystem_id - APPL –
application_name"
D05_BF_POOL bf_pool_id "MVS - mvs_system_id - SUBS - db2_subsystem_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 1to 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.
|
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.
|
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_SUBSYSTEM
|
PCHILD
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
MVS_SUBSYSTEM
|
D05_APPL
|
PCHILD
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
MVS_SUBSYSTEM
|
D05_BF_POOL
|
PCHILD
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D05_APPL
|
D05_PKG
|
PCHILD
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
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
|
4
|
PCHILD
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
SHARED
|
|
2
|
2
|
3
|
PCHILD
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
SHARED
|
|
3
|
3
|
5
|
PCHILD
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
|
4
|
3
|
6
|
PCHILD
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
|
5
|
4
|
7
|
PCHILD
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
|
6
|
3
|
8
|
PCHILD
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
|
7
|
4
|
9
|
PCHILD
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
|
8
|
3
|
10
|
PCHILD
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
|
9
|
4
|
11
|
PCHILD
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
|
10
|
7
|
12
|
PCHILD
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D05
|
This table is not used by
this warehouse pack.
|
AttrTyp_Cd
CHAR (17)
|
AttrTyp_Nm
* VARCHAR (120)
|
MSrc_Corr_Cd
CHAR (6)
|
|
MVS_SUBSYS_TYPE
|
MVS Subsystem 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.
|
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_SUBSYSTEM
|
MVS_SUBSYS_TYPE
|
2002-01-01-00.00.000000
|
9999-01-01-00.00.000000
|
N
|
N
|
If your application does not have the
IP_HOST attribute, delete its rule from the table.
This table is not used by this warehouse
pack.
|
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
|
3
|
MVS_SUBSYS_TYPE
|
2003-03-11-14.09.48.713047
|
9999-01-01-00.00.00.000000
|
DB2
|
SHARED
|
This
table is not used by this warehouse pack.
This
table is not used by this warehouse pack.
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.
|
MGrpTyp_Cd
CHAR (6)
|
MGrpTyp_Nm
* VARCHAR (120)
|
|
CATEG
|
Category
|
|
GROUP
|
Aggregate Types or Group
Functions
|
|
TRANS
|
State Transition Groups
|
|
* This column is
translated.
|
|
MGrp_Cd
CHAR (6)
|
MGrpTyp_Cd
CHAR (6)
|
MGrp_Parent_Cd
CHAR (6)
|
MGrp_Nm
* VARCHAR (120)
|
|
PERF
|
CATEG
|
|
Performance
|
|
UTIL
|
CATEG
|
|
Utilization
|
|
D05IC1
|
TRANS
|
|
DB2 Subsystem State
Transition Measurements
|
|
AVG_E
|
GROUP
|
|
Average Value Exists
|
|
MIN_E
|
GROUP
|
|
Minimum Value Exists
|
|
MAX_E
|
GROUP
|
|
Maximum Value Exists
|
|
TOT_E
|
GROUP
|
|
Total Value Exists
|
|
* This column is
translated.
|
Delete measurement groups that your
application does not use.
|
MGrp_Cd CHAR (6)
|
MGrpTyp_Cd CHAR (6)
|
MsmtTyp_ID INTEGER
|
|
UTIL
|
CATEG
|
12-72
|
|
PERF
|
CATEG
|
1-11
|
|
D05IC1
|
TRANS
|
73-75
|
|
AVG_E
|
GROUP
|
1,4-11,13-20,40-43,51-54,69-70
|
|
MIN_E
|
GROUP
|
1,4-11,13-20,40-43,51-54,69-70
|
|
MAX_E
|
GROUP
|
1,4-11,13-20,40-43,51-54,69-70
|
|
TOT_E
|
GROUP
|
2-3,12,21-39,44-50,55-68,71-75
|
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.
|
MunitCat_Cd
CHAR (6)
|
MunitCat_Nm
* VARCHAR (120)
|
|
TM
|
Time Duration
|
|
QTY
|
Quantity
|
|
PRC
|
Percentage
|
|
* This column is
translated.
|
Delete measurement unit categories that
your application does not use.
|
MUnit_Cd
CHAR (6)
|
MUnitCat_Cd
CHAR (6)
|
Munit_Nm
* VARCHAR (120)
|
|
PRC
|
PRC
|
Percentage
|
|
QTY
|
QTY
|
Quantity
|
|
KB
|
QTY
|
Kilobytes
|
|
Sec
|
TM
|
Seconds
|
|
Min
|
TM
|
Minutes
|
|
* This column is
translated.
|
Delete measurement units that your
application does not use.
This
table is not used by this warehouse pack.
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
|
|
P
|
Period
|
|
* This column is
translated.
|
|
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
|
|
|
|
|
This table is not used by this warehouse pack.
|
MsmtTyp_ID
INTEGER
|
MUnit_Cd
CHAR (6)
|
MSrc_Cd
CHAR (6)
|
MsmtTyp_Nm
* VARCHAR (120)
|
MsmtTyp_Ds
* VARCHAR (254)
|
|
1
|
Sec
|
D05
|
DB2 Elapsed Time
|
The elapsed time in seconds
|
|
2
|
QTY
|
D05
|
DB2 Commit Count
|
The number of commits that occurred
|
|
3
|
QTY
|
D05
|
DB2 Abort Count
|
The number of aborts that occurred
|
|
4
|
Sec
|
D05
|
DB2 Other I/O Wait Time
|
The I/O wait time for events other than
database and log write, in seconds
|
|
5
|
Sec
|
D05
|
DB2 Service Wait Time
|
The wait time due to synchronous unit switching to DB2 services, in
seconds
|
|
6
|
Sec
|
D05
|
DB2 Lock/Latch Time
|
The time spent in lock/latch management within DB2, in seconds
|
|
7
|
Sec
|
D05
|
DB2 Archive Log Wait Time
|
The wait time due to processing of ARCHIVE LOG MODE commands, in
seconds
|
|
8
|
Sec
|
D05
|
DB2 Archive Log Read Time
|
The wait time for an archive read from tape, in seconds
|
|
9
|
Sec
|
D05
|
DB2 Drain Time
|
The wait time for a drain or a drain lock, in seconds
|
|
10
|
Sec
|
D05
|
DB2 Log Write I/O Time
|
The wait time for log write I/O, in seconds
|
|
11
|
Sec
|
D05
|
DB2 Database I/O Wait Time
|
The wait time for database I/O, in seconds
|
|
12
|
Sec
|
D05
|
DB2 CPU Time
|
Total CPU time
|
|
13
|
PRC
|
D05
|
DB2 Database Descriptors Read Efficiency
|
The hit ratio for database descriptors (DBD) within the EDM pool (for
example, how often DB2 finds the required DBD in the EDM pool)
|
|
14
|
PRC
|
D05
|
DB2 Cursor Table Read Efficiency
|
The hit ratio for cursor table sections within the EDM pool (for
example, how often DB2 finds the required cursor table section in the EDM
pool)
|
|
15
|
PRC
|
D05
|
DB2 Package Table Read Efficiency
|
The hit ratio for package table sections
within the EDM pool (for example, how often DB2 finds the required package
table section in the EDM pool)
|
|
16
|
PRC
|
D05
|
DB2 EDM Pool Utilization Percentage
|
The utilization percentage of the EDM pool (for example, what
percentage of the EDM pool is used for database descriptors, cursor table
sections and package table sections
|
|
17
|
PRC
|
D05
|
DB2 CPU Utilization (DBM1 Address Space)
|
Relative CPU consumption for DBM1 address space
|
|
18
|
PRC
|
D05
|
DB2 CPU Utilization (MSTR Address Space)
|
Relative CPU consumption for MSTR address space
|
|
19
|
PRC
|
D05
|
DB2 CPU Utilization (DIST Address Space)
|
Relative CPU consumption for DIST address space
|
|
20
|
PRC
|
D05
|
DB2 CPU Utilization (IRLM Address Space)
|
Relative CPU consumption for IRLM address space
|
|
21
|
QTY
|
D05
|
DB2 Lock Requests
|
The number of lock requests for physical locks
|
|
22
|
QTY
|
D05
|
DB2 Unlock Requests
|
The number of unlock requests for physical locks
|
|
23
|
QTY
|
D05
|
DB2 Change Requests
|
The number of change requests for physical locks
|
|
24
|
QTY
|
D05
|
DB2 Successful Identify Requests
|
The number of successful identify requests. This is the number of
successful connections to DB2 by TSO, IMS, CICS, CAF, or a DB2 utility
|
|
25
|
QTY
|
D05
|
DB2 Successful Sign-On Requests
|
The number of successful sign-on requests by IMS or CICS
|
|
26
|
QTY
|
D05
|
DB2 User Threads
|
The number of successful create threads requests. This is the number
of threads created, excluding database access threads
|
|
27
|
QTY
|
D05
|
DB2 Log Writes
|
The total number of log write requests processed
|
|
28
|
QTY
|
D05
|
DB2 Commands
|
The number of all DB2 commands issued. This includes normal or
abnormal completion of the commands
|
|
29
|
QTY
|
D05
|
DB2 DML Type SQL Statements
|
The number of DML type SQL statements
|
|
30
|
QTY
|
D05
|
DB2 DDL Type SQL Statements
|
The number of DDL type SQL statements
|
|
31
|
QTY
|
D05
|
DB2 Control Type SQL
Statements
|
The number of control type SQL statements
|
|
32
|
QTY
|
D05
|
DB2 Plan Allocations
|
The number of successful plan allocations. This is the number of
times DB2 successfully completed requests by the user to create a thread by
the attachment facility
|
|
33
|
QTY
|
D05
|
DB2 Plans And Packages Bound
|
The number of plans and packages successfully bound
|
|
34
|
QTY
|
D05
|
DB2 Plans And Packages Rebound
|
The number of plans and packages successfully rebound
|
|
35
|
QTY
|
D05
|
DB2 IRLM Lock Requests
|
The number of IRLM lock requests issued
|
|
36
|
QTY
|
D05
|
DB2 Deadlocks
|
The number of times deadlocks were detected
|
|
37
|
QTY
|
D05
|
DB2 Lock Suspends
|
The number of lock suspends. This is the number of times a lock could
not be obtained because of a lock conflict and the unit of work was suspended
|
|
38
|
QTY
|
D05
|
DB2 Lock Timeouts
|
The number of lock timeouts. This is the number of times a unit of
work was suspended because a time exceeded the time-out value
|
|
39
|
QTY
|
D05
|
DB2 Lock Escalations
|
The total number of lock escalations (exclusive and shared mode)
|
|
40
|
QTY
|
D05
|
DB2 Service Units Limit
|
Maximum number of MVS service units that can be used for a thread
|
|
41
|
KB
|
D05
|
DB2 Monitor Buffer Size
|
Monitor trace buffer size, in kilobytes
|
|
42
|
KB
|
D05
|
DB2 Log Output Buffer Pool Size
|
Log output buffer pool size for writing active log data sets, in
kilobytes
|
|
43
|
KB
|
D05
|
DB2 Log Input Buffer Pool Size
|
Log input buffer pool size, in kilobytes
|
|
44
|
QTY
|
D05
|
DB2 Synchronous Reads
|
The number of synchronous read I/O operations
|
|
45
|
QTY
|
D05
|
DB2 Sequential Prefetch Requests
|
The number of sequential prefetch requests issued
|
|
46
|
QTY
|
D05
|
DB2 List Prefetch Requests
|
The number of list prefetch requests issued
|
|
47
|
QTY
|
D05
|
DB2 Buffer Updates
|
The number of times a buffer update occurred for system pages. This
is the number of updates performed against a page in the buffer pool
|
|
48
|
QTY
|
D05
|
DB2 Pages Written
|
The number of pages written for the buffer pool. This is the number
of pages in the buffer pool written to DASD
|
|
49
|
QTY
|
D05
|
DB2 Asynchronous Writes
|
The number of asynchronous write I/Os for the buffer pool
|
|
50
|
QTY
|
D05
|
DB2 Data Set OPENs performed
|
The number of data set OPENs performed successfully for the buffer
pool
|
|
51
|
PRC
|
D05
|
DB2 Buffer Pool Read Efficiency
|
The hit ratio within the buffer pool (for example, how often DB2
finds the required page in the buffer pool
|
|
52
|
PRC
|
D05
|
DB2 Prefetch Availability
|
The availability of the sequential prefetch mechanism
|
|
53
|
PRC
|
D05
|
DB2 DASD Write Efficiency
|
The DASD write efficiency
|
|
54
|
PRC
|
D05
|
DB2 Buffer Update Efficiency
|
The buffer update efficiency
|
|
55
|
QTY
|
D05
|
DB2 Changed Pages Synchronously Written
|
The number of changed pages synchronously written from the member
virtual pool to the group buffer pool
|
|
56
|
QTY
|
D05
|
DB2 Clean Pages Synchronously Written
|
The number of clean pages synchronously written from the member
virtual pool to the group buffer pool
|
|
57
|
QTY
|
D05
|
DB2 Changed Pages Asynchronously Written
|
The number of changed pages asynchronously written from the member
virtual pool to the group buffer pool
|
|
58
|
QTY
|
D05
|
DB2 Read Failed No Storage
|
The number of coupling facility read requests that could not complete
due to a lack of coupling facility storage resources
|
|
59
|
QTY
|
D05
|
DB2 Write Failed No Storage
|
The number of coupling facility write requests that could not
complete due to a lack of coupling facility storage resources
|
|
60
|
QTY
|
D05
|
DB2 Requests To Register A Page List
|
The number of requests to register a page list in the coupling
facility
|
|
61
|
QTY
|
D05
|
DB2 SQL Statements
|
The number of SQL statements for a package
|
|
62
|
QTY
|
D05
|
DB2 User Defined Functions Executed
|
The total number of user defined functions that were executed
|
|
63
|
QTY
|
D05
|
DB2 User Defined Functions Abended
|
The total number of times that a user defined function abended
|
|
64
|
QTY
|
D05
|
DB2 User Defined Functions Timed Out
|
The total number of times that a user defined function timed out
while waiting to be scheduled
|
|
65
|
QTY
|
D05
|
DB2 User Defined Functions Rejected
|
The total number of times that a user defined function was rejected
|
|
66
|
QTY
|
D05
|
DB2 Statement Triggers Activated
|
The total number of times that a statement trigger was activated
|
|
67
|
QTY
|
D05
|
DB2 Row Triggers Activated
|
The total number of times that a row
trigger was activated
|
|
68
|
QTY
|
D05
|
DB2 Trigger Errors
|
The total number of times that an SQL error occurred during the execution
of a trigger action
|
|
69
|
QTY
|
D05
|
DB2 Average TCB Seconds
|
The average CPU time used for TCB, in seconds
|
|
70
|
QTY
|
D05
|
DB2 Average SRB Seconds
|
The average CPU time used for SRB, in seconds
|
|
71
|
QTY
|
D05
|
DB2 Resource Starts
|
Number of times the resource started
|
|
72
|
QTY
|
D05
|
DB2 Resource Stops
|
Number of times the resource stopped
|
|
73
|
Min
|
MODEL1
|
Available
|
The amount of time that the resource is available
|
|
74
|
Min
|
MODEL1
|
Unavailable
|
The amount of time that the resource is not available
|
|
75
|
Min
|
MODEL1
|
Unknown
|
The amount of time that the state of the resource is unknown
|
|
*This column is translated.
|
Refer to Measurement
unit (table MUnit) for the values of the MUnit_Cd column.
|
CompTyp_Cd CHAR (17)
|
MsmtTyp_ID INTEGER
|
|
MVS_SUBSYSTEM
|
12-43,71-75
|
|
D05_APPL
|
1-11,62-70
|
|
D05_BF_POOL
|
44-60
|
|
D05_PKG
|
61
|
|
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
|
6
|
1
|
H
|
2002-02-05
|
08.00.00
|
0.34
|
0.44
|
0.39
|
|
|
|
|
D05
|
|
2
|
6
|
1
|
H
|
2002-02-05
|
16.00.00
|
0.33
|
0.47
|
0.43
|
|
|
|
|
D05
|
|
3
|
6
|
1
|
H
|
2002-02-05
|
18.00.00
|
1.3
|
1.3
|
1.3
|
|
|
|
|
D05
|
|
….
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This
table is not used by this warehouse pack.
This
table is not used by this warehouse pack.
This
table is not used by this warehouse pack.
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.
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.”
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.”
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 d05.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:
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, DB2
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.
Products for ISO-certified sites should
add their appropriate boilerplate. See your editor.
