![]() |
![]() |
[ Bottom of Page | | Contents | Index ]
Before using this information and the product it supports, read the information in Notices
This edition applies to Version 3, Release 1 of IBM Tivoli Business Systems Manager and to all subsequent releases and modifications until otherwise indicated in new editions.
This document describes the Warehouse Pack, Version 3.2.0.0., for IBM(R) Tivoli(R) Business Systems Manager, Version 3.1. This warehouse pack is created for Tivoli Data Warehouse, Version 1.2.
This guide is for people who do any of the following activities:
Administrators and installers should have the following knowledge or experience:
Additionally, report designers and warehouse pack creators should have the following knowledge or experience:
This section lists publications in the Tivoli Data Warehouse and the Tivoli Business Systems Manager product libraries and related documents. It also describes how to access Tivoli publications online and how to order Tivoli publications.
The following documents are available in the Tivoli Data Warehouse library:
Describes how Tivoli Data Warehouse fits into your enterprise, explains how to plan for its deployment, and gives installation and configuration instructions. Additionally, this guide contains maintenance procedures and describes how to install warehouse packs and reports. This document also describes how to install DB2 Universal Database and Crystal Enterprise Professional v.9 for Tivoli for use with Tivoli Data Warehouse.
Lists the messages generated by Tivoli Data Warehouse and describes the actions you should take. It also contains troubleshooting information related to installing, configuring, and using Tivoli Data Warehouse.
Describes the database schemas used in the Tivoli Data Warehouse central data warehouse and data mart. This includes the data model for the central data warehouse and data mart and the tables in the central data warehouse.
The Tivoli Data Warehouse information center contains the documents from the Tivoli Data Warehouse library in PDF and HTML formats. The information center is available from the Tivoli Software Information Center Web site.
The Tivoli Data Warehouse Documentation CD, LK3T-8111, provides all documents in the Tivoli Data Warehouse library, except for Enabling an Application for Tivoli Data Warehouse, GC32-0745. Enabling an Application for Tivoli Data Warehouse is available only on the Tivoli Data Warehouse Support Web site. All documents are available in English; selected documents are available in other languages.
The following publications are in the IBM Tivoli Business Systems Manager library:
This document is written for network planners, system designers, systems administrators, and others who are responsible for planning and implementing the product.
This document is written for system administrators and others who are responsible for installing and configuring Tivoli Business Systems Manager.
This document is written for operators and administrators.
This document is written for system administrators and others who perform administrative tasks for Tivoli Business Systems Manager.
This document is written for system programmers.
This document is written for system administrators and others who run commands and scripts for Tivoli Business Systems Manager.
This document is written for system programmers, network planners, operations managers, system designers, system administrators, network operators, and others who need message information for Tivoli Business Systems Manager.
This document is written for system administrators and others who perform diagnostic tasks for Tivoli Business Systems Manager.
This document is written for administrators and others who plan for and install the warehouse pack, use and maintain the warehouse pack and its reports, or create new reports.
An index is provided for searching the Tivoli Business Systems Manager library. If you have Adobe Acrobat on your system, you can use the Search command to locate specific text in the library. For more information about using the index to search the library, see the online help for Acrobat.
The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available at the following Tivoli software library Web site:
http://www.ibm.com/software/tivoli/library/
Access the glossary by clicking the Glossary link on the left pane of the Tivoli software library window.
The documentation CD contains the publications that are in the product library. The format of the publications is PDF and HTML.
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. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address:
Scroll down and click the Product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click the Tivoli Business Systems Manager link to access the product library at the Tivoli software information center.
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 other countries, see the following Web site for a list of telephone numbers:
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. With this product, you can use assistive technologies to hear and navigate the interface. You can also use the keyboard instead of the mouse to operate all features of the graphical user interface.
For information about installing the Tivoli Business Systems Manager product using the built-in screen reader, see the IBM Tivoli Business Systems Manager: Installation and Configuration Guide. For information about the shortcut keys that can be used with the Tivoli Business Systems Manager console, see the Accessibility appendix in IBM Tivoli Business Systems Manager: Introducing the Consoles.
For Tivoli technical training information, refer to the following IBM Tivoli Education Web site:
If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need:
For more information about these three ways of resolving problems, see Support information.
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 news reader programs. These groups are primarily intended for user-to-user communication and are not a replacement for formal support.
To access a newsgroup, use the instructions appropriate for your browser.
IBM Tivoli Business Systems Manager:
news://news.software.ibm.com/ibm.software.tivoli.business-systems-manager
IBM Tivoli Enterprise Console(R):
news://news.software.ibm.com/ibm.software.tivoli.enterprise-console
IBM Tivoli Service Level Advisor:
news://news.software.ibm.com/ibm.software.tivoli.service-level-advisor
IBM Tivoli Switch Analyzer:
news://news.software.ibm.com/ibm.software.tivoli.switch-analyzer
IBM Tivoli NetView(R) for UNIX(R) and IBM Tivoli NetView for Windows(R):
news://news.software.ibm.com/ibm.software.tivoli.netview-unix-windows
IBM Tivoli NetView for z/OS(R):
news://news.software.ibm.com/ibm.software.netview
This guide uses several conventions for special terms and actions and for commands and paths that vary according to the operating system.
This guide uses the following typeface conventions:
This guide uses the UNIX convention for specifying environment variables and for directory notation.
When using the Windows command line, replace $variable with %variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. The names of environment variables are not always the same in Windows and UNIX. For example, %TEMP% in Windows is equivalent to $TMPDIR in UNIX.
For a list of terms and definitions for Tivoli and other IBM products, refer to the IBM terminology Web site:
http://www.ibm.com/ibm/terminology/
For brevity and readability, the term Tivoli NetView for z/OS refers to both the Tivoli NetView for z/OS product and the Tivoli NetView for OS/390(R) product.
The following sections provide an overview of Tivoli Data Warehouse and the Tivoli Business Systems Manager warehouse pack.
Tivoli Data Warehouse provides the infrastructure for the following processes:
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.
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 tables or columns 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 Business Systems Manager is an enterprise management product that captures resource states and the events for those resources.
The warehouse pack for Tivoli Business Systems Manager includes the following ETLs:
There is a set of database triggers in the Tivoli Business Systems Manager database that track resource creation, deletion, and changes for use by the Tivoli Business Systems Manager ETLs. These triggers can be enabled or disabled by the ETL steps. By default, these triggers are disabled.
When these database triggers are enabled, resource creation, deletion, and change information is stored in the tracking tables as the changes occur in Tivoli Business Systems Manager. Using triggers may slow Tivoli Business Systems Manager performance if there are many resource changes. As an alternative, there is also a synchronize procedure that populates the resource change tracking tables based on the data in Tivoli Data Warehouse and Tivoli Business Systems Manager. This procedure is run during initialization. When the triggers are disabled, the procedure is used to accumulate the resource data at the ETL run time
After Tivoli Business Systems Manager sends resource data to Tivoli Data Warehouse using the ETLs, the information can be used with other applications, such as the IBM Tivoli Service Level Advisor product. For example, the Tivoli Service Level Advisor product can analyze the Tivoli Business Systems Manager data stored in the Tivoli Data Warehouse and generate Service Level Advisor reports.
Figure 2 presents a high-level view of the Tivoli Business Systems Manager central data warehouse ETL and data mart ETL.
Using the Tivoli Business Systems Manager warehouse pack, you can enable the following configurations:
See Installing and configuring the warehouse pack for information on how to set up these configurations.
This warehouse pack also contains predefined reports. For more information about the predefined reports that are provided, see Reports.
See Appendix. Data modeling for data modeling information.
The Tivoli Business Systems Manager central data warehouse ETL extracts data from the Tivoli Business Systems Manager database, maps and transforms and loads this information to the Tivoli Data Warehouse. It loads only enough resource, event, and measurement data for Tivoli Business Systems Manager reporting and integration with the Tivoli Service Level Advisor.
Specifically, the central data warehouse ETL does the following tasks:
Tivoli Business Systems Manager central data warehouse ETL also does the following maintenance tasks:
The Tivoli Business Systems Manager data mart ETL retrieves the Tivoli Business Systems Manager data that was loaded by the central data warehouse ETL from Tivoli Data Warehouse and loads it into the GTM star schema in the Tivoli Data Warehouse data mart. This data can be used for Tivoli Business Systems Manager reports.
The data mart ETL does the following tasks:
A source database contains the information that an ETL uses and a target is the database in which the output data from the ETL is stored.
The warehouse pack uses the following data sources and targets:
Name in DB2 Data Warehouse Center | Description |
---|---|
GTM_OBJECT_Source | The warehouse source for the central data warehouse ETL. It uses the twh_objs table in the Tivoli Business Systems Manager Object database as the connection table and OBJECT ODBC System Data Source defined with DataWHSE 3.60 32-bit SQL server driver. |
GTM_TWH_CDW_Target | The warehouse target for the central data warehouse ETL. It uses the GTM.CUST_LOOKUP table in the Tivoli Data Warehouse database as the connection table and TWH_CDW ODBC System Data Source defined with IBM DB2 ODBC DRIVER. |
GTM_TWH_CDW_Source | The warehouse source for the data mart ETL. It uses the GTM.CUST_LOOKUP table in the Tivoli Data Warehouse database as the connection table and TWH_CDW ODBC System Data Source defined with IBM DB2 ODBC DRIVER. |
GTM_TWH_MART_Target | The warehouse target for the data mart ETL. It uses the GTM.D_AS_METRIC table in the Tivoli Data Warehouse data mart as the connection table and TWH_MART ODBC System Data Source defined with IBM DB2 ODBC DRIVER. |
This section provides information about the predefined reports provided by the warehouse pack.
The warehouse pack provides the following reports:
Many of these reports have a main report and a sub-report. The main report is used to select a starting resource that is then used as a resource filter in the sub-report. All reports are basic columnar reports. Some reports also have a predefined grouping which is noted in the individual report descriptions that follow.
Many reports use database views that are defined in the GTM schema of the TWH_MART database. These views use a combination of tables and other views to produce the set of columns they return. In the Table section of each report, (view) indicates that the item listed is a view and (table) indicates it is a table. An indented structure is used to show the collection of tables and views that are used to define other views. The following example shows that the GTM.REPORT_VIEW_1 uses the tables GTM.TABLE_1 and GTM.TABLE_2:
GTM.REPORT_VIEW_1(view) GTM.TABLE_1(table) GTM.TABLE_2(table)
The following example shows that the GTM.REPORT_VIEW_2 uses the GTM.REPORT_VIEW_1 and the tables GTM.TABLE_3 and GTM.TABLE_4:
GTM.REPORT_VIEW_2(view) GTM.REPORT_VIEW_1(view) GTM.TABLE_3(table) GTM.TABLE_4(table)
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_P(view) GTM.D_COMP(table) GTM.D_OBJ_CLASS(table) GTM.D_COMP_PATH(table)
Sub report:
GTM.GTM_PHYTREE_V(view) GTM.GTM_COMP_P(view) GTM.D_OBJ_CLASS(table)
SELECT GTM_COMP_P.RESOURCE_PATH, GTM_COMP_P.IDPATH, GTM_COMP_P.NAME FROM GTM.GTM_COMP_P GTM_COMP_P WHERE GTM_COMP_P.NAME LIKE resource_name
Sub report:
SELECT GTM_PHYTREE_V.NAME, GTM_PHYTREE_V.RESOURCE_PATH, GTM_PHYTREE_V.SRC_CID, GTM_PHYTREE_V.LABEL, GTM_PHYTREE_V.ID, GTM_PHYTREE_V.IDPATH FROM GTM.GTM_PHYTREE_V GTM_PHYTREE_V WHERE GTM_PHYTREE_V.IDPATH LIKE GTM_COMP_P.ID_PATH passed from Main Report + '%'
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_L(view) GTM.D_COMP(table) GTM.D_LOB_LINK(table) GTM.D_OBJ_CLASS(table) D_COMP_PATH(table)
Sub report:
GTM.GTM_LOBTREE_V(view) GTM.GTM_COMP_L(view) GTM.D_OBJ_CLASS(table)
SELECT GTM_COMP_L.RESOURCE_PATH, GTM_COMP_L.IDPATH, GTM_COMP_L.NAME FROM GTM.GTM_COMP_L GTM_COMP_L WHERE GTM_COMP_L.NAME LIKE resource_name
Sub report:
SELECT GTM_LOBTREE_V.NAME, GTM_LOBTREE_V.RESOURCE_PATH, GTM_LOBTREE_V.SRC_CID, GTM_LOBTREE_V.LABEL, GTM_LOBTREE_V.ID, GTM_LOBTREE_V.IDPATH FROM GTM.GTM_LOBTREE_V GTM_LOBTREE_V WHERE GTM_LOBTREE_V.IDPATH LIKE GTM_COMP_P.ID_PATH passed from Main Report + '%'
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_P(view) GTM.D_COMP(table) GTM.D_OBJ_CLASS(table) GTM.D_COMP_PATH(table)
Sub report:
GTM.GTM_COMP_P(view) GTM.D_COMP(table) GTM.D_OBJ_CLASS(table) GTM.D_COMP_PATH(table)
SELECT GTM_COMP_P.NAME, GTM_COMP_P.IDPATH, GTM_COMP_P.RESOURCE_PATH FROM GTM.GTM_COMP_P GTM_COMP_P WHERE GTM_COMP_P.NAME LIKE resource_name
Sub report:
SELECT GTM_COMP_P.RESOURCE_PATH, GTM_COMP_P.C_DESC, GTM_COMP_P.NAME, GTM_COMP_P.COMP_ST_DTTM, GTM_COMP_P.IDPATH FROM GTM.GTM_COMP_P GTM_COMP_P WHERE GTM_COMP_P.IDPATH LIKE {?GTM_COMP_P.ID_PATH passed from Main Report } + '%' AND GTM_COMP_P.COMP_ST_DTTM>={?date_range}
Main report:
Sub report:
Sub report:
GTM.GTM_MVS_V(view) GTM.D_COMP_PATH(table) GTM.D_COMP(table)
Sub report:
GTM.PHYS_COMP_EVENTS(view) GTM.F_EVENT(table) GTM.GTM_COMP_P(view) GTM.D_ETYP_METRIC(table) GTM.D_AS_METRIC(table) GTM.D_PRI_METRIC(table)
SELECT GTM_MVS_V.COMPLEX_NAME, GTM_MVS_V.OS_NAME, GTM_MVS_V.NAME, GTM_MVS_V.RESOURCE_PATH, GTM_MVS_V.CID, GTM_MVS_V.IDPATH FROM GTM.GTM_MVS_V GTM_MVS_V WHERE GTM_MVS_V.OS_NAME LIKE {?os_name} AND GTM_MVS_V.COMPLEX_NAME LIKE {?complex_name} AND GTM_MVS_V.NAME LIKE {?resource_name} AND GTM_MVS_V.CID={?resource_type}
Sub report:
SELECT PHYS_COMP_EVENTS.EVENTTYP_NM, PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.PRIORITY, PHYS_COMP_EVENTS.EVENT_NAME, PHYS_COMP_EVENTS.EVENT_DETAIL, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.NAME, PHYS_COMP_EVENTS.COMPLEX_NAME, PHYS_COMP_EVENTS.OS_NAME, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.EVENTTYP_ID FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND PHYS_COMP_EVENTS.IDPATH LIKE '%' {?GTM_COMP_P.ID_PATH passed from Main Report? } AND PHYS_COMP_EVENTS.EVENT_NAME LIKE '{?event_name}' AND PHYS_COMP_EVENTS.EVENT_DETAIL LIKE '{?event_detail}' ORDER BY PHYS_COMP_EVENTS.COMPLEX_NAME, PHYS_COMP_EVENTS.OS_NAME, PHYS_COMP_EVENTS.NAME
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_L(view) GTM.D_COMP(table) GTM.D_LOB_LINK(table) GTM.D_OBJ_CLASS(table) D_COMP_PATH(table)
Sub report:
GTM.LOB_COMP_EVENTS(view) GTM.GTM_COMP_L(view) GTM.F_EVENT(table) GTM.D_ETYP_METRIC(table) GTM.D_AS_METRIC(table) GTM.D_PRI_METRIC(table)
SELECT GTM_COMP_L.NAME, GTM_COMP_L.RESOURCE_PATH, GTM_COMP_L.OS_NAME, GTM_COMP_L.MACH_NAME, GTM_COMP_L.IDPATH FROM GTM.GTM_COMP_L GTM_COMP_L WHERE GTM_COMP_L.NAME LIKE {?resource_name}
Sub report:
SELECT LOB_COMP_EVENTS.EVENTTYP_NM, LOB_COMP_EVENTS.ALERTSTATE, LOB_COMP_EVENTS.PRIORITY, LOB_COMP_EVENTS.ALERTSTATE_ID, LOB_COMP_EVENTS.EVENT_DTTM, LOB_COMP_EVENTS.EVENT_NAME, LOB_COMP_EVENTS.EVENT_DETAIL, LOB_COMP_EVENTS.PRIORITY_ID, LOB_COMP_EVENTS.CID, LOB_COMP_EVENTS.NAME, LOB_COMP_EVENTS.IDPATH, LOB_COMP_EVENTS.EVENTTYP_ID FROM GTM.LOB_COMP_EVENTS LOB_COMP_EVENTS WHERE (LOB_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND LOB_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND LOB_COMP_EVENTS.EVENT_NAME LIKE '?event_name' AND LOB_COMP_EVENTS.EVENT_DETAIL LIKE '?event_detail' AND LOB_COMP_EVENTS.IDPATH LIKE {?GTM_COMP_L.ID_PATH passed from Main Report } + '%' ORDER BY LOB_COMP_EVENTS.CID, LOB_COMP_EVENTS.NAME
Main report:
Sub report:
Sub report: none
GTM.GTM_COMP_L(view) GTM.D_COMP(table) GTM.D_LOB_LINK(table) GTM.D_OBJ_CLASS(table) GTM.D_COMP_PATH(table)
Sub report:
GTM.GTM_LOBTREE_V(view) GTM.GTM_COMP_L(view) GTM.D_COMP GTM.D_OBJ_CLASS
SELECT GTM_COMP_L.NAME, GTM_COMP_L.RESOURCE_PATH, GTM_COMP_L.OS_NAME, GTM_COMP_L.MACH_NAME, GTM_COMP_L.IDPATH FROM GTM.GTM_COMP_L GTM_COMP_L WHERE GTM_COMP_L.NAME LIKE {?resource_name}
Sub report:
SELECT GTM_LOBTREE_V.NAME, GTM_LOBTREE_V.LABEL, GTM_LOBTREE_V.ID, GTM_LOBTREE_V.IDPATH FROM GTM.GTM_LOBTREE_V GTM_LOBTREE_V WHERE GTM_LOBTREE_V.IDPATH LIKE {?GTM_COMP_L.ID_PATH passed from Main Report } + '%' ORDER BY GTM_LOBTREE_V.LABEL
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_P(view) GTM.D_COMP(table) GTM.D_OBJ_CLASS(table) GTM.D_COMP_PATH(table)
Sub report:
GTM.PHYS_COMP_EVENTS(view) GTM.F_EVENT(table) GTM.GTM_COMP_P(view) GTM.D_ETYP_METRIC(table) GTM.D_AS_METRIC(table) GTM.D_PRI_METRIC(table)
SELECT GTM_COMP_P.NAME, GTM_COMP_P.IDPATH, GTM_COMP_P.RESOURCE_PATH FROM GTM.GTM_COMP_P GTM_COMP_P WHERE GTM_COMP_P.NAME LIKE LIKE {?resource_name}
Sub report:
SELECT PHYS_COMP_EVENTS.EVENTTYP_NM, PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.PRIORITY, PHYS_COMP_EVENTS.EVENT_NAME, PHYS_COMP_EVENTS.EVENT_DETAIL, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.NAME, PHYS_COMP_EVENTS.CID, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.MACH_NAME, PHYS_COMP_EVENTS.OS_NAME, PHYS_COMP_EVENTS.LABEL, PHYS_COMP_EVENTS.EVENTTYP_ID FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND PHYS_COMP_EVENTS.IDPATH LIKE {?GTM_COMP_L.ID_PATH passed from Main Report } AND PHYS_COMP_EVENTS.EVENT_NAME LIKE {?event_name} AND PHYS_COMP_EVENTS.EVENT_DETAIL LIKE {?event_detail} ORDER BY PHYS_COMP_EVENTS.CID, PHYS_COMP_EVENTS.NAME
Main report:
Sub report:
Sub report: none
GTM.GTM_COMP_P(view) GTM.D_COMP(table) GTM.D_OBJ_CLASS(table) GTM.D_COMP_PATH(table)
Sub report:
GTM.GTM_COMP_L(view) GTM.D_COMP(table) GTM.D_LOB_LINK(table) GTM.D_OBJ_CLASS(table) GTM.D_COMP_PATH(table)
SELECT GTM_COMP_P.RESOURCE_PATH, GTM_COMP_P.IDPATH, GTM_COMP_P.NAME FROM GTM.GTM_COMP_P GTM_COMP_P WHERE GTM_COMP_P.NAME LIKE {?resource_name}
Sub report:
SELECT GTM_COMP_L.COMP_SOURCE_ID, GTM_COMP_L.RESOURCE_PATH FROM GTM.GTM_COMP_L GTM_COMP_L WHERE GTM_COMP_L.COMP_SOURCE_ID= {GTM_COMP_P.COMP_ID passed form main report}
Main report:
Sub report:
Main report:
Sub report:
GTM.D_OBJ_CLASS(table)
Sub report:
GTM.PHYS_COMP_EVENTS(view) GTM.F_EVENT(table) GTM.GTM_COMP_P(view) GTM.D_ETYP_METRIC(table) GTM.D_AS_METRIC(table) GTM.D_PRI_METRIC(table)
SELECT D_OBJ_CLASS.LABEL, D_OBJ_CLASS.C_DESC, D_OBJ_CLASS.CID FROM GTM.D_OBJ_CLASS D_OBJ_CLASS WHERE D_OBJ_CLASS.LABEL LIKE {?resource_name} + '%'
Sub report:
SELECT PHYS_COMP_EVENTS.EVENTTYP_NM, PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.PRIORITY, PHYS_COMP_EVENTS.EVENT_NAME, PHYS_COMP_EVENTS.EVENT_DETAIL, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.CID, PHYS_COMP_EVENTS.NAME, PHYS_COMP_EVENTS.LABEL, PHYS_COMP_EVENTS.EVENTTYP_ID FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE PHYS_COMP_EVENTS.EVENT_DETAIL LIKE {?event_detail} AND PHYS_COMP_EVENTS.CID={ CID value passed from main report} ORDER BY PHYS_COMP_EVENTS.LABEL, PHYS_COMP_EVENTS.NAME
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_L(view) GTM.D_COMP(table) GTM.D_LOB_LINK(table) GTM.D_OBJ_CLASS(table) D_COMP_PATH(table)
Sub report:
LOB_NOTES(view) GTM.LOB_COMP_EVENTS(view) GTM.F_NOTE(table)
SELECT GTM_COMP_L.NAME, GTM_COMP_L.RESOURCE_PATH, GTM_COMP_L.OS_NAME, GTM_COMP_L.MACH_NAME, GTM_COMP_L.IDPATH FROM GTM.GTM_COMP_L GTM_COMP_L WHERE GTM_COMP_L.NAME LIKE {?resource_name}
Sub report:
SELECT LOB_NOTES.NAME, LOB_NOTES.EVENTTYP_DESC, LOB_NOTES.EVENT_NAME, LOB_NOTES.ALERTSTATE, LOB_NOTES.PRIORITY, LOB_NOTES.EVENT_DETAIL, LOB_NOTES.NOTE_EXECUTER, LOB_NOTES.NOTE_SUBJECT, LOB_NOTES.NOTE_BODY, LOB_NOTES.OWNERSHIP_DTTM, LOB_NOTES.MACH_NAME, LOB_NOTES.OS_NAME, LOB_NOTES.LABEL, LOB_NOTES.IDPATH, LOB_NOTES.EVENT_OWNED, LOB_NOTES.EVENT_DTTM FROM GTM.LOB_NOTES LOB_NOTES WHERE LOB_NOTES.IDPATH LIKE {GTM_COMP_L.COMP_ID passed from main report} + '%' ORDER BY LOB_NOTES.MACH_NAME, LOB_NOTES.OS_NAME, LOB_NOTES.LABEL
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_P(view) GTM.D_COMP(table) GTM.D_OBJ_CLASS(table) D_COMP_PATH(table)
Sub report:
PHYS_NOTES(view) GTM.PHYS_COMP_EVENTS(view) GTM.F_NOTE(table)
SELECT GTM_COMP_P.NAME, GTM_COMP_P.RESOURCE_PATH, GTM_COMP_P.OS_NAME, GTM_COMP_P.MACH_NAME, GTM_COMP_P.IDPATH FROM GTM.GTM_COMP_P GTM_COMP_P WHERE GTM_COMP_P.NAME LIKE {?resource_name}
Sub report:
SELECT PHYS_NOTES.NAME, PHYS_NOTES.EVENTTYP_DESC, PHYS_NOTES.EVENT_NAME, PHYS_NOTES.ALERTSTATE, PHYS_NOTES.PRIORITY, PHYS _NOTES.EVENT_DETAIL, PHYS_NOTES.NOTE_EXECUTER, PHYS_NOTES.NOTE_SUBJECT, PHYS_NOTES.NOTE_BODY, PHYS_NOTES.OWNERSHIP_DTTM, PHYS_NOTES.MACH_NAME, PHYS_NOTES.OS_NAME, PHYS_NOTES.LABEL, PHYS_NOTES.IDPATH, PHYS_NOTES.EVENT_OWNED, PHYS_NOTES.EVENT_DTTM FROM GTM.PHYS_NOTES PHYS_NOTES WHERE PHYS_NOTES.IDPATH LIKE {GTM_COMP_P.COMP_ID passed from main report} + '%' ORDER BY PHYS_NOTES.MACH_NAME, PHYS_NOTES.OS_NAME, PHYS_NOTES.LABEL
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_L(view) GTM.D_COMP(table) GTM.D_LOB_LINK(table) GTM.D_OBJ_CLASS(table) D_COMP_PATH(table)
Sub report:
GTM.LOB_COMP_EVENTS (view) GTM.GTM_COMP_L(view) GTM.F_EVENT(table) GTM.D_ETYP_METRIC(table) GTM.D_AS_METRIC(table) GTM.D_PRI_METRIC(table)
SELECT GTM_COMP_L.NAME, GTM_COMP_L.IDPATH, GTM_COMP_L.RESOURCE_PATH FROM GTM.GTM_COMP_L GTM_COMP_L WHERE GTM_COMP_L.NAME LIKE LIKE {?resource_name}
Sub report:
SELECT LOB_COMP_EVENTS.ALERTSTATE, LOB_COMP_EVENTS.ALERTSTATE_ID, LOB_COMP_EVENTS.PRIORITY_ID, LOB_COMP_EVENTS.IDPATH, LOB_COMP_EVENTS.EVENTTYP_ID, LOB_COMP_EVENTS.EVENT_DTTM, LOB_COMP_EVENTS.EVENTTYP_NM FROM GTM.LOB_COMP_EVENTS LOB_COMP_EVENTS WHERE (LOB_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND LOB_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND LOB_COMP_EVENTS.IDPATH LIKE {GTM_COMP_L.COMP_ID passed from main report} + '%' ORDER BY LOB_COMP_EVENTS.ALERTSTATE_ID DESC
SELECT LOB_COMP_EVENTS.ALERTSTATE, LOB_COMP_EVENTS.ALERTSTATE_ID, LOB_COMP_EVENTS.PRIORITY_ID, LOB_COMP_EVENTS.PRIORITY, LOB_COMP_EVENTS.IDPATH, LOB_COMP_EVENTS.EVENTTYP_ID, LOB_COMP_EVENTS.EVENT_DTTM, LOB_COMP_EVENTS.EVENTTYP_NM FROM GTM.LOB_COMP_EVENTS LOB_COMP_EVENTS WHERE (LOB_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND LOB_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND LOB_COMP_EVENTS.IDPATH LIKE {GTM_COMP_L.COMP_ID passed from main report} + '%'
SELECT LOB_COMP_EVENTS.ALERTSTATE, LOB_COMP_EVENTS.ALERTSTATE_ID, LOB_COMP_EVENTS.PRIORITY_ID, LOB_COMP_EVENTS.EVENT_DTTM, LOB_COMP_EVENTS.EVENTTYP_ID, LOB_COMP_EVENTS.IDPATH, LOB_COMP_EVENTS.EVENTTYP_NM FROM GTM.LOB_COMP_EVENTS LOB_COMP_EVENTS WHERE (LOB_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND LOB_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND LOB_COMP_EVENTS.IDPATH LIKE {GTM_COMP_L.COMP_ID passed from main report} + '%'
SELECT LOB_COMP_EVENTS.ALERTSTATE, LOB_COMP_EVENTS.ALERTSTATE_ID, LOB_COMP_EVENTS.PRIORITY_ID, LOB_COMP_EVENTS.EVENT_DTTM, LOB_COMP_EVENTS.IDPATH, LOB_COMP_EVENTS.EVENTTYP_ID, LOB_COMP_EVENTS.EVENTTYP_NM FROM GTM.LOB_COMP_EVENTS LOB_COMP_EVENTS WHERE (LOB_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND LOB_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND LOB_COMP_EVENTS.IDPATH LIKE {GTM_COMP_L.COMP_ID passed from main report} + '%'
SELECT LOB_COMP_EVENTS.ALERTSTATE, LOB_COMP_EVENTS.ALERTSTATE_ID, LOB_COMP_EVENTS.PRIORITY_ID, LOB_COMP_EVENTS.EVENT_DTTM, LOB_COMP_EVENTS.IDPATH, LOB_COMP_EVENTS.EVENTTYP_ID, LOB_COMP_EVENTS.EVENTTYP_NM WHERE (LOB_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND LOB_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND LOB_COMP_EVENTS.IDPATH LIKE {GTM_COMP_L.COMP_ID passed from main report} + '%'
SELECT LOB_COMP_EVENTS.ALERTSTATE, LOB_COMP_EVENTS.ALERTSTATE_ID, LOB_COMP_EVENTS.PRIORITY_ID, GTM_COMP_P.LABEL, LOB_COMP_EVENTS.IDPATH, LOB_COMP_EVENTS.EVENT_DTTM, LOB_COMP_EVENTS.EVENTTYP_ID, LOB_COMP_EVENTS.EVENTTYP_NM FROM GTM.GTM_COMP_P GTM_COMP_P INNER JOIN GTM.LOB_COMP_EVENTS LOB_COMP_EVENTS ON GTM_COMP_P.COMP_ID=LOB_COMP_EVENTS.COMP_SOURCE_ID WHERE (LOB_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND LOB_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND LOB_COMP_EVENTS.IDPATH LIKE {GTM_COMP_L.COMP_ID passed from main report} + '%'
SELECT LOB_COMP_EVENTS.ALERTSTATE, LOB_COMP_EVENTS.ALERTSTATE_ID, LOB_COMP_EVENTS.PRIORITY_ID, GTM_COMP_P.LABEL, LOB_COMP_EVENTS.IDPATH, LOB_COMP_EVENTS.EVENTTYP_ID, LOB_COMP_EVENTS.EVENT_DTTM, LOB_COMP_EVENTS.EVENTTYP_NM FROM GTM.GTM_COMP_P GTM_COMP_P INNER JOIN GTM.LOB_COMP_EVENTS LOB_COMP_EVENTS ON GTM_COMP_P.COMP_ID=LOB_COMP_EVENTS.COMP_SOURCE_ID WHERE (LOB_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND LOB_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND LOB_COMP_EVENTS.IDPATH LIKE {GTM_COMP_L.COMP_ID passed from main report} + '%' ORDER BY GTM_COMP_P.LABEL
SELECT LOB_COMP_EVENTS.ALERTSTATE, LOB_COMP_EVENTS.ALERTSTATE_ID, LOB_COMP_EVENTS.PRIORITY_ID, GTM_COMP_P.LABEL, LOB_COMP_EVENTS.PRIORITY, LOB_COMP_EVENTS.IDPATH, LOB_COMP_EVENTS.EVENTTYP_ID, LOB_COMP_EVENTS.EVENT_DTTM, LOB_COMP_EVENTS.EVENTTYP_NM FROM GTM.GTM_COMP_P GTM_COMP_P INNER JOIN GTM.LOB_COMP_EVENTS LOB_COMP_EVENTS ON GTM_COMP_P.COMP_ID=LOB_COMP_EVENTS.COMP_SOURCE_ID WHERE (LOB_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND LOB_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND LOB_COMP_EVENTS.IDPATH LIKE {GTM_COMP_L.COMP_ID passed from main report} + '%' ORDER BY GTM_COMP_P.LABEL, LOB_COMP_EVENTS.ALERTSTATE_ID DESC
SELECT LOB_COMP_EVENTS.ALERTSTATE, LOB_COMP_EVENTS.ALERTSTATE_ID, LOB_COMP_EVENTS.PRIORITY_ID, GTM_COMP_P.LABEL, LOB_COMP_EVENTS.EVENT_NAME, LOB_COMP_EVENTS.IDPATH, LOB_COMP_EVENTS.EVENT_DTTM, LOB_COMP_EVENTS.EVENTTYP_ID, LOB_COMP_EVENTS.EVENTTYP_NM FROM GTM.GTM_COMP_P GTM_COMP_P INNER JOIN GTM.LOB_COMP_EVENTS LOB_COMP_EVENTS ON GTM_COMP_P.COMP_ID=LOB_COMP_EVENTS.COMP_SOURCE_ID WHERE ?date_range} AND LOB_COMP_EVENTS.EVENT_DTTM<{ts ?date_range}) AND LOB_COMP_EVENTS.IDPATH LIKE {GTM_COMP_L.COMP_ID passed from main report} + '%' ORDER BY GTM_COMP_P.LABEL
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_P(view) GTM.D_COMP(table) GTM.D_OBJ_CLASS(table) D_COMP_PATH(table)
Sub report:
GTM.PHYS_COMP_EVENTS (view) GTM.gtm_comp_p(view) GTM.f_event E(table) GTM.D_ETYP_METRIC(table) GTM.D_AS_METRIC(table) GTM.D_PRI_METRIC(table)
SELECT GTM_COMP_P.NAME, GTM_COMP_P.IDPATH, GTM_COMP_P.RESOURCE_PATH FROM GTM.GTM_COMP_P GTM_COMP_P WHERE GTM_COMP_P.NAME LIKE LIKE {?resource_name}
Sub report:
SELECT PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.EVENTTYP_ID, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.EVENTTYP_NM FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range }) AND PHYS_COMP_EVENTS.IDPATH LIKE {GTM_COMP_P.COMP_ID passed from main report} + '%' ORDER BY PHYS_COMP_EVENTS.ALERTSTATE_ID DESC
SELECT PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.PRIORITY, PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.EVENTTYP_ID, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.EVENTTYP_NM WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range }) AND PHYS_COMP_EVENTS.IDPATH LIKE {GTM_COMP_P.COMP_ID passed from main report} + '%'
SELECT PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.EVENTTYP_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.EVENTTYP_NM FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range }) AND PHYS_COMP_EVENTS.IDPATH LIKE {GTM_COMP_P.COMP_ID passed from main report} + '%'
SELECT PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.EVENTTYP_ID, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.EVENTTYP_NM FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range }) AND PHYS_COMP_EVENTS.IDPATH LIKE {GTM_COMP_P.COMP_ID passed from main report} + '%'
SELECT PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.EVENTTYP_ID, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.EVENTTYP_NM FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range }) AND PHYS_COMP_EVENTS.IDPATH LIKE {GTM_COMP_P.COMP_ID passed from main report} + '%'
SELECT PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.LABEL, PHYS_COMP_EVENTS.EVENTTYP_ID, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.EVENTTYP_NM FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range }) AND PHYS_COMP_EVENTS.IDPATH LIKE {GTM_COMP_P.COMP_ID passed from main report} + '%'
SELECT PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.LABEL, PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.EVENTTYP_ID, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.EVENTTYP_NM FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range }) AND PHYS_COMP_EVENTS.IDPATH LIKE {GTM_COMP_P.COMP_ID passed from main report} + '%' ORDER BY PHYS_COMP_EVENTS.LABEL
SELECT PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.EVENTTYP_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.LABEL, PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.PRIORITY, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.EVENTTYP_NM FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range }) AND PHYS_COMP_EVENTS.IDPATH LIKE {GTM_COMP_P.COMP_ID passed from main report} + '%' PHYS_COMP_EVENTS.ALERTSTATE_ID DESC
SELECT PHYS_COMP_EVENTS.ALERTSTATE_ID, PHYS_COMP_EVENTS.PRIORITY_ID, PHYS_COMP_EVENTS.LABEL, PHYS_COMP_EVENTS.EVENT_NAME, PHYS_COMP_EVENTS.EVENTTYP_ID, PHYS_COMP_EVENTS.ALERTSTATE, PHYS_COMP_EVENTS.IDPATH, PHYS_COMP_EVENTS.EVENT_DTTM, PHYS_COMP_EVENTS.EVENTTYP_NM FROM GTM.PHYS_COMP_EVENTS PHYS_COMP_EVENTS WHERE (PHYS_COMP_EVENTS.EVENT_DTTM>={ts ?date_range} AND PHYS_COMP_EVENTS.EVENT_DTTM<{ts ?date_range }) AND PHYS_COMP_EVENTS.IDPATH LIKE {GTM_COMP_P.COMP_ID passed from main report} + '%' ORDER BY PHYS_COMP_EVENTS.LABEL
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_L(view) GTM.D_COMP(table) GTM.D_LOB_LINK(table) GTM.D_OBJ_CLASS(table) D_COMP_PATH(table)
Sub report:
GTM.CICS_STOP_START(view) GTM.LOB_COMP_EVENTS(view GTM.D_COMP(table)
SELECT GTM_COMP_L.NAME, GTM_COMP_L.IDPATH, GTM_COMP_L.RESOURCE_PATH FROM GTM.GTM_COMP_L GTM_COMP_L WHERE GTM_COMP_L.NAME LIKE {?resource_name}
Sub report:
SELECT CICS_STOP_START.COMPLEX_NAME, CICS_STOP_START.NAME, CICS_STOP_START.EVENT_DTTM, CICS_STOP_START.EVENT_NAME, CICS_STOP_START.IDPATH FROM GTM.CICS_STOP_START CICS_STOP_START WHERE CICS_STOP_START.IDPATH LIKE {GTM_COMP_L.IDPATH passed from main report} + '%' AND (CICS_STOP_START.EVENT_DTTM>={ts ?date_range} AND CICS_STOP_START.EVENT_DTTM<{ts ?date_range }) ORDER BY CICS_STOP_START.COMPLEX_NAME, CICS_STOP_START.NAME
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_L(view) GTM.D_COMP(table) GTM.D_LOB_LINK(table) GTM.D_OBJ_CLASS(table) D_COMP_PATH(table)
Sub report:
GTM.LOB_NOTES(view) GTM.LOB_COMP_EVENTS(view) GTM.F_NOTE(table)
SELECT GTM_COMP_L.NAME, GTM_COMP_L.IDPATH, GTM_COMP_L.RESOURCE_PATH FROM GTM.GTM_COMP_L GTM_COMP_L WHERE GTM_COMP_L.NAME LIKE LIKE {?resource_name}
Sub report:
SELECT LOB_NOTES.COMPLEX_NAME, LOB_NOTES.OS_NAME, LOB_NOTES.ALERTSTATE, LOB_NOTES.PRIORITY, LOB_NOTES.EVENT_NAME, LOB_NOTES.EVENT_DTTM, LOB_NOTES.NOTE_EXECUTER, LOB_NOTES.NOTE_SUBJECT, LOB_NOTES.NOTE_BODY, LOB_NOTES.RESOURCE_PATH, LOB_NOTES.LABEL, LOB_NOTES.NAME, LOB_NOTES.ALERTSTATE_ID, LOB_NOTES.PRIORITY_ID, LOB_NOTES.IDPATH, LOB_NOTES.EVENTTYP_NM FROM GTM.LOB_NOTES LOB_NOTES WHERE (LOB_NOTES.EVENT_DTTM>={ts ?date_range} AND LOB_NOTES.EVENT_DTTM<{ts ?date_range }) AND LOB_NOTES.EVENTTYP_NM='Exception' AND LOB_NOTES.EVENT_NAME='SCHV' AND LOB_NOTES.IDPATH LIKE {GTM_COMP_L.IDPATH passed from main report} + '%' ORDER BY LOB_NOTES.RESOURCE_PATH"
Main report:
Sub report:
Sub report:
GTM.GTM_COMP_L(view) GTM.D_COMP(table) GTM.D_LOB_LINK(table) GTM.D_OBJ_CLASS(table) D_COMP_PATH(table)
Sub report:
GTM.LOB_ALERT_STATE(view) GTM.GTM_COMP_L(view) GTM.F_ALERTSTATEHIS(table) GTM.D_ETYP_METRIC (table) GTM.D_AS_METRIC(table) GTM.F_EVENT(table)
SELECT GTM_COMP_L.NAME, GTM_COMP_L.RESOURCE_PATH, GTM_COMP_L.OS_NAME, GTM_COMP_L.MACH_NAME, GTM_COMP_L.IDPATH FROM GTM.GTM_COMP_L GTM_COMP_L WHERE GTM_COMP_L.NAME LIKE {?resource_name} + '%'
Sub report:
SELECT LOB_ALERT_STATE.NAME, LOB_ALERT_STATE.RESOURCE_PATH, LOB_ALERT_STATE.ALERTSTATE_ID, LOB_ALERT_STATE.IDPATH, LOB_ALERT_STATE.SRC_EVENT_DTTM, LOB_ALERT_STATE.ALERTSTATE, LOB_ALERT_STATE.DURATION, LOB_ALERT_STATE.EVENTTYP_DESC, LOB_ALERT_STATE.GTM_ID FROM GTM.LOB_ALERT_STATE LOB_ALERT_STATE WHERE (LOB_ALERT_STATE.SRC_EVENT_DTTM>={ts ?date_range} AND LOB_ALERT_STATE.SRC_EVENT_DTTM<{ts ?date_range}) AND LOB_ALERT_STATE.IDPATH LIKE {GTM_COMP_L.IDPATH passed from main report} + '%' ORDER BY LOB_ALERT_STATE.NAME, LOB_ALERT_STATE.RESOURCE_PATH
This section describes the installation and configuration of the Tivoli Business Systems Manager warehouse pack.
Before installing the warehouse pack, you must install the following software:
For information about Tivoli Data Warehouse hardware and software requirements, refer to Tivoli Data Warehouse Release Notes.
This warehouse pack supports central data warehouses and data marts on the following environments:
_SetSystemConfiguration 'ROOT', 0, 'TWH', 'GMT_CHANGE_TIME', <date time>, DATETIME'In this example, <date time> is the date and time that you need to change. The format is YYYY-MM-DD HH:MM:SS.xxx, where the xxx is fractions of seconds. For example: 2004-09-01 11:00:00.000 changes the date to September 1, 2004 and the time to 11:00 a.m. Set this value before the time change occurs.
The warehouse pack loads component, measurement, and event data in Tivoli Data Warehouse. Ensure that you have sufficient space in the Tivoli Data Warehouse databases for the historical data collected by the warehouse pack. To estimate how much space is required for the warehouse pack, complete the worksheets in Table 2, Table 3, and Table 4. Refer to Installing and Configuring Tivoli Data Warehouse for more information about Tivoli Data Warehouse database structure.
For example, before adding /3GB switch boot.ini has:
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /PAE /fastdetect
after modifing it should be:
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /PAE /fastdetect /3GB
To estimate sizing for the central data warehouse, complete Table 2. Get appropriate sizing information for columns by using the directions that follow.
Data type | Number of components | Number of days to keep | Number of events per day | Disk space (MB) |
---|---|---|---|---|
Component | x | x | ||
Measurement | x | x | ||
Event | x | |||
Static data | x | x | x | 100 |
Staging tables | x | x | x | 500 |
Total | x | x | x |
SELECT DISTINCT cid, id FROM ObjPathCacheThe number of rows returned is the number of the non-deleted components in the Tivoli Business Systems Manager database.
SELECT PMSMTC_AGE_IN_DAYS FROM TWG.PRUNE_MSMT_CONTROL WHERE MSRC_CD= 'GTM'
SELECT event_age FROM TWG.PRUNE_EVENT_CTRL WHERE MSRC_CD = 'GTM'
select count(*) from event where ctime between DATEADD(dd, -7, getdate()) and getdate() select count(*) from AlertStateHistory where cid = 'LOB' and ctime between DATEADD(dd, -7, getdate()) and getdate() select count(*) from NoteHistory where TimeExecuted between DATEADD (dd, -7, getdate()) and getdate()
<Number of components>* 1.3(MB)
SELECT COUNT(*) FROM LineOfBusiness_V WHERE deleted = 0Calculate the disk space for the measurement using the following formula:
Number of Business System components>
*<Number of times ETL runs per day>
*<Number of days to keep from the measurement row in Table 2>
<Number of days to keep from the event row in Table 2> * <Number of events per day from Table 2> *12(KB) + <Number of events per day from Table 2> * 0.1% * 20(KB)
To estimate sizing for the data mart, complete Table 3. Get appropriate sizing information for columns by using the directions that follow.
Data type | Number of days to keep | Disk space (MB) |
---|---|---|
Component | x | |
Event | ||
Static data | x | 500 |
Staging tables | x | 500 |
Total | x |
SELECT *FROM GTM.EVENT_PRUNE
<Number of components from Table 2>*6.1(KB)
<Number of days to keep from table 3 for event> * <Number of event per day from table 3> * 12(KB) + <Number of event per day from table 3> * 1%*12(KB) + <Number of events per day from table 3> * 0.1%*20(KB)
To estimate the total storage needed, complete Table 4. Get appropriate sizing information for columns by using the directions that follow.
Database | Fixed storage requirement | Variable storage requirement | Estimated total storage (fixed + variable) |
---|---|---|---|
Central data warehouse | 110 MB | ||
Control database | 10 MB | 0 | 10 MB |
Data mart | 10 MB |
The storage usage for the control database does not change very much across environments. The fixed values are shown in the Fixed storage requirement column.
Review the tasks in this section before you begin to install the warehouse pack.
If you have not installed Tivoli Business Systems Manager warehouse pack, version 3.1.0.0 and will be running the DB2 Universal Database data warehouse agent on the Windows platform for this warehouse pack, install the Microsoft SQL Server 2000 client on the server on which you run the DB2 Universal Database data warehouse agent.
Create an alias using the Microsoft SQL server client network utility tool with the parameters shown in Table 5.
Parameter | Value |
---|---|
Server alias | Short computer name of the Tivoli Business Systems Manager database server |
Network libraries | TCP/IP |
Server name | Fully-qualified name of the Tivoli Business Systems Manager database server |
Install the warehouse pack as described in Installing and Configuring Tivoli Data Warehouse, using the twh_install_props.cfg installation properties file. The twh_install_props.cfg installation properties file, is located in Tivoli Business Systems Manager 3.1.0.0-TIV-BSM-IF004 in the <tdw_apps/gtm> directory.
After you install the warehouse pack, you must do the following steps.
SELECT * FROM TWG.CUR_COMP WHERE COMPTYP_CD = 'TBSM_LOB'
The central data warehouse ETL uses the PMsmtC_Age_In_Days value of the TWG.Prune_Msmt_Control table to control how much of the measurement data should be loaded during the initialization process. The default value is 180. For larger databases, set the PMsmtC_Age_In_Days value to 90 using the following SQL command in a DB2 Universal Database command window on the DB2 Universal Database data warehouse control server:
DB2 connect to TWH_CDW user <username> using <password> DB2 UPDATE TWG.Prune_Msmt_Control SET PMsmtC_Age_In_Days = 90 WHERE MSRC_CD = 'GTM'
DB2 connect to TWH_CDW user <username> using <password> DB2 UPDATE TWG.Prune_Msmt_Control SET PMsmtC_Age_In_Days = 180 WHERE MSRC_CD = 'GTM'
Run the steps of the process in the following order:
Be sure to promote the following steps to test mode to avoid loading Tivoli Data Warehouse reporting data:
EXEC _GetETLTriggerState
By default, the triggers are disabled.
To enable the triggers, from the DB2 Universal Database Data Warehouse Center, run the GTM_c05_s020_Enable_RPT_Trigger step in the process GTM_c05_Maintenance_Process.
To disable the triggers, from the DB2 Universal Database Data Warehouse Center, run the GTM_c05_s030_Disable_RPT_Trigger step in the process GTM_c05_Maintenance_Process.
Make sure there are no Tivoli Business Systems Manager ETL steps running when you enable or disable the triggers.
This warehouse pack only loads Messages, Exceptions, and Child Events from the operational database into the data warehouse during the initialization. Existing Alert State change and Note information in the operational database is not loaded into the central data warehouse the first time you install.
Run the steps of the process in the following order:
SELECT * FROM TWG.CUR_COMP WHERE COMPTYP_CD = 'TBSM_LOB'
DB2 connect to TWH_CDW user <user name> using <password> DB2 UPDATE TWG.Prune_Msmt_Control SET PMsmtC_Age_In_Days = 90 WHERE MSRC_CD = 'GTM'
The warehouse pack supports two configurations, using Triggers and not using triggers, to capture Tivoli Business Systems Manager data for Tivoli Data Warehouse reporting. Make sure your configuration is correct by running the following command in the Microsoft SQL Query Analyzer on the Tivoli Business Systems Manager Object database:
EXEC _GetETLTriggerState
By default, the triggers are disabled.
To enable the triggers, from the DB2 Universal Database Data Warehouse Center, run the GTM_c05_s020_Enable_RPT_Trigger step in the process GTM_c05_Maintenance_Process.
To disable the triggers, from the DB2 Universal Database Data Warehouse Center, run the GTM_c05_s030_Disable_RPT_Trigger step in the process GTM_c05_Maintenance_Process.
Make sure there are no Tivoli Business Systems Manager ETL steps running when you enable or disable the triggers.
This warehouse pack loads only Messages, Exceptions, and ChildEvents from the operational database into the data warehouse during the initialization. Existing Alert State change and Note information in the operational database is not loaded into the central data warehouse during the initialization.
DB2 connect to TWH_CDW user <user name> using <password> DB2 UPDATE TWG.Prune_Msmt_Control SET PMsmtC_Age_In_Days = 180 WHERE MSRC_CD = 'GTM'
The migration process migrates all resources loaded with the Tivoli Business Systems Manager Warehouse Pack, version 2.1.1 to resources used in the Tivoli Business Systems Manager Warehouse Pack, version 3.2.0.0. The Tivoli Business Systems Manager Warehouse Pack, version 3.2.0.0 uses the BUSINESS_SYSTEM common component type for the Tivoli Business Systems Manager business system resource class (instead of the TBSM_LOB component type in the TWH_CDW database that was used in the previous release). The measurement matrix of the Tivoli Business Systems Manager business systems is changed from a percentage (in hours) to the state transition measurement matrix.
For the warehouse pack and Tivoli Service Level Advisor to function correctly, do the following steps:
The data in the GTM.MIGR_COPM table is used to perform the migration in the Tivoli Service Level Advisor database for the resource changes. The branch value mapping rules are described in the APAR IY48333-13 document.
Uninstall the warehouse pack as described in Installing and Configuring Tivoli Data Warehouse. When the warehouse pack is uninstalled, all the staging and working tables in the GTM schema are removed, but the data in the central data warehouse remains and is still usable by other applications.
This section describes maintenance tasks for the warehouse pack.
The GTM_c10_Load_Process and GTM_m10_Load_process processes load data incrementally using the extraction control in the Tivoli Business Systems Manager database. Run the GTM_c05_Init_Process and GTM_c15_Migration_Process processes only as documented and do not run them regularly.
The warehouse pack does not require any special procedure for backing up databases.
For common backup procedures, refer to the Installing and Configuring Tivoli Data Warehouse guide.
If you restore either the Tivoli Business Systems Manager Object database or the central data warehouse databases before you create new business systems and executive dashboard service resources, use the following procedure to synchronize the extraction control in Tivoli Business Systems Manager and Tivoli Data Warehouse before you schedule the ETL:
To keep the size of the databases manageable, every once in a while you should delete, or prune, data.
The CDW_c05_Prune_and_Mark_Active process in the CDW_Tivoli_Data_Warehouse_v1.2.0_Subject_Area controls the deletion. By default, this process runs daily at 6:00 am.
To manage the high volume of measurement data, use the TWG.Prune_Msmt_Control table to delete the data that is not needed. The TWG.Prune_Msmt_Log table keeps a history of data deletion. The Tivoli Business Systems Manager measurement data is retained in the Central Data Warehouse for 180 days by default. This default value is saved in the PMsmtC_Age_In_Days column of the TWG.Prune_Msmt_Control table. You can change the PMsmtC_Age_In_Days value using the following command from the DB2 Universal Database command window on the Tivoli data warehouse control server:
DB2 UPDATE TWG.Prune_Msmt_Control SET PMSMTC_AGE_IN_DAYS = 30 WHERE MSRC_CD = 'GTM' AND TMSUM_CD = 'P'
Measurement data is pruned from the TWG.MSMT table based on the age specified in the PMsmtC_Age_In_Days column.
The PMsmtC_Age_In_Days value should be set back to 180 days after completing the post initialization process described in Post-installation procedures.
Tivoli Data Warehouse uses the event age and the event date and time to find aged events. Aged events are events that are older than the value specified in the Event_Age column. The data is deleted in the following order:
The value in the Event_Age column for MSRC_CD = 'GTM' is set to 90 during installation. You may change it using the following command in the central data warehouse:
Update TWG.PRUNE_EVENT_CTRL SET EVENT_AGE = <number of days to keep> WHERE MSRC_CD = 'GTM'
Data is pruned from the fact tables using the GTM_m10_s050_Event_Prune step. The GTM.Event_Prune table in the data mart governs which data is pruned. The event_age_in_days column contains the number of days of data for the GTM.F_EVENT, GTM.F_NOTE, and GTM.F_ASHISTORY fact tables. By default, all data in the fact tables older than 365 days is pruned when the step runs. The GTM.Event_Prune_Log table keeps a history of data pruning.
You may change the event_age_in_days value by using the following command in the data mart:
Update GTM.EVENT_PRUNE SET EVENT_AGE_IN_DAYS =WHERE MSRC_CD = 'GTM'
The extraction control table, as shown in Table 6, assists you in incrementally extracting data from a source database. For an example of incremental extraction, refer to the Enabling an Application for Tivoli Data Warehouse guide.
ExtCtl_
Source VARCHAR (120) |
ExtCtl_
Target VAR CHAR (120) |
ExtCtl_
From_ Raw Seq CHAR (10) |
ExtCtl_
To_ Raw Seq CHAR (10) |
ExtCtl_
From_ IntSeq BIG INT |
ExtCtl_
To_ IntSeq BIG INT |
ExtCtl_
From_ DtTm TIME STAMP |
ExtCtl_
To_ DtTm TIME STAMP |
MSrc_
Corr_ Cd CHAR (6) |
---|---|---|---|---|---|---|---|---|
ETL1 | MSMT | - | - | 9999-01-01-00.00.00.000000 | 2004-10-26-21.04.45.183000 | GTM | ||
ETL1_linkc | CDW | 0 | 0 | 2004-10-07-15.17.38.030000 | 2004-10-07-15.17.38.030000 | GTM | ||
ETL1_linkp | CDW | 0 | 0 | 2004-10-07-15.17.38.030000 | 2004-10-07-15.17.38.030000 | GTM | ||
ETL1_MESG | CDW | 20 | 2692120 | 2004-10-29-09.48.54.287000 | 2004-10-29-09.48.54.287000 | GTM | ||
ETL1_events | CDW | 0 | 0 | 2004-10-29-10.08.27.357000 | 2004-10-28-09.01.41.363000 | GTM | ||
ETL1_ash | CDW | 6 | 1352660 | 2004-10-28-13.54.23.107000 | 2004-10-28-09.01.41.347000 | GTM | ||
ETL1_note history | CDW | 0 | 0 | 2004-10-28-13.54.23.373000 | 2004-10-28-09.01.41.363000 | GTM | ||
EVENT_ID | MART | 0 | 10101 | 2004-10-26-20.40.52.312004 | 2004-10-26-21.04.45.183000 | GTM | ||
ETL1_EXCP | CDW | 20 | 269147 | 2004-10-28-13.54.23.373000 | 2004-10-28-09.01.41.363000 | GTM | ||
ETL1_CHEV | CDW | 19 | 145692 | 2004-10-26-20.40.52.312004 | 2004-10-26-21.04.45.183000 | GTM |
For common problems and solutions, refer to the Installing and Configuring Tivoli Data Warehouse guide. This section only documents the guidelines and problem determination strategies specific to the warehouse pack. If any of the central data warehouse ETL steps fail, there are three places to get the error messages:
For the further problem determination, use the following utilities:
The warehouse pack requires the Microsoft SQL Server network client to be installed on the server where the DB2 Universal Database warehouse agent is used. You can install either the Microsoft SQL client or the Microsoft SQL network client, though you can use the Microsoft SQL client for debugging. After the Tivoli Business Systems Manager Warehouse Pack, version 3.2.0.0 is installed, the connection should be tested during the installation procedure. If anything changes for the network connectivity after the installation, the following methods can be used to verify the connection:
The following extraction control tables are used in the Tivoli Business Systems Manager Object database:
To view the data in Microsoft SQL query analyzer, use the following code:
SELECT * FROM table_name
For example,
SELECT * FROM twh_objs
The following extraction controls are provided in the Tivoli Data Warehouse database:
Use the following DB2 Universal Database command to view the data in the Tivoli Data Warehouse database:
SELECT * FROM TWG.EXTRACT_CONTROL WHERE ExtCtl_MSrc_Corr_Cd = 'GTM' SELECT * FROM GTM.Resource
The following stored procedures in the Tivoli Business Systems Manager Object database can be run as diagnostic tools:
These can be run multiple times without affecting the ETL processes.
The subject area GTM_Tivoli_Business_Systems_Manager_v3.1_Subject_Area contains the following processes:
This process is used for the central data warehouse ETL.
The GTM_c05_Maintenance_Process process is designed for the initialization and migration of the Tivoli Data Warehouse central data warehouse ETL. For performance reasons, the Tivoli Business Systems Manager central data warehouse ETL saves the extraction control and mapping tables in both the Tivoli Business Systems Manager database (source database) and the Tivoli Data Warehouse central database (target database). You must synchronize the extraction controls and the mapping tables in these databases before the normal process, which is performed by the initialization steps in GTM_c05_Maintenance_Process.
This process does the following tasks:
See the following sections for instructions on how to use this process:
Run this process after installing the warehouse pack, applying fixes, or restoring databases. It is defined to run on-demand.
This process has the following steps:
See Migrating from a previous release of the warehouse pack for more information about the migration process.
This process is used for the central data warehouse ETL.
This process extracts, transforms, and loads the business systems and executive dashboard services information, the measurement data of the BUSINESS SYSTEM components, all the managed resource information, and events from the Tivoli Business Systems Manager database to the TWH_CDW database. The data is saved in the staging tables in the GTM schema of the TWH_CDW database, and then the transformed data is loaded from the staging tables into the permanent tables in the TWH_CDW database based on the mapping of the Tivoli Business Systems Manager resources to the Tivoli Data Warehouse components. This process is designed to run incrementally after initialization using the extraction control in Tivoli Business Systems Manager application database.
There are two groups of steps in the GTM_c10_Load_Data_Process process. The following steps integrate Tivoli Business Systems Manager with Tivoli Service Level Advisor:
You need the following additional steps for Tivoli Business Systems Manager reports:
Run this process after installing the warehouse pack and the initialization process. It is scheduled to run once a day before the Tivoli Service Level Advisor ETL runs, if applicable. You can schedule these two groups together or separately. Refer to the information about installing warehouse packs in Installing and Configuring Tivoli Data Warehouse for the procedure to schedule ETLs.
The GTM_c10_Load_Data_Process process consists of the following steps:
The GTM_m05_Maintenance_Process process is used for the data mart ETL initialization and maintenance.
This process has one step. The GTM_m05_s010_Init step rebuilds the extraction controls in the Tivoli Data Warehouse central database and data mart based on the data in the Tivoli Data Warehouse data mart. It also reloads the meta data, such as Alert State, Priority, and OBJ_CLASS.
This process should run on-demand.
The GTM_m10_Load_Data_Process process is used for the data mart ETL.
This process extracts, transforms, and loads the components and their changes, events, the relationships of events, and the relationship of components with events loaded from the Tivoli Business Systems Manager database from the Tivoli Data Warehouse central databases into the GTM star schemas defined in the Tivoli Data Warehouse data mart. The data is saved in the staging tables in the GTM schema, and then the transformed data is loaded from the staging tables into the permanent tables.
The resource path and id path for the new components are constructed using the component relationships. The paths or id paths for the existing components are reconstructed for the name or relationship changes. This process is designed to run incrementally using the extraction control in the Tivoli Data Warehouse data mart. Run this process after installing the warehouse pack and the initialization process. It is scheduled to run once a day after the GTM_c10_Load_Data_Process process.
This process has the following steps:
Before reading this section, read about the generic schema for the central data warehouse, which is described in Tivoli Data Warehouse Schema Reference. That document defines the content of each table and explains the relationships between the tables in this document.
Shaded columns in the following tables are translated. These columns are also marked with an asterisk (*) after the column name.
The following sections describe the component configuration.
Table 7 shows the fields of the TWG.CompTyp table.
CompTyp_Cd
CHAR(17) |
CompTyp_
Parent_ Cd CHAR(17) |
CompTyp_Nm*
CHAR(120) |
CompTyp_Strt_
DtTm TIMESTAMP |
CompTyp_End_
DtTm TIMESTAMP |
MSrc_Corr_Cd
CHAR(6) |
---|---|---|---|---|---|
MVS_SYSTEM | NULL | MVS System | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
LOGICAL_PARTITION | NULL | Logical Partition | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
GTM_RESOURCE | NULL | Tivoli Business Systems Manager Generic Type | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | GTM |
IP_HOST | NULL | IP Host | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
GTM_HOST | NULL | Short Named IP Host | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 | GTM |
IP_NODE | NULL | IP Node | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
IP_INTERFACE | NULL | IP Interface | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
MQ_QUEUE_MANAGER | NULL | MQ Queue Manager | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
MQ_QUEUE | NULL | MQ Queue | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
MQ_CHANNEL | NULL | MQ Channel | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
SNA_NETWORK | NULL | SNA Network | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
SNA_CCU | NULL | SNA Communication Control Unit | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
BUSINESS_
SYSTEM |
NULL | Business System | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
SERVICE | NULL | Service | 2002-07-13-00.00.00..000000 | 9999-01-01-12.00.00.000000 | MODEL1 |
This warehouse pack does not use the TWG.Comp_Ext table.
Table 8 shows the fields of the Comp table.
Comp
_ID BIG INT |
CompTyp_Cd
CHAR (17) |
Centr_Cd
CHAR (6) |
Cust_ID
INT |
Comp_
Corr_ID INT |
Comp_Nm
CHAR (254) |
Comp_
Corr_ Val CHAR (254) |
Comp_Strt
_DtTm TIMESTAMP |
Comp_End_
DtTm TIMESTAMP |
Comp
_Ds CHAR (254) |
MSrc_
Corr_ Cd CHAR (6) |
---|---|---|---|---|---|---|---|---|---|---|
1 | BUSINESS_
SYSTEM |
CDW | 1 | NULL | Data Centers | LOB1 | 2002-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
2 | BUSINESS_
SYSTEM |
CDW | 1 | NULL | Eastern Complex | LOB2 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
3 | BUSINESS_
SYSTEM |
CDW | 1 | NULL | Bank1 | LOB3 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
4 | BUSINESS_
SYSTEM |
CDW | 1 | NULL | CICS A | LOB4 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
5 | BUSINESS_
SYSTEM |
CDW | 1 | NULL | Western Complex | LOB5 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
6 | BUSINESS_
SYSTEM |
CDW | 1 | NULL | Bank1 | LOB6 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
7 | BUSINESS_
SYSTEM |
CDW | 1 | NULL | CICS B | LOB7 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
8 | SERVICE | CDW | 1 | NULL | Eastern Saving | 7614a3bb-13cf-3841-91cd-5e845c831ada | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
9 | SERVICE | CDW | 1 | NULL | Data Centers | 64b73f0a-839d-3cd2-999f-6dd4cc76dfed | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
10 | GTM_
RESOURCE |
CDW | 1 | NULL | Eastern Bank | ENT|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | GTM |
9 | GTM_
RESOURCE |
CDW | 1 | NULL | DD01 | MACH|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | GTM |
12 | LOGICAL_
PARTITION |
CDW | 1 | NULL | P001 | LPAR|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
13 | MVS_
SYSTEM |
CDW | 1 | NULL | YSYS | OS|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
14 | BUSINESS_
SYSTEM |
CDW | 1 | NULL | Machine 2 | LOB|8 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | GTM |
15 | BUSINESS_
SYSTEM |
CDW | 1 | NULL | YSYS | LOB9 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
16 | GTM_
RESOURCE |
CDW | 1 | NULL | MQ Series A | MSER|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | GTM |
17 | MQ_QUEUE_
MANAGER |
CDW | 1 | NULL | MQ Manager A | MMGR|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
18 | MQ_QUEUE | CDW | 1 | NULL | Local Queue1A | MQLC|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
19 | MQ_QUEUE | CDW | 1 | NULL | Remote Queue1A | MQRT|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
20 | MQ_
CHANNEL |
CDW | 1 | NULL | Sender Channel A | MQSD|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
21 | SNA_
NETWORK |
CDW | 1 | NULL | USIBMNT | SNNT|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
22 | SNA_CCU | CDW | 1 | NULL | t4 Node Gateway | T4NG|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
21 | GTM_
RESOURCE |
CDW | 1 | NULL | Network Location A | NLOC|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | GTM |
24 | IP_HOST | CDW | 1 | NULL | fhmachine.raleigh.ibm.com | UNIX|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
25 | IP_NODE | CDW | 1 | NULL | tsgtermb.tivlab.raleigh.ibm.com | ROUT|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
26 | IP_
INTERFACE |
CDW | 1 | NULL | 9.42.16.172 | INTR|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | SHARED |
27 | GTM_HOST | CDW | 1 | NULL | NLGS000034 | NODE|1 | 2001-11-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NULL | GTM |
Table 9 shows the fields of the TWG.RelnTyp table.
Any component type from the resource diagram can be linked to the business system with the GTM_LB relation type.
Table 10 shows the fields of the TWG.RelnRul table.
CompTyp_Source_Cd
CHAR(17) |
CompTyp_Target_Cd
CHAR(17) |
RelnTyp_Cd
CHAR(6) |
RelnRul_Strt_
DtTm TIMESTAMP |
RelnRul_End_
DtTm TIMESTAMP |
---|---|---|---|---|
GTM_RESOURCE | GTM_RESOURCE | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
GTM_RESOURCE | LOGICAL_PARTITION | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
MVS_SYSTEM | LOGICAL_PARTITION | RUNSON | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
LOGICAL_PARTITION | MVS_SYSTEM | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
MVS_SYSTEM1 | GTM_RESOURCE | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
MVS_SYSTEM | SNA_NETWORK | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
SNA_NETWORK | SNA_CCU | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
SNA_NETWORK1 | GTM_RESOURCE | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
SNA_CCU1 | GTM_RESOURCE | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
GTM_RESOURCE | MQ_QUEUE_MANAGER | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
MQ_QUEUE_MANAGER | MQ_QUEUE | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
MQ_QUEUE_MANAGER | MQ_CHANNEL | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
MQ_QUEUE_MANAGER1 | GTM_RESOURCE | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
GTM_RESOURCE | IP_HOST | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
GTM_RESOURCE | IP_NODE | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
GTM_RESOURCE | GTM_HOST | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
IP_HOST | IP_INTERFACE | NETWRK | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
IP_NODE | IP_INTERFACE | NETWRK | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
GTM_HOST | IP_INTERFACE | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
IP_INTERFACE1 | GTM_RESOURCE | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | MQ_QUEUE_MANAGER | GTM_LB | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | MQ_QUEUE | GTM_LB | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | MQ_CHANNEL | GTM_LB | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | IP_HOST | GTM_LB | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | IP_NODE | GTM_LB | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | IP_INTERFACE | GTM_LB | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | GTM_HOST | GTM_LB | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | SNA_NETWORK | GTM_LB | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | SNA_CCU | GTM_LB | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | BUSINESS_SYSTEM | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
BUSINESS_SYSTEM | SERVICE | SUPPRT | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
SERVICE | SERVICE | PCHILD | 2002-07-13-00.00.00..000000 | 9999-01-01-00.00.00.00 |
Table 11 shows the fields of the TWG.CompReln table.
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 | 2 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
2 | 3 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
3 | 4 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
1 | 5 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
5 | 6 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
6 | 4 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
6 | 7 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
8 | 3 | SUPPRT | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
9 | 1 | SUPPRT | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
10 | 11 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | GTM |
13 | 12 | RUNSON | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
11 | 12 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | GTM |
13 | 16 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | GTM |
16 | 17 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | GTM |
17 | 18 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
17 | 19 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
17 | 20 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
13 | 21 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | GTM |
21 | 22 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
10 | 23 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | GTM |
23 | 25 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | GTM |
23 | 24 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | GTM |
23 | 27 | PCHILD | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | GTM |
24 | 26 | NETWRK | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SHARED |
1 | 13 | GTM_LB | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | GTM |
This warehouse pack does not use the TWG.CompTyp_Keyword table.
Table 12 shows the fields of the TWG.AttrTyp table.
AttrTyp_Cd
CHAR(17) |
AttrTyp_Nm*
CHAR(120) |
MSrc_
Corr_Cd CHAR(6) |
---|---|---|
* This column is translated. | ||
GTM_CID | Tivoli Business Systems Manager Class Identification | GTM |
GTM_DELETE | Tivoli Business Systems Manager Logical Delete Attribute | GTM |
GTM_ENABLE | Service Component Status | GTM |
GTM_ID | Tivoli Business Systems Manager Object Identification | GTM |
GTM_RTYPE | Physical Resource Type | GTM |
NAME | Name | MODEL1 |
NAME_GUID | Name Global Unique Identifier | MODEL1 |
USER_LABEL | User Label | MODEL1 |
Table 13 shows the fields of the TWG.AttrRul table.
CompTyp_Cd
CHAR(17) |
AttrTyp_Cd
CHAR(17) |
AttrRul_Strt_
DtTm TIMESTAMP |
AttrRul_End_DtTm
TIMESTAMP |
AttrRul_
Dom_Ind CHAR(1) |
AttrTyp_
Multi_ Val CHAR(1) |
---|---|---|---|---|---|
BUSINESS_
SYSTEM |
GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
BUSINESS_
SYSTEM |
GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
BUSINESS_
SYSTEM |
GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
BUSINESS_
SYSTEM |
GTM_RTYPE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
BUSINESS_
SYSTEM |
NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
GTM_HOST | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
GTM_HOST | GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
GTM_HOST | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
GTM_HOST | NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
GTM_
RESOURCE |
GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
GTM_
RESOURCE |
GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
GTM_
RESOURCE |
GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
GTM_
RESOURCE |
NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_HOST | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_HOST | GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_HOST | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_HOST | IP_SHORT_HOSTNAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_
INTERFACE |
GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_
INTERFACE |
GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_
INTERFACE |
GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_NODE | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_NODE | GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_NODE | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_NODE | NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
IP_NODE | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
LOGICAL_
PARTITION |
GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
LOGICAL_
PARTITION |
GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
LOGICAL_
PARTITION |
GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
LOGICAL_
PARTITION |
NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
LOGICAL_
PARTITION |
USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_CHANNEL | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_CHANNEL | GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_CHANNEL | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_CHANNEL | NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_CHANNEL | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_QUEUE | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_QUEUE | GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_QUEUE | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_QUEUE | NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_QUEUE | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_QUEUE_
MANAGER |
GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_QUEUE_
MANAGER |
GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_QUEUE_
MANAGER |
GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_QUEUE_
MANAGER |
NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MQ_QUEUE_
MANAGER |
USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MVS_SYSTEM | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MVS_SYSTEM | GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MVS_SYSTEM | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MVS_SYSTEM | NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
MVS_SYSTEM | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SERVICE | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SERVICE | GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SERVICE | GTM_ENABLE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SERVICE | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SERVICE | NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SERVICE | NAME_GUID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SERVICE | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SNA_CCU | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SNA_CCU | GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SNA_CCU | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SNA_CCU | NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SNA_CCU | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SNA_
NETWORK |
GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SNA_
NETWORK |
GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SNA_
NETWORK |
GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SNA_
NETWORK |
NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
SNA_
NETWORK |
USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | N | N |
This warehouse pack does not use the TWG.AttrDom table.
Table 14 shows the fields of the TWG.CompAttr table.
Comp_ID
BIGINT |
AttrTyp_Cd
CHAR(17) |
CompAttr_
Strt_DtTm TIMESTAMP |
CompAttr_End_
DtTm TIMESTAMP |
CompAttr_Val
VARCHAR(254) |
MSrc_Corr_Cd
CHAR(6) |
---|---|---|---|---|---|
1 | NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | Data Centers | GTM |
1 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | GTM |
1 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | LOB | GTM |
2 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 2 | GTM |
2 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | LOB | GTM |
3 | NAME | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | Bank1 Enterprise | GTM |
3 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 3 | GTM |
3 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | LOB | GTM |
4 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 4 | GTM |
4 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | LOB | GTM |
4 | GTM_RTYPE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | CICS | GTM |
5 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 5 | GTM |
5 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | LOB | GTM |
6 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 6 | GTM |
6 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | LOB | GTM |
7 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 7 | GTM |
7 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | LOB | GTM |
7 | GTM_RTYPE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | CICS | GTM |
8 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | GTM |
8 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | EXES | GTM |
8 | NAME_GUID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 7614a3bb-13cf-3841-91cd-5e845c831ada | GTM |
8 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | Mortgage | GTM |
9 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 9 | GTM |
9 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | EXES | GTM |
9 | NAME_GUID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 64b73f0a-839d-3cd2-999f-6dd4cc76dfed | GTM |
8 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | Data Centers | GTM |
9 | GTM_ENABLE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 0 | GTM |
10 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | ENT | GTM |
10 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | GTM |
11 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | MACH | GTM |
11 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | GTM |
12 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | MACH | MODEL1 |
12 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
12 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | EA01 | MODEL1 |
13 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | LPAR | MODEL1 |
13 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
13 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | OS 1 | MODEL1 |
16 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | MSER | GTM |
16 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | GTM |
17 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | MMGR | MODEL1 |
17 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
17 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | MQ Manager 1 | MODEL1 |
18 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | MQLA | MODEL1 |
18 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
18 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | Local Queue | MODEL1 |
19 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | MQRT | MODEL1 |
19 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
19 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | Remote Queue | MODEL1 |
20 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | MQRV | MODEL1 |
20 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
20 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | MQ Channel | MODEL1 |
21 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SNNT | MODEL1 |
21 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
21 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SNA Network1 | MODEL1 |
22 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | T4NG | MODEL1 |
22 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
22 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | SNA Gateway | MODEL1 |
23 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | NLOC | GTM |
23 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | GTM |
25 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | ROUT | MODEL1 |
25 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
25 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | Router 1 | MODEL1 |
24 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | UNIX | MODEL1 |
24 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
24 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | UNIX 1 | MODEL1 |
26 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | INTR | MODEL1 |
26 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | MODEL1 |
26 | USER_LABEL | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 9.9.24.12 | MODEL1 |
27 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | Ornage12 | GTM |
27 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | GTM |
14 | GTM_DELETE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 1 | GTM |
14 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | LOB | GTM |
14 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 8 | GTM |
15 | GTM_CID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | LOB | GTM |
15 | GTM_ID | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | 9 | GTM |
15 | GTM_RTYPE | 2003-1-28-11.36.54.000000 | 9999-01-01-00.00.00.00 | Operating System | GTM |
This warehouse pack does not use the TWG.CTypReln table.
This warehouse pack does not use the TWG.ATypReln table.
The following sections describe the component measurement tables.
Table 15 shows the fields of the TWG.MGrpTyp table.
MGrpTyp_Cd
CHAR(6) |
MGrpTyp_Nm*
CHAR(120) |
---|---|
* This column is translated. | |
GROUP | Aggregate Types or Group Functions |
TRANS | State Transition Groups |
Table 16 shows the fields of the TWG.MGrp table.
MGrp_Cd
CHAR(6) |
MGrpTyp_Cd
CHAR(6) |
MGrp_Parent_Cd
CHAR(6) |
MGrp_Nm*
CHAR(120) |
---|---|---|---|
* This column is translated. | |||
GTMOBJ | TRANS | NULL | Tivoli Business Systems Manager Management State Transition Measurement |
TOT_E | GROUP | NULL | Total Value Exists |
Table 17 shows the fields of the TWG.MGrpMbr table.
MGrp_Cd
CHAR(6) |
MGrpTyp_Cd
CHAR(6) |
MsmtTyp_ID
INT |
---|---|---|
GTMOBJ | TRANS | 1 |
GTMOBJ | TRANS | 2 |
GTMOBJ | TRANS | 3 |
GTMOBJ | TRANS | 4 |
GTMOBJ | TRANS | 5 |
GTMOBJ | TRANS | 6 |
TOT_E | GROUP | 1 |
TOT_E | GROUP | 2 |
TOT_E | GROUP | 3 |
TOT_E | GROUP | 4 |
TOT_E | GROUP | 5 |
TOT_E | GROUP | 6 |
Table 18 shows the fields of the TWG.MUnitCat table.
MUnitCat_Cd
CHAR(6) |
MUnitCat_Nm*
CHAR(120) |
---|---|
* This column is translated. | |
TM | Time Duration |
Table 19 shows the fields of the TWG.MUnit table.
MUnit_Cd
CHAR(6) |
MUnitCat_Cd
CHAR(6) |
MUnit_Nm*
CHAR(120) |
---|---|---|
* This column is translated. | ||
Min | TM | Minutes |
This warehouse pack does not use the TWG.MTypReln table.
This warehouse pack does not use the TWG.TmSum table.
Table 20 shows the fields of the TWG.MSrc table.
MSrc_Cd
CHAR(6) |
MSrc_Parent_Cd
CHAR(6) |
MSrc_Nm*
CHAR(120) |
---|---|---|
* This column is translated. | ||
GTM | NULL | Tivoli Business Systems Manager |
This warehouse pack does not use the TWG.MSrc_History table.
Table 21 shows the fields of the TWG.MsmtTyp table.
MsmtTyp_ID
INT |
MUnit_Cd
CHAR(6) |
MSrc_Cd
CHAR(6) |
MsmtTyp_Nm
CHAR(120) |
MsmtTyp_Ds*
CHAR(254) |
---|---|---|---|---|
* This column is translated. | ||||
1 | Min | MODEL1 | Available | The amount of time that the resource is available |
2 | Min | MODEL1 | Degrading | The amount of time that the resource is degrading |
3 | Min | MODEL1 | Unavailable | The amount of time that the resource is unavailable |
4 | Min | MODEL1 | Repairing | The amount of time that it took to fix the problem associated with the resource |
5 | Min | MODEL1 | Unmanaged | The amount of time that the resource is unmanaged |
6 | Min | MODEL1 | Unknown | The amount of time that the state of the resource is unknown |
Table 22 shows the fields of the TWG.MsmtRul table.
CompTyp_Cd
CHAR(17) |
MsmtTyp_ID
INT |
---|---|
BUSINESS_SYSTEM | 1 |
BUSINESS_SYSTEM | 2 |
BUSINESS_SYSTEM | 3 |
BUSINESS_SYSTEM | 4 |
BUSINESS_SYSTEM | 5 |
BUSINESS_SYSTEM | 6 |
Table 23 shows the fields of the TWG.Msmt table.
Comp
_ID BIGINT |
MsmtTyp
_ID INT |
TmSum
_Cd CHAR(1) |
Msmt
_Strt_DT DATE |
Msmt
_Strt_TM TIME |
Msmt
_Min_Val DOUBLE |
Msmt
_Max_Val DOUBLE |
Msmt
_Avg_Val DOUBLE |
Msmt
_Tot _Val DOUBLE |
Msmt
_Smpl _Cnt INT |
Msmt
_Err _Cnt INT |
MSrc
_Corr _Cd CHAR(6) |
Msmt
_StdDev _Val DOUBLE |
---|---|---|---|---|---|---|---|---|---|---|---|---|
3 | 2 | P | __DATE
(__NOW _TIME STAMP _GMT) |
11:00:00 AM | NULL | NULL | NULL | 10 | 0 | 0 | GTM | 0 |
3 | 3 | P | __DATE
(__NOW _TIME STAMP _GMT) |
16:00:00 | NULL | NULL | NULL | 70 | 0 | 0 | GTM | 0 |
3 | 4 | P | __DATE
(__NOW _TIME STAMP _GMT) |
15:00:00 | NULL | NULL | NULL | 3530 | 0 | 0 | GTM | 0 |
3 | 2 | P | __DATE
(__NOW _TIME STAMP _GMT) |
17:00:00 | NULL | NULL | NULL | 130 | 0 | 0 | GTM | 0 |
This warehouse pack does not use the TWG.MObj table.
This warehouse pack does not use the TWG.MObjRng table.
This warehouse pack does not use the TWG.SevLvl table.
The following section describes the component events.
Table 24 shows the fields of the TWG.EventTyp table.
EventTyp_ID
INT |
EventTyp_Nm
CHAR(254) |
MSrc_Cd
CHAR(6) |
EventTyp_Ds*
CHAR(254) |
---|---|---|---|
* This column is translated. | |||
1 | Alert State Change | GTM | Tivoli Business Systems Manager alert state change event |
2 | Child Event | GTM | Tivoli Business Systems Manager child event |
3 | Exception | GTM | Tivoli Business Systems Managerexception |
4 | Message | GTM | Tivoli Business Systems Manager message |
5 | Note | GTM | Tivoli Business Systems Manager note |
Table 25 shows the fields of the TWG.Event table.
Event_
ID BIGINT |
EventTyp_
ID INT |
Event_
DtTm TIMESTAMP |
TmSum_
Cd CHAR (1) |
MSrc_Cd
CHAR (6) |
Repeat_
Cnt INT |
Centr_Cd
CHAR (6) |
Cust_ID
INT |
Event_
Corr_ID INT |
Event_
Corr_ Val CHAR (254) |
---|---|---|---|---|---|---|---|---|---|
1 | 1 | 2003-1-28-11.36.54.000000 | P | GTM | 0 | CDW | 1 | NULL | GTM|1 |
2 | 2 | 2003-1-28-11.36.54.000000 | P | GTM | 0 | CDW | 1 | NULL | GTM|2 |
3 | 3 | 2003-1-28-11.36.54.000000 | P | GTM | 0 | CDW | 1 | NULL | GTM|3 |
4 | 4 | 2003-1-28-11.36.54.000000 | P | GTM | 0 | CDW | 1 | NULL | GTM|4 |
5 | 5 | 2003-1-28-11.36.54.000000 | P | GTM | 0 | CDW | 1 | NULL | GTM|5 |
Table 26 shows the fields of the TWG.EventAttr table.
Event_ID
BIGINT |
EAttrTyp_Cd
CHAR(254) |
MSrc_Cd
CHAR(6) |
EventAttr_Val
CHAR(3500) |
---|---|---|---|
1 | GTM_NAME | GTM | EA1043 |
1 | GTM_DETAIL | GTM | CICSTA0A ERROR:AFS LEVEL 4 EVENT ENGINE HALTED! CANNOT OBTAIN MASTER BANK, SQLSTATE = 51002L056. NOTIFY AFS(R) XPRESS SUPPORT ASAP. |
1 | GTM_EVENT_CID_ID | GTM | MESG: 1 |
1 | GTM_EVENT_ID | GTM | 1 |
1 | GTM_PRIORITY_ID | GTM | 2 |
1 | GTM_AS_ID | GTM | 3 |
2 | GTM_NAME | GTM | #TOTUTIL |
2 | GTM_DETAIL | GTM | PROCESSOR % total utilization = 23.000000 |
2 | GTM_EVENT_CID_ID | GTM | EXCP: 1 |
2 | GTM_EVENT_ID | GTM | 50 |
2 | GTM_EXCP_ID | GTM | 30 |
2 | GTM_PRIORITY_ID | GTM | 5 |
2 | GTM_ ALERTSTATE | GTM | 2 |
3 | GTM_NAME | GTM | NLOC-179 |
3 | GTM_DETAIL | GTM | NS_Node_Down_TEC
10485292691 |
3 | GTM_EVENT_CID_ID | GTM | CHEV: 1 |
3 | GTM_EVENT_ID | GTM | 101 |
3 | GTM_PRIORITY_ID | GTM | 1 |
3 | GTM_AS_ID | GTM | 3 |
4 | GTM_NAME | GTM | Bank_Topologi |
4 | GTM_DETAIL | GTM | Problem Note created by Problem Ticket Create GUI with problem id of 00023662 |
4 | GTM_NOTEID | GTM | 1 |
4 | GTM_NOTE_
EXECUTER |
GTM | tbsmoper1 |
4 | GTM_NOTE_ACTION | GTM | Opened |
4 | GTM_NOTE_TYPE | GTM | Ownership |
4 | GTM_NOTE_SUBJECT | GTM | Problem Note created by Problem Ticket Create GUI |
5 | GTM_OLD_AS_ID | GTM | 2 |
5 | GTM_AS_ID | GTM | 3 |
5 | GTM_DETAIL | GTM | CICSTA0A ERROR:AFS LEVEL 4 EVENT ENGINE HALTED! CANNOT OBTAIN MASTER BANK, SQLSTATE = 51002L056. NOTIFY AFS XPRESS SUPPORT ASAP. |
Table 27 shows the fields of the TWG.EAttrTyp table.
EAttrTyp_Cd
CHAR(254) |
EAttrTyp_Nm*
CHAR(254) |
MSrc_Cd
CHAR(6) |
---|---|---|
* This column is translated. | ||
EVENTTYP_ID | Tivoli Business Systems Manager Source Event Type Identifier | GTM |
GTM_AS_ID | Tivoli Business Systems Manager Alert State Identifier | GTM |
GTM_DETAIL | Tivoli Business Systems Manager Event Detail | GTM |
GTM_EVENT_ID | Tivoli Business Systems Manager Event identifier | GTM |
GTM_EVENT_CID_ID | Tivoli Business Systems Manager Event Unique Identifier | GTM |
GTM_NAME | Tivoli Business Systems Manager Event Name | GTM |
GTM_NOTE_ACTION | Tivoli Business Systems Manager Note Action | GTM |
GTM_NOTE_EXECUTER | Tivoli Business Systems Manager Note Executer | GTM |
GTM_NOTE_ID | Tivoli Business Systems Manager Note Identifier | GTM |
GTM_NOTE_SUBJECT | Tivoli Business Systems Manager Note Subject | GTM |
GTM_NOTE_TYPE | Tivoli Business Systems Manager Note Type | GTM |
GTM_OLD_AS_ID | Tivoli Business Systems Manager Exception Identifier | GTM |
GTM_PRIORITY_ID | Tivoli Business Systems Manager Priority Identifier | GTM |
Table 28 shows the fields of the TWG.EGrp table.
EGrp_Cd
CHAR(6) |
EGrpTyp_Cd
CHAR(6) |
EGrp_Parent_Cd
CHAR(6) |
EGrp_Nm*
CHAR(254) |
---|---|---|---|
* This column is translated. | |||
GTM | TIVOLI | NULL | Tivoli Business Systems Manager Event Group |
Table 29 shows the fields of the TWG.EGrpMbr table.
EGrp_Cd
CHAR(6) |
EGrpTyp_Cd
CHAR(6) |
EventTyp_ID
INT |
---|---|---|
GTM | TIVOLI | 1 |
GTM | TIVOLI | 2 |
GTM | TIVOLI | 3 |
GTM | TIVOLI | 4 |
GTM | TIVOLI | 5 |
Table 30 shows the fields of the TWG.EGrpTyp table.
EGrpTyp_Cd
CHAR(6) |
EGrpTyp_Nm*
CHAR(254) |
---|---|
* This column is translated. | |
TIVOLI | Event Group for Tivoli Products |
This warehouse pack does not use the TWG.ETypReln table.
Table 31 shows the fields of the TWG.EventReln table.
Event_Reln_
ID INT |
Event_Source_ID
INT |
Event_Target_ID
INT |
RelnTyp_Cd
CHAR(6) |
MSrc_Cd
CHAR(6) |
---|---|---|---|---|
1 | 1 | 4 | CAUSES | GTM |
2 | 1 | 5 | CAUSES | GTM |
Table 32 shows the fields of the TWG.CEReln table.
Cereln_ID
BIGINT |
Event_ID
BIGINT |
Comp_ID
BIGINT |
RelnTyp_Cd
CHAR(6) |
MSrc_Cd
CHAR(6) |
---|---|---|---|---|
1 | 1 | 10 | SOURCE | GTM |
2 | 2 | 11 | SOURCE | GTM |
3 | 3 | 12 | SOURCE | GTM |
Table 33 shows the fields of the TWG.ERelnRul table.
ETyp_Source_ID
INT |
ETyp_Target_ID
INT |
RelnTyp_Cd
CHAR(6) |
ERul_Strt_DtTm
TIMESTAMP |
ERul_End_DtTm
TIMESTAMP |
---|---|---|---|---|
1 | 4 | CAUSES | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | 4 | CAUSES | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | 4 | CAUSES | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | 5 | CAUSES | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | 5 | CAUSES | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | 5 | CAUSES | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
Table 34 shows the fields of the TWG.CERelnRul table.
EventTyp_ID
INT |
CompTyp_Cd
CHAR(17) |
RelnTyp_Cd
CHAR(6) |
CERul_Strt_DtTm
TIMESTAMP |
CERul_End_DtTm
TIMESTAMP |
---|---|---|---|---|
1 | GTM_RESOURCE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | GTM_RESOURCE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | GTM_RESOURCE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | MVS_SYSTEM | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | MVS_SYSTEM | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | MVS_SYSTEM | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | LOGICAL_
PARTITION |
SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | LOGICAL_
PARTITION |
SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | LOGICAL_
PARTITION |
SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | GTM_HOST | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | GTM_HOST | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | GTM_HOST | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | BUSINESS_SYSTEM | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | BUSINESS_SYSTEM | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | BUSINESS_SYSTEM | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | MQ_QUEUE_MANAGER | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | MQ_QUEUE_MANAGER | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | MQ_QUEUE_MANAGER | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | MQ_QUEUE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | MQ_QUEUE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | MQ_QUEUE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | MQ_CHANNEL | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | MQ_CHANNEL | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | MQ_CHANNEL | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | SNA_NETWORK | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | SNA_NETWORK | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | SNA_NETWORK | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | SNA_CCU | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | SNA_CCU | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | SNA_CCU | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | IP_HOST | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | IP_HOST | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | IP_HOST | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | IP_NODE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | IP_NODE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | IP_NODE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
1 | IP_INTERFACE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
2 | IP_INTERFACE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
3 | IP_INTERFACE | SOURCE | 2003-01-01-00.00.00.00 | 9999-01-01-00.00.00.00 |
Level INTEGER | CompTyp_Cd
CHAR(17) |
cid
VARCHAR(4) |
Label *
VARCHAR (254) |
Description *
VARCHAR (1024) |
---|---|---|---|---|
1 | MVS_SYSTEM | OS | Operating System | Operating System |
2 | LOGICAL_PARTITION | LPAR | Logical Partition | Logical Partition |
3 | GTM_RESOURCE | ENT | Enterprise | Enterprise |
Id
INTEGER |
Name *
VARCHAR (254) |
START_DTTM
TIMESTAMP |
---|---|---|
0 | Unknown | 2003-1-28-11.00.00.00000 |
1 | Green | 2003-1-28-11.00.00.00000 |
2 | Yellow | 2003-1-28-11.00.00.00000 |
3 | Red | 2003-1-28-11.00.00.00000 |
Id
INTEGER |
Name
VARCHAR (254) |
START_DTTM
TIMESTAMP |
---|---|---|
0 | Unknown | 2003-1-28-11.00.00.00000 |
1 | Critical | 2003-1-28-11.00.00.00000 |
2 | High | 2003-1-28-11.00.00.00000 |
3 | Medium | 2003-1-28-11.00.00.00000 |
4 | Low | 2003-1-28-11.00.00.00000 |
5 | Ignore | 2003-1-28-11.00.00.00000 |
6 | Eliminate | 2003-1-28-11.00.00.00000 |
NAME
VARCHAR (40) |
TYPE
VARCHAR (40) |
Val
VARCHAR (254) |
START_DTTM
TIMESTAMP |
CHANGED_DTTM
TIMESTAMP |
---|---|---|---|---|
max_resource_depth | INTEGER | 8 | 2003-1-28-11.00.00.00000 | 2003-1-28-11.00.00.00000 |
This warehouse pack does not use the exception tables.
Both ETLs use incremental extraction after initialization.
The extraction control for the central data warehouse ETL is stored in both Tivoli Data Warehouse and Tivoli Business Systems Manager databases for better performance. The following extraction controls are stored in the TWG.EXTRACT_CONTROL table in the Tivoli Data Warehouse:
Ctrl_Source | Ctrl_target | Ctrl_description |
---|---|---|
ETL1 | MSMT | Date and time of the measurement data that is loaded from the Tivoli Business Systems Manager database into the Tivoli Data Warehouse central database on the last source ETL run |
ETL1_linkc | CDW | Date and time of the link information loaded for the common components from the Tivoli Business Systems Manager database into the Tivoli Data Warehouse central database on the last central data warehouse ETL run |
ETL1_linkp | CDW | Date and time of the link information loaded for the private components from the Tivoli Business Systems Manager database into the Tivoli Data Warehouse central database on the last central data warehouse ETL run |
ETL1_MESG | CDW | The last ID for the messages that are successfully loaded from the Message_V view in the Tivoli Business Systems Manager database into the Tivoli Data Warehouse central database during the last initialization |
ETL1_EXCP | CDW | The last ID for the exceptions that are successfully loaded from the Exception_V view in the Tivoli Business Systems Manager database into the Tivoli Data Warehouse central database during the last initialization |
ETL1_CHEV | CDW | The last ID for the child events that are successfully loaded from the ChildEvent_V view in the Tivoli Business Systems Manager database into the Tivoli Data Warehouse central database during the last initialization |
ETL1_events | CDW | The last timestamp for the events that are successfully loaded from the event table in the Tivoli Business Systems Manager object database into the Tivoli Data Warehouse central database on the last central data warehouse ETL run |
ETL1_ash | CDW | The last ash_id for the events that are successfully loaded from the AlertStateHistory table in the Tivoli Business Systems Manager object database into the Tivoli Data Warehouse central database on the last central data warehouse ETL run |
ETL1_note | CDW | The last ident for the notes that are successfully loaded from the NoteHistory table in the Tivoli Business Systems Manager database into the Tivoli Data Warehouse central database on the last central data warehouse ETL run |
EVENT_ID | MART | The last event_id that is successfully loaded from the Tivoli Data Warehouse central database into the data mart on the last data mart ETL run |
The extraction controls for the data mart ETL is stored in both Tivoli Data Warehouse and the data mart for better performance. The following extraction controls are stored in the GTM.MEXTRACT_CTRL table in the data mart:
Ctrl_Source | Ctrl_target | Ctrl_description |
---|---|---|
COMP_ID | MART | The last COMP_ID for components that are successfully loaded from Tivoli Data Warehouse into the data mart when the last data mart ETL runs |
COMPATTR_ID | CDW | The last COMPATTR_ID for the component attributes that are successfully loaded from the Tivoli Data Warehouse into the data mart when the last data mart ETL runs |
COMPRELN_ID | CDW | The last COMPRELN_ID for component relationships that are successfully loaded from the Tivoli Data Warehouse into the data mart when the last data mart ETL runs |
EVENT_ID | CDW | The last EVENT_ID for the events that are successfully loaded from the Tivoli Data Warehouse into the data mart when the last data mart ETL runs |
The following sections contain the definition of star schemas, metric dimension tables and dimension tables provided with the warehouse pack. This section is intended primarily for report designers and warehouse pack creators. For information about reports, see Reports.
Shaded columns in the following tables are translated. These columns are also marked with an asterisk (*) after the column name.
Before using this section, read about the star schemas 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.
This data mart uses the following star schemas:
The following table defines the Event star schema. The description of the star schema is translated.
Description of star schema (in IWH_STARSCHEMA) | |
---|---|
Name of fact table | GTM.F_Event |
Name of metric dimension table | GTM.D_AS_METRIC |
GTM.D_ETYP_METRIC | |
GTM.D_PRI_METRIC | |
Names of other dimension tables | GTM.D_COMP |
GTM.D_COMP_PATH | |
GTM.D_OBJ_CLASS | |
GTM.D_LOB_LINK |
The following columns are used in the GTM.F_Event fact table:
Table 41 defines the Note star schema. The description of the star schema is translated.
Description of star schema (in IWH_STARSCHEMA) | |
---|---|
Name of fact table | GTM.F_Note |
Name of metric dimension table | GTM.D_AS_METRIC |
GTM.D_ETYP_METRIC | |
GTM.D_PRI_METRIC | |
Names of other dimension tables | GTM.D_COMP |
GTM.D_COMP_PATH | |
GTM.D_OBJ_CLASS |
The following columns are used in the GTM.F_Note fact table:
Table 42 defines the Alert State History star schema. The description of the star schema is translated.
Description of star schema (in IWH_STARSCHEMA) | |
---|---|
Name of fact table | GTM.F_ALERTSTATEHIS |
Name of metric dimension table | GTM.D_AS_METRIC |
GTM.D_ETYP_METRIC | |
GTM.D_PRI_METRIC | |
Names of other dimension tables | GTM.D_COMP |
GTM.D_COMP_PATH | |
GTM.D_OBJ_CLASS |
The following columns are used in the GTM.F_ALERTSTATEHIS fact table:
This section describes the metric dimension tables used by the star schemas in the warehouse pack. Shaded columns in the following tables are translated. These columns are also marked with an asterisk (*) after the column name.
Table 43 defines the GTM.D_PRI_METRIC table.
Priority_ID
INTEGER |
Priority *
VARCHAR (254) |
---|---|
0 | Unknown |
1 | Critical |
2 | High |
3 | Medium |
4 | Low |
5 | Ignore |
6 | Eliminate |
Table 44 defines the GTM.D_AS_METRIC table.
ALERTSTATE_ID
INTEGER |
AlertState *
VARCHAR (254) |
---|---|
0 | Unknown |
1 | Green |
2 | Yellow |
3 | Red |
Table 45 defines the GTM.D_ETYP_METRIC table.
EVENTTYP_ID
INTEGER |
EVENTTYP_NM *
VARCHAR (254) |
EVENTTYP_Desc *
VARCHAR(254) |
---|---|---|
1 | Message | Tivoli Business Systems Manager Messages |
2 | Exception | Tivoli Business Systems Manager Exceptions |
3 | Child Event | Tivoli Business Systems Manager Child Events |
4 | Note | Tivoli Business Systems Manager Notes |
5 | Alert State Change | Alert states changed in Tivoli Business Systems Manager |
The following columns are used in the GTM.D_COMP dimension table:
The following columns are used in the GTM.D_COMP_PATH dimension table:
The following columns are used in the GTM.D_OBJ_CLASS dimension table:
The following columns are used in the GTM.D_LOB_LINK dimension table:
The warehouse pack loads resource, event, and measurement data for business systems into the Tivoli Data Warehouse. This chapter describes how this Tivoli Business Systems Manager data is modeled in the central data warehouse.
Refer to Getting Started from the Tivoli Business Systems Manager document library for information on how Tivoli Business Systems Manager stores data. Refer to Enabling an Application for Tivoli Data Warehouse for information on Tivoli Data Warehouse schemas.
The managed resource classes in the Tivoli Business Systems Manager database are referred to as component types in the Tivoli Data Warehouse database. Only the managed classes in the Tivoli Business Systems Manager database are defined in the Tivoli Data Warehouse database. Some of the managed resource classes are defined using the Common Data Model (CDM) in the Tivoli Data Warehouse database. For information about the mapping of the common component types used for the Tivoli Business Systems Manager managed resource classes, see Table 46. The Tivoli Business Systems Manager link types for the common component types are mapped in Table 47.
The rest of the managed resource classes, including the classes created dynamically, are modeled with the GTM_RESOURCE Tivoli Business Systems Manager private component type.
Table 46 lists the mapping of the common component types used for the Tivoli Business Systems Manager managed resource classes. Following is a description of the table headers:
Label, Description, and cid are loaded in the GTM.CompTyp_EXT private table of the Tivoli Data Warehouse database. If Tivoli Business Systems Manager does not have the fully-qualified host name for the instances of IP Host component type. The instances are defined with GTM_HOST private component type.
cid | Label | Description | CompTyp_CD | CompTyp_NM |
---|---|---|---|---|
LPAR | Logical Partition | Logical Partition | LOGICAL_PARTITION | Logical Partition |
OS | Operating System | Operating System | MVS_SYSTEM | MVS System |
ROUT | Router | Network Router | IP_NODE | IP Node |
UNIX2 | OS type | IP_HOST | IP Host | |
NODE2 | Network Node | Network Node | IP_HOST | IP Host |
PCXX2 | Network PC | Network PC | IP_HOST | IP Host |
CPTR2 | Computer | Computer | IP_HOST | IP Host |
SRVR2 | Server Host | Server Host | IP_HOST | IP Host |
G02K2 | Server | Server | IP_HOST | IP Host |
NTSV2 | Windows NT(R) Server | Windows NT Server | IP_HOST | IP Host |
RASS2 | Network RAS Server | Network RAS Server | IP_HOST | IP Host |
INTR | Network Interface | The physical connection between a node and the network | IP_INTERFACE | IP Interface |
MMGR | MQ Manager | MQ Manager | MQ_QUEUE_MANAGER | MQ Queue Manager |
MQLC | MQ Local Queue | MQ Local Queue | MQ_QUEUE | MQ Queue |
MQMD | MQ Model Queue | MQ Model Queue | MQ_QUEUE | MQ Queue |
MQRT | MQ Remote Queue | MQ Remote Queue | MQ_QUEUE | MQ Queue |
MQXT | MQ Xmit Queue | MQ Xmit Queue | MQ_QUEUE | MQ Queue |
MQRV | MQ Receiver Channel | MQ Receiver Channel | MQ_CHANNEL | MQ Channel |
MQSD | MQ Sender Channel | MQ Sender Channel | MQ_CHANNEL | MQ Channel |
SNNT | SNA/APPN Network | Uniquely named network with SNA AND APPN resources | SNA_NETWORK | SNA Network |
T4NG | t4NodeGateway | SNA type-4 node that provides communication controller support FOR single-domain, multiple-domain, AND interconnected network capability. It can also provide gateway function, intermediate routing function, AND boundary function | SNA_CCU | SNA Communication Control Unit |
LOB | Business System | Business System | BUSINESS_SYSTEM | Business System |
EXES | Executive View Service | Represents an Executive View Service. Always associated to a single LOB object | SERVICE | Service |
The Tivoli Business Systems Manager link types for the common component types are mapped in Table 47. Following is a description of the table headers:
If Reversed_Mapped = 0, Source_Comp_CD is mapped to src_cid and Target_Comp_CD to dst_cid.
If Reversed_Mapped = 1, Source_Comp_CD is mapped to dst_cid and Target_Comp_CD to src_cid.
Src_
cid |
Dst_
cid |
Link_type | Source_COMP_CD | Target_COMP_CD | RelnTyp | Reverse_
Mapped |
---|---|---|---|---|---|---|
LPAR | OS | PHYC | MVS_SYSTEM | LOGICAL_PARTITION | RUNSON | 1 |
LOB | LOB | LOBC | BUSINESS_SYSTEM | BUSINESS_SYSTEM | PCHILD | 0 |
EXES | LOB | EVSL | BUSINESS_SYSTEM | SERVICE | SUPPRT | 1 |
MMGR | MQLC | PHYC | MQ_QUEUE_MANAGER | MQ_QUEUE | PCHILD | 0 |
MMGR | MQMD | PHYC | MQ_QUEUE_MANAGER | MQ_QUEUE | PCHILD | 0 |
MMGR | MQRT | PHYC | MQ_QUEUE_MANAGER | MQ_QUEUE | PCHILD | 0 |
MMGR | MQRV | PHYC | MQ_QUEUE_MANAGER | MQ_CHANNEL | PCHILD | 0 |
MMGR | MQSD | PHYC | MQ_QUEUE_MANAGER | MQ_CHANNEL | PCHILD | 0 |
MMGR | MQXT | PHYC | MQ_QUEUE_MANAGER | MQ_QUEUE | PCHILD | 0 |
SNNT | T4NG | PHYC | SNA_NETWORK | SNA_CCU | PCHILD | 0 |
The parent and child relationship is used for the following component types:
The Business System Containment Link of a Business System with the resource is modeled with Business System and resource link, GTM_LB.
The instance names of the common component types in the Tivoli Data Warehouse are based on the Common Data Model naming rules. The User Label attribute is used for the resource name in the Tivoli Business Systems Manager database for all common components except business systems. When a business system is renamed, the Name attribute is updated. When the GTM_RESOURCE and GTM_HOST private components are renamed, the Name attribute is updated.
GTM_CID, GTM_ID, and GTM_DELETE attributes are defined for all Tivoli Business Systems Manager components except business systems and executive dashboard services in Tivoli Data Warehouse. Because Business System and Service resources are used for both Tivoli Business Systems Manager reporting and Tivoli Service Level Advisor integration, extra attributes are defined and described in Table 48 and Table 49.
When the business systems from the Tivoli Business Systems Manager program are loaded into the Tivoli Data Warehouse program, the business system information is saved in the Tivoli Data Warehouse database, as described in Table 48.
Tivoli Business Systems Manager | Tivoli Data Warehouse |
---|---|
Object name | Component name |
Class ID | GTM_CID attribute |
Ctime | Component start date |
Ctime | Component start time |
Object ID | GTM_ID attribute |
Resource type | GTM_RTYPE attribute |
The service components are modeled differently from the business systems in the Tivoli Data Warehouse database. The executive dashboard service resource information is saved in the Tivoli Data Warehouse database, as described in Table 49.
Tivoli Business Systems Manager | Tivoli Data Warehouse |
---|---|
Object name | User label attribute |
_ServiceID | Component name |
Name_GUID | NAME_GUID attribute |
Ctime | Component start date |
Ctime | Component start time |
Class ID | GTM_CID attribute |
Object ID | GTM_ID attribute |
*_Flag of linked business system | GTM_Enable |
* When an executive dashboard service is created, it is enabled in Tivoli Data Warehouse and there is no record for the GTM_Enable attribute. Clearing the Service check box in the Tivoli Business Systems Manager executive dashboard property page changes the value for the GTM_Enable attribute of the Service component in the Tivoli Data Warehouse to 0. When the Service is marked as a service again (by selecting the Service check box in the Tivoli Business Systems Manager executive dashboard property page), then the GTM_Enable attribute value of the Service component in the Tivoli Data Warehouse database is set to 1. |
Table 50 describes what happens when you delete or rename component types in Tivoli Business Systems Manager.
Component Type | Action | Result |
---|---|---|
Executive view service | Logically (deleted =1) or physically (entries are removed from the tables) deleted in Tivoli Business Systems Manager | The component, attributes, and its relationships in the central data warehouse are expired during the next run of the central database warehouse ETL. |
Business system | Logically or physically deleted from Tivoli Business Systems Manager | The component, attributes, and its relationships in the central data warehouse are expired during the next run of the central database warehouse ETL. |
GTM_RESOURCE GTM_HOST |
Logically deleted | The GTM_DELETED attribute is updated to 1. |
Physically deleted | The component is expired in the central data warehouse. | |
BUSINESS_SYSTEM, GTM_RESOURCE, and GTM_HOST | Renamed in Tivoli Business Systems Manager | A new Name attribute of the business system component is inserted with the new Name as the CompAttr_Val in TWG.CompAttr table of the central data warehouse. |
Other public component type | Logically or physically deleted from Tivoli Business Systems Manager | The GTM_DELETED attribute is updated to 1. |
Renamed in Tivoli Business Systems Manager | A new USER_LABEL attribute of the Service component is inserted with the new display name as the CompAttr_Val in TWG.CompAttr table of the central data warehouse. The original attribute is expired by the Tivoli Data Warehouse trigger or Tivoli Business Systems Manager central data warehouse ETL. |
All the managed resources in the Tivoli Business Systems Manager database are created in the Tivoli Data Warehouse database as components in TWG.COMP table. The relationships of the resources are loaded in TWG.COMPRELN table.
Dragging and dropping a business system in Tivoli Business Systems Manager creates a business system shortcut. In the Tivoli Business Systems Manager database, the business system shortcut has the same children as the source resource from which it was copied. The specified link type (a business system logical link) enables this function. In Tivoli Data Warehouse, there is no distinction for the source resource with the business system shortcuts. They are all modeled as components of the BUSINESS_SYSTEM component type. Using the LOBL link type, the _get_dependent stored procedure can get the children of the business system shortcut from the source business system.
The relationship of business systems is modeled differently in Tivoli Data Warehouse than in Tivoli Business Systems Manager for business systems shortcuts. The following example shows the children of the Bank 1 business system shortcut being resolved by an LOBL link type in Tivoli Business Systems Manager. In Tivoli Data Warehouse, the central data warehouse ETL creates a direct link.
Data Centers (business system) Eastern Complex (business system) ---Original--- Bank 1 (business system) CICS A (business system resource) Western Complex (business system) Bank 1 (business system shortcut) ---Dragging and Dropping--- CICS A (business system resource) CICS B (business system resource)
The state changes of all business systems are provided for the Tivoli Service Level Advisor measurements using the state transition matrix. The alert states or resource states in the Tivoli Business Systems Manager are mapped into the Tivoli Service Level Advisor availability measurement types, as shown in Table 51.
Object state in Tivoli Business Systems Manager | Measurement type in IBM Tivoli Service Level Advisor |
---|---|
Green | Available |
Yellow | Degrading |
Red | Unavailable |
In maintenance | Unmanaged |
Owned (Red)* | Repairing |
Unknown | Unknown |
* The Owned (Red) state is only recorded for the time period when the resource has an ownership note due to a Red event. When the resource has an ownership note because of a Yellow event, the ETL transfers it as either Degrading or Available, based on the alert state of the resource. |
Tivoli Business Systems Manager event, note, and alert state history information is loaded as events in Tivoli Data Warehouse with the following event types:
The events are loaded in the twg.event table. The relationship of an event with a component is stored in the twg.cereln table. Messages, Exceptions, or Child Events can cause an Alert State Change event or Note event. This relationship is stored in the twg.eventreln table. The event attributes are mapped in Table 52.
EventTyp_Nm | EAttrTyp_Cd | Column in TWG.EventAttr EVENTATTR_LONG_VAL | Tivoli Business Systems Manager database object name | Tivoli Business Systems Manager column name |
---|---|---|---|---|
Message | GTM_NAME | EVENTATTR_VAL | event | name |
Message | GTM_EVENT_ID | EVENTATTR_VAL | event | evt_id |
Message | GTM_DETAIL | EVENTATTR_VAL | event | detail |
Message | GTM_PRIORITY_ID | EVENTATTR_VAL | event | priority |
Message | GTM_AS_ID | EVENTATTR_VAL | event | alertstate |
Message | GTM_EVENT_CID_ID | EVENTATTR_VAL | event | cid\evt_id |
Exception | GTM_NAME | EVENTATTR_VAL | event | name |
Exception | GTM_EVENT_ID | EVENTATTR_VAL | event | evt_id |
Exception | GTM_DETAIL | EVENTATTR_VAL | event | detail |
Exception | GTM_PRIORITY_ID | EVENTATTR_VAL | event | priority |
Exception | GTM_AS_ID | EVENTATTR_VAL | event | alertstate |
Exception | GTM_EVENT_CID_ID | EVENTATTR_VAL | event | cid\evt_id |
Child Event | GTM_NAME | EVENTATTR_VAL | event | name |
Child Event | GTM_EVENT_ID | EVENTATTR_VAL | event | evt_id |
Child Event | GTM_DETAIL | EVENTATTR_VAL | event | detail |
Child Event | GTM_PRIORITY_ID | EVENTATTR_VAL | event | priority |
Child Event | GTM_AS_ID | EVENTATTR_VAL | event | alertstate |
Child Event | GTM_EVENT_CID_ID | EVENTATTR_VAL | event | cid\evt_id |
Alert State Change | GTM_AS_ID | EVENTATTR_VAL | AlertStateHistory | AlertStateID |
This section describes the following options for obtaining support for IBM products:
If you have a problem with your IBM software, you want it resolved quickly. Begin by searching the available knowledge bases to determine whether the resolution to your problem is already documented.
IBM provides extensive documentation that can be installed on your local computer or on an intranet server.
An index is provided for searching the Tivoli Business Systems Manager library. If you have Adobe Acrobat on your system, you can use the Search command to locate specific text in the library. For more information about using the index to search the library, see the online help for Acrobat.
If you cannot find an answer to your question in the information center, search the Internet for the latest, most complete information that might help you resolve your problem. To search multiple Internet resources for your product, expand the product folder in the navigation frame to the left and select Web search. From this topic, you can search a variety of resources including:
A product fix might be available to resolve your problem. You can determine what fixes are available for your IBM software product by checking the product support Web site:
To receive weekly e-mail notifications about fixes and other news about IBM products, follow these steps:
For more information about types of fixes, see the Software Support Handbook (http://techsupport.services.ibm.com/guides/handbook.html).
IBM Software Support provides assistance with product defects.
Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:
If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to the contacts page of the IBM Software Support Handbook on the Web (http://techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region for phone numbers of people who provide support for your location.
Follow the steps in this topic to contact IBM Software Support:
When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem you are reporting. Use the following criteria:
Severity 1 | Critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. |
Severity 2 | Significant business impact: The program is usable but is severely limited. |
Severity 3 | Some business impact: The program is usable with less significant features (not critical to operations) unavailable. |
Severity 4 | Minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem has been implemented. |
When explaining a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions:
You can submit your problem in one of two ways:
If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround for you to implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM product support Web pages daily, so that other users who experience the same problem can benefit from the same resolutions.
For more information about problem resolution, see Searching knowledge bases and Obtaining fixes.
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 give 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-0032, 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 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 information 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 measurements 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 is for planning purposes only. The information herein is subject to change before the products described become available.
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 illustrate 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.
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, AFS, AIX, CICS, DB2, DB2 Universal Database, DRDA(R), Informix(R), MVS, NetView, OS/2(R), OS/390(R), Tivoli Enterprise Console, TME(R), and z/OS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.
Intel(TM), the Intel Inside logos, MMX(TM), and Pentium(R) are trademarks of Intel 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.
SET(TM) and the SET Logo are trademarks owned by SET Secure Electronic Transaction(TM) LLC.
Java(TM) and all -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.
[ Top of Page | | Contents | Index ]