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 (CICS)â.
This warehouse enablement pack (hereafter referred to as warehouse pack) is
created for Tivoli Data Warehouse, Version 1.2.
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, CICS Performance Feature Guide and Reference, Version 1.6,
SH19-6820
Provides information for
administrators and users about collecting and reporting performance data
generated by Customer Information and Control System (CICS®).
·
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 3.
·
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 CICS
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 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 figures 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 tables show 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)
|
|
CICS_A_BASIC_H
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
APPLICATION_NAME
|
(C) D04_APPL
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
RESPONSE_MIN_SEC, RESPONSE_MAX_SEC, RESPONSE_SUM_SEC /
RECORDS
|
(M) 'CICS Response Time for All Tasks'
|
|
DISPATCH_SEC / RECORDS
|
(M) 'CICS Dispatch Time'
|
|
DISPATCH_WAIT_SEC / RECORDS
|
(M) 'CICS Re-Dispatch Wait Time'
|
|
( TC_IO_WAIT_SEC + TS_IO_WAIT_SEC + TSSHWAIT_CLOCK +
TD_IO_WAIT_SEC + JC_IO_WAIT_SEC
+ FC_IO_WAIT_SEC + RLSWAIT_CLOCK +
CFDTWAIT_CLOCK + SOIOWTT_CLOCK +
MRO_WAIT_SEC + LU61_IO_WAIT_SEC + LU62_IO_WAIT_SEC + FE_WAIT_SEC +
DISPATCH_DELAY_SEC + ENQ_WAIT_SEC + GNQDELAY_CLOCK + ICDELAY_CLOCK +
LMDELAY_CLOCK + WTEXWAIT_CLOCK +
WTCEWAIT_CLOCK + GVUPWAIT_CLOCK + RMI_SUSPEND_SEC + RUNTRWTT_CLOCK +
SRVSYWTT_CLOCK + SYNCDLY_CLOCK + MAXOTDLY_CLOCK + RRMSWAIT_CLOCK ) / RECORDS
|
(M) 'CICS Dispatcher Suspended Time '
|
|
CICS_A_DBCTL_H
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
APPLICATION_NAME
|
(C) D04_APPL
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
DLI_CALL_CNT
|
(M) CICS DBCTL Calls
|
|
CICS_A_DLI_H
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
APPLICATION_NAME
|
(C) D04_APPL
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
CALL_CNT
|
(M) CICS DL/I Database Calls
|
|
CICS_S_DB2CONN_D
|
DB2_CONN_NAME
|
(C) D04_DB2CONN
|
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
DB2_GMT_DISC_TIME-DB2_GMT_CONN_TIME
|
(M)
‘CICS DB2 Connection Time’
|
|
DB2_TCB_LIMIT
|
(M)
‘CICS Task Control Block Limit’
|
|
DB2_TCB_HWM
|
(M)
‘CICS Subtask Task Control Blocks’
|
|
DB2_COMD_CALLS
|
(M)
‘CICS DB2 Commands ‘
|
|
CICS_S_DB2ENTRY_T
|
DB2_ENTRY_NAME
|
(C ) D04_DB2ENTRY
|
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
|
(C) MVS_SUBSYSTEM
|
|
|
(A) MVS_SUBSYS_TYPE
|
|
|
(M) ‘CICS SQL Calls’
|
|
DB2_SIGNONS
|
(M) ‘CICS DB2 Signons’
|
|
DB2_THREAD_LIMIT
|
(M) ‘CICS Threads Limit’
|
|
DB2_THREAD_HWM
|
(M) ‘CICS Active Threads ‘
|
|
DB2_TASK_HWM
|
(M) ‘CICS Tasks ‘
|
|
DB2_TASK_TOT
|
(M) ‘CICS Completed Tasks’
|
|
CICS_S_FILE_T
|
FILE_NAME
|
(C) D04_FILE
|
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
GET_REQUESTS + BROWSE_REQUESTS
|
(M) ‘CICS GET Requests’
|
|
ADD_REQUESTS + UPDATE_REQUESTS
|
(M) ‘CICS PUT Requests’
|
|
DELETE_REQ_LOCAL+ DELETE_REQ_REMOTE
|
(M) ‘CICS DELETE Requests’
|
|
VSAM_EXCP_REQ_DATA
|
(M) ‘CICS VSAM I/Os’
|
|
CICS_S_GLOBAL_T
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
LIBRARY_LOAD_REQ
(Statistics_Area = ‘LOADER’)
|
(M) ‘CICS MVS LOAD Requests’
|
|
LOAD_SEC (Statistics_Area = ‘LOADER’)
|
(M) ‘CICS Overall Library Load Time’
|
|
TS_MAIN_PUTS (Statistics_Area =‘TEMP_STORAGE’)
|
(M) ‘CICS Temporary Storage PUTs’
|
|
TS_MAIN_GETS (Statistics_Area =‘TEMP_STORAGE’)
|
(M) ‘CICS Temporary Storage GETs’
|
|
TS_MAIN_PEAK_BYTES
(Statistics_Area =‘TEMP_STORAGE’)
|
(M) ‘CICS Temporary Storage’
|
|
RPL_PEAK_USED (Statistics_Area =‘VTAM’)
|
(M) ‘CICS VTAM Request Parameter Lists Posted’
|
|
VTAM_SOS_COUNT (Statistics_Area =‘VTAM’)
|
(M) ‘CICS VTAM Short On Storage Events’
|
|
CICS_TRAN_USR_H
|
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) VS_SUBSYSTEM
|
|
TRANSACTION_ID
|
(C) D04_TRANS
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
RECORDS
|
(M) ‘CICS Transactions’
|
|
CPU_SUM_SEC
|
(M) ‘CICS CPU Time’
|
|
PGM_LOAD_REQUESTS
|
(M) ‘CICS Program
LOAD Requests’
|
|
PGM_LOADS
|
(M) ‘CICS Program Library Fetches’
|
|
FC_REQUESTS_TOTAL
|
(M) ‘CICS File Control Requests’
|
|
EXCEPTIONS
|
(M) ‘CICS Exceptions’
|
|
STORAGE_PGM_TOTAL
|
(M) ‘CICS Program Storage’
|
|
( GETMAINS_EUDSA + GETMAINS_ECDSA ) / RECORDS
|
(M) ‘CICS GETMAINs Above 16MB’
|
|
( GETMAINS_UDSA + GETMAINS_CDSA ) / RECORDS
|
(M) ‘CICS GETMAINs Below 16MB’
|
|
CICS_AVAIL_T
|
MVS_SYSTEM_ID
|
(C)
‘MVS_SYSTEM’
|
|
RESOURCE_NAME
(where RESOURCE_TYPE=’CICSSYS’)
|
(C)
‘MVS_SUBSYSTEM’
|
|
RESOURCE_NAME
(where RESOURCE_TYPE=’DB2CONN’)
|
(C)
‘D04_DB2CONN’
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
Count(Substr(INTERVAL_TYPE,1,1)
= ‘|’)
|
(M)
‘CICS Resource Starts’
|
|
Count(Substr(INTERVAL_TYPE,3,1)
= ‘|’)
|
(M)
‘CICS 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’
|
|
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)
|
|
CICS_A_BASIC_HP
|
MVS_SYSTEM_ID
|
( C ) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
( C )
MVS_SUBSYSTEM
|
|
APPLICATION_NAME
|
( C ) D04_APPL
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
RESPONSE_SUM_SEC / RECORDS, RESPONSE_MIN_SEC,
RESPONSE_MAX_SEC
|
(M) ‘CICS Response Time for All Tasks’
|
|
DISPATCH_SEC/ RECORDS
|
(M) ‘CICS Dispatch Time’
|
|
DISPATCH_WAIT_SEC/ RECORDS
|
(M) ‘CICS Re-Dispatch Wait Time’
|
|
( TC_IO_WAIT_SEC + TS_IO_WAIT_SEC + TSSHWAIT_CLOCK +
TD_IO_WAIT_SEC + JC_IO_WAIT_SEC
+ FC_IO_WAIT_SEC + RLSWAIT_CLOCK +
CFDTWAIT_CLOCK + SOIOWTT_CLOCK + MRO_WAIT_SEC
+ LU61_IO_WAIT_SEC + LU62_IO_WAIT_SEC + FE_WAIT_SEC + DISPATCH_DELAY_SEC +
ENQ_WAIT_SEC + GNQDELAY_CLOCK + ICDELAY_CLOCK + LMDELAY_CLOCK + WTEXWAIT_CLOCK + WTCEWAIT_CLOCK +
GVUPWAIT_CLOCK + RMI_SUSPEND_SEC + RUNTRWTT_CLOCK + SRVSYWTT_CLOCK + SYNCDLY_CLOCK
+ MAXOTDLY_CLOCK + RRMSWAIT_CLOCK ) / RECORDS
|
|
|
CICS_A_DBCTL_HP
|
SUSPEND_SEC/ RECORDS
|
(M) ‘CICS Dispatcher Suspended Time ‘
|
|
MVS_SYSTEM_ID
|
( C )
MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
( C )
MVS_SUBSYSTEM
|
|
APPLICATION_NAME
|
( C ) D04_APPL
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
DLI_CALL_CNT
|
(M) ‘CICS DBCTL Calls’
|
|
CICS_A_DLI_HP
|
MVS_SYSTEM_ID
|
( C ) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
( C )
MVS_SUBSYSTEM
|
|
APPLICATION_NAME
|
( C ) D04_APPL
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
CALL_CNT
|
(M) ‘CICS DL/I Database Calls’
|
|
CICS_S_DB2CONN_DP
|
DB2_CONN_NAME
|
(C) D04_DB2CONN
|
|
MVS_SYSTEM_ID
|
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
DB2_GMT_DISC_TIME-DB2_GMT_CONN_TIME
|
(M) 'CICS DB2 Connection Time'
|
|
DB2_TCB_LIMIT
|
(M) 'CICS Task Control Block Limit'
|
|
DB2_TCB_HWM
|
(M) 'CICS Subtask Task Control Blocks'
|
|
DB2_COMD_CALLS
|
(M) 'CICS DB2 Commands '
|
|
CICS_S_DB2ENTRY_TP
|
DB2_ENTRY_NAME
|
(C) D04_DB2ENTRY
|
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
DB2_CALLS
|
(M) ‘CICS SQL Calls’
|
|
|
DB2_SIGNONS
|
(M) ‘CICS DB2 Signons’
|
|
DB2_THREAD_LIMIT
|
(M) ‘CICS Threads Limit’
|
|
DB2_THREAD_HWM
|
(M) ‘CICS Active Threads ‘
|
|
DB2_TASK_HWM
|
(M) ‘CICS Tasks ‘
|
|
DB2_TASK_TOT
|
(M) ‘CICS Completed Tasks’
|
|
CICS_S_FILE_TP
|
FILE_NAME
|
(C) D04_FILE
|
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
GET_REQUESTS + BROWSE_REQUESTS
|
(M) ‘CICS GET Requests’
|
|
ADD_REQUESTS + UPDATE_REQUESTS
|
(M) ‘CICS PUT Requests’
|
|
DELETE_REQ_LOCAL+ DELETE_REQ_REMOTE
|
(M) ‘CICS DELETE Requests’
|
|
VSAM_EXCP_REQ_DATA
|
(M) ‘CICS VSAM I/Os’
|
|
CICS_S_GLOBAL_TP
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
LIBRARY_LOAD_REQ
(Statistics_Area = ‘LOADER’)
|
(M) ‘CICS MVS LOAD Requests’
|
|
LOAD_SEC (Statistics_Area = ‘LOADER’)
|
(M) ‘CICS Overall Library Load Time’
|
|
TS_MAIN_PUTS (Statistics_Area =‘TEMP_STORAGE’)
|
(M) ‘CICS Temporary Storage PUTs’
|
|
TS_MAIN_GETS (Statistics_Area =‘TEMP_STORAGE’)
|
(M) ‘CICS Temporary Storage GETs’
|
|
TS_MAIN_PEAK_BYTES
(Statistics_Area =‘TEMP_STORAGE’)
|
(M) ‘CICS Temporary Storage’
|
|
RPL_PEAK_USED (Statistics_Area =‘VTAM’)
|
(M) ‘CICS VTAM Request Parameter Lists Posted’
|
|
VTAM_SOS_COUNT (Statistics_Area =‘VTAM’)
|
(M) ‘CICS VTAM Short On Storage Events’
|
|
CICS_TRAN_USR_HP
|
MVS_SYSTEM_ID
|
(C) MVS_SYSTEM
|
|
CICS_SYSTEM_ID
|
(C) MVS_SUBSYSTEM
|
|
TRANSACTION_ID
|
(C) D04_TRANS
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
RECORDS
|
(M) ‘CICS Transactions’
|
|
CPU_SUM_SEC
|
(M) ‘CICS CPU Time’
|
|
PGM_LOAD_REQUESTS
|
(M) ‘CICS Program
LOAD Requests’
|
|
PGM_LOADS
|
(M) ‘CICS Program Library Fetches’
|
|
FC_REQUESTS_TOTAL
|
(M) ‘CICS File Control Requests’
|
|
EXCEPTIONS
|
(M) ‘CICS Exceptions’
|
|
STORAGE_PGM_TOTAL
|
(M) ‘CICS Program Storage’
|
|
( GETMAINS_EUDSA + GETMAINS_ECDSA ) / RECORDS
|
(M) ‘CICS GETMAINs Above 16MB’
|
|
( GETMAINS_UDSA + GETMAINS_CDSA ) / RECORDS
|
(M) ‘CICS GETMAINs Below 16MB’
|
|
CICS_AVAIL_TP
|
MVS_SYSTEM_ID
|
(C) ‘MVS_SYSTEM’
|
|
RESOURCE_NAME
(where
RESOURCE_TYPE=’CICSSYS’)
|
(C)
‘MVS_SUBSYSTEM’
|
|
RESOURCE_NAME
(where RESOURCE_TYPE=’DB2CONN’)
|
(C)
‘D04_DB2CONN’
|
|
‘CICS’
|
(A) MVS_SUBSYS_TYPE
|
|
Count(Substr(INTERVAL_TYPE,1,1)
= '|’)
|
(M)
‘CICS Resource Starts’
|
|
Count(Substr(INTERVAL_TYPE,3,1)
= '|’)
|
(M)
‘CICS 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: The “CICS Resource Stops “ measure is not available or loaded
for MVS_SUBSYSTEM both for partitioning feature and the not partitioning one.
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 CICS component, you must install the following software:
·
IBM Tivoli Decision Support for OS/390 Version 1.6 CICS
performance feature with one of the following
feature and component:
Ø
CICS performance
feature with the following components:
ü
CICS Monitoring component:
·
Basic subcomponent
·
DBCTL
subcomponent
·
DL/I
subcomponent
·
Basic Application Analysis subcomponent
·
DBCTL Application Analysis subcomponent
·
DL/I Application Analysis subcomponent
·
CICS/MVS subcomponent (Global + Accounting)
ü
CICS
Statistics component
Ø
CICS partitioning feature
with the following components:
ü
CICS Monitoring Partitioned component:
·
Basic subcomponent
·
DBCTL
subcomponent
·
DL/I
subcomponent
·
Basic Application Analysis subcomponent
·
DBCTL Application Analysis subcomponent
·
DL/I Application Analysis subcomponent
·
CICS/MVS subcomponent (Global + Accounting)
ü
CICS Statistics Partitioned 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 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 CICS availability data into Tivoli Decision
Support for OS/390 you must configure the CICS_AVAIL_RES lookup table. The
following can be used as a sample:
|
MVS_SYSTEM_ID
|
CICS_SYSTEM_ID
|
RESOURCE_SOURCE_NAME
|
RESOURCE_TYPE
|
RESOURCE_TARGET_NAME
|
RESOURCE_CHKPOINT
|
SCHEDULE_NAME
|
AVAIL_OBJ_PCT
|
|
%
|
%
|
CICS3T8X
|
CICSSYS
|
|
3600
|
STANDARD
|
95.0
|
|
%
|
%
|
CICS3TTS
|
CICSSYS
|
|
3600
|
STANDARD
|
95.0
|
|
%
|
%
|
DB23%
|
DB2CONN
|
DB23
|
3600
|
STANDARD
|
95.0
|
Where:
·
MVS_SYSTEM_ID: Name of your MVS system (% can be used
as a wildcard).
·
CICS_SYSTEM_ID: The CICS Subsystem ID that the resource
is associated with. (% can be used as a
wildcard).
·
RESOURCE_SOURCE_NAME: Name of the resource you want to
monitor. (% can be used as a wildcard).
·
RESOURCE_TYPE: In this field you must specify “CICSSYS” to collect availability data for
the CICS Subsystems, or 'DB2CONN' to collect availability data for the CICS DB2
connection.
·
RESOURCE_TARGET_NAME: The name used as a component name
in Tivoli Data Warehouse.
·
RESOURCE_CHKPOINT: Resource checkpoint interval in
seconds.
·
SCHEDULE_NAME: Schedule name to use for the resource.
If nothing is specified, STANDARD is used as default.
Note:
The RESOURCE_TARGET_NAME is the
identifier that is used in the Data Warehouse when loading the data. In
particular, for the CICSSYS resource type:
·
The RESOURCE_TARGET_NAME must be left blank. This means
that the value of the RESOURCE_SOURCE_NAME will be used.
·
Inconsistencies must also be avoided between the
CICS_SYSTEM_ID and the RESOURCE_SOURCE_NAME. It is recommended to leave % in
the first column, and specify the CICS name in the second one.
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\d04\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
List any configuration steps
the customer must perform after running the warehouse pack installation
program. For example, this might include tasks such as configuring warehouse
sources and targets.
If there are none, say: This
warehouse pack requires no post-installation procedures.
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.
Tivoli
Data Warehouse, during installation of the warehouse pack, schedules for
execution only the Tivoli Decision Support for OS/390 CICS non-partitioning ETL
process.
If you are
using the Tivoli Decision Support for OS/390 CICS partitioning you need to
change the scheduled process after the installation of the warehouse pack.
1.
From
the Data Warehouse Center, expand the object tree until you find the Subject
Area D04_TDS/390-CICS_v1.6.0_Subject_Area. Expand the Processes folder and you
will see the following processes:
·
D04_c05_CICS_Process
(process for CICS using Tivoli Decision Support for OS/390 CICS non-partitioning)
·
D04_c10_CICS_Partitioning_Process
(process for CICS using Tivoli Decision Support for OS/390 CICS partitioning)
2. Select the first process
(D04_c05_CICS_Process). Move the first step (D04_c05_s010_processCICS) into
"test mode", then go in the schedule notebook and remove its
schedule.
3. Select the second process
(D04_c10_CICS_Partitioning_Process). Move the first step
(D04_c10_s010_processCICS) into "test mode", then go in the schedule
notebook and add your preferred schedule.
4. Promote
the two steps of the second process (D04_c10_CICS_Partitioning_Process) to
“production mode”.
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
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\d04\v1200\misc directory,
the name is d04_data_delete.sql. The sample deletes both 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\d04\v1200\misc
directory:
db2 –z <your logfile
name> -tvf d04_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
|
D04.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
|
D04.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.
It is your responsibility to ensure you have sufficient backup 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)
|
|
D04
|
P
|
100
|
|
D04
|
H
|
100
|
|
D04
|
D
|
300
|
|
D04
|
W
|
10000
|
|
D04
|
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 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.
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 processes:
·
D04_c05_CICS _Process
·
D04_c10_CICS _Partitioning_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:
·
D04_c05_s010_processCICS
This step populates the component
table (Comp table), the component attribute table (CompAttr table) and the
component relationship table (CompReln table).
·
D04_c05_s020_processCICS
This step populates the
measurement table (Msmt table).
This process is used to load Component and Measurement
tables from CICS Partitioning feature
source data.
The process has the following steps:
·
D04_c10_s010_processCICS
This step populates the Component
table (Comp table), the Component Attribute table (CompAttr table) and the
Component Relationship table (CompReln table).
·
D04_c10_s020_processCICS
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
|
|
D04_APPL
|
|
Application
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D04
|
|
D04_DB2CONN
|
|
DB2 Connection
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D04
|
|
D04_DB2ENTRY
|
|
DB2 Entry
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D04
|
|
D04_FILE
|
|
File
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D04
|
|
D04_TRANS
|
|
Transaction
|
2002-01-01-
00.00.00.000000
|
9999-01-01-00.00.00.000000
|
D04
|
|
* 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)
|
|
20
|
MVS_SYSTEM
|
CDW
|
1
|
|
ESJ4
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
SHARED
|
|
21
|
MVS_SUBSYSTEM
|
CDW
|
1
|
|
CICS1
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
SHARED
|
|
22
|
MVS_SUBSYSTEM
|
CDW
|
1
|
|
CICSP
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
SHARED
|
|
23
|
MVS_SUBSYSTEM
|
CDW
|
1
|
|
CICSTEC
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
SHARED
|
|
24
|
MVS_SUBSYSTEM
|
CDW
|
1
|
|
CICSTEST
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
SHARED
|
|
25
|
D04_APPL
|
CDW
|
1
|
|
ACCOUNTING
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D04
|
|
26
|
D04_APPL
|
CDW
|
1
|
|
CUSTOMERS
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D04
|
|
27
|
D04_APPL
|
CDW
|
1
|
|
OTHER
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D04
|
|
28
|
D04_APPL
|
CDW
|
1
|
|
OTHER
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D04
|
|
29
|
D04_APPL
|
CDW
|
1
|
|
PAYROLL
|
|
2002-01-01-00.00.00.000000
|
9999-01-01-00.00.00.000000
|
|
D04
|
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_SUBSYSTEM subsystem_id "MVS -
mvs_system_id"
D04_APPL appl_name "MVS - mvs_system_id ! CICS - cics_subsystem_id"
D04_DB2CONN db2conn_id "MVS - mvs_system_id
! CICS - cics_subsystem_id"
D04_DB2ENTRY db2entry_id "MVS - mvs_system_id ! CICS - cics_subsystem_id"
D04_FILE file_name
"MVS - mvs_system_id ! CICS - cics_subsystem_id"
D04_TRANS trans_id "MVS - mvs_system_id ! CICS - cics_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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
20
|
21
|
|
|
|
|
|
2
|
20
|
22
|
PCHILD
|
00.00.00.000000
|
|
|
|
3
|
20
|
23
|
PCHILD
|
00.00.00.000000
|
|
|
|
4
|
20
|
24
|
PCHILD
|
00.00.00.000000
|
|
|
|
5
|
22
|
25
|
|
|
|
|
|
6
|
22
|
26
|
PCHILD
|
00.00.00.000000
|
|
|
|
7
|
22
|
27
|
PCHILD
|
00.00.00.000000
|
|
|
|
8
|
24
|
28
|
PCHILD
|
00.00.00.000000
|
|
|
|
9
|
22
|
29
|
PCHILD
|
00.00.00.000000
|
|
|
|
10
|
22
|
30
|
|
|
|
|
|
11
|
24
|
31
|
|
|
|
|
|
12
|
24
|
32
|
PCHILD
|
|
9999-01-01-00.00.00.000000
|
|
This table is not used by this warehouse
pack.
|
AttrTyp_Cd
CHAR (17)
|
AttrTyp_Nm *
VARCHAR (120)
|
MSrc_Corr_Cd
CHAR (6)
|
|
|
MVS Subsystem Type
|
|
|
|
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)
|
|
|
|
|
|
|
|
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)
|
|
|
|
|
00.00.00.000000
|
|
|
SHARED
|
|
|
|
|
00.00.00.000000
|
|
|
SHARED
|
|
|
|
|
00.00.00.000000
|
|
|
SHARED
|
|
|
|
|
00.00.00.000000
|
|
CICS
|
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
|
|
|
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
|
NULL
|
Performance
|
|
UTIL
|
CATEG
|
NULL
|
Utilization
|
|
AVG_E
|
GROUP
|
NULL
|
Average Value Exists
|
|
MIN_E
|
GROUP
|
NULL
|
Minimum Value Exists
|
|
MAX_E
|
GROUP
|
NULL
|
Maximum Value Exists
|
|
TOT_E
|
GROUP
|
NULL
|
Total Value Exists
|
|
DRLIC1
|
TRANS
|
NULL
|
CICS Subsystem State Transition Measurements
|
|
DRLIC2
|
TRANS
|
NULL
|
CICS DB2 Connection State Transition Measurements
|
|
* 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
|
1,
3, 8,9, 10-24, 26-33, 35-39
|
|
PERF
|
CATEG
|
2,
4-7, 25
|
|
DRLIC1
|
TRANS
|
|
|
DRLIC2
|
TRANS
|
|
|
AVG_E
|
GROUP
|
|
|
MIN_E
|
GROUP
|
|
|
MAX_E
|
GROUP
|
2, 3, 11, 12, 16
|
|
TOT_E
|
GROUP
|
1, 8,9,10, 13-15, 17-35,38-42
|
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
|
|
* 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)
|
|
QTY
|
QTY
|
Quantity
|
|
B
|
QTY
|
Bytes
|
|
Sec
|
TM
|
Seconds
|
|
Min
|
TM
|
Minutes
|
|
Hr
|
TM
|
Hours
|
|
* 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
|
|
D
|
Daily
|
|
P
|
Point
|
|
* 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
|
QTY
|
D04
|
CICS DBCTL Calls
|
Number of DL/I calls and requests through the DBCTL
interface
|
|
2
|
Sec
|
D04
|
CICS Response Time for All Tasks
|
Transaction
response time for all tasks, in seconds
|
|
3
|
Sec
|
D04
|
CICS CPU Time
|
CPU
time consumed by Transactions, in seconds
|
|
4
|
Sec
|
D04
|
CICS Dispatch Time
|
Transaction
elapsed time for which tasks were dispatched, in seconds
|
|
5
|
Sec
|
D04
|
|
Transaction time that
tasks were waiting to be redispatched, in seconds
|
|
6
|
Sec
|
D04
|
CICS Wait Time
|
Sum of I/O and non I/O Transaction wait time
|
|
7
|
Sec
|
D04
|
CICS Dispatcher Suspended Time
|
Transaction
elapsed time, in seconds, for which tasks were suspended by the dispatcher
|
|
8
|
QTY
|
D04
|
CICS DL/I
Database Calls
|
Number
of direct DL/I calls and requests
|
|
9
|
QTY
|
D04
|
CICS Transactions
|
Number
of transaction occurrences
|
|
10
|
Hr
|
D04
|
CICS
DB2 Connection Time
|
Total
number of hours that CICS was
connected to DB2
|
|
11
|
QTY
|
D04
|
CICS
Task Control Block Limit
|
The
maximum number of subtask Task Control Blocks that can be attached to service
DB2 requests
|
|
12
|
QTY
|
D04
|
CICS
Subtask Task Control Blocks
|
The
peak number of subtasks Task Control Blocks attached to service DB2 requests
|
|
13
|
QTY
|
D04
|
CICS
DB2 Commands
|
The
number of DB2 commands issued using the DSNC transaction
|
|
14
|
QTY
|
D04
|
CICS
SQL Calls
|
The
total number of SQL calls made using this DB2ENTRY
|
|
15
|
QTY
|
D04
|
CICS
DB2 Signons
|
The
total number of DB2 sign-ons performed for this DB2ENTRY
|
|
16
|
QTY
|
D04
|
CICS
Threads Limit
|
The
current maximum number of threads allowed for the DB2ENTRY
|
|
17
|
QTY
|
D04
|
CICS
Active Threads
|
The
number of active threads for this DB2ENTRY
|
|
18
|
QTY
|
D04
|
CICS Tasks
|
The
number of tasks for this DB2ENTRY
|
|
19
|
QTY
|
D04
|
CICS
Completed Tasks
|
The
total number of completed tasks that have used this DB2ENTRY
|
|
20
|
QTY
|
D04
|
CICS
GET Requests
|
Number
of GET requests issued
|
|
21
|
QTY
|
D04
|
CICS
PUT Requests
|
Number
of PUT requests issued
|
|
22
|
QTY
|
D04
|
CICS
DELETE Requests
|
Number
of DELETE requests issued
|
|
23
|
QTY
|
D04
|
CICS
VSAM I/Os
|
Number
of data I/O operations on this VSAM file
|
|
24
|
QTY
|
D04
|
CICS
MVS LOAD Requests
|
Number
of times the loader has issued an MVS LOAD request
|
|
25
|
Sec
|
D04
|
CICS
Overall Library Load Time
|
Time
taken for all the library loads, in seconds
|
|
26
|
QTY
|
D04
|
CICS
Temporary Storage PUTs
|
Number
of records that the application programs wrote to main temporary storage
|
|
27
|
QTY
|
D04
|
CICS Temporary Storage GETs
|
Number of records that the application programs obtained
from main temporary storage
|
|
28
|
B
|
D04
|
CICS
Temporary Storage
|
Virtual storage used for temporary storage
|
|
29
|
QTY
|
D04
|
CICS
VTAM Request Parameter Lists Posted
|
Number
of VTAM Request Parameter Lists posted
|
|
30
|
QTY
|
D04
|
CICS
VTAM Short On Storage Events
|
Number
of times VTAM was short on storage
|
|
31
|
QTY
|
D04
|
CICS Program LOAD Requests
|
Number
of program LOAD requests
|
|
32
|
QTY
|
D04
|
CICS Program Library Fetches
|
Number of program library fetches
|
|
33
|
QTY
|
D04
|
CICS
File Control Requests
|
Total
number of file control requests. Incremented even if the request is function
shipped
|
|
34
|
QTY
|
D04
|
CICS
Exceptions
|
Number
of exception conditions. This is valid for CICS V3 and later
|
|
35
|
B
|
D04
|
CICS Program Storage
|
Program storage both above and below the 16MB line, in bytes
|
|
36
|
QTY
|
D04
|
CICS GETMAINs Above 16MB
|
Average
number of user storage GETMAIN requests above the 16MB line
|
|
37
|
QTY
|
D04
|
CICS GETMAINs Below 16MB
|
Average
number of user storage GETMAIN requests below the 16MB line
|
|
38
|
QTY
|
D04
|
CICS Resource Starts
|
Number
of times the resource started
|
|
39
|
QTY
|
D04
|
CICS Resource Stops
|
Number
of times the resource stopped
|
|
40
|
Min
|
MODEL1
|
Available
|
The
amount of time that the resource is available
|
|
41
|
Min
|
MODEL1
|
Unavailable
|
The amount of time that the resource is not available
|
|
42
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D04
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D04
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D04
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
d04.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:
