ClearPath OS 2200 TeamQuest Baseline and Online User Guide

ClearPath OS 2200 TeamQuest Baseline® and TeamQuest Online® User Guide February 2015 Level 7R5A TQ–01011.20 Copyright © 2015 TeamQuest Corporation. All Rights Reserved. The names,...

ClearPath OS 2200 TeamQuest Baseline® and TeamQuest Online® User Guide February 2015 Level 7R5A TQ–01011.20 Copyright © 2015 TeamQuest Corporation. All Rights Reserved. The names, places and/or events used in this publication are purely fictitious and are not intended to correspond to any real individual, group, company or event. Any similarity or likeness to any real individual, company or event is purely coincidental and unintentional. NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THE DOCUMENT. Any product and related material disclosed herein are only furnished pursuant and subject to the terms and conditions of a license agreement. The only warranties made, remedies given, and liability accepted by TeamQuest, if any, with respect to the products described in this document are set forth in such license agreement. TeamQuest cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, indirect, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. U.S. Government Rights. All documents, product and related material provided to the U.S. Government are provided and delivered subject to the commercial license rights and restrictions described in the governing license agreement. All rights not expressly granted therein are reserved. TeamQuest, the TeamQuest logo, TeamQuest Alert, TeamQuest Analyzer, TeamQuest Baseline, TeamQuest CMIS, TeamQuest CMIS for Storage, TeamQuest Harvest, TeamQuest IT Service Analyzer, TeamQuest IT Service Reporter, TeamQuest Manager, TeamQuest Model, TeamQuest On the Web, TeamQuest Predictor, TeamQuest Online, TeamQuest Surveyor, TeamQuest View, and Performance Surveyor are trademarks or registered trademarks of TeamQuest Corporation in the US and/or other countries. Unisys and ClearPath are registered trademarks of Unisys Corporation in the US and/or other countries. All other trademarks and service marks are the property of their respective owners. About This Guide TeamQuest Baseline® and TeamQuest Online® are required OS 2200 software packages that provide the services for the TeamQuest Performance Software family. TeamQuest Baseline is installed on a host system and provides the components to collect, store, manage, and administer your performance data. Purpose The OS 2200 TeamQuest Baseline and TeamQuest Online User Guide describes TeamQuest Baseline and TeamQuest Online. It tells you how to use TeamQuest Baseline as a tool for performing performance management and performance analysis tasks on your system and how to use TeamQuest Online as a performance monitoring tool. Scope This guide describes the TeamQuest Baseline and TeamQuest Online software. It provides conceptual information for TeamQuest Baseline and the performance database structure. It tells how to use the probes to collect and store performance data in the performance database. Audience This guide is intended for those who are interested in performance analysis and capacity management of OS 2200 systems. TeamQuest Online addresses the needs of the performance analyst. TeamQuest Baseline addresses the needs of the performance analyst and the capacity planner. The performance analyst who is typically interested in detailed data can use TeamQuest Baseline or TeamQuest Online to collect system data at a fine granularity. The capacity planner can use TeamQuest Baseline to collect data across long periods of time. Marketing representatives and technical managers who are interested in the performance management of OS 2200 systems might also use TeamQuest Baseline. TQ–01011.20 iii About This Guide Prerequisites This guide assumes that you have basic knowledge of the Software Instrumentation Package (SIP), TPM log, IOTRACE, the MAPPER accounting log, the system log, and other existing performance analysis software on the OS 2200 system. How to Use This Guide This guide is intended to be used with the TeamQuest View User Guide to view TeamQuest Baseline and TeamQuest Online reports. The OS 2200 TeamQuest Baseline and TeamQuest Online User Guide contains information specific to the host component of the software. The TeamQuest View User Guide describes the workstation software and explains how to use the TeamQuest View® user interface to view reports from data collected by the TeamQuest Performance Software applications. This guide is divided into two parts. Part 1 contains information that will familiarize you with the TeamQuest Baseline product and the basic concepts needed to use and administer TeamQuest Baseline as installed. It is intended for first-time users and those who have no need to change the default settings. Part 2 contains advanced concepts and information for customizing TeamQuest Baseline to meet the specific needs for your site. Organization This guide contains the following: Part 1. Getting Up and Running Section 1. Introduction This section provides an introduction to TeamQuest Performance Software family. It describes the TeamQuest Baseline and TeamQuest Online products and tells how the products work. Section 2. TeamQuest Baseline and TeamQuest Online Concepts This section explains the architecture of TeamQuest Baseline and TeamQuest Online and describes the performance database structure. Section 3. TeamQuest Baseline Administration This section provides basic information on administering TeamQuest Baseline or TeamQuest Online with the default settings as installed. It contains information on default aggregation sets, and alarm handling. It also outlines steps you can take to ensure that you are collecting the data you need for your site requirements. iv TQ–01011.20  About This Guide Part 2. Customizing Your Site Section 4. TeamQuest Performance Software Administration This section provides information to establish and terminate an administration session. TeamQuest Performance Software Administration allows you to perform maintenance tasks for workloads, aggregations, and derived statistics. Section 5. Customizing Workloads This section provides information on the workloads used by TeamQuest Baseline. It describes workload characteristics and the definition language for defining workloads. It also tells you how to use the tqzip program to unload and load workload definitions to an output file. Section 6. Customizing Aggregation Sets This section contains advanced concepts about the aggregation sets in the performance database and tells how you can customize the aggregation sets to meet the particular needs of your site. It provides information for using the tqasa and tqagg programs to perform tasks for maintaining aggregation sets. Section 7. Customizing Alarms and Thresholds This section provides information on the alarms and thresholds capability of TeamQuest Baseline. It tells you how to perform the various tasks in creating and maintaining alarms and thresholds for database parameters and derived statistics. Section 8. Customizing Derived Statistics This section contains advanced concepts for using derived statistics with TeamQuest Baseline. It also tells you how to use the tqzip program to unload and load your derived statistic definitions to an output file. Section 9. Customizing Data Collection Probes This section provides information you need to customize the data collection for each of the TeamQuest probes. It also tells you how to write your own probes for collecting site-specific data. Section 10. Customizing Performance Databases This section tells you how create additional databases, delete databases, estimate disk space requirements for a database, clear database locks, and remove database parameters from a database. It also provides backup and recovery information. Section 11. Customizing Tables This section provides the information you need to maintain the table data collected by the TeamQuest Baseline probes. It tells you how to use the tqzip program to define collection periods and retention specifications, delete records from tables, and register a table in the database. It also tells you how and why to use the tqrorg program to reorganize your table files for improved efficiency. TQ–01011.20 v About This Guide Appendix A. OS 2200 Parameters This appendix lists the statistics that are collected by the TeamQuest Baseline and TeamQuest Online host software. Appendix B. Predefined Report Descriptions This appendix provides a description of each of the predefined reports for your host system. Appendix C. Report Definition File This appendix describes the format of the report definition file. It provides the format of the file and a description of the fields specified in the file. Appendix D. Host-Based Reporting for Aggregation Set Data This appendix describes how to use the TeamQuest Baseline tqrpt program to generate reports containing aggregation set data directly from the performance database on the host system. This program is available with TeamQuest Baseline only. Appendix E. Host-Based Reporting for Table Data This appendix describes how to use the TeamQuest Baseline tqrep program to generate reports containing table data directly from the performance database on the host system. This program is available with TeamQuest Baseline only. Appendix F. The tqgetm Program for TeamQuest Model This appendix describes the tqgetm program that allows you to export data from TeamQuest Baseline to TeamQuest Model. Appendix G. Alarm History Table This appendix describes the format of the alarm history table. Appendix H. tqzip Processor Call Format This appendix serves as a reference for the tqzip processor call format. Appendix I. 2200 Socket Interface This appendix provides the information necessary to connect an OS 2200 system to TeamQuest View using a socket connection. Appendix J. 2200 SNMP Trap Alarms This appendix describes how to define thresholds that will send alarm events to any management console that accepts Simple Network Management Protocol (SNMP) traps. vi TQ–01011.20  About This Guide Results After reading and using this guide, you will be able to use TeamQuest Baseline or TeamQuest Online on the host system, maintain the performance database, and use the data collection probes to gather measurement data in the database. Related Product Information The following related documents may be helpful to you when using TeamQuest Baseline and TeamQuest Online. Refer to the version that corresponds to the level of software in use at your site. TeamQuest Product Documentation If you are using TeamQuest manuals, you can find related product information in the following documents. TeamQuest Model User Guide for Unisys Systems (TQ–01424) This guide describes how to use the TeamQuest Model® product with Unisys systems. TeamQuest Model allows you to build and solve models to predict the performance of your computer system should conditions change. OS 2200 TeamQuest PMLog End Use Reference Manual (TQ–01351) This manual provides information for using the TeamQuest PMLog software with TeamQuest Baseline. OS 2200 TeamQuest Probes End Use Reference Manual (TQ–01361) This manual provides information for using the TeamQuest Probes software with TeamQuest Baseline or TeamQuest Online. OS 2200 TeamQuest Products Installation Guide (TQ–01013) This guide contains information you will need to install any of the TeamQuest software products for ClearPath OS 2200 systems. TeamQuest View User Guide (TQ–01401) This guide describes how to use the TeamQuest View software. TeamQuest View is the user interface to TeamQuest Baseline and TeamQuest Online. You use TeamQuest View to view reports from data collected by the TeamQuest Performance Software applications. TQ–01011.20 vii About This Guide Unisys Product Documentation If you are using Unisys manuals, you can find related product information in the following documents. Business Information Server for ClearPath OS 2200 Administration Guide (7831 9415) This guide provides information system configuration, database management, user and run registration, and configuring communications links with other Business Information Server systems. ClearPath OS 2200 Cipher Application Programming Interface (API) Programming Reference Manual (3826 6110) This manual provides specific information on the Cipher API product used for FIPS 140-2 compliant encryption of data. If installed, the user-id and password supplied in the TQTCP configuration element can be encrypted for security reasons for TeamQuest Baseline and TeamQuest Online. ClearPath OS 2200 Exec System Software Administration Reference Manual (7831 0323) This manual provides specific information for setting up and administering the OS 2200 system. This information includes instructions for booting, initializing, monitoring, reconfiguring, and recovering the system. This manual also contains information on the Software Instrumentation Package (SIP). TeamQuest Baseline and TeamQuest Online use data collected by SIP for data reduction and report generation. ClearPath OS 2200 Software Products Installation Guide (7831 0612) This guide explains how to use the Software Library Administrator (SOLAR) to install OS 2200 software products from a software package tape. OS 2200 Exec System Software Operations Reference Manual (7831 0281) This manual explains the operator interface with the system console and peripherals. It also discusses operator responsibilities, describes procedures, and lists keyins. OS 2200 Linking System Subsystems Programming Guide (7830 7451) This guide describes software subsystems including how to create, install, and use them. It includes a discussion of security as it relates to the installation and usage of subsystems. OS 2200 System Log Operations and Support Reference Manual (7831 0315) This manual explains system log processing and the resulting log entries of the OS 2200 system. The TeamQuest Baseline system log probe collects system log data for its reporting. viii TQ–01011.20  About This Guide OS 2200 Transaction Processing Administration and Operations Reference Manual (7830 7881) This manual tells you how to turn on the Transaction Processing (TIP) log accounting feature if you have TIP running on your system. It also describes the TIP Performance Monitor (TPM) logging mechanism for reporting Transaction Processing (TIP) and High-Volume Transaction Processing (HVTIP) statistics. Single Point Autoaction Message System Administration Guide (7833 4760) This guide provides information on the Single Point Autoaction Message System (SP-AMS). The alarm capability of TeamQuest Baseline can be integrated with the message automation and alarm handling functionality of SP-AMS. SMART for ClearPath OS 2200 Administration and Operations Guide (7830 7337) This guide provides information on SMART. The alarm capability of TeamQuest Baseline can be integrated with the message automation and alarm handling functionality of SMART. How to Access Portable Document Format (PDF) Files All TeamQuest product documentation is available as PDF files. PDF files can either be downloaded from the TeamQuest Web site or they can be viewed from your product CD or DVD. You must have the Adobe Reader software from www.adobe.com installed on your workstation to view the PDF files. To download product documentation from the Web site: 1. Access the TeamQuest Web site at www.teamquest.com. 2. Click the Support tab, then Customer Area. 3. Log in to the Customer Area. 4. Click the Downloads link. 5. Click the Product Documentation link for the desired release level and product platform. 6. Select the document you wish to download. When the download is complete, the PDF file will open. 7. Select the Save As command from the File menu to save a copy of this document. TQ–01011.20 ix About This Guide To access product documentation from your product CD or DVD: 1. Load the CD or DVD in your disk drive. The disk contents dialog box is displayed. 2. Open the welcome.pdf file. The welcome.pdf file can be used to navigate to the desired PDF file. You may wish to copy the welcome.pdf file and the pdfdocs folder to your server so multiple users have convenient access to the product documentation. Note: When copying the welcome file and the pdfdocs directory, you must maintain the established directory structure. If the directory structure is not maintained, the navigation links within the welcome.pdf file will not open the documents located in the pdfdocs directory. Notation Conventions The examples in this guide show, as nearly as possible, how your input, system output, and screens appear on a terminal. Program names are shown in boldface type. In this guide, the following conventions apply for command formats when using TeamQuest Baseline and TeamQuest Online on the host system: You can enter any commands or other required input in either uppercase or lowercase letters. Both ways are shown in the examples in this guide. In command and format examples, anything that appears in regular type must be entered exactly as shown. For example, in the following command: @tqbsp [-r,] -i,parameter-table, you must enter @tqbsp exactly as shown. Brackets are used to indicate optional entries. In the following command: [-d,databasename,] that which appears between the brackets, -d,databasename, is optional. You are not required to enter the -d parameter. Italics are used to indicate variable values that you must supply, depending on the circumstances. In the following command: -a,aggset1, you must supply a valid aggregation set name in place of aggset1. For menu selections within the graphical user interfaces, a command sequence is shown as Administration > Workloads This sequence indicates that to perform the necessary function, you select Workloads from the Administration menu. x TQ–01011.20 Contents About This Guide Part 1. Getting Up and Running Section 1. Introduction 1.1. What Is TeamQuest Performance Software?.............. 1–1 1.2. What Can You Do with TeamQuest Performance  Software?................................................................ 1–3 1.3. What Is TeamQuest Baseline?.................................... 1–4 1.4. What Can You Do with TeamQuest Baseline and  TeamQuest Online?................................................ 1–5 1.5. Processing Overview.................................................. 1–5 1.5.1. Data Collection................................................... 1–6 1.5.2. Data Display....................................................... 1–6 1.6. How Do TeamQuest Baseline and TeamQuest Online  Work?...................................................................... 1–8 1.6.1. The Host Software Component.......................... 1–8 1.6.1.1. Probes........................................................ 1–8 1.6.1.2. Performance Database.............................. 1–10 1.6.1.3. Host to TeamQuest View Interface............ 1–11 1.6.2. TeamQuest View Software................................. 1–11 1.7. Product Compatibility.................................................. 1–11 Section 2. TeamQuest Baseline and TeamQuest Online Concepts 2.1. Overview..................................................................... 2–1 2.2. Performance Database............................................... 2–1 2.2.1. Aggregation Sets................................................ 2–1 2.2.2. Parameters......................................................... 2–2 2.2.3. Data Values........................................................ 2–3 2.2.4. Table Data.......................................................... 2–4 2.3. Data Collection............................................................ 2–4 2.4. Workload Management............................................... 2–4 2.5. Alarms and Thresholds............................................... 2–5 2.6. Derived Statistics......................................................... 2–6 TQ–01011.20 xi Contents Section 3. TeamQuest Baseline Administration 3.1. tq-ini Element.............................................................. 3–1 3.2. Aggregation Sets........................................................ 3–3 3.3. Alarm Handling........................................................... 3–3 3.3.1. Default Threshold Definitions............................. 3–4 3.3.2. Using the Default Threshold Definitions............. 3–4 3.3.3. Changing the Default Threshold Definitions....... 3–5 3.4. What’s Next................................................................. 3–5 Part 2. Customizing Your Site Section 4. TeamQuest Performance Software Administration 4.1. Introduction................................................................. 4–1 4.2. What is a Session?..................................................... 4–1 4.3. Activating TeamQuest Performance Software  Administration......................................................... 4–2 4.4. Creating a Session..................................................... 4–3 4.4.1. Using a Socket Connection................................ 4–5 4.4.2. Using a SSL Connection.................................... 4–6 4.4.3. Using a Named Pipe Connection....................... 4–6 4.5. Additional Sessions.................................................... 4–6 4.6. Session Timeout Warnings......................................... 4–7 4.7. Terminating the Communications Session.................. 4–8 Section 5. Customizing Workloads 5.1. Introduction................................................................. 5–1 5.2. Concepts..................................................................... 5–1 5.2.1. Workload Qualifiers............................................ 5–2 5.2.2. Workload Definition Language........................... 5–2 5.2.2.1. Using Numerical Conditions...................... 5–3 5.2.2.2. Using String Conditions............................. 5–4 5.2.2.3. Using Regular Expressions in String Conditions 5–5 5.2.2.4. Using Boolean Expressions in Definitions. 5–7 5.2.2.5. Definition Example..................................... 5–7 5.3. Maintaining Workloads with TeamQuest Performance  Software Administration.......................................... 5–8 5.3.1. Performing Workload Administration Tasks........ 5–9 5.3.2. Creating a New Workload Set Definition............ 5–10 5.3.3. Displaying or Modifying a Workload Set Definition 5–11 5.3.4. Deleting a Workload Set.................................... 5–12 5.3.5. Creating a New Workload.................................. 5–13 5.3.6. Displaying or Modifying a Workload Definition... 5–16 5.3.7. Importing Workload Sets and Workload Definitions 5–17 5.3.8. Exporting Workload Sets and Workload Definitions 5–17 5.3.9. Deleting a Workload........................................... 5–18 xii TQ–01011.20  Contents 5.4. Maintaining Workloads with tqzip................................ 5–18 5.4.1. Unloading Workload Definitions......................... 5–19 5.4.2. Loading Workload Definitions............................. 5–22 Section 6. Customizing Aggregation Sets 6.1. Introduction................................................................. 6–1 6.2. Concepts..................................................................... 6–1 6.2.1. Aggregation Set Structure.................................. 6–2 6.2.2. Moving Window Concept for Data Storage......... 6–4 6.2.3. Aggregation Set Consolidation........................... 6–4 6.2.4. Feeding Aggregation Sets.................................. 6–7 6.2.5. Compact and Expanded Aggregation Set Format 6–7 6.3. Maintaining Aggregation Sets with TeamQuest  Performance Software Administration.................... 6–8 6.3.1. Performing Aggregation Set Administration Tasks 6–9 6.3.2. Creating an Aggregation Set.............................. 6–10 6.3.3. Displaying or Modifying Aggregation Set Definitions 6–14 6.3.4. Deleting an Aggregation Set............................... 6–15 6.4. Maintaining Aggregation Sets with tqasa.................... 6–15 6.4.1. Creating an Aggregation Set.............................. 6–16 6.4.2. Removing an Aggregation Set............................ 6–19 6.4.3. Listing Aggregation Sets..................................... 6–20 6.4.4. Unloading Aggregation Set Definitions............... 6–21 6.4.5. Loading Aggregation Set Definitions.................. 6–24 6.4.6. Converting Expanded Aggregation Sets............ 6–26 6.4.7. Performing Data Aggregation............................. 6–27 Section 7. Customizing Alarms and Thresholds 7.1. Introduction................................................................. 7–1 7.2. Concepts..................................................................... 7–1 7.3. Opening the Alarms and Thresholds Menu................. 7–5 7.4. Creating Threshold Definitions.................................... 7–6 7.5. Reusing Threshold Definitions.................................... 7–11 7.6. Updating Threshold Definitions................................... 7–12 7.7. Viewing Thresholds..................................................... 7–13 7.8. Creating Derived Statistic Threshold Definitions......... 7–14 7.9. Updating Derived Statistic Threshold Definitions........ 7–16 7.10. Viewing Derived Statistic Threshold Definitions.......... 7–18 7.11. Deleting Thresholds.................................................... 7–19 7.12. Notifying Probes of Threshold Changes..................... 7–21 7.13. Unloading Threshold Definitions................................. 7–21 7.14. Loading Threshold Definitions..................................... 7–24 7.15. Turning Threshold Checking On and Off..................... 7–25 7.15.1. Using the Alarms and Thresholds Menu............ 7–25 7.15.2. Using the tqzip Processor Call........................... 7–26 7.16. Generating Alarm Lists................................................ 7–27 7.17. Using tqalm................................................................. 7–28 7.18. Alarm Messages......................................................... 7–30 TQ–01011.20 xiii Contents 7.19. Site-Specific Alarm Handling...................................... 7–31 7.20. Single Point Operations (SPO) Considerations.......... 7–32 Section 8. Customizing Derived Statistics 8.1. Introduction................................................................. 8–1 8.2. Concepts..................................................................... 8–1 8.2.1. Derived Statistic Identification............................ 8–1 8.2.2. Parameter References and Substitution............ 8–2 8.2.3. Formula Definition.............................................. 8–3 8.3. Maintaining Derived Statistics with TeamQuest  Performance Software Administration.................... 8–4 8.3.1. Performing Derived Statistic Administration Tasks 8–5 8.3.2. Derived Statistic Hierarchy................................. 8–6 8.3.3. Creating a New Derived Statistic Definition........ 8–8 8.3.3.1. Defining an Alias........................................ 8–11 8.3.3.2. Qualifying Parameter References............. 8–12 8.3.3.3. Deleting an Alias........................................ 8–13 8.3.4. Saving a Derived Statistic Definition.................. 8–13 8.3.5. Viewing Long Key Names.................................. 8–14 8.3.6. Importing Derived Statistic Definitions................ 8–15 8.3.7. Exporting Derived Statistic Definitions............... 8–15 8.3.8. Displaying or Modifying a Derived Statistic Definition 8–16 8.3.9. Deleting a Derived Statistic Definition................ 8–17 8.4. Maintaining Derived Statistics with tqzip..................... 8–17 8.4.1. Unloading Derived Statistic Definitions.............. 8–18 8.4.2. Loading Derived Statistic Definitions.................. 8–21 Section 9. Customizing Data Collection Probes 9.1. Introduction................................................................. 9–1 9.2. tqctl Runstream........................................................... 9–1 9.3. SIP Data Collection..................................................... 9–2 9.3.1. tqbsp Processor Call Statement......................... 9–2 9.3.2. Terminating Data Collection............................... 9–3 9.3.3. Abnormal Termination of Data Collection........... 9–3 9.3.4. SIP File Input...................................................... 9–4 9.4. System Activity Monitor Collection.............................. 9–5 9.4.1. tqsam Processor Call Statement........................ 9–5 9.4.2. Terminating Data Collection............................... 9–6 9.4.3. Abnormal Termination of Data Collection........... 9–7 9.4.4. Workload Characteristics for the System Activity  Monitor Probe................................................ 9–7 9.4.5. tqsam Table Data............................................... 9–8 9.4.5.1. Runs Table Information.............................. 9–8 9.4.5.2. Transactions Table Information.................. 9–8 9.5. MIPS Metering Data Collection................................... 9–9 9.5.1. tqmips Processor Call Statement....................... 9–9 9.5.2. Terminating Data Collection............................... 9–11 9.5.3. Abnormal Termination of Data Collection........... 9–11 xiv TQ–01011.20  Contents 9.5.4. Trail Selection By Date Range or Relative Time 9–11 9.5.5. System Log File Input......................................... 9–12 9.6. Open Distributed Transaction Processing Collection.. 9–14 9.6.1. tqodtp Processor Call Statement........................ 9–14 9.6.2. Terminating Data Collection................................ 9–15 9.6.3. Abnormal Termination of Data Collection........... 9–15 9.6.4. tqodtp Table Data............................................... 9–16 9.6.4.1. System Table Information.......................... 9–16 9.6.4.2. Server Table Information............................ 9–16 9.6.4.3. Client Table Information............................. 9–16 9.6.4.4. Service Table Information.......................... 9–16 9.7. Real-Time TPM and TPM Log Data Collection........... 9–17 9.7.1. tqrtpm Processor Call Statement........................ 9–18 9.7.2. Terminating tqrtpm Data Collection.................... 9–19 9.7.3. tqtpm Processor Call Statement......................... 9–20 9.7.4. TPM Log File Input............................................. 9–21 9.7.5. Workload Characteristics for the RTPM and TPM  Log File Probes.............................................. 9–23 9.7.6. Log File User Area.............................................. 9–24 9.8. IOTRACE Data Collection........................................... 9–25 9.8.1. Data Collection Runstream................................. 9–25 9.8.2. tqiot Processor Call Statement........................... 9–26 9.8.3. Workload Characteristics for the IOTRACE Probe 9–28 9.9. MAPPER Log Data Collection..................................... 9–29 9.9.1. Data Collection Runstream................................. 9–29 9.9.2. tqmpr Processor Call Statement......................... 9–29 9.9.3. MAPPER Log File Input...................................... 9–31 9.9.4. Changing Default MAPPER Log File Names..... 9–32 9.9.5. Workload Characteristics for the MAPPER Log  Probe.............................................................. 9–33 9.10. System Log Data Collection........................................ 9–33 9.10.1. tqsys Processor Call Statement.......................... 9–34 9.10.2. System Log File Input......................................... 9–35 9.10.3. Workload Characteristics for the System Log Probe 9–37 9.11. User Data Probes........................................................ 9–38 9.11.1. Writing a User Probe for Performance Data....... 9–39 9.11.1.1. Data Storage.............................................. 9–45 9.11.1.2. Running tqusrprb in Continuous Mode...... 9–46 9.11.1.3. Installing Your User Probe......................... 9–47 9.11.1.4. Restrictions................................................ 9–47 9.11.2. Writing a User Probe for Table Data................... 9–48 9.11.2.1. Creating a Table......................................... 9–49 9.11.2.2. Storing Table Data...................................... 9–57 9.11.2.3. Examples of Table Data Collection............ 9–58 9.11.2.4. Command Syntax...................................... 9–62 9.11.2.5. Keyword Definitions................................... 9–65 TQ–01011.20 xv Contents Section 10. Customizing Performance Databases 10.1. Introduction................................................................. 10–1 10.2. Performance Databases............................................. 10–1 10.3. Database Files............................................................ 10–2 10.4. Creating Additional Databases................................... 10–3 10.5. Deleting Databases..................................................... 10–3 10.6. Listing Existing Databases.......................................... 10–4 10.7. Estimating Disk Space Requirements......................... 10–4 10.8. Listing Database Parameters...................................... 10–4 10.9. Removing Database Parameters from a Database.... 10–6 10.10. Database Locking....................................................... 10–7 10.11. Backup and Recovery................................................. 10–8 Section 11. Customizing Tables 11.1. Introduction................................................................. 11–1 11.2. Concepts..................................................................... 11–1 11.2.1. Collections.......................................................... 11–1 11.2.2. Retentions.......................................................... 11–2 11.2.3. Registration........................................................ 11–2 11.2.4. Manual Record Deletion..................................... 11–2 11.3. Opening the Table Administration Menu..................... 11–3 11.4. Displaying a List of Tables.......................................... 11–4 11.5. Administering Collection Periods................................ 11–4 11.5.1. Listing Collection Periods................................... 11–6 11.5.2. Adding a Collection Period................................. 11–7 11.5.3. Deleting a Collection Period............................... 11–8 11.5.4. Turning Data Collection On and Off................... 11–9 11.5.5. Exiting the Collection Period Menu.................... 11–9 11.6. Defining Retention Specifications............................... 11–9 11.6.1. Listing Retention Specifications......................... 11–11 11.6.2. Modifying the Primary Retention Specification... 11–12 11.6.3. Adding a Retention Specification....................... 11–13 11.6.4. Deleting a Retention Specification..................... 11–14 11.6.5. Setting the Retention Start Time........................ 11–15 11.6.6. Exiting the Retention Specification Menu........... 11–15 11.7. Deleting Records from Tables..................................... 11–16 11.7.1. Deleting Records Based on Time....................... 11–17 11.7.2. Deleting Records for a System.......................... 11–17 11.7.3. Deleting All Records for a Table......................... 11–18 11.8. Registering a Table..................................................... 11–18 11.9. Deregistering a Table.................................................. 11–20 11.10. Unloading Table Specifications................................... 11–21 11.11. Loading Table Specifications...................................... 11–25 11.12. Reorganizing Table Files............................................ 11–26 11.12.1. Why Do I Need To Reorganize My Table Files?. 11–27 11.12.2. Executing tqrorg................................................. 11–28 xvi TQ–01011.20  Contents Appendix A. OS 2200 Parameters A.1. Introduction................................................................. A–1 A.2. SIP Parameters........................................................... A–2 A.2.1. System Statistics................................................ A–5 A.2.2. Processor Statistics............................................ A–7 A.2.2.1. Performance Monitor................................. A–9 A.2.2.2. Dedicated Java Processor Statistics.......... A–14 A.2.3. Memory Statistics............................................... A–18 A.2.3.1. Program Load Statistics............................. A–18 A.2.4. Paging Statistics................................................. A–22 A.2.5. I/O Activity Statistics........................................... A–24 A.2.6. SIP Parameters for the XPC............................... A–36 A.2.7. Queue Statistics.................................................. A–39 A.3. TPM Log Parameters.................................................. A–41 A.4. MIPS Parameters........................................................ A–43 A.4.1. MIPS Probe Derived Statistics............................ A–43 A.5. IOTRACE Parameters................................................. A–44 A.6. MAPPER Log Parameters.......................................... A–45 A.7. System Log Parameters.............................................. A–46 A.8. Workload Performance Derived Statistics................... A–51 A.8.1. SIP Probe Derived Statistics............................... A–51 A.8.2. MAPPER Log Probe Derived Statistics.............. A–53 A.8.3. System Log Probe Derived Statistics................. A–54 A.9. System Activity Monitor Statistics................................ A–58 A.9.1. Runs Table.......................................................... A–58 A.9.2. Transaction Table............................................... A–59 A.10. Open Distributed Transaction Processing Statistics.... A–61 A.10.1. System Table Information................................... A–61 A.10.2. Server Table Information.................................... A–62 A.10.3. Client Table Information...................................... A–64 A.10.4. Service Table Information................................... A–64 Appendix B. Predefined Report Descriptions B.1. Introduction................................................................. B–1 B.2. Report Definition Directory.......................................... B–1 B.3. SIP Reports................................................................. B–2 B.3.1. I/O Reports......................................................... B–2 B.3.2. Java Reports...................................................... B–6 B.3.3. Memory Reports................................................. B–7 B.3.4. Processor Reports.............................................. B–8 B.3.5. System Reports.................................................. B–10 B.3.6. Summary Reports............................................... B–11 B.4. IOTRACE Reports....................................................... B–13 B.5. MIPS Report................................................................ B–14 B.6. MAPPER Log Reports................................................ B–14 B.7. System Log Reports.................................................... B–15 B.8. TPM Log Reports........................................................ B–17 B.9. Workload Performance Reports.................................. B–19 TQ–01011.20 xvii Contents Appendix C. Report Definition File C.1. Introduction................................................................. C–1 C.2. Notation Conventions.................................................. C–2 C.3. File Format.................................................................. C–2 C.4. General Section.......................................................... C–3 C.5. Parameter-Group Sections......................................... C–28 C.6. Individual Parameter Setting Sections........................ C–31 Appendix D. Host-Based Reporting for Aggregation Set Data D.1. Using tqrpt for Condensed Output.............................. D–4 D.2. Using tqrpt for Reporting Derived Statistics................ D–5 Appendix E. Host-Based Reporting for Table Data E.1. Overview of tqrep........................................................ E–1 E.2. Command Format....................................................... E–2 E.3. Report Definition File Format...................................... E–3 E.3.1. Report Section Keys.......................................... E–5 E.3.2. Table Section Keys............................................. E–8 E.3.3. Using Special Identifiers in Section Keys........... E–10 E.4. Using Default Reports................................................. E–12 E.5. Exporting Data............................................................ E–12 Appendix F. The tqgetm Program for TeamQuest Model Appendix G. Alarm History Table Appendix H. tqzip Processor Call Format Appendix I. 2200 Socket Interface I.1. Communications Application Program Interface......... I–2 I.2. TQTCP........................................................................ I–2 I.2.1. Background Run................................................ I–3 I.2.2. Processor Call.................................................... I–4 I.2.3. Configuration Element........................................ I–4 I.2.3.1. Same User-id For All TQTCP Runs........... I–5 I.2.3.2. Unique User-ids For Each TQTCP Run.... I–7 I.2.4. Error Messages.................................................. I–9 I.2.5. Security Considerations..................................... I–9 I.2.5.1. User-id and Password Encryption............. I–10 I.3. Connecting to the Socket............................................ I–10 xviii TQ–01011.20  Contents Appendix J. 2200 SNMP Trap Alarms J.1. Overview..................................................................... J–1 J.2. CPCOMM Configuration............................................. J–2 J.3. TeamQuest Alarm Administration Interface................. J–2 J.4. SNMP Trap Contents.................................................. J–4 J.4.1. SNMP Trap Mappings........................................ J–4 J.4.2. Variable Fields.................................................... J–5 J.5. Management Console Configurations......................... J–6 J.5.1. HP OpenView Configuration............................... J–7 J.5.2. Tivoli Management Environment Configuration.. J–7 J.5.3. Computer Associates Unicenter TNG................ J–9 J.6. TeamQuest MIB Definition.......................................... J–9 J.7. Special Considerations................................................ J–12 Glossary...................................................................................... 1 Bibliography................................................................................ 1 Index............................................................................................ 1 TQ–01011.20 xix Figures 1–1. TeamQuest Performance Software Family........................................... 1–2 1–2. TeamQuest Baseline Components........................................................ 1–7 6–1. Parameter Grouping for an Aggregation Set......................................... 6–3 6–2. Data Consolidation from Aggregation Set 1 to Aggregation Set 2........ 6–6 7–1. Threshold Zones................................................................................... 7–3 E–1. Report Generated by tqrep................................................................... E–1 TQ–01011.20 xxi Part 1 Getting Up and Running Section 1 Introduction 1.1. What Is TeamQuest Performance Software? TeamQuest Performance Software is a family of products which addresses the needs of performance management and performance analysis of your computer systems. This integrated family of products allows you to choose the tools that you need to manage the performance at your site. The TeamQuest Performance Software family consists of the following products: TeamQuest Baseline, TeamQuest SMFII, and TeamQuest Manager® The TeamQuest Performance Software includes TeamQuest Baseline for Unisys ClearPath OS 2200 systems, TeamQuest SMFII for Unisys MCP systems, TeamQuest Manager for UNIX/Linux systems, and TeamQuest Manager for Microsoft Windows systems. These products provide the services required for all of the products in the TeamQuest Performance Software family. These products provides the following features: – performance data measurement, collection, and storage services – administrative interfaces – alarm handling capabilities – basic textual data access and reporting capabilities TeamQuest Online This product provides a subset of the services provided by TeamQuest Baseline. All other products in the TeamQuest Performance Software family require the TeamQuest Performance Software. TeamQuest Alert® This product provides a performance console that allows you to monitor the current health of a large number of systems. TeamQuest Alert obtains performance data and alarm events from TeamQuest Manager on monitored system. It provides a top-down approach to monitoring large numbers of systems with a tightly coupled drill-down capability for problem investigation. TeamQuest Model® TeamQuest Model is a client application that runs on your workstation. TeamQuest Model provides capacity planning and “what-if ” analysis. TeamQuest Model obtains its data from TeamQuest products running on Unisys ClearPath OS 2200 systems, Unisys MCP systems, and UNIX/Linux systems. It provides an easy-to-use interface to a set of powerful modeling algorithms. TQ–01011.20 1–1 Introduction TeamQuest View® This product provides a graphical user interface for detailed data reporting and analysis. TeamQuest View obtains performance data from TeamQuest Baseline, TeamQuest SMFII, or TeamQuest Manager for display and analysis on your workstation. TeamQuest View allows you to monitor the performance of one or more systems and to quickly drill down to the exact cause of a problem. The TeamQuest Performance Software family of products offers something for anyone who requires access to performance management data. Figure 1–1 shows the relationship between the products within the TeamQuest Performance Software family. Monitored System TeamQuest Manager TeamQuest TeamQuest TeamQuest View Alert Model Figure 1–1. TeamQuest Performance Software Family 1–2 TQ–01011.20  Introduction 1.2. What Can You Do with TeamQuest Performance Software? The TeamQuest Performance Software family allows you to address a wide range of performance problems on your network of computers. When the TeamQuest Performance Software is installed on every monitored system in your network, you can deploy performance applications such as TeamQuest View, TeamQuest Alert, and TeamQuest Model, as needed. This structure allows you to deliver the right performance information to the right people at the right time. The TeamQuest Performance Software allows you to Monitor large numbers of systems from a single console. Investigate problems from the same tool with a few clicks of the mouse. Use alarms to detect complex situations and rules of thumb for casual monitoring. Typical users would include: operators and system administrators. Monitor one or more systems in detail with graphical and textual reports and use a powerful drill-down facility to investigate problems. Use correlation analysis to detect cause and effect situations. Typical users include: system administrators and performance analysts. Analyze historical data with the powerful time selection and reporting capabilities, including trend analysis. Typical users are: performance analysts and capacity planners. Characterize workloads along business lines to understand and monitor resource usage and requirements. Typical users are: performance analysts and capacity planners. Monitor systems from anywhere you have a standard web browser. Automatically publish current and historical performance reports using your web browser. Typical users are performance analysts (remote or on site), help desk, and management. Model your systems for hardware sizing, capacity planning, and what-if tuning scenarios. Typical users include: performance analysts and capacity planners. TQ–01011.20 1–3 Introduction 1.3. What Is TeamQuest Baseline? TeamQuest Baseline is the OS 2200 software product that provides the services for the TeamQuest Performance Software family on your OS 2200 system. The TeamQuest Baseline must be installed on every monitored host and consists of the components that collect, store, manage, and administer the performance data. TeamQuest Baseline performs the following functions for the TeamQuest Performance Software family: Data collection and storage Data is collected by probes and stored in a performance database. You can select from a predefined set of probes or you can define new probes. Administration You can control the data that is collected, how often it is collected, and how it is stored. You can also derive statistics and characterize workloads. Alarms and Thresholds You can specify conditions and actions for the TeamQuest Baseline to test and act upon. Application interfaces TeamQuest Baseline makes the collected and stored data available to the performance applications (TeamQuest View and TeamQuest Model) using secure application interfaces. 1–4 TQ–01011.20  Introduction 1.4. What Can You Do with TeamQuest Baseline and TeamQuest Online? The TeamQuest Baseline is the required product within the TeamQuest Performance Software family. TeamQuest Online is a subset of TeamQuest Baseline. These products allow you to perform the following tasks: Analyze and view system performance data using a real-time monitor Present reports simultaneously from multiple hosts Perform correlation analysis between performance statistics Produce hard-copy output of reports using a printer or a plotter TeamQuest Baseline provides the additional capabilities to perform the following tasks: Characterize the workloads on the system Build and maintain a database containing performance data on global system activity, network activity, and database activity, performance data by workloads, and performance data on process activity Perform threshold checking on performance data and derived statistics and generate alarms when values exceed predefined thresholds Consolidate data collected at a fine granularity into an aggregation set of coarser granularity Collect, reduce, and store process data Create your own user data probes Generate character-based reports on the host system 1.5. Processing Overview TeamQuest Baseline and TeamQuest Online processing consists of two phases: data collection and data display. These phases include the various activities involved in creating the performance database, maintaining the database, and using the data stored in the database for report generation and graphics displays. TeamQuest Baseline and TeamQuest Online control the activities for data collection and work with TeamQuest View for data display processing. TQ–01011.20 1–5 Introduction 1.5.1. Data Collection TeamQuest Baseline and TeamQuest Online use system monitors in the OS 2200 Executive (Exec) to gather data. TeamQuest Baseline and TeamQuest Online probes collect data from the various system monitors and store that data in the performance database. This data is then available for future retrieval and reporting. The performance database holds all data used to generate reports and to monitor the system in real time. Both TeamQuest Baseline and TeamQuest Online use the performance database for data storage. 1.5.2. Data Display TeamQuest View, the tqrpt program, and the tqrep program can be used to display the data collected and stored in the performance database. TeamQuest View is a graphical user interface providing graphical representation of data. The tqrpt program provides character-base reporting for aggregation set data (see Appendix D). The tqrep program provides character-base reporting for table data (see Appendix E). During the data display phase, the TeamQuest View software retrieves data from the performance database. You can then use this data to generate reports and display them in textual or graphic format. See the TeamQuest View User Guide for more information. Figure 1–2 shows the components of TeamQuest Baseline. TeamQuest Online consists of all these components except the workload probes (which receive data from HVTIP, TPM, IOTRACE, and MAPPER systems), tqagg, tqalm, tqzip, tqrep, and tqrpt. 1–6 TQ–01011.20  Introduction Data Collection Exec HVTIP MAPPER IOTRACE System Probes tqagg tqalm Database Management Performance Database tqzip Reports tqrep Reports tqdata tqrpt Reports Printer Files TeamQuest View Exported Report Data Display Data Files Figure 1–2. TeamQuest Baseline Components TQ–01011.20 1–7 Introduction 1.6. How Do TeamQuest Baseline and TeamQuest Online Work? TeamQuest Baseline and TeamQuest Online consist of a host software component and the TeamQuest View user interface software. The host software collects performance data, stores this data in the performance database, and maintains the database. TeamQuest View requests performance data from the performance database and creates reports. 1.6.1. The Host Software Component The TeamQuest Baseline and TeamQuest Online host software runs on your OS 2200 system collecting data and maintaining the performance database. The host software uses probes to collect data. Individual probes collect data from different sources. Once the data is collected, TeamQuest Baseline or TeamQuest Online stores the data for future retrieval. 1.6.1.1. Probes The TeamQuest Baseline data collection probes are initiated on the host system. These probes start the data collection and automatically process the data. They also extract statistical values and date and time information for performance parameters and store that information in the performance database. TeamQuest Baseline and TeamQuest Online come packaged with the tqbsp probe. The tqbsp probe collects Software Instrumentation Package (SIP) data from the Exec. Using the ER SYSBAL$ mechanism, the tqbsp probe starts the data collection and automatically processes that data. The tqbsp probe extracts statistical values for performance parameters and stores this information in the performance database. 1–8 TQ–01011.20  Introduction TeamQuest Baseline comes packaged with the following additional probes that provide the workload capability of the product: tqsam The tqsam probe collects information on active runs and transactions using calls to Exec INSP$. TeamQuest Baseline contributes additional capability to dynamically put the data collected by the tqsam probe into workloads and to change various collection attributes. tqrtpm The tqrtpm probe processes TIP/HVTIP statistics from the TIP Performance Monitor (TPM) audit trails created when TIP logging is configured. This probe requires that your TPM audit trail be configured to mass storage or moved to mass storage prior to starting either probe. The tqrtpm probe runs continuously to report the data in near real time mode. tqtpm The tqtpm probe processes TIP/HVTIP statistics from the TIP Performance Monitor (TPM) audit trails created when TIP logging is configured. This probe requires that your TPM audit trail be configured to mass storage or moved to mass storage prior to starting either probe. The tqtpm probe automatically processes the TPM audit trail(s) from the previous day, from TPM audit trail(s) specified on the call statement, or based on a relative time selection also specified on the call line. The tqtpm probe extracts statistical values plus date and time information from the TPM audit trail(s), determines the workload that used the resource, and stores this information in the performance database according to the workloads defined for the system. tqiot The tqiot probe processes statistics from the IOTRACE data collection file. The tqiot probe processes the IOTRACE data files specified on its processor call statement. The tqiot probe extracts statistical values on system resource utilization plus date and time information from the data file, determines the workload that used the resource, and stores this information in the performance database according to the workloads defined for the system. tqmpr The tqmpr probe processes data from the MAPPER accounting log files. The tqmpr probe processes the set of MAPPER accounting log files from the previous day or the MAPPER accounting log files specified on its processor call statement. tqmpr extracts statistical values on MAPPER resource utilization plus date and time information from the log file, determines which workload used the resource, and stores this information in the performance database according to the workloads defined for the system and the MAPPER environments. TQ–01011.20 1–9 Introduction tqsys The tqsys probe processes data from the system log files. The tqsys probe automatically processes the system log files from the previous day or the system log files specified on its processor call statement. The tqsys probe extracts statistical values on system resource utilization plus date and time information from the log file, determines the workload that used the resource, and stores this information in the performance database according to the workloads defined for the system. tqodtp The tqodtp probe collects information in an Open Distributed Transaction Processing (ODTP) environment. The tqodtp probe retrieves information from an ODTP environment for configured clients, servers, and system service programs. TeamQuest Baseline provides two user probe interface programs, called tqusrprb and tqtblprb, that allow you to develop your own site-specific probes. These programs, coupled with user-supplied information, insert data into the performance database. Any number of user-developed probes can exist on your system. The TeamQuest Probes software is also available for use with TeamQuest Baseline and TeamQuest Online. This separately packaged product contains additional probes to gather and store data from other system monitors. It provides probes for the Message Control Bank (MCB), the Universal Data System (UDS), and mass storage. See the OS 2200 TeamQuest Probes End Use Reference Manual for more information. The TeamQuest PMLog software provides an additional probe for the TeamQuest Baseline software. It gathers ClearPath OS 2200 Performance Monitor log data for TeamQuest Baseline. See the OS 2200 TeamQuest PMLog End Use Reference Manual for more information. 1.6.1.2. Performance Database The performance database holds all data used to generate history reports and to monitor the system in real time. Data is stored into various aggregation sets in the database. An aggregation set defines the level of granularity of the data and the length of time data is stored. The performance database, which is maintained automatically on a daily basis, is created during the initial product installation and set-up process. Additional databases can be created. 1–10 TQ–01011.20  Introduction 1.6.1.3. Host to TeamQuest View Interface The host to TeamQuest View interface is called tqdata. You use the TeamQuest View user interface software to connect to the host system using a socket interface. A run is automatically started on the host system which executes tqdata and handles all communications between the host and TeamQuest View. 1.6.2. TeamQuest View Software The TeamQuest View software provides the user interface to the TeamQuest Baseline and TeamQuest Online host software. TeamQuest View lets you access the host system, retrieve data, and create reports. Using TeamQuest View, you can generate reports showing historical data and view system performance data by using the real-time monitor. Each of the probes is released with a set of predefined reports. The SIP reports give a general overview of system performance on your system. The TPM reports show high-volume TIP/HVTIP usage by workload. The IOTRACE probe reports I/O information by workload. The MAPPER log reports show MAPPER accounting log data by workload. The system log reports show the usage of system resources by workload. 1.7. Product Compatibility When using TeamQuest Probes or TeamQuest PMLog with TeamQuest Baseline or TeamQuest Online, you must ensure that the base levels of the products are the same. The result of mixing base product levels could be database corruption. For example, you can run a level 7R3 product level with a level 7R3A product, but it is incorrect to run a level 7R2 product with a level 7R3 or a level 7R3A product. TQ–01011.20 1–11 Section 2 TeamQuest Baseline and TeamQuest Online Concepts 2.1. Overview The TeamQuest Baseline consists of the components that collect, store, manage, and administer the performance data. This section describes the major concepts involved. 2.2. Performance Database The TeamQuest Baseline probes obtain performance data from the server system and store the data in the performance database. The performance database consists of data values for the parameters gathered from the various collection sources. Data is collected and stored in the database according to defined data aggregation sets. Aggregation sets, parameters, and data values are concepts essential to the understanding of the performance database and the use of TeamQuest View to retrieve and display data from the database. Table data is also maintained in the performance database at the interval where it was originally collected. Like aggregation set data, table data can be retrieved and displayed by using the TeamQuest View. 2.2.1. Aggregation Sets The TeamQuest Baseline lets you collect and store your performance data at different sampling intervals or levels of granularity. Depending on your needs, you may be interested in data sampled at a small granularity, such as 1-minute intervals, or at a larger granularity, such as 1-hour intervals. TeamQuest Baseline and TeamQuest Online use aggregation sets to define the granularity of the data in the database, as well as the length of time the data is retained in the database. TeamQuest Online allows only one aggregation set in the database. Data records are saved into a 1-minute aggregation set. This means that data is collected at 1-minute intervals and is retained in the database for a period of 32 hours. TQ–01011.20 2–1 TeamQuest Baseline and TeamQuest Online Concepts TeamQuest Baseline allows multiple aggregation sets in your database. So, for example, if you are interested in real-time monitoring of your system, you might have an aggregation set that collects and stores data at 30-second intervals and retains that data for a 1-day time period. If you are interested in trend analysis of your system, you might want to store data at half-hour intervals for a 6-month period. You can have both of these aggregation sets in your database, as well as others that you defined to meet your particular needs. TeamQuest Baseline is released with some default aggregation sets (see 3.2). You can also define your own aggregation sets by using TeamQuest Performance Software Administration (see 6.3). 2.2.2. Parameters The term parameter refers to a performance data item in the database. A parameter consists of a statistic and optional resource, workload, and application group qualifiers. The term parameter applies only to performance data stored in the performance database aggregation sets; it does not apply to table data. A statistic describes the information being collected and stored in the database. A statistic is defined by a hierarchy of key names, which identify the statistic for retrieval from the database. The key names used for the classification of statistics are system, category group, category, subcategory, and statistic name. System specifies the system on which the data was collected. A system is defined as a group of closely coupled components that function together and allow measurement of system performance characteristics. Category group identifies a group of categories with similar characteristics. Any given system may have many categories and the category group specification is used to group related categories. For example, category groups can include processor, memory, IO activity, and system. A category breaks down a category group. Examples of categories within the category group memory are utilization, dynamic allocator, and program load. A subcategory further breaks down a category into a group of related statistics. For example, a category called processor can be grouped into subcategories of Exec requests, utilization, and hardware interrupts. A statistic name is the name of the information being collected and stored in the database. For example, percent busy, requests per second, and K words per request are statistic names. The following examples show the hierarchy of key names for various statistics: System Category Group Category Subcategory Statistic Name CL01 Processor Total Utilization Total Exec CL01 IO Activity Logical Channel Cache Summary Transfer Time CL01 Memory Paging Activity Working Sets Inputs/Sec 2–2 TQ–01011.20  TeamQuest Baseline and TeamQuest Online Concepts Resource Specification A parameter can be further qualified by a resource specification. A resource is a component of the system that does work. A resource could be a physical resource, such as a disk unit or tape unit. Or, it could be a logical resource, such as a system call. For example, a statistic with a hierarchy of CL01, IO Activity, Logical Channel, Cache Summary, Transfer Time can be further qualified by the specific logical channel of LC1. In this case, TeamQuest Baseline or TeamQuest Online would report the transfer time statistics for LC1 of your system. Workload Specification With the workload capability of TeamQuest Baseline, a parameter can be further qualified by a workload specification. A workload is a logical classification of the work performed on the system. These classifications are site-specific and are expressed in terms that are meaningful to the business. For example, workloads can be defined to track how much of the system resources are used by the payroll department, the order entry department, or a software development project. Note: The workload capability is not available with TeamQuest Online. Application Group Specification A parameter can further be qualified by an application group specification. For the MAPPER probe (tqmpr), the MAPPER name is specified using the application group specification. For the UDS and MCB probes supplied with the TeamQuest Probes product, the UDS or MCB application name is specified using the application group specification. For parameters collected by any of the other TeamQuest Baseline probes, the application group specification is null. 2.2.3. Data Values The term data value refers to a specific instance of data in the database for a specific parameter. A data value is identified by the parameter, aggregation set, and time and date. Based on this, when you request values from the database, you are requesting statistics for a particular time and date that were stored at a specified granularity. Note: Data for an interval t to t+1 is stored at time t. Therefore, when you see a data value at 10:00 a.m., it represents the activity for the interval starting at 10:00 a.m. In the case of snapshot values such as disk space available, the data value at 10:00 a.m. represents the disk space available at the end of the interval started at 10:00 a.m. TQ–01011.20 2–3 TeamQuest Baseline and TeamQuest Online Concepts 2.2.4. Table Data The term table data refers to the data that is stored in tables. A table is a collection of records containing columns that are related to one another in some way. For example, all data about an alarm is stored in a table. A record contains one set of column values for the table. For example, data for a particular alarm on a system at a given time makes up one record in the alarm table. Each field in a table contains a particular type of data. The field may contain a string or a number. The numbers may be integers, real numbers, elapsed times, or timestamps. Selected fields in a table can be used to help identify records in the table. These fields are called identifiers. Examples of identifiers are system name, severity, and alarm identifier. Tables are created by the TeamQuest Baseline probes. Table records are inserted by TeamQuest Baseline and the TeamQuest Baseline probes as is appropriate for the type of records being created. 2.3. Data Collection TeamQuest Baseline and TeamQuest Online use probes to gather data. The probes collect data about the host system on which they are running. They also extract statistical values, and date and time information for performance parameters, and store that information in the performance database. 2.4. Workload Management Note: The workload capability is not available with TeamQuest Online. TeamQuest Baseline allows you to track the activity on your system based on a logical classification of the work performed on the system. This logical classification of work is called workload characterization. Workload characterization is the process whereby groups of related performance data are organized into meaningful units called workloads. You define workloads for your performance database and the TeamQuest Baseline probes distribute the data they collect according to the defined workloads. The workload data is stored in the aggregation sets of the performance database. Workload characterization is used to summarize a large set of data in ways that reduce the level of detail required to understand the operation of the computer system and its relationship to the various business operations it supports. This process is essential to understanding how well your computer system is meeting the requirement of providing acceptable levels of service to the users. 2–4 TQ–01011.20  TeamQuest Baseline and TeamQuest Online Concepts Workload characterization allows you to identify the workloads and track their use of system resources. Each workload is uniquely identified and defines a criteria for distributing the system resources used by each activity. For example, you can define your workload to track how much of the system resources are used by payroll, order entry, or a software development project. The system activity monitor, TPM, IOTRACE, MAPPER log, and system log probes use the workload definitions to distribute the statistics for the work performed by each activity to the appropriate workload. TeamQuest Baseline supports the definition of multiple workload sets, each containing unique workload definitions. A workload set is defined as a set of workloads that represents the system resources used by all activities on the system. TeamQuest Baseline uses each workload set for distributing the work performed by each activity. This allows you to track the activities on the system using a different view of the system. Creating multiple workload sets is useful for testing new workload definitions because they can be used without affecting the existing production workloads. TeamQuest Performance Software Administration and the host-based tqzip program are used to perform workload management tasks on your system. Workload statistics can be viewed using the TeamQuest View application. 2.5. Alarms and Thresholds Note: The alarms and thresholds capability is not available with TeamQuest Online. The TeamQuest Baseline probes collect data from various data sources at the sample interval defined for the user-specified aggregation set. The probes can also check the data obtained at each sample interval to determine if the data values exceed user-specified threshold limits. If a data value for a parameter is found to exceed a threshold, the probe can generate an alarm to alert you that a threshold condition has been met. The tqalm program handles all alarms generated by the TeamQuest Baseline probes. tqalm sends console messages, makes the alarm messages available for display by TeamQuest View, and performs site-specific actions for each alarm. The tqalm program can optionally send an SNMP trap when an alarm occurs (see Appendix J). The tqalm program also performs threshold checking on any derived statistics for which thresholds are defined. TQ–01011.20 2–5 TeamQuest Baseline and TeamQuest Online Concepts 2.6. Derived Statistics Note: The derived statistic capability is not available with TeamQuest Online. TeamQuest Baseline allows you to create your own statistics that are derived using data values collected by the TeamQuest Baseline data collection probes. You create derived statistics using TeamQuest View. Once you have created a derived statistic, it can be used in history, monitor, correlation, and host-based reporting. You can also use the tqzip program to define thresholds for your derived statistics. The thresholds are used by tqalm to determine when alarm messages need to be generated for a derived statistic. A derived statistic is saved in the performance database as a formu