Tandem Capacity Model (TCM) Manual
HP Part Number: 522695-010
Published: October 2014
Edition: J06.03 and subsequent J-series RVUs, H06.03 and subsequent H-series RVUs, and G06.14 and subsequent G-series RVUs
© Copyright 2002, 2014 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor’s standard commercial license.
Warranty
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Export of the information contained in this publication may require authorization from the U.S. Department of Commerce.
Acknowledgements
Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® are U.S. registered trademarks of Microsoft Corporation. Intel®
and Intel® Itanium® are trademarks of Intel Corporation in the U.S. and other countries. Motif, OSF/1, UNIX®, X/Open®, and the X device is a
trademark of X/Open Company Ltd. in the UK and other countries. OSF, OSF/1, OSF/Motif, Motif, and Open Software Foundation are trademarks
of the Open Software Foundation in the U.S. and other countries.
© 1990, 1991, 1992, 1993 Open Software Foundation, Inc. The OSF documentation and the OSF software to which it relates are derived in part
from materials supplied by the following: © 1987, 1988, 1989 Carnegie-Mellon University. © 1989, 1990, 1991 Digital Equipment Corporation.
© 1985, 1988, 1989, 1990 Encore Computer Corporation. © 1988 Free Software Foundation, Inc. © 1987, 1988, 1989, 1990, 1991
Hewlett-Packard Company. © 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. © 1988, 1989
Massachusetts Institute of Technology. © 1988, 1989, 1990 Mentat Inc. © 1988 Microsoft Corporation. © 1987, 1988, 1989, 1990, 1991,
1992 SecureWare, Inc. © 1990, 1991 Siemens Nixdorf Informations systeme AG. © 1986, 1989, 1996, 1997 Sun Microsystems, Inc. © 1989,
1990, 1991 Transarc Corporation. OSF software and documentation are based in part on the Fourth Berkeley Software Distribution under license
from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth
C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983, 1985,
1986, 1987, 1988, 1989 Regents of the University of California. OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF
MATERIAL PROVIDED HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing,
performance, or use of this material.
Contents
About This Document...................................................................................11
New TCM Features and Microsoft Excel 2010............................................................................11
Enhancements...................................................................................................................11
Considerations..................................................................................................................11
Supported Release Version Updates (RVUs)................................................................................12
Intended Audience..................................................................................................................12
New and Changed Information................................................................................................12
Changes to the 522695-010 Manual....................................................................................12
Changes to the 522695-009 Manual...................................................................................12
Changes to the 522695-008 Manual...................................................................................13
Changes to the 522695-007 Manual....................................................................................13
Changes to the 522695-006 Manual...................................................................................14
Changes to the 522695-004 Manual...................................................................................14
Document Organization..........................................................................................................14
Notation Conventions..............................................................................................................15
General Syntax Notation....................................................................................................15
Related Information.................................................................................................................17
Publishing History...................................................................................................................17
HP Encourages Your Comments................................................................................................17
1 Introduction.............................................................................................18
TCM and Related Products.......................................................................................................18
Functions and Features............................................................................................................18
Assumptions......................................................................................................................19
Caveat.............................................................................................................................19
Architecture and Components...................................................................................................19
TCM User Levels.....................................................................................................................20
TCM and the Capacity Planning Process....................................................................................21
Understanding the Application............................................................................................21
Tuning the System..............................................................................................................22
Collecting Performance Data...............................................................................................22
Apportioning Performance Data...........................................................................................23
Checking an Apportionment Method....................................................................................23
Performing What-If Analyses................................................................................................23
Reporting Results................................................................................................................24
2 TCM System Setup....................................................................................25
System Requirements...............................................................................................................25
Installation Overview...............................................................................................................25
Installing MeasTCM on the Host...............................................................................................26
Installing TCM on the PC.........................................................................................................26
Finding Version Information......................................................................................................27
Converting TCM Models From Earlier TCM Product Versions.........................................................27
Loading Models From Other Folders..........................................................................................28
3 Using MeasTCM......................................................................................29
Features and Functions............................................................................................................29
Components and Architecture...................................................................................................29
MeasTCM Procedures.............................................................................................................30
Collecting Measure Samples....................................................................................................30
Drawing a Process Flow Diagram.............................................................................................31
Customizing Your Process Category Control File.........................................................................33
CNTLFILE File Format...............................................................................................................40
Contents
3
Environmental Entries..........................................................................................................40
Process Category (PCAT) Statements.....................................................................................54
TITLE Statements.................................................................................................................59
File Defaults......................................................................................................................60
TXN Entries.......................................................................................................................60
Running MeasTCM to Create CSV Files......................................................................................61
Running MeasTCM.............................................................................................................61
Using the Process Category Audit Report...................................................................................63
Checking Category 98.......................................................................................................63
4 Getting Started With TCM.........................................................................65
Guidelines.............................................................................................................................65
TCM Users........................................................................................................................65
TCM Online Help..............................................................................................................65
Selecting Ribbons, Tabs and Options....................................................................................65
TCM Status.......................................................................................................................65
Moving From Screen to Screen.............................................................................................65
Getting Started With Sample Data.......................................................................................65
Creating a Folder for Your Model.............................................................................................65
TCM File Names................................................................................................................66
TCM Initial Menu....................................................................................................................67
Workload Apportionment Options.......................................................................................68
Performance Model Options................................................................................................69
TCM Expert Option............................................................................................................69
Security.................................................................................................................................69
User Authorization Levels.....................................................................................................69
Passwords.........................................................................................................................70
Online Help...........................................................................................................................71
Getting Help for a Specific Field..........................................................................................71
Getting Help for Function Keys.............................................................................................71
Customizing Help Messages................................................................................................71
5 Creating a WA Model..............................................................................72
Overview..............................................................................................................................72
Apportionment Tables.............................................................................................................72
Example of an Apportionment Weights Table........................................................................72
Example of a Transaction Count Table..................................................................................73
Transaction Count Table Versus Transaction Count File............................................................74
WA Model Flowchart..............................................................................................................76
Loading Performance Data Into TCM.........................................................................................76
Downloading Performance Data Samples..............................................................................76
Loading Samples Into TCM..................................................................................................77
Modifying the Apportionment Weights Table..............................................................................77
Modifying the Transaction Count Table......................................................................................78
Saving the Tables...............................................................................................................79
Reviewing Apportionment Results..............................................................................................80
Updating the Capacity History Database...................................................................................81
Saving a WA Model..........................................................................................................82
Checking an Apportionment Method.........................................................................................83
Updating History With Several Examples..............................................................................83
Analyzing Capacity History................................................................................................84
Non-Pathway Example............................................................................................................84
Workload Apportionment Weights Table..............................................................................86
Transaction Count Table......................................................................................................86
4
Contents
6 Creating a Performance Model..................................................................87
Creating a New Performance Model.........................................................................................87
Working With an Existing Performance Model...........................................................................89
Modifying the Planning Unit................................................................................................90
Modifying Percentile Response Times....................................................................................91
Using the Consumption Model.................................................................................................91
About the Results...............................................................................................................92
Using the Planning Timeline Model...........................................................................................92
Throughput Trending..........................................................................................................93
Printing Charts.......................................................................................................................96
Saving the Model...................................................................................................................96
Deleting Transactions or Applications........................................................................................96
Merging Performance Models..................................................................................................96
7 Modeling Batch Workloads.......................................................................97
Assumptions...........................................................................................................................97
Transaction Types...................................................................................................................98
Batch Examples ................................................................................................................99
Differences in Modeling Batch Transactions..............................................................................100
Running MeasTCM...........................................................................................................100
Creating a WA Model.....................................................................................................100
Creating a Performance Model..........................................................................................101
Calibrating Batch Response Time............................................................................................105
Uncalibrate Transaction....................................................................................................106
8 Workload Apportionment Model..............................................................107
Data Source.........................................................................................................................107
Category Demand Report......................................................................................................108
Significant Rows..............................................................................................................108
Significant Columns.........................................................................................................109
CPU Workload Apportionment Screen.....................................................................................109
Significant Rows..............................................................................................................110
Significant Columns.........................................................................................................110
Disk Read Workload Apportionment Screen.............................................................................111
Significant Rows..............................................................................................................111
Significant Columns.........................................................................................................112
Disk Write Workload Apportionment Screen............................................................................113
Significant Rows..............................................................................................................113
Significant Columns.........................................................................................................114
Workload Summary Screen...................................................................................................114
Significant Rows..............................................................................................................115
Significant Columns.........................................................................................................115
WA Model TCM Parameters Screen........................................................................................116
Significant Rows..............................................................................................................116
Significant Columns.........................................................................................................117
Workload Apportionment Weights Table.................................................................................117
Significant Row................................................................................................................118
Significant Columns.........................................................................................................118
Transaction Count Table........................................................................................................119
Significant Columns.........................................................................................................119
Maximum Transactions.....................................................................................................121
Transaction Count Table Versus Transaction Count File..........................................................121
Using Process Pairs..........................................................................................................122
Workload Detail by Category Screen......................................................................................122
Significant Row................................................................................................................123
Significant Columns.........................................................................................................123
Contents
5
Changing Process Category Priorities.................................................................................123
Capacity History Screens.......................................................................................................124
Significant Rows..............................................................................................................124
Significant Columns.........................................................................................................125
History Charts......................................................................................................................125
Trend Chart.....................................................................................................................126
Mix Chart.......................................................................................................................126
Workload Apportionment Ribbon...........................................................................................126
File Tab...............................................................................................................................126
Open (F5).......................................................................................................................126
Save (F6)........................................................................................................................126
Save As..........................................................................................................................126
Close (SF5).....................................................................................................................127
Delete............................................................................................................................127
Exit (SF6)........................................................................................................................127
Find Tab..............................................................................................................................127
Update Tab.........................................................................................................................127
Load Category Data (F3)..................................................................................................127
Workload Apportionment (SF10).......................................................................................127
History Tab..........................................................................................................................128
Update History (F10)........................................................................................................128
Search History (F11)..........................................................................................................128
Delete History..................................................................................................................128
Sort History.....................................................................................................................129
Chart History...................................................................................................................129
Display Tab.........................................................................................................................129
Display (or Undisplay) Scratch Areas..................................................................................129
Change Display Fonts.......................................................................................................129
Show Value (Control-V).....................................................................................................129
Print Tab..............................................................................................................................130
Print (F8).........................................................................................................................130
Page Setup.....................................................................................................................131
Change Printer Fonts........................................................................................................132
Printer Setup....................................................................................................................132
Options Tab.........................................................................................................................132
Change Authorization Level (SF7).......................................................................................132
Undo Entry.....................................................................................................................132
Notepad (SF2)................................................................................................................132
Calculate Now (F12)........................................................................................................132
Unprotect (or Protect) Admin Fields.....................................................................................132
Change Password............................................................................................................133
Enter Excel (F4)...............................................................................................................133
Expert Tab...........................................................................................................................133
Generate Expert Apportionment Weights............................................................................133
Update History With Selected CSVs...................................................................................134
Create Default Transaction Count Table...............................................................................134
Pick Best CSV Sample.......................................................................................................135
TCM Expert Parameters.....................................................................................................135
Help Tab.............................................................................................................................136
TCM Help (F1).................................................................................................................136
Function Keys (SF1)..........................................................................................................136
About.............................................................................................................................136
9 The Performance Model...........................................................................137
Performance Model Components............................................................................................137
6
Contents
Data Source.........................................................................................................................138
Navigation..........................................................................................................................138
Screen Descriptions...............................................................................................................139
Capacity Baseline—Actual Screen..........................................................................................139
Significant Rows..............................................................................................................140
Significant Columns.........................................................................................................141
Consumption Model Screen...................................................................................................141
Significant Rows..............................................................................................................142
Significant Columns.........................................................................................................144
Planning Timeline Model Screen.............................................................................................145
Significant Rows..............................................................................................................146
Significant Columns.........................................................................................................148
TCM Parameters Screen.........................................................................................................148
Significant Rows..............................................................................................................149
CPU Factors Screen...............................................................................................................150
Disk Factors Screen...............................................................................................................151
Actual Baseline Detail by Category Screen..............................................................................155
Significant Rows..............................................................................................................155
Significant Columns.........................................................................................................155
Plan Baseline Detail by Category Screen.................................................................................156
Significant Rows..............................................................................................................157
Significant Columns.........................................................................................................157
Capacity History Screens.......................................................................................................158
Capacity History Database Screen.....................................................................................158
Capacity History Trend Charts Screen.................................................................................160
Capacity History Mix Chart Screen....................................................................................160
TCM User Customization Screen.............................................................................................160
Restoring Default Properties...............................................................................................162
Performance Model Charts.....................................................................................................162
Planning Timeline Model Chart..........................................................................................163
Performance Model Ribbons...................................................................................................164
File Tab...............................................................................................................................164
Open (F4).......................................................................................................................164
Save/Save As (F5)...........................................................................................................164
Close (SF4).....................................................................................................................164
Return to the TCM Initial Menu (SF3)..................................................................................164
Exit TCM (SF5)................................................................................................................165
Find Tab..............................................................................................................................165
Update Tab.........................................................................................................................165
Load Baseline Data (F3)....................................................................................................165
Refresh Formulas..............................................................................................................166
Timeline Trends................................................................................................................167
Calibrate Batch Response Time..........................................................................................168
Merge Performance Models..............................................................................................169
Add Transaction..............................................................................................................172
Add Similar Transaction....................................................................................................173
Delete Transaction............................................................................................................174
Add Category.................................................................................................................174
Delete Category..............................................................................................................174
Display Tab.........................................................................................................................174
Show Gridlines................................................................................................................174
Zoom In..........................................................................................................................174
Display Scratch Areas.......................................................................................................174
Show Headings...............................................................................................................174
Change Display Fonts.......................................................................................................174
Contents
7
Show Value (Control-V).....................................................................................................174
Widen Column................................................................................................................175
Narrow Column...............................................................................................................175
Print Tab..............................................................................................................................175
Print (F6).........................................................................................................................175
Page Setup.....................................................................................................................176
Change Printer Fonts........................................................................................................177
Printer Setup....................................................................................................................177
Options Tab.........................................................................................................................177
Change Authorization Level (SF6).......................................................................................177
Calculate Now (F9)..........................................................................................................177
Undo Entry.....................................................................................................................177
Notepad (SF2)................................................................................................................177
Select Response Time Method............................................................................................177
Change Password............................................................................................................178
Customize TCM...............................................................................................................178
Chart Tab............................................................................................................................178
Create Timeline Chart (F8)................................................................................................178
Customize ......................................................................................................................178
Help Tab.............................................................................................................................178
TCM Help (F1).................................................................................................................178
Function Keys (SF1)..........................................................................................................178
About.............................................................................................................................179
10 Using TCM Expert.................................................................................180
CSV Sample Data Required...................................................................................................180
Data Splitting..................................................................................................................180
Generating an Apportionment Weights Table for CSV Files...................................................181
Creating a Default Transaction Count Table and Workload Apportionment Weights Table..............182
Generating Expert Apportionment Weights..............................................................................183
Updating Capacity History With Selected CSV Files..................................................................186
Picking the Best CSV Sample and Loading It Into the Performance Model.....................................187
Viewing or Changing Expert Parameters..................................................................................188
A TCM File Names....................................................................................189
Distribution Folder for the PC Using Excel 2003........................................................................189
Distribution Folder for the PC Using Excel 2007........................................................................190
Custom Folder......................................................................................................................191
B MeasTCM Error Messages.......................................................................192
MeasTCM Termination Messages............................................................................................192
Informational Messages.........................................................................................................216
C TCM Menus..........................................................................................222
Menu Items for Excel 2003....................................................................................................222
For Workload Apportionment Model..................................................................................222
For Performance Model.....................................................................................................224
Ribbon Items for Excel 2007/2010.........................................................................................226
For Workload Apportionment Model..................................................................................226
For Performance Model.....................................................................................................228
D TCM Response Time Formulas..................................................................230
E Common TCM Procedures.......................................................................231
Adding a Transaction............................................................................................................232
Analyzing Capacity History...................................................................................................232
Calculating Throughput Trending............................................................................................233
Calibrating Batch Response Time............................................................................................233
8
Contents
Changing Authorization Levels................................................................................................233
Changing Default Priorities....................................................................................................234
Changing Expert Parameters..................................................................................................234
Changing Individual Priorities.................................................................................................235
Changing Passwords.............................................................................................................235
Checking an Apportionment Method.......................................................................................235
Checking Category 98..........................................................................................................236
Collecting Measure Samples..................................................................................................236
Converting TCM Models From Earlier TCM Product Versions.......................................................236
Creating Additional Workload Apportionment Models..............................................................236
Creating a Mix Chart............................................................................................................237
Creating a New Workload Apportionment Model....................................................................237
Creating a New Performance Model.......................................................................................237
Creating a Trend Chart.........................................................................................................237
Customizing the MeasTCM CNTLFILE......................................................................................238
Customizing Help Messages..................................................................................................238
Customizing TCM Screens.....................................................................................................238
Downloading Performance Data Samples................................................................................239
Finding Product Version Information........................................................................................239
Generating a Timeline Chart..................................................................................................239
Getting Help for Function Keys...............................................................................................240
Getting Help for Specific Fields..............................................................................................241
Loading a CSV Sample Into a WA Model................................................................................241
Loading Models Created by Other Users.................................................................................241
Merging Performance Models................................................................................................242
Modifying Apportioned Data Using an .AWA File in the Current Session.....................................242
Modifying Apportioned Data Using an .AWA File Not in the Current Session...............................243
Modifying the Percentile Response Times..................................................................................244
Modifying the Planning Unit...................................................................................................244
Modifying the Transaction Count Table....................................................................................244
Modifying the Workload Apportionment Weights Table.............................................................245
Moving Between Screens.......................................................................................................245
Picking the Best CSV Sample and Loading It Into the Performance Model.....................................245
Printing a Chart....................................................................................................................246
Returning to TCM From a Chart..............................................................................................246
Running MeasTCM...............................................................................................................246
Saving Apportionment Tables.................................................................................................247
Saving a Performance Model.................................................................................................247
Saving a Workload Apportionment Model...............................................................................248
Sorting Capacity History Data................................................................................................248
Uncalibrating Batch Response Time.........................................................................................249
Updating the Capacity History Database.................................................................................249
Updating the Capacity History Database With Selected CSV Files..............................................249
Using Online Help................................................................................................................250
Using TCM Expert to Generate an Apportionment Weights Table for CSV Files.............................250
Using the Consumption Model...............................................................................................251
Using the Process Category Audit (PCAT) Report.......................................................................252
Using the Planning Timeline Model.........................................................................................252
Viewing TCM Expert Parameters.............................................................................................253
Glossary..................................................................................................254
accelerated mode.................................................................................................................254
application..........................................................................................................................254
Apportionment Weights table.................................................................................................254
batch transaction..................................................................................................................254
Contents
9
Capacity Baseline.................................................................................................................254
Capacity History..................................................................................................................254
Category Demand report.......................................................................................................254
Consumption model..............................................................................................................254
CPU conversion factors..........................................................................................................254
custom folder.......................................................................................................................255
Disk Factors.........................................................................................................................255
distribution folder..................................................................................................................255
Distribution model.................................................................................................................255
Expert.................................................................................................................................255
MeasTCM............................................................................................................................255
MeasTCM control file............................................................................................................255
Measure..............................................................................................................................255
model.................................................................................................................................255
model set............................................................................................................................255
native mode.........................................................................................................................255
online transaction.................................................................................................................256
performance data sample......................................................................................................256
Planning Timeline model........................................................................................................256
PM model............................................................................................................................256
process category..................................................................................................................256
query transaction..................................................................................................................256
TCM...................................................................................................................................256
TCM parameters...................................................................................................................256
TNS mode...........................................................................................................................256
TNS-R native mode...............................................................................................................256
Transaction Count file............................................................................................................256
Transaction Count table.........................................................................................................257
WA model...........................................................................................................................257
workload apportionment.......................................................................................................257
Workload Summary..............................................................................................................257
Index.......................................................................................................258
10
Contents
About This Document
Tandem Capacity Model (TCM) is a host-based and workstation-based capacity management tool
that predicts the number of processors and logical disk volumes required for a well-tuned system,
and estimates the expected response time and transaction throughput for OLTP and batch
transactions. TCM works with MeasTCM. TCM uses data collected by Measure on HP NonStop
host systems and summarized by MeasTCM.
New TCM Features and Microsoft Excel 2010
Starting with SPR T6945H01^AAY and later, TCM supports Microsoft Excel 2010 in addition to
Microsoft Excel 2007 and 2003. This manual uses examples based on Microsoft Excel 2010, and
is also compatible with Microsoft Excel 2007 and 2003. (See Appendix C: “TCM Menus” (page 222)
for Excel 2003 examples.)
Enhancements
TCM and MeasTCM now includes these new features:
•
Support of new CPU types released after SPR T6945H01^AAX.
•
Support of SAS Disks released after SPR T6945H01^AAX.
•
Support for P9500 array.
•
Support for Solid state disks.
•
Support for OSS pathnames (MeasTCM only).
•
Support of Microsoft Excel 2010 in addition to 2007 and 2003.
•
Support of x86 and x64 versions of Microsoft Windows 7 and Windows Vista Operating
systems.
Considerations
•
Some of the TCM custom ribbon menus do not work when used with Excel 2007 on Microsoft
Windows 7 or Windows Vista. This Excel 2007 defect has been fixed with Microsoft Service
Pack 3, but this service pack is not available for Windows 7 or Windows Vista.
•
TCM based on Excel 2007 does not support the Quick Access toolbar. These functions can
be accessed with the customized Excel 2007 ribbons.
•
To access help from the help menu of TCM, install the required patch (depending on the system
hardware) as follows:
◦
Click the link http://support.microsoft.com/kb/917607.
◦
Locate Resolution section on the page, and choose the appropriate Windows help program
depending on the operating system installed.
◦
Validate the operating system installed.
–
◦
◦
Select the language, and click Continue.
Validation of operating system.
–
Click CONTINUE, and run the downloaded GenuineCheck.exe file to generate
the code.
–
Paste the generated code in the text box provided, and click VALIDATE.
Select the language, and click Download in the next screen.
New TCM Features and Microsoft Excel 2010
11
◦
Choose the file to download, depending on the operating system installed (32 or 64 bit),
and click Next.
◦
After the download is complete, run the downloaded file (.exe) to install the necessary
files in the system.
Supported Release Version Updates (RVUs)
This manual supports J06.03 and all subsequent J-series RVUs, H06.03 and all subsequent H-series
RVUs, and G06.14 and all subsequent G-series RVUs, until otherwise indicated in a replacement
publication.
Intended Audience
This manual can be used by capacity planners and system administrators to determine future
resource needs.
New and Changed Information
Changes to the 522695-010 Manual
Refer to Section : “New TCM Features and Microsoft Excel 2010” (page 11) for an overview of
the updates in this manual. Specific additions and changes are listed here:
•
Updated the template control file in the section “Customizing Your Process Category Control
File” (page 33).
•
Updated Table 2 (page 41) with new processor type, model, and NonStop product version.
•
Updated Table 3 (page 43) with new default values and processor models.
•
Updated the section “DISKCONVERTTO Entry” (page 45).
•
Updated the section “DISKFACTOR Entry” (page 47).
•
Added a Note after Table 5 (page 48).
•
Updated the screen shot of Figure 48 (page 151).
Changes to the 522695-009 Manual
Refer to Section : “New TCM Features and Microsoft Excel 2010” (page 11) for an overview of
the updates in this manual. Specific additions and changes are listed here:
12
•
Added the support for OSS pathnames feature in the section “Features and Functions”
(page 29).
•
Updated the template control file in the section “Customizing Your Process Category Control
File” (page 33).
•
Added SSDDISKFACTOR and ACTUALDISK50 in the section “Environmental Entries” (page 40).
•
Updated Table 2 (page 41) with new processor type, model, and NonStop product version.
•
Updated Table 3 (page 43) with new default values and processor models.
•
Updated Table 4 (page 45) with new SAS and SSD disks.
•
Added a note to the section “DISKCONVERTTO Entry” (page 45).
•
Added a section “SSDDISKFACTOR Entry” (page 46).
•
Updated Table 5 (page 48) with new SAS and SSD disks.
•
Added a section “ACTUALDISK50 Entry” (page 52).
•
Updated the section “ACTUALDISK52 Entry” (page 53).
•
Updated the screen shot of Figure 45 (page 142).
•
Updated the screen shot of Figure 46 (page 146).
•
Updated the screen shot of Figure 48 (page 151).
•
Updated the screen shot of Figure 49 (page 152).
•
Added a note to the Figure 49 (page 152).
•
Added Excel 2010 to Table 1 (page 25).
Changes to the 522695-008 Manual
•
Updated the “DISKCONVERTTO Entry” (page 45) to support XP disks partially.
•
Updated the “DISKCONVERTTO Entry” (page 45) to support SAS disks and added Table 4
(page 45), which lists the SAS disks.
•
Updated the “DISKFACTOR Entry” (page 47) to support SAS disks and XP disks (partially).
Changes to the 522695-007 Manual
•
Replaced most of the figures to show Excel 2007 screens and made the appropriate updates
to the descriptions.
•
Changed prequisite manuals under “Related Information” (page 17).
•
Indicated, under “Functions and Features” (page 18), that both single-core and multi-core
processors are supported.
•
Under “Understanding the Application” (page 21), changed UPDT to UPD.
•
Updated the file name of the MeasTCM softdoc under “Installing MeasTCM on the Host”
(page 26)
•
Added Excel 2007 and Windows 7 to Table 1 (page 25).
•
Updated the list of environmental entries in the CNTLFILE (see “Environmental Entries” (page 40))
•
Updated the list of CPUs under “CONVERTTO Entry” (page 41).
•
Updated the “CPUFACTOR Entry” (page 42).
•
Deleted the obsolete CLXTYPE entry.
•
Added the optional “NUMTMFTRAIL Entry” (page 45) to support multiple TMF audit trails.
•
Updated the “DISKCONVERTTO Entry” (page 45) to support SAS disks, HP XP disks, and
write cache enable.
•
Updated the “DISKFACTOR Entry” (page 47) to support SAS disks and HP XP disks and added
an example showing the CLIM controller type.
•
Added the “ACTUALDISK51 Entry” (page 52) for SAS disks associated with subtype 51.
•
Added the “ACTUALDISK52 Entry” (page 53) for HP XP disks associated with subtype 52.
•
Added new entries for OSS, SQLMP and SQLMX to Figure 8: PCAT Template File (page 56)
in Chapter 3.
•
Updated “TITLE Statements” (page 59) and the process category types and descriptions table.
Added new title entries for OSS, SQLMP and SQLMX category types.
•
Updated the Figure 44: “Capacity Baseline—Actual Screen” (page 139) in Chapter 9 and
modified its fields and their descriptions.
•
Updated the Figure 45: “Consumption Model” (page 142) in Chapter 9 and modified its fields
and their descriptions.
New and Changed Information
13
•
Updated the Figure 46: “Planning Timeline Model” (page 146) in Chapter 9 and and modified
its fields and their descriptions.
•
Updated the Figure 48: “CPU Factors Screen” (page 151) in Chapter 9 and updated text to
read that the rightmost column is read-only and displays the IPU count for multi-core processors.
•
Added new error messages and changed some existing error messages in Appendix B:
MeasTCM Error Messages (page 192).
Changes to the 522695-006 Manual
•
Supported release statements have been updated to include J-series RVUs.
•
Updated Template Control File under Customizing Your Process Category Control File.
•
Updated the list of CPUs under CONVERTTO Entry.
•
Updated the list of CPUs under CPUFACTOR Entry.
•
Updated the list of disk model numbers under DISKCONVERTTO Entry.
•
Updated the list of disk model numbers under DISKFACTOR Entry.
•
Added ACTUALDISK53 Entry as new example under DISKFACTOR Entry.
Changes to the 522695-004 Manual
The template control file has been updated and five new environmental entries have been described
in Chapter 3, Using MeasTCM.
Document Organization
This document is organized as follows:
Chapter 1: “Introduction”
gives an overview of the product.
Chapter 2: “TCM System Setup”
describes the system requirements for TCM and MeasTCM and describes the installation
procedures. The section also discusses version information and models.
Chapter 3: “Using MeasTCM”
discusses the product MeasTCM that provides an interface between Measure and TCM.
Chapter 4: “Getting Started With TCM”
provides some guidelines to help you start working with TCM. This chapter also describes the
TCM Initial menu, explains how TCM handles security issues, how to access TCM online help,
and how to load TCM models created by other users.
Chapter 5: “Creating a WA Model”
describes how to create a customized Workload Apportionment (WA) model for a new
application (or set of applications).
Chapter 6: “Creating a Performance Model”
describes how to create a Performance model (PM) for your application or a set of applications.
Chapter 7: “Modeling Batch Workloads”
describes batch transactions modeling and compares it with the performance model and WA
model.
Chapter 8: “Workload Apportionment Model”
describes the screens and menus of the WA model.
Chapter 9: “The Performance Model”
is used to answer the “what if” questions about the baseline sample data that has already been
computed in the WA model of TCM.
14
Chapter 10: “Using TCM Expert”
describes TCM Expert, which helps in capacity planning when you have limited knowledge of
application design or architecture.
Appendix A: “TCM File Names”A
lists the TCM file names and gives a brief description of the files.
Appendix B: “MeasTCM Error Messages”
lists MeasTCM error messages.
Appendix C: “TCM Menus”
lists the TCM items for the TCM WA and PM menus.
Appendix D: “TCM Response Time Formulas”
lists the TCM response time formulas.
Appendix E: “Common TCM Procedures”
contains step-by-step procedures for common TCM procedures.
Notation Conventions
General Syntax Notation
This list summarizes the notation conventions for syntax presentation in this manual.
UPPERCASE LETTERS
Uppercase letters indicate keywords and reserved words. Type these items exactly as shown.
Items not enclosed in brackets are required. For example:
MAXATTACH
Italic Letters
Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in
brackets are required. For example:
file-name
Computer Type
Computer type letters indicate:
•
C and Open System Services (OSS) keywords, commands, and reserved words. Type
these items exactly as shown. Items not enclosed in brackets are required. For example:
Use the cextdecs.h header file.
•
Text displayed by the computer. For example:
Last Logon: 14 May 2006, 08:02:23
•
A listing of computer code. For example
if (listen(sock, 1) < 0)
{
perror("Listen Error");
exit(-1);
}
Bold Text
Bold text in an example indicates user input typed at the terminal. For example:
ENTER RUN CODE
?123
CODE RECEIVED:
123.00
The user must press the Return key after typing the input.
Notation Conventions
15
[ ] Brackets
Brackets enclose optional syntax items. For example:
TERM [\system-name.]$terminal-name
INT[ERRUPTS]
A group of items enclosed in brackets is a list from which you can choose one item or none.
The items in the list can be arranged either vertically, with aligned brackets on each side of
the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For
example:
FC [ num ]
[ -num ]
[ text ]
K [ X | D ] address
{ } Braces
A group of items enclosed in braces is a list from which you are required to choose one item.
The items in the list can be arranged either vertically, with aligned braces on each side of the
list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example:
LISTOPENS PROCESS { $appl-mgr-name }
{ $process-name }
ALLOWSU { ON | OFF }
| Vertical Line
A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
For example:
INSPECT { OFF | ON | SAVEABEND }
… Ellipsis
An ellipsis immediately following a pair of brackets or braces indicates that you can repeat
the enclosed sequence of syntax items any number of times. For example:
M address [ , new-value ]…
- ] {0|1|2|3|4|5|6|7|8|9}…
An ellipsis immediately following a single syntax item indicates that you can repeat that syntax
item any number of times. For example:
"s-char…"
Punctuation
Parentheses, commas, semicolons, and other symbols not previously described must be typed
as shown. For example:
error := NEXTFILENAME ( file-name ) ;
LISTOPENS SU $process-name.#su-name
Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required
character that you must type as shown. For example:
"[" repetition-constant-list "]"
Item Spacing
Spaces shown between items are required unless one of the items is a punctuation symbol such
as a parenthesis or a comma. For example:
CALL STEPMOM ( process-id ) ;
If there is no space between two items, spaces are not permitted. In this example, no spaces
are permitted between the period and any other items:
$process-name.#su-name
16
Line Spacing
If the syntax of a command is too long to fit on a single line, each continuation line is indented
three spaces and is separated from the preceding line by a blank line. This spacing distinguishes
items in a continuation line from items in a vertical list of selections. For example:
ALTER [ / OUT file-spec / ] LINE
[ , attribute-spec ]…
Related Information
Before using this manual, you should be familiar with the information in these manuals:
•
Measure Reference Manual
•
The planning guide for your NonStop system
Publishing History
Part Number
Product Version
Publication Date
522695-002
TCM G06
August 2002
522695-003
TCM G06
December 2002
522695-004
TCM G06
August 2004
522695-006
TCM H01
August 2008
522695-007
TCM H01
February 2012
522695-008
TCM H01
August 2012
522695-009
TCM H01
August 2013
522695-010
TCM H01
August 2014
HP Encourages Your Comments
HP encourages your comments concerning this document. We are committed to providing
documentation that meets your needs. Send any errors found, suggestions for improvement, or
compliments to [email protected].
Include the document title, part number, and any comment, error found, or suggestion for
improvement you have concerning this document.
Related Information
17
1 Introduction
TCM is a workstation-based capacity planning tool for NonStop systems. Capacity planners can
use TCM to estimate future system performance from current data.
The TCM system is modeled in terms of transactions so that the results can be readily understood
by a wide audience. TCM uses data from the Measure product, a performance monitoring product
that runs on the HP NonStop system. Because Measure does not instrument transactions, TCM
helps you convert Measure data into transaction-oriented data. TCM then uses the
transaction-oriented data to predict performance for changing workloads and configurations.
TCM does the following:
•
Estimates the amount of hardware required to meet current and projected business needs
•
Predicts the performance of user applications
•
Forecasts the maximum capacity of your current systems
TCM and Related Products
TCM works with the Measure and MeasTCM HP products. TCM uses data collected by Measure
on the NonStop host system and summarized by MeasTCM. For detailed information about Measure,
consult the Measure Reference Manual. For detailed information about how to use MeasTCM, see
Chapter 3: “Using MeasTCM”.
TCM includes MeasTCM and the workstation-based TCM software. For a complete list of the
hardware and software required to run TCM, see the SOFTDOC file.
Functions and Features
You can use TCM to:
•
Translate process-oriented performance data from MeasTCM into transaction-oriented
performance data.
This process, known as workload apportionment, is a major aspect of capacity planning for
HP NonStop systems.
•
•
Predict the following usage:
◦
Number of CPUs
◦
Number of logical disk volumes
◦
Average and percentile host response times for OLTP transactions and average response
times for batch transactions
◦
Online CPU utilization for both single-core and multi-core processors
◦
Disk utilization
Archive and organize historical performance data.
This feature helps the capacity planner in many crucial activities, such as model validation,
sample selection, and trend analysis.
18
•
Predict future transaction throughput based on historical information.
•
Answer what-if questions regarding apportioned baseline data; estimated throughputs; host
response times; and the number of processors, disks, or both for various user-defined scenarios.
•
Generate charts to aid in decision making and the presentation of capacity management
alternatives and recommendations.
Introduction
Assumptions
To keep TCM simple and easy to use, TCM is based on the following assumptions:
•
Your HP NonStop system is well-tuned. (You can tune your HP NonStop systems by using the
Guardian Performance Analyzer, HP product number T6942.) If the system is not well-tuned,
response times might be higher than expected, more CPUs or disks might be necessary to
support predicted workloads, or both.
•
TCM computes only the CPU and disk components of response time. It does not compute
end-to-end response time, which includes communication line time.
•
TCM does not model memory, disk controllers, or disk space, and it is assumed that none of
these would cause a performance problem.
•
TCM is not intended as a configuration or system resource manager.
•
If an HP NonStop Transaction Management Facility (TMF) audit volume exists, TCM assumes
that the audit disks do not have any application data residing on them and TMF activity will
be distributed equally among the audit volumes.
NOTE: Because of the sensitivity of the HP NonStop SQL/MP optimizer to such database attributes
as demographics and selectivity, use caution in modeling SQL applications using TCM. Access
plans might change as the application’s database grows. However, TCM accurately models SQL
applications under most conditions.
Caveat
Sometimes, if the actual and the planned systems are different processor types, the mileage might
vary depending on the situation or application. The processor speed factors are based on the
Order Entry internal benchmark. This benchmark has shown excellent correlation for a variety of
capacity planning situations for a large number of customers, but some particular situations might
scale differently.
The recommendation that TCM provides is a starting point only. Capacity planners need to analyze
their own system environment and budgetary constraints for a definitive solution.
Architecture and Components
The overall architecture of TCM appears in Figure 1 (page 20). On the NonStop host system, you
use Measure to collect performance samples on your application and then analyze and aggregate
the data provided by Measure using MeasTCM. MeasTCM provides process category data used
by TCM on the workstation and creates downloadable files that detail the process category activities
of your application.
TCM has two major components:
•
Workload Apportionment (WA) model
The WA model is used to apportion the process-oriented performance data collected and
summarized on the NonStop host system through Measure and MeasTCM into
transaction-oriented CPU and disk demands. The WA model also maintains a Capacity History
database of performance information. It requires the data supplied by MeasTCM.
•
Performance model
The Performance model is used to answer what-if questions regarding the transaction information
that was computed by the WA model. It enables you to pose questions about the behavior of
system performance factors, such as response time, average CPU utilization, and average
disk utilization, under increasing transaction rates.
You often have a number of options regarding the system’s response to increased workload.
For example, you can add hardware to reduce CPU utilization and improve response time,
or you can leave hardware unchanged and tolerate longer response times.
Architecture and Components
19
With the Performance model, you can explore possibilities by imposing constraints on the
modeling process. You can impose constraints on either hardware configuration or performance
factors. For instance, you can ask what will happen to response time if the average transaction
rate doubles but the hardware configuration remains the same. Or you can ask what is the
lowest-cost combination of CPUs and disk drives that will maintain an average response time
below two seconds.
The Performance model generates presentation-quality charts of forecasted throughputs and
host response times.
Figure 1 TCM Architecture
TCM User Levels
TCM is designed for users who are familiar with capacity planning methodology and techniques:
•
Capacity planners
Capacity planners have a good understanding of capacity planning in general, but they might
not thoroughly understand its application to HP NonStop systems. Planners define and analyze
alternative capacity management approaches and have access to the basic TCM commands
necessary to perform these tasks.
They establish explicit performance objectives for each category of work and periodically
make predictions of how various workloads will grow. Capacity planners assess upgrade
alternatives and recommend the best upgrade alternative.
•
TCM administrators
TCM administrators have knowledge of capacity planning on HP NonStop systems as well as
a thorough understanding of the application under study. TCM administrators define and
20
Introduction
check workload apportionment methods that translate process-oriented performance data into
transaction demands. In addition to the basic TCM functions, TCM administrators have access
to the TCM administrative functions and can directly modify more data in the models than
capacity planners.
•
Super users
Super users can do everything that TCM administrators can do, and they also have the authority
to resecure the model to gain access to all fields within TCM. Super users need to understand
the internal operation of TCM and must have a good knowledge of Excel.
The TCM functions performed by TCM administrators and super users are passwordprotected. For
information about TCM security, see “Security” (page 69).
TCM and the Capacity Planning Process
This section describes how TCM fits into the capacity planning process.
The
1.
2.
3.
4.
5.
6.
7.
seven main steps in the capacity planning process are:
“Understanding the Application” (page 21)
“Tuning the System” (page 22)
“Collecting Performance Data” (page 22)
“Apportioning Performance Data” (page 23)
“Checking an Apportionment Method” (page 23)
“Performing What-If Analyses” (page 23)
“Reporting Results” (page 24)
Understanding the Application
To begin the capacity planning process with TCM, you must understand the application.
The capacity planner must have good knowledge of the structure of the application to be modeled,
including an understanding of the major transactions involved and how they flow through the
application. Develop a process flow diagram for each transaction and apportionment methods for
relating process category information (collected on the NonStop host system) to transaction
information.
If you have a limited knowledge of the application architecture, use TCM Expert to create the
workload apportionment weights portion of the WA model automatically.
To analyze your HP NonStop system configuration and application:
1. Identify major transactions as batch, OLTP, or query.
2.
3.
4.
•
A batch transaction is a workload that processes several transactions at once. Batch
transactions have the following characteristics: long job duration, low priority, significant
disk activity, little or no terminal interaction, and work within a closed system.
•
An OLTP transaction is a method of processing transactions in which entered transactions
are immediately applied to the database. The information within the database is readily
available to all users through online screens and printed reports. They occur randomly,
often generated by a multitude of users. Generally, OLTP transactions require only modest
CPU and disk resource consumption per transaction.
•
A query transaction is one that is modeled as a batch or online transaction, depending
on the CPU demand of the query transaction. Large demand queries are modeled as
batch. Small demand queries are modeled as OLTP.
Draw a process flow diagram for each major transaction.
Combine the process flow diagrams into one system-level flow diagram.
Design the model.
TCM and the Capacity Planning Process
21
Figure 2 (page 22) shows a system-level process flow diagram for a sample application. Each
oval in the figure represents a process category. This application has four transactions: standard
(ST1), inquiry (INQ), big (BIG), and update (UPD). The application is described in the following
list:
•
The server classes for each of the transaction types are ST1, INQ, BIG, and UPD.
•
The terminal control process (TCP) for ST1 is ST1_TCP. For INQ, BIG, and UPD, it is ST2_TCP.
•
The line handler for ST1 is ST1_SIM. For INQ, BIG, and UPD, it is ST2_SIM.
•
All four transactions share the same disks. DISK is the aggregation of all the disk processes
in the system.
Figure 2 System-Level Process Flow Diagram of a Sample Application
Tuning the System
The second step in the capacity planning process is tuning the system.
Before the hardware requirements of the system can be accurately predicted, you must tune the
system software bottlenecks. You might want to use the Guardian Performance Analyzer (GPA) as
an aid for tuning your system. For more information on tuning, see the Guardian Performance
Analyzer (GPA) Manual and the Measure Reference Manual.
Collecting Performance Data
The third step in the capacity planning process is collecting performance data.
Performance data must be collected on the NonStop host system using Measure on each node on
which the application runs. The samples are summarized by MeasTCM for use with TCM.
Use Measure to take measurement and performance samples of your application. Samples should
have different transaction mixes and varying utilization, including peak periods. Be sure to collect
enough samples of your application so that TCM can accurately model your application. The
recommended number of samples is at least four to five times the number of defined transactions,
especially if you intend to use the Expert features of TCM to automatically apportion data. For
example, if your application has three transactions named Withdrawal, Deposit, and Customer
Update, you should collect at least 12 to 15 samples with different transaction mixes and at varying
utilization levels.
22
Introduction
Use MeasTCM to aggregate and analyze the samples into process category data in the form of
comma separated values (CSV) files. When you are finished collecting performance data, download
the CSV files created by MeasTCM to the custom folder on your workstation. For information about
MeasTCM, see Chapter 3: “Using MeasTCM”.
Apportioning Performance Data
The fourth step in the capacity planning process is apportioning performance data.
Typically, a TCM administrator translates the capacity planner’s apportionment methods into TCM
using the apportionment tables in the WA model. Chapter 5: “Creating a WA Model”, provides
instructions for each step.
To apportion performance data:
1. Create a new WA model and load the CSV file into the Workload Apportionment model.
(See “WA Model Flowchart” (page 76).)
2. Modify an Apportionment Weights Table (see “Modifying the Apportionment Weights Table”
(page 77)) and a Transaction Count Table (see “Modifying the Transaction Count Table”
(page 78)) for your application.
3. Update the capacity history database with this sample. To update the Capacity History
database, select History > Update History.
4. Update capacity history database for each CSV file downloaded. (See “Load Category Data
(F3)” (page 127)).
Checking an Apportionment Method
The fifth step in the capacity planning process is checking an apportionment method.
To ensure the accuracy of the TCM modeling results, you must examine the reasonableness of both
the performance data sample and the method used to apportion this data. Selecting an appropriate
method involves collecting and apportioning multiple performance samples and then analyzing
the results.
To check the workload apportionment model of your application, compare your results from all
samples by reviewing the Capacity History file. In general, an Apportionment Weights table can
be viewed as reasonable if CPU and disk demands per transaction are relatively constant across
many performance samples with varying transaction mixes and throughput levels. The requirement
for a variety of transaction mixes is crucial. If mixes do not vary, any apportionment method will
appear to be reasonable but might not be.
If your model is not reasonable, you need to collect performance data again or redesign your
Apportionment Weights or Transaction Count tables. For more information, see “Collecting Measure
Samples” (page 30), “Modifying Apportioned Data Using an .AWA File Not in the Current Session”
(page 243), and “Modifying the Transaction Count Table” (page 78).
If you use TCM Expert to generate a Workload Apportionment Weights table and to update the
History file, TCM Expert will check for inconsistent transaction costs in the History file. For more
information about TCM Expert, see Chapter 10: “Using TCM Expert”.
Performing What-If Analyses
The sixth step in the capacity planning process is performing what-if analyses.
Once you select a representative performance sample, you can use the TCM Performance model
to answer what-if questions such as estimated throughputs, host response times, and the number
of processors and disks required for different userdefined scenarios.
Select a representative Workload Apportionment model, also called a baseline, to use with the
Performance model. You can also use TCM Expert to pick the most representative CSV sample and
to load that sample into the Performance model automatically.
TCM and the Capacity Planning Process
23
Use TCM to:
•
Load the baseline into the Performance model
•
Modify scenarios and make projections
•
Create charts of possible scenarios
Reporting Results
The final step in the capacity planning process is reporting the results.
Once you have determined the system resource needs, report the results to management. TCM
helps you create a capacity plan using your Performance model projections and presentation-quality
charts that are easy to read and understand.
24
Introduction
2 TCM System Setup
This chapter describes the system requirements for TCM and MeasTCM, provides installation
procedures, explains how to find version information, discusses how TCM converts models from
earlier TCM versions, and describes how to load models from other directories.
System Requirements
Before you begin using MeasTCM and TCM, make sure that you have the system requirements
shown in Table 1 (page 25).
NOTE: Required product versions of the host and PC software can change frequently, so see the
latest softdoc for the most recent product version information.
Table 1 System Requirements
Component
Requirements
MeasTCM
Any NonStop system running the NonStop Kernel operating system. See the softdoc for the
specific product version.
The Measure product.
The FastSort product.
TCM
Host file exchange facility (any method for transferring files from the NonStop host system to
the PC).
Standard requirements for running Microsoft Excel 2010/2007/2003, based on the Windows
95, 98, NT, 2000, XP, Vista (X86 and X64 bit) or Windows 7 (X86 and X64 bit) operating
systems. For specific hardware and software requirements, consult the Microsoft Excel
documentation.
Recommended for the
PC
Additional memory to allow for larger TCM models and improved performance.
A fast processor to increase the speed of calculations performed by TCM
Installation Overview
For detailed and updated installation instructions, see the README file on the installation subvolume
(ISV). Figure 3 (page 26) shows what you need to install on the HP system and the workstation to
use TCM.
System Requirements
25
Figure 3 Installing TCM Flowchart
Installing MeasTCM on the Host
Install MeasTCM software files from the SUT. The MeasTCM installation subvolume uses about 175
KB of disk space.
When you restore MeasTCM files from the SUT, the following files are located in the ISV:
File name
Description
CNTLFILE
Template control file
MEASTCM
MeasTCM program
T6042ABE
MeasTCM softdoc
Installing TCM on the PC
The instructions in this manual assume that your folder is named TCM. If you have given it another
name, replace that with the correct folder name.
1. Make sure you have the correct versions of Microsoft Excel and Windows installed on your
PC. For version information about an application, select Help About. For updated version
26
TCM System Setup
2.
3.
4.
requirements, see the latest TCM softdoc. If necessary, follow the procedures described in the
application documentation to install the correct version of Windows, and Excel, or both.
To determine whether you need to download any other files, see the README file on the ISV.
Download any necessary files.
If you have an earlier version of TCM installed on your PC, delete the TCM application files
or put them in a different folder. Only one folder for TCM is allowed on a workstation.
Log on to the host as you would normally and make the TCM ISV your current subvolume by
entering:
1> VOLUME TCM-ISV-name
5.
If you do not already have one, create a folder named TCM on your workstation and open
it.
For more information on how to create a folder, see the online help for your PC operating
system.
6.
Download the file TCM7EXE as TCM7.EXE to the TCM folder.
If you have a network connection to the NonStop host system, you can copy a network file
by dragging the TCM7EXE file from the host drive to the PC drive.
If you use FTP to transfer the file, remember that TCM7EXE is a binary file.
7.
8.
9.
Run TCM7.EXE to extract the files.
Create a shortcut to the TCM.XLSM file.
Optionally, use the Properties feature to change the associated icon to TCM.ICO, which resides
in the TCM distribution folder.
10. To save disk space, you can delete the file TCM.EXE. TCM does not need it.
11. To run TCM, double-click the TCM shortcut you created in Step 8.
Finding Version Information
You can use the Excel macro VPROC.XLAM to get the version information about any TCM file.
VPROC.XLAM is included in your TCM folder.
To use VPROC:
1. Run VPROC.XLAM.
2. Enter the name of the file.
3. VPROC responds with the version of TCM.
4. Click OK to close the dialog.
NOTE:
TCM.EXE, TCM.XLS, VPROC.XLA are the corresponding files in TCM 2003.
Converting TCM Models From Earlier TCM Product Versions
NOTE:
•
Models generated using previous versions of TCM cannot be imported to the new version of
TCM (from SPR TCM:T6945H01^AAY and later versions), as the Excel template itself differs.
•
Models generated using the Excel 2003 versions of TCM cannot be used with the Excel 2007
version of TCM due to Excel incompatibility.
If you open a file created with an older product version of TCM, an alert message notifies you of
the product version mismatch. For the nonperformance models, TCM automatically converts the
file and then renames the older file by replacing the first letter of the file name with an underscore
( _ ).
Finding Version Information
27
For example, the original file bank.HST is renamed _ank.HST, and the converted file is now named
bank.HST. A Microsoft Excel dialog box shows when the conversion is done.
•
The Performance Models (the .SPM and .WPM files) created by pre-G06 TCM product versions
will not open (the Work with an Existing Model of the TCM Initial menu) in G06 TCM. To
migrate these old Performance Models to this RVU:
1. Select TCM Initial Create a new Performance Model.
2. Create the new Performance Model from the corresponding Workload Apportionment
model (.WWA file), or the CSV file and the Apportionment Method (.AWA file).
•
The charts created in the pre-G06 product versions will not open in G06 TCM through the
Open option of the File menu. To regenerate these charts, use the Create Timeline Chart option
in the Chart menu of the TCM toolbar. Also, from the TCM G06 onwards, the charts are saved
along with the model, so saving the charts as a *.CPM file is no longer an option.
Loading Models From Other Folders
If you need to load a TCM model created by another user, or if you have renamed your distribution
or custom folder do not open the Workload Apportionment model (.WWA file) or the Performance
Model (.WPM file) as you would normally do.
The .WWA and WPM files are pointer files containing path names, and these files become invalid
when folder names or paths change.
To open a TCM model after such a change, use the .SWA or .SPM files the first time. Once you
open a .SWA or .SPM file, its new .WWA or .WPM file is created, and you can once again work
with the pointer files.
Other workspace files, such as .HST or .AWA files, can be opened as part of your normal session
activities and require no special handling.
To load a TCM model created in another folder:
1. From the “TCM Initial Menu” (page 67), select Work with an Existing WA Model or Work
with an Existing Performance Model and then click OK.
The Open PM Model or Open WA Model dialog box appears.
2.
3.
4.
5.
28
To view all possible Workload Apportionment models, type *.SWA in the Model to Open
field. Type *.SPM to see all possible Performance models.
Choose a file from the list or type the name of the file you want to open, including its .SWA
or .SPM extension.
Click OK. TCM loads the model file (rather than the Excel workspace file).
Click File Save to resave the model.
TCM System Setup
3 Using MeasTCM
MeasTCM provides the interface between Measure on the NonStop host system and TCM on your
workstation. Running under TACL on the NonStop host system, MeasTCM summarizes and
categorizes the performance data collected by Measure and formats it for use by TCM.
MeasTCM reduces Measure performance data to a manageable form for capacity planning.
Typically, MeasTCM reduces a Measure data file to just a few kilobytes—a size that contains all
the performance data required by TCM.
Features and Functions
MeasTCM does the following:
•
Determines the amount of CPU and disk activity that each process category consumes and
computes the average priority of each process category.
Using the CPU, Process, DISC, and DISCOPEN entities of Measure, MeasTCM calculates the
amount of CPU and physical disk activity and the number of cache hits and misses for each
collection of processes in a category. MeasTCM then summarizes process-related and
disk-related Measure performance data into a small number of process categories.
•
Summarizes performance data from multiple Measure sessions, or multiple HP nodes, or both.
MeasTCM accepts input from up to 10 Measure data files and summarizes that data into one
file for use by TCM. This feature is particularly useful for applications that span HP nodes via
HP wide area networks (WANs).
•
Ensures that all sample data is allocated to the appropriate process categories in such a way
that no data is omitted or counted twice.
•
Creates a CSV file or files for use by TCM that will be downloaded to the workstation.
•
Documents the results of MeasTCM processing.
•
From SPR T6042H01^ABE onwards, OSS pathnames are supported in the audit trail report.
MeasTCM is capable of providing OSS pathnames in the audit document instead of the OSS
file — equivalent Guardian names for those files for which OSS journals are specified.
If the measurement is taken on one system and analyzed on the other system, an OSS journal
must be present to map the OSS pathnames. Therefore, to enable the OSS journals wherever
OSS pathnames are specified, use the command START MEASUREMENT <DATAFILENAME>,
OSS. If OSS journals are not available, relevant message is displayed at the home terminal.
Components and Architecture
The major components of MeasTCM are:
•
MeasTCM program
This program launches MeasTCM, which is a single COBOL85 program.
•
MeasTCM control file
This file contains all the parameters of the current MeasTCM session. A template file called
CNTLFILE is provided for your customization.
The overall architecture of MeasTCM appears in Figure 4 (page 30). The diagram shows that
MeasTCM uses its control file and one or more Measure data files to create one or more CSV files
of process category for use by TCM on the workstation. CSV (comma separated values) is a
standard file format for Microsoft Excel files.
Features and Functions
29
Figure 4 MeasTCM Architecture
MeasTCM Procedures
To use MeasTCM:
1. Collect the Measure samples.
2. Draw a process flow diagram for your application.
3. Customize the MeasTCM control file.
4. Run MeasTCM to create the CSV file or files.
Collecting Measure Samples
For MeasTCM to extract and summarize Measure data, the Measure sample data must meet these
requirements:
•
Data must be collected using a currently supported version of Measure.
•
All CPU, DISC, PROCESS, and DISCOPEN entities must be collected for each system being
studied. If all of your performance data is contained in one Measure file, for example, these
MeasCOM commands would be needed to configure Measure:
1>
1+
2+
3+
4+
30
MEASCOM
ADD CPU *
ADD DISC *
ADD PROCESS *
ADD DISCOPEN *
•
If multiple Measure samples are used, they must have the same time boundaries for the time
window you set when configuring MeasTCM.
•
Intervals are not required for Measure samples, but they are recommended. The CSVLO and
CSVHI entries define the time window used to filter the data in all the specified Measure files.
If you do not supply one or both of these times, MeasTCM determines an appropriate time
based on the actual start and stop times of the input Measure data files.
Using MeasTCM
•
If you are modeling a batch job that runs when the online transaction application is running
at a lower throughput or is shut down, create two models:
◦
One model for the online transaction application during its peak period
◦
One model for the batch job
•
If you are modeling a batch job that runs at the same time as the peak period for the online
transaction application, the Measure sample should include all of the batch run and exclude
the online transaction application startup and shutdown.
•
Because checking an apportionment method for reasonableness requires several performance
samples, collect at least 4 or 5 samples for each type of transaction. For example, if your
application has 3 transactions (Withdrawal, Deposit, and Update), collect at least 12 to 15
samples.
The samples you collect should be independent of one another. Thus, the samples should have
varying transaction mixes. To get independent samples, you might have to take several
measurements. For instance, to get 12 independent samples, you might have to take 12
one-hour intervals over a 12-hour period. For other applications, you might take measurements
at the same time but over a 12-day period to get 12 independent samples.
In an automated teller machine (ATM) application, for example, you will get different transaction
mixes on a traditional payday (such as the 1st or 16th of the month) versus other days. You
would also get a different transaction mix on a Friday when customers want to withdraw
money for the weekend or on the day before a holiday.
For more information, see the Measure Reference Manual.
Drawing a Process Flow Diagram
The primary function of MeasTCM is to extract and summarize the raw performance data in the
Measure files into process categories for use by TCM in capacity planning. Process categories
represent summarized performance data for any collection of the CPU, PROCESS, DISC, and
DISCOPEN entities that satisfy certain user-specified rules. The rules that define process categories
are contained in the MeasTCM control file.
The concept of process categories is essential to understanding workload apportionment. A process
category is a group of processes whose workload demand values are linked to common processes,
such as a disk process category, a TMF process category, or a server class category. By using
process categories, MeasTCM compresses data by a significant factor. For example, a 14-megabyte
Measure file can be reduced to approximately 2 kilobytes of downloadable data. To understand
how to best create process categories, it is helpful to understand that TCM converts this process
category information to transaction information.
The workload associated with all processes in a category is divided among the transactions.
Categories reduce the number of entities the workload apportionment functions must deal with.
Figure 5 (page 32) shows a simplified picture of the workload apportionment process. In the
workload apportionment process, processes are allocated to transactions.
Drawing a Process Flow Diagram
31
Figure 5 From Process Categories to Transactions
You download the MeasTCM results into the WA model. During the workload apportionment
processing, TCM divides categories into units that are allocated to transactions. After the workload
apportionment process is complete, each transaction has a value for CPU seconds and disk seconds.
If you obtain consistent CPU and disk seconds from the WA model for several Measure samples
with a variety of transaction mixes, you have a reasonable WA model.
You can use a process flow diagram to define the categories and to customize your control file.
Figure 6 (page 33) shows a system-level process flow diagram for a sample application. Each
oval in the figure represents a process category. This application has four transaction types: standard
(ST1), inquiry (INQ), update (UPD), and BIG. The application is described in the following list:
32
•
The server classes for each of the transaction types are ST1, INQ, BIG, and UPD.
•
The terminal control process (TCP) for ST1 is ST1_TCP. For INQ, BIG, and UPD, it is ST2_TCP.
•
The line handler for ST1 is ST1_LH. For INQ, BIG, and UPD, it is ST2_LH.
•
All four transactions share the same disks. DISK is the aggregation of all the disk processes
in the system.
Using MeasTCM
Figure 6 System-Level Process Flow Diagram of a Sample Application
Processes in a category must not only recognize the same set of transaction types but also expend
roughly the same proportion of effort on the transaction types they recognize. For example, suppose
a requester and a server class processes T-1 and T- 2 (and no other types), and the requester
expends twice as many CPU seconds on T-1 as T-2, but the ratio in the server class is 3:1. These
process groups must be in separate categories.
When you draw your process flow diagrams:
•
Use a separate set of arrows for each transaction type.
•
The arrow points to a server.
•
Application disk processes are lumped together.
•
Ignore TMF activity.
Customizing Your Process Category Control File
You must now translate the process flow diagram into process category (PCAT) statements for
MeasTCM. A template of the Process Category Control File (CNTLFILE) is available in the MeasTCM
installation subvolume (ZMEASTCM). To define the process categories for your Measure data,
copy the template control file to your working subvolume and edit the file according to your
application needs.
Figure 7 (page 34) shows the template CNTLFILE. Each section of the template CNTLFILE is described
following the figure.
Customizing Your Process Category Control File
33
Figure 7 Template Control File
! CNTLFILE T6042H01^ABE (22AUG14)
! This is a sample MeasTCM control file which defines MeasTCM
! processing requirements. This file must be modified to
! include actual data before it can be used.
!
!***********************************************************************
! Syntax for environmental entries
! -------------------------------!
! MEASURE data-file [measfh]
!
!
where: data-file
a disk file containing measurement data
!
measfh
the name of an object file containing a MEASFH
!
program; the default is the current
!
$SYSTEM.SYSnn.MEASFH.
!
! CSVLO yyyy/mm/dd;hh:mm:ss
! CSVHI yyyy/mm/dd;hh:mm:ss
!
!
these entries define the time window used to filter the data in
!
all the specified MEASURE files.
!
! APPL application
!
!
where: application the name of the application for the MEASURE
!
data sample (max 20 characters); this is a
!
required entry.
!
! CONVERTTO t u
!
!
where: t
the output CPU type; this entry is required
!
when the measurement data file(s) contain(s)
!
different CPU types.
!
Allowed values are: NSE-AD,NSE-AB(2-CORE),NSE-AB(4-CORE),
!
NSE-AB,NSE-AF(2-CORE,NSE-AF(4-CORE,NSE-AF,NSE-AG,NSE-AH,NSE-M,
!
NSE-W,NSE-S,NSE-K,NSE-I,NSE-T,NSE-Q,NSE-A,NSE-B,NSE-D,NSR-Z,
!
NSR-H,NSR-Y,NSR-X,NSR-V,NSR-J,NSR-E,NSR-D,NSR-T,NSR-G,NSR-W
!
!
u
the output NSK version; this entry is required
!
when t (first parameter of CONVERTTO) is
!
different from the CPU type(s) contained in
!
the measurement data file(s).
!
Allowed values (as per TCM) are as follows :
!
Value of t
Corresp. value(s) of u
!
------------------------------!
NSE-AD
J06
!
NSE-AB(2-CORE)
J06
!
NSE-AB(4-CORE)
J06
!
NSE-AF(2-CORE)
J06
!
NSE-AF(4-CORE)
J06
!
NSE-AF
J06
!
NSE-AG
J06
!
NSE-AH
J06
!
NSE-AB
J06
!
NSE-AE
J06
!
NSE-M
J06
!
NSE-W
J06
!
NSE-S
H06
!
NSE-K
H06
!
NSE-I
H06
!
NSE-T
H06
!
NSE-Q
H06
!
NSE-A
H06
!
NSE-B
H06
!
NSE-D
H06
!
NSR-Z
G06
!
NSR-H
G06
!
NSR-Y
G06
!
NSR-X
G06
!
NSR-V
G06
!
NSR-J
G06
!
NSR-E
G06
!
NSR-D
G06
!
NSR-T
G06
!
NSR-G
G06, G05, G03, G02
!
NSR-W
G05, G03, G02
!
! CPUFACTOR t [r] xxxx.yy s [i]
34
Using MeasTCM
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
where: t
the CPU type for which the default
conversion factor will be overriden.
Allowed values are: NSR-W,NSR-G,NSR-T,NSR-D,
NSR-E,NSR-J,NSR-V,NSR-X,NSR-H,NSR-Y,NSR-Z,NSE-A,
NSE-D,NSE-B,NSE-Q,NSE-T,NSE-K,NSE-I,NSE-S,NSE-M,
NSE-W,NSE-AD,NSE-AB(2-CORE),NSE-AB(4-CORE)/NSE-AB,
NSE-AE,NSE-AF(2-CORE),NSE-AF(4-CORE),NSE-AF,NSE-AG,
NSE-AH.
[r]
the OS release level,G H or J.
This is optional. The default is G.
xxxx.yy
the new conversion factor for CPU type t;
this is a positive number between 0001.00 and
9999.99.
s
[i]
Type,Subtype of the CPU.
this is required only for new CPU type.Type,subtype
is not overridden for existing CPUs.
Both Type and Subtype are numeric values
separated by the delimiter ','.
IPU Count of the CPU type t;
this is applicable only for multi-core CPUs.
CSVDATA data-file
The CSVDATA <name> is a string that contains the first 5 characters
of the CSV file(s) to be downloaded to the workstation. If the CSVDATA
keyword is not specified, the default is CSVDA in the current volume and
subvolume. For example, if the entry is CSVDATA ABCDE, the CSV data files
produced will be named ABCDE001, ABCDE002, and so on.
REPORT $a[.#b[.c]]
if this entry is present, a process category audit report will be
generated and sent to the spooler collector/location specified.
NUMCSVS *|ALL|n
This entry identifies the number of CSV data files to be generated.
This entry is not required. If not specified, the default is value 1.
If the parameter value is "*" or "ALL", the maximum number of CSV data
files will be generated. If the parameter value is n - an integer, n
number of CSV data files will be generated provided n does not exceed
the maximum number of files possible.
DISKCONVERTTO m [w] [p]
where: m
[w]
the output disk model number. This entry is required
when the measurement data file(s) contain(s)
different Disk subtypes.
Allowed values are: 4160,4170,4230,4240,4250,4255,
4260,4265,4330,4500,4510,4560,4570,4580,4590,4604,
4608,4609,4618,4619,4636,4637,4638,4672,BF07255B2C,
BF0725754B,BF07258243,BF14658244,46144,BF0725A476,
BF1465A477,BF3005A478, BF072D6186, BF146DA47C,
BF300DA482,BF450DA483, BF072DAJZN, BF146DAJZP,
BF300DAJZQ,BF450DAJZR, BF600DAJZT, BF036574C9,
BF07258222,BF14658227, BF0725A692, BF1465A693,
BF146DA47A,BF300DA47B, BF300D6188, BF450D6189,
BF300DASTH,BF450DASTK, BF600DASTL,DG072BB975,
DH072BB978,DG0146BAHZP,DG0300BAHZQ,DG0146BALVN,
DG0300BALVP,DG0146FAMWL,EG0146FAWHU,DG0300FAMWN,
EG0300FAWHV,DH0072BALWL,DH0146BALWN,DH0072FAQRD,
EH0072FAWJA,DH0146FAQRE,EH0146FAWJB,DG072BAAJA,
DG146BAAJB,DG0146BAMYQ,DG0300BAMYR,DG0146FARVU,
DG0300FARVV,EG0146FAWJC,EG0300FAWJD,EH0072FARWC,
EH0146FARWD,EG0300FBDBR,EG0600FBDBU,DH072BAAKN,
DG072BABCE,DG146BABCF,DG0146BARTP,DG0300BARTQ,
EG0146FARTR,EG0300FARTT,EH0072FARUA,EH0146FARUB,
EG0300FBDSP,EG0600FBDSR,DG146BB976,EG0900FBLSK,
EG0900FCHHV,EG0600FBLSH,EG0600FCHHU,EH0300FBQDD,
EG0300FCHHR,EG0300FBLSE,EG0300FBVFL,EG0300FBQDD,
EH0300FCBVC,EH0146FBQDC,EH0146FCBV,EH0146FCBVB,
EH0146FAWJB,EO0200FBRVV.
is an optional field and is only for SAS and SSD disk types,
Customizing Your Process Category Control File
35
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
36
valid values can be ON/OFF. By default value will be
OFF.
[p]
is the number of partitions in the disk. Valid values
are 1 to 8. This is an optional entry. Default value is 1.
DISKFACTOR m r c s readseek [write seek]
where: m
the disk model number for which the default RPM,
controller type of the disk will be overridden.
Allowed values are: 4160,4170,4230,4240,4250,4255,
4260,4265,4330,4500,4510,4560,4570,4580,4590,4604,
4608,4609,4618,4619,4636,4637,4638,4672,BF07255B2C,
BF0725754B,BF07258243,BF14658244,46144,BF0725A476,
BF1465A477,BF3005A478, BF072D6186, BF146DA47C,
BF300DA482,BF450DA483, BF072DAJZN, BF146DAJZP,
BF300DAJZQ,BF450DAJZR, BF600DAJZT, BF036574C9,
BF07258222,BF14658227, BF0725A692, BF1465A693,
BF146DA47A,BF300DA47B, BF300D6188, BF450D6189,
BF300DASTH,BF450DASTK, BF600DASTL,DG072BB975,
DH072BB978,DG0146BAHZP,DG0300BAHZQ,DG0146BALVN,
DG0300BALVP,DG0146FAMWL,EG0146FAWHU,DG0300FAMWN,
EG0300FAWHV,DH0072BALWL,DH0146BALWN,DH0072FAQRD,
EH0072FAWJA,DH0146FAQRE,EH0146FAWJB,DG072BAAJA,
DG146BAAJB,DG0146BAMYQ,DG0300BAMYR,DG0146FARVU,
DG0300FARVV,EG0146FAWJC,EG0300FAWJD,EH0072FARWC,
EH0146FARWD,EG0300FBDBR,EG0600FBDBU,DH072BAAKN,
DG072BABCE,DG146BABCF,DG0146BARTP,DG0300BARTQ,
EG0146FARTR,EG0300FARTT,EH0072FARUA,EH0146FARUB,
EG0300FBDSP,EG0600FBDSR,DG146BB976,EG0900FBLSK,
EG0900FCHHV,EG0600FBLSH,EG0600FCHHU,EH0300FBQDD,
EG0300FCHHR,EG0300FBLSE,EG0300FBVFL,EG0300FBQDD,
EH0300FCBVC,EH0146FBQDC,EH0146FCBV,EH0146FCBVB,
EH0146FAWJB.
Note: Apart from above overridden disk model numbers,
five new (extra) disk model numbers can be entered.
r
the RPM value of a disk; this is a positive
number between 00001 and 99999 of format xxxxx.
c
the disk controller type.
Allowed values are: MFC, Ext, Snet, FCSA, CLIM.
s
the disk subtype; to be entered when an extra
record of a new disk is required; subtype is not
overridden for existing disk model numbers;
this is a positive number between 49 and 99.
readseek
is the read seek time of the disk in
milliseconds. This value is a positive number
between 01.00 to 09.99 of format xx.yy.
[writeseek]
is the write seek time of the disk in
milliseconds. This is optional; if not specified,
it will be considered to be same as read seek time.
This value is a positive number between 01.00
to 09.99 of format xx.yy.
SSDDISKFACTOR m [r] [w]
where: m
the disk model number of subtype 50;
Allowed value is: EO0200FBRVV.
[r]
the read speedup factor.
[w]
the write speedup factor.
Note: Measure may not display the disk model number
correctly. Physical checking of disk model number
used during measurement is recommended.
ACTUALDISK42 m
where: m
ACTUALDISK43 m
Using MeasTCM
the disk model number of subtype 42;
Allowed values are: 4608, 4609.
Note: Measure may not display the disk model number
correctly. Physical checking of disk model number
used during measurement is recommended.
!
where: m
the disk model number of subtype 43;
!
Allowed values are: 4618, 4619.
!
Note: Measure may not display the disk model number
!
correctly. Physical checking of disk model number
!
used during measurement is recommended.
!
! ACTUALDISK44 m
!
!
where: m
the disk model number of subtype 44;
!
Allowed values are: 4636, 4637, 4638.
!
Note: Measure may not display the disk model number
!
correctly. Physical checking of disk model number
!
used during measurement is recommended.
!
! ACTUALDISK50 m [w]
!
!
where: m
the disk model number of subtype 50;
!
Allowed value is: EO0200FBRVV
!
!
[w]
this is an optional field for WCE configuration;
!
Allowed values are ON or OFF; By default it will be OFF.
!
! ACTUALDISK51 m [w]
!
!
where: m
the disk model number of subtype 51;
!
Allowed values are: DG072BB975,DG146BB976,
!
DH072BB978,DG0146BAHZP,DG0300BAHZQ,DG0146BALVN,
!
DG0300BALVP,DG0146FAMWL,EG0146FAWHU,DG0300FAMWN,
!
EG0300FAWHV,DH0072BALWL,DH0146BALWN,DH0072FAQRD,
!
EH0072FAWJA,DH0146FAQRE,EH0146FAWJB,DG072BAAJA,
!
DG146BAAJB,DG0146BAMYQ,DG0300BAMYR,DG0146FARVU,
!
DG0300FARVV,EG0146FAWJC,EG0300FAWJD,EH0072FARWC,
!
EH0146FARWD,EG0300FBDBR,EG0600FBDBU,DH072BAAKN,
!
DG072BABCE,DG146BABCF,DG0146BARTP,DG0300BARTQ,
!
EG0146FARTR,EG0300FARTT,EH0072FARUA,EH0146FARUB,
!
EG0300FBDSP,EG0600FBDSR,EG0900FBLSK,EG0900FCHHV,
!
EG0600FBLSH,EG0600FCHHU,EH0300FBQDD,EG0300FCHHR,
!
EG0300FBLSE,EG0300FBVFL,EG0300FBQDD,EH0300FCBVC,
!
EH0146FBQDC,EH0146FCBV,EH0146FCBVB,EH0146FAWJB.
!
!
[w]
this is an optional field for WCE configuration;
!
Allowed values are ON or OFF; By default it will be OFF.
!
! ACTUALDISK52 m
!
!
where: m
supported disk models for subtype 52;
!
Allowed values are: XP24KRG5A, XP24KRG5B, AV482A,
!
AV483A.
!
where,
!
XP24KRG5A stands for XP24K RAID5 (3D+1P) array group
!
XP24KRG5B stands for XP24K RAID5 (7D+1P) array group
!
AV482A stands for P9500 146GB 6G SAS 15k rpm dual port hard drive
!
AV483A stands for P9500 300GB 6G SAS 15k rpm dual port hard drive
!
! ACTUALDISK53 m
!
!
where: m
the disk model number of subtype 53;
!
Allowed values are: BF07255B2C, BF0725754B,
!
BF07258243, BF14658244,BF0725A476,BF1465A477,
!
BF3005A478, BF072D6186, BF146DA47C, BF300DA482,
!
BF450DA483, BF072DAJZN, BF146DAJZP, BF300DAJZQ,
!
BF450DAJZR, BF600DAJZT, BF036574C9, BF07258222,
!
BF14658227, BF0725A692, BF1465A693, BF146DA47A,
!
BF300DA47B, BF300D6188, BF450D6189, BF300DASTH,
!
BF450DASTK, BF600DASTL.
! NUMTMFTRAIL m
!
!
where: m
the total number of audit trails configured;
!
Allowed values are between 1 and 16.
!
!
!***********************************************************************
MEASURE
CSVLO
CSVHI
APPL
CSVDATA
NUMCSVS
$data.meas.measdata
2011/11/06;15:10:00
2011/11/06;15:50:00
test
CSVDA
*
!***********************************************************************
Customizing Your Process Category Control File
37
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
Syntax for PCAT entries
----------------------PCATnn B,C,D $E $F.G.H
where:
(Process Category aggregate control)
nn
"category" number for aggregation, a number between 00
and 97, which identifies one of a set of counters used
to summarize interval detail information
B
node name
C
D
CPU number
PIN number
( "*" means
starting
( "*" means
( "*" means
any or full Node name
with "\")
any )
any )
note that elements B,C,D are separated by a comma
$E
process name
( "$???????" or "*" means any)
$F
G
H
program volume name
program subvol name
program file name
( "$???????" or "*" means any)
( "????????" or "*" means any)
( "????????" or "*" means any)
note that name is in external format
"?" can be used as a wildcard character in E,F,G,H
I
J
userid group
userid user
( "*" means any)
( "*" means any)
note that elements I,J are separated by a comma
!
TMF processes
PCAT01 *,*,4 *
PCAT01 *,*,* $audit
PCAT01 *,*,* $tmp
PCAT01 *,*,* *
PCAT01 *,*,* *
38
I,J
*,*
*,*
*,*
*,*
*,*
!
!
!
!
!
TMF monitor
audit disk
$TMP
>= D30 TMF
backout process <D30
!
Requester (PATHWAY) processes
PCAT02 *,*,* *
$system.system.pathtcp2
PCAT02 *,*,* *
$system.system.pathmon
PCAT02 *,*,3 $zl??
$system.sys??.osimage
PCAT02 *,*,* $zl??
$system.sys??.ROUT
PCAT02 *,*,* $zacs
$system.sys??.BC
PCAT02 *,*,* $zp??
$system.sys??.PB
PCAT02 *,*,* $zcs?? $system.sys??.CS
*,*
*,*
*,*
*,*
*,*
*,*
*,*
!
!
!
!
!
!
!
PATHWAY TCP
PATHWAY monitor
PATHWAY linkmon
Linkmon >=D40
Broadcast Manager
Process Broker
Configuration
!
MEASURE subsystem
!
PCAT03 *,*,* *
$system.sys??.meascom
PCAT03 *,*,* *
$system.sys??.measctl
PCAT03 *,*,* *
$system.sys??.measfh
PCAT03 *,*,* *
$system.sys??.measmon
*,*
*,*
*,*
*,*
!
Disk processes other than audit
!
PCAT04 *,*,* $system $system.sys??.osimage
PCAT04 *,*,* $data* $system.sys??.osimage
PCAT04 *,*,* $data* $system.sys??.TSYSDP2
*,*
*,*
*,*
!
Other system processes
!
PCAT05 *,*,* *
$system.sys??.osimage
PCAT05 *,*,* *
$system.sys??.*
PCAT05 *,*,* *
$system.system.*
*,*
*,*
*,*
!
Server processes
!
PCAT06 *,*,* *
$data??.obj.*
*,*
!
OSS processes
!
PCAT07 *,*,* $ZMSGQ
PCAT07 *,*,* $ZPMON
PCAT07 *,*,* $ZFM??
PCAT07 *,*,* $ZLS??
PCAT07 *,*,* $ZPLS??
PCAT07 *,*,* *
PCAT07 *,*,* $ZPP??
PCAT07 *,*,* $ZSP??
PCAT07 *,*,* $ZTA??
PCAT07 *,*,* $ZTT??
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
Using MeasTCM
$system.sys??.osimage
$system.sys??.*
$system.sys??.*
$system.sys??.tmf*
$system.sys??.backout
$system.sys??.ZMSGQ
$system.sys??.OSSMON
$system.sys??.OSSFM
$system.sys??.OSSLS2
$system.sys??.OSSLS
$system.sys??.NS
$system.sys??.OSSPS
$system.sys??.OSSSP
$system.sys??.OSSTA
$system.sys??.OSSTH
! Disk >= G00
!
!
!
!
!
!
!
!
!
!
Message Queue Servers
OSS Monitor
File Manager
Local Server2
Local Server
Name Server
Pipe Server
OSP Server
Transport Agent
Terminal Helper
PCAT07 *,*,* *
PCAT07 *,*,* *
$system.sys??.OSSTTY
$system.sys??.TELSERV
!
SQL/MP processes
!
PCAT08 *,*,* *
$system.system.sqlci
PCAT08 *,*,* *
$system.system.sqlci2
PCAT08 *,*,* *
$system.system.sqlcat
PCAT08 *,*,* *
$system.system.sqlcomp
PCAT08 *,*,* *
$system.system.audserv
PCAT08 *,*,* *
$system.system.sqlesp
PCAT08 *,*,* *
$system.system.sqlespmg
PCAT08 *,*,* *
$system.system.statsrv
PCAT08 *,*,* *
$system.system.sqlutil
PCAT08 *,*,* *
$system.system.Goaway
PCAT08 *,*,* *
$system.sys??.initdll
PCAT08 *,*,* *
$system.sys??.recgen
PCAT08 *,*,* *
$system.sys??.sortprog
PCAT08 *,*,* *
$system.zdtload2.dataload
! SQL/MX Processes
!
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
$system.system.MXTOOL
$system.system.MXCMP
$system.system.MXAUDSERV
$system.system.MXRTDSRV
$system.system.MXESP
$system.system.MXUDR
$system.ztempl.ZMXSTMPL
$system.zmxtools.MXVQP
$system.zmxtools.T0607ET
$system.zmxtools.T0607SET
$system.zmxtools.T0610SET
*,* ! OSSTY Processes
*,* ! Telnet Server Process
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
!***********************************************************************
! Syntax for TITLE entries
! -----------------------!
! TITLEnn U,V
(Process category description)
!
! where:
nn
"category" number for aggregation, a number between 00
!
and 97, which identifies one of a set of counters used
!
to summarize interval detail information
!
!
U
1 character process category type code
!
V
1 to 8 character process category description
TITLE01
TITLE02
TITLE03
TITLE04
TITLE05
TITLE06
TITLE07
TITLE08
TITLE09
T,tmf
R,requestr
F,measure
D,disc
O,system
S,server
O,OSS
R,SQLMP
R,SQLMX
!***********************************************************************
! Syntax for TXN entries
! ---------------------!
! TXN W,Z
!
! where:
W
1 character transaction type code
!
Z
transaction name (up to 20 chars)
TXN X,bigtrans
Customizing Your Process Category Control File
39
CNTLFILE File Format
The control file has four sections:
Section
Description
Environmental entries
Defines the names of measurement data file or files, the extraction window, the application
name, the output CPU type, the processor type, the name of the CSV file, and a report
location
PCAT (process category)
entries
Defines the process categories
TITLE entries
Provides a name and a type for each process category listed in the PCAT entries
TXN (transaction) entries
Contains a list of transaction names and types
The first section, environmental entries, is required. For applications with OLTP transactions only,
the three other sections are optional. For applications with batch transactions, the last section, TXN
entries, is required. If the last three sections are included, they must be specified in the order listed
in the template file.
Environmental Entries
The environmental entries in CNTLFILE include:
MEASURE data-file [ measfh ]
CSVLO yyyy/mm/dd;hh:mm:ss
CSVHI yyyy/mm/dd;hh:mm:ss
APPL application
CONVERTTO t u
CPUFACTOR t [r] xxxx.yy s [i]
CSVDATA data-file
REPORT $a[.#b[.c]]
NUMCSVS *|ALL|n
NUMTMFTRAIL m
DISKCONVERTTO m [w]
SSDDISKFACTOR m r w
DISKFACTOR m r c s readseek [writeseek]
ACTUALDISK42 m
ACTUALDISK43 m
ACTUALDISK44 m
ACTUALDISK50 m [w]
ACTUALDISK51 m [w]
ACTUALDISK52 m
ACTUALDISK53 m
MEASURE Entry
MEASURE data-file is a disk file containing data collected by Measure. It is required. Measfh
is the name of an object file containing a MEASFH program. The default is the current
$SYSTEM.SYSnn.MEASFH file. You can have multiple entries of this type:
MEASURE datafile1 [ measfh ]
MEASURE datafile2 [ measfh ]
CSVLO and CSVHI Entry
The CSVLO and CSVHI entries define the time window used to filter the data in all the specified
Measure files. These entries are recommended, but not required. If you do not supply one or both
of these times, MeasTCM determines an appropriate time based on the actual start and stop times
of the input Measure data files.
If no data occurs during the user-specified CSVLO to CSVHI time period, no CSVs are produced,
and MeasTCM displays an appropriate message.
40
Using MeasTCM
HP recommends that the Measure data have intervals so the first and last intervals can be excluded
from the MeasTCM analysis by specifying appropriate CSVLO and CSVHI entries. The first and
last intervals might contain Measure startup or shutdown inconsistencies. The intervening period
or periods will contain data that is more consistent.
APPL Entry
Application is the name of the application for the Measure data sample (maximum 20 characters)
that you select. This entry is required. The first character of the application name must be a letter.
The following characters can be numbers or letters. No special characters can be used. The
application appears in the Workload Apportionment and Performance models on your
workstation.
CONVERTTO Entry
The CONVERTTO entry represents the output CPU type. This entry is required when the measurement
data file or files contains mixed CPU types.
The syntax is:
CONVERTTO t u
Where:
t
is the output CPU type.
u
is the output NonStop Kernel product version.
This entry is required when t (first parameter of CONVERTTO) is different from the CPU types
contained in the measurement data files.
The valid TCM values are in this table.
Table 2 CONVERTTO Values — Type, Model and Version
Processor Type
Processor Model
NonStop Product Version
NB54000c*, NB54000c-CG*
NSE-AB(2-CORE)
J06
NB54000c*, NB54000c-CG*
NSE-AB(4-CORE)
J06
NB54000c*, NB54000c-CG*
NSE-AB
J06
NS2200*
NSE-AD
J06
NS2100
NSE-AE
J06
NB56000c
NSE-AF(2–CORE)
J06
NB56000c
NSE-AF(4–CORE)
J06
NS2300
NSE-AG
J06
NS2400
NSE-AH
J06
NB56000c
NSE-AF
J06
NS2000*, NS2000T*, NS2000ST* NSE-W
J06
NB50000c*, NB5000c-CG*
NSE-M
J06
NS14200
NSE-S
H06
NS5000T, NS5000CG
NSE-I
H06
NS3000AC
NSE-K
H06
NS16200, NS16200CG
NSE-T
H06
CNTLFILE File Format
41
Table 2 CONVERTTO Values — Type, Model and Version (continued)
Processor Type
Processor Model
NonStop Product Version
NS1000
NSE-B
H06
NS14000
NSE-D
H06
NS16000, NS16000CG
NSE-A
H06
S88K
NSR-Z
G06
S86K
NSR-Y
G06
S78K
NSR-H
G06
S76K
NSR-X
G06
S74K
NSR-V
G06
S78c
NSR-J
G06
S76c
NSR-E
G06
S74c
NSR-D
G06
S72K
NSR-T
G06
S70K
NSR-G
G06, G05, G03, G02
S07K
NSR-W
G05, G03, G02
* Indicates multi-core processor
When you use the CONVERTTO t u entry to normalize a measurement data file with mixed CPU
types to an output CPU type, you can get a fractional number of CPUs.
CPUFACTOR Entry
CPUFACTOR is an optional entry that enables you to override the default CPU conversion factors.
These factors represent approximate relative CPU speeds. This entry has no effect when the
measurement data contains only one CPU type. The default values are identical to the ones used
by TCM.
The syntax is:
CPUFACTOR t [r] xxxx.yy s [i]
Where:
t
is the CPU type for which the default conversion factor will be overridden. Values are found
in the table, below.
r
is an optional NonStop Kernel version. G, H, or J are acceptable values.
xxxx.yy
is the new conversion factor for the CPU type t. It is a positive number between 0000.01 and
9999.99. This value must be exactly seven characters long.
s
is the type, subtype of the CPU. Both type and subtype are numeric values separated by the
delimiter ','. e.g... 10,71 for NSE-M
[i]
is the IPU count of the CPU. This field is optional and is applicable only for multi-core CPUs.
The valid values are found in this table, where default values are based on the speedup of NSR-T
CPU as 51.88.
42
Using MeasTCM
Table 3 CPUFACTOR Values
Processor Model
Type, Subtype
Name
NonStop Product
Version
Default Values
IPU Count
NSR-W
8,1
S07K
G05, G03, G02 16.56
N.A.
NSR-G
9,0
S70K
G06, G05, G03, 39.11
G02
N.A.
NSR-T
9,1
S72K
G06
51.88
N.A.
NSR-D
9,10
S74c
G06
40.12
N.A.
NSR-E
9,11
S76c
G06
63.76
N.A.
NSR-J
9,14
S78c
G06
82.42
N.A.
NSR-V
9,2
S74K
G06
67.10
N.A.
NSR-X
9,3
S76K
G06
99.77
N.A.
NSR-H
9,13
S78K
G06
113.58
N.A.
NSR-Y
9,4
S86K
G06
121.65
N.A.
NSR-Z
9,1
S88K
G06
152.83
N.A.
NSE-Q
10,91
NS1200
H06
271.45
N.A.
NSE-T
10,83
NS16200,
NS16200CG
H06
418.64
N.A.
NSE-A
10,1
NS16000,
NS16000CG
H06
358.14
N.A.
NSE-D
10,2
NS14000
H06
276.83
N.A.
NSE-K
10,63
NS3000AC
H06
231.06
N.A.
NSE-I
10,51
NS5000T,
NS5000CG
H06
319.93
N.A.
NSE-S
10,82
NS14200
H06
302.44
N.A.
NSE-B
10,11
NS1000
H06
247.81
N.A.
NSE-M
10,71
NB50000c*,
NB5000c-CG*
J06
703.16
2
NSE-W
10,67
NS2000*,
NS2000T*,
NS2000ST*
J06
536.27
2
NSE-AD
10,121
NS2200*
J06
614.56
2
NSE-AB(2–CORE) 10,112
NB54000c*,
NB54000c-CG*
J06
723.01
4
NSE-AB(4–CORE) 10,112
NB54000c*,
NB54000c-CG*
J06
1277.67
4
NSE-AB
10,112
NB54000c*,
NB54000c-CG*
J06
1277.67
4
NSE-AE
10,123
NS2100
J06
317.44
1
NSE-AF(2–CORE) 10,131
NB56000c
J06
108.48
2
NSE-AF(4–CORE) 10,131
NB56000c
J06
1944.77
4
NSE-AF
10,131
NB56000c
J06
1944.77
4
NSE-AG
10,141
NS2300
J06
328.24
1
CNTLFILE File Format
43
Table 3 CPUFACTOR Values (continued)
Processor Model
Type, Subtype
Name
NonStop Product
Version
Default Values
IPU Count
NSE-AH
10,142
NS2400
J06
1
802.29
* Indicates multi-core processor
Example
Either of the following statements changes the NSE-K value from 0231.06 to 0240.20.
CPUFACTOR NSE-K H 0240.20 10,63
CPUFACTOR NSE-K 0240.20 10,63
CSVDATA Entry
The CSVDATA name is a string that contains the first five characters of the CSV file to be
downloaded to the workstation. The entry CSVDATA ABCDE, for example, produces CSV files
named ABCDE001, ABCDE002, ABCDE003, and so on. If you do not specify the CSVDATA
keyword, the default name CSVDA (plus a three-digit number) is used for naming CSV files.
REPORT Entry
The REPORT entry (optional) is the spooler location where a process category audit report is
generated.
NUMCSVS Entry
The NUMCSVS entry specifies the number of CSV files you want MeasTCM to produce. If you do
not specify a value, the default is 1.
The syntax follows:
NUMCSVS * | ALL | n
where:
* | ALL
instructs MeasTCM to produce as many CSVs as possible.
n
is a positive integer.
The number of CSV files generated depends on the start time, stop time, and intervals used in the
input Measure data file or files in addition to the user-supplied CSVLO and CSVHI keyword
parameters. The number of CSV files produced can differ from the requested number.
MeasTCM first calculates the maximum number of CSV files possible based on the lowest common
multiple of the interval times, the start and stop times of the Measure data files, and the user-supplied
CSVLO and CSVHI times if any.
For example, suppose that one Measure data file used has a start time of 10 a.m., a stop time of
11 a.m., and an interval of 5 minutes. With no CSVLO and CSVHI time supplied, the maximum
number of CSVs is 12 (one for every 5-minute interval). If you specify NUMCSVS *, MeasTCM
creates 12 CSVs, each including one interval of 5 minutes.
If you specify NUMCSVS 5, MeasTCM creates 5 CSVs. The first four CSVs include 2 intervals each
(12/5 = 2 intervals, ignoring the remainder), for a total of 10 minutes each. The last CSV includes
4 intervals, for a total of 20 minutes.
Example
This example shows the required entries:
MEASURE measdata
APPL
bankcard
44
Using MeasTCM
NUMTMFTRAIL Entry
The optional NUMTMFTRAIL entry supports multiple auxiliary TMF audit trails in MeasTCM. If you
do not specify NUMTMFTRAIL in the control file, the default value of one master audit trail is
generated in the CSV file.
The syntax follows:
NUMTMFTRAIL m
where:
m
specifies the number of audit trails used in the measurement. The default value is one master
audit trail (MAT). In addition to the one master audit trail, you can specify up to 15 auxiliary
(AUX) audit trails. Therefore, if you enter 2, one master audit trail and one auxiliary audit trail
is used.
NOTE:
NUMTMFTRAIL is a new feature available only from SPR T6042H01^ABC.
DISKCONVERTTO Entry
The DISKCONVERTTO entry represents the output disk model number. If the measurement data
file contains mixed disk types, the CSV file has disk busy seconds scaled to this disk type.
Effective with SPR T6042H01^ABE and later, SAS disks and the write cache enable option are
supported. However, XP disks are partially supported.
If the system has XP or P9500 disks, changes in the template control file for the DISKCONVERTTO
statement are required. The DISKCONVERTTO keyword requires a SAS disk model to be specified
when XP disks exist (MeasTCM does not accept JBOD or XP disk models). The disk model specified
for SAS disk is not of concern, but the disk model’s subtype must be 51 (SAS).
Table 4 (page 45) lists the disks that can be used in DISKCONVERTTO statement.
Table 4 List of Disks
4160
4170
4230
4240
4250
4255
4260
4265
4330
4500
4510
4560
4570
4580
4590
4604
4608
4609
4618
4619
4636
4637
4638
4672
46144
BF07255B2C
BF0725754B
BF07258243
BF14658244
BF0725A476
BF1465A477
BF1465A477
BF072D6186
BF146DA47C
BF300DA482
BF450DA483
BF072DAJZN
BF146DAJZP
BF146DAJZP
BF450DAJZR
BF600DAJZT
BF036574C9
BF07258222
BF14658227
BF0725A692
BF1465A693
BF146DA47A
BF300DA47B
BF300D6188
BF450D6189
BF300DASTH
BF450DASTK
BF600DASTL
DG072BB975
DG146BB976
DH072BB978
DG0146BAHZP
DG0300BAHZQ
DG0146BALVN
DG0300BALVP
DG0146FAMWL
EG0146FAWHU
DG0300FAMWN
EG0300FAWHV
DH0072BALWL
DH0146BALWN
DH0072FAQRD
EH0072FAWJA
DH0146FAQRE
EH0146FAWJB
DG072BAAJA
DG146BAAJB
CNTLFILE File Format
45
Table 4 List of Disks (continued)
DG0146BAMYQ
DG0300BAMYR
DG0146FARVU
DG0300FARVV
EG0146FAWJC
EG0300FAWJD
EH0072FARWC
EH0146FARWD
EG0300FBDBR
EG0600FBDBU
DH072BAAKN
DG072BABCE
DG146BABCF
DG0146BARTP
DG0300BARTQ
EG0146FARTR
EG0300FARTT
EH0072FARUA
EH0146FARUB
EG0300FBDSP
EG0600FBDSR
EG0900FBLSK
EG0900FCHHV
EG0600FBLSH
EH0300FBQDD
EG0300FCHHR
EG0300FBLSE
EG0600FCHHU
EH0300FCBVC
EH0146FBQDC
EH0146FCBV
EG0300FBVFL
EG0300FBQDD
EH0146FCBVB
EH0146FAWJB
EO0200FBRVV*
* Indicates SSD disks.
The preceded disk models must be used in the DISKCONVERTTO statement respectively.
The syntax follows:
DISKCONVERTTO m [w]
where:
m
is the disk model number.
This entry can contain only one disk model number.
[w]
specifies the write cache enable (WCE) option. This is an optional entry. If not specified, default
values are used. Values can be ON or OFF, with the following defaults:
•
For disks that support WCE, the default value is OFF.
•
For disks that do not support WCE, this field is left blank.
Table 5: DISKFACTOR Model, Speed, Controller, Subtype and Seek Times (page 48) lists the disks
supported by TCM, with their model numbers, rotational speeds, controllers, and subtypes.
NOTE: If SSD disk (EO0200FBRVV) is used in the DISKCONVERTTO statement, then use the
following DISKCONVERTTO syntax:
DISKCONVERTTO m [w] [p]
where:
m
is the disk model number.
This entry can contain only one disk model number.
[w]
specifies the write cache enable (WCE) option. This is an optional entry. If not specified, default
values are used. Values can be ON or OFF. For disks that support WCE, the default value is
OFF.
[p]
is the number of partitions in the disk. Valid values are 1 to 8. This is an optional entry.
Default value is 1.
SSDDISKFACTOR Entry
SSDDISKFACTOR is an optional entry that can be used to override the read and write speed up
factors of an existing disk model and replace them with user-specified values.
46
Using MeasTCM
The syntax follows:
SSDDISKFACTOR m [r] [w]
where:
m
is the disk model number for which the default RPM and controller type changes. Acceptable
values for SSDDISKFACTOR Model, Speed, Controller, Subtype and Seek Times are shown in
Table 5 (page 48).
[r]
is the read speed up factor. This is a numeric value and is in the format X.XX, where X is any
number, for example 1.34.
[w]
is the write speed up factor. This is a numeric value and is in the format X.XX, where X is any
number, for example 1.34.
NOTE: [r] and [w] are optional entries. If you do not specify a value to these entries, the default
value is 1.
DISKFACTOR Entry
DISKFACTOR is an optional entry that can be used to override the rotational speed and controller
type of an existing disk model number and replace them with user-specified values.
Effective with SPR T6042H01^ABD and later, SAS disks are supported with CLIM as the controller
and XP disks are partially supported.
If XP or P9500 disks (subtype 52) are installed, then the DISKFACTOR directive must specify a
SAS disk model name and subtype as 51, while the controller, read seek, and write seek times
can reflect the actual values of the real disk types in the system.
The syntax follows:
DISKFACTOR m r c s readseek [writeseek]
where:
m
is the disk model number for which the default RPM, controller type will change. Acceptable
values for DISKFACTOR Model, Speed, Controller, Subtype and Seek Times are shown in
Table 5 (page 48).
r
is the RPM value of a disk, which is a measure of the speed of rotation. This value is a positive
number between 00000.01 and 99999.99.
c
is the disk controller type. Acceptable values are MFC, Ext, Snet, FCSA, and CLIM.
s
is the disk subtype, to be entered when an extra record of a new disk is required. The subtype
is not overridden for existing disk model numbers. This value is a positive number between 49
and 99.
readseek
is the read seek time of the disk in milliseconds. This value is a positive number between 01.00
to 09.99.
[writeseek]
is the write seek time of the disk in milliseconds. This is optional; if not specified, it will be
considered to be same as the readseek time. This value is a positive number between 01.00
to 09.99.
CNTLFILE File Format
47
This entry also allows the user to add up to five new disk model numbers.
When MEASTCM is run with or without a DISKFACTOR entry, the following warning message is
displayed:
WARNING! The Disk Count has not been scaled, only the Disk Busy Seconds have been scaled
according to the DISKCONVERTTO Type.
As per the warning message, users need not explicitly specify a DISKFACTOR entry for the disk
model specified in the DISKCONVERTTO, in order to ensure the correct attributes used by MeasTCM.
The default values of the rotational speed, controller type, subtype, read seek and write seek times
for various disk model numbers are:
Table 5 DISKFACTOR Model, Speed, Controller, Subtype and Seek Times
48
Disk Model
Number
Rotational Speed
Controller
Subtype
Read Seek Time
(ms)
Write Seek Time
(ms)
4160
3600
Ext
16
3.8
3.8
4170
3600
Ext
18
3.8
3.8
4230
3600
MFC
21
3.8
3.8
4240
3600
MFC
23
3.8
3.8
4250
5400
MFC
29
3.8
3.8
4255
5400
MFC
34
3.8
3.8
4260
7200
MFC
30
3.8
3.8
4265
7200
MFC
35
3.8
3.8
4330
7200
Ext
24
3.8
3.8
4500
3600
Ext
22
3.8
3.8
4510
5400
Ext
31
3.8
3.8
4560
5400
Ext
38
3.8
3.8
4570
7200
Ext
39
3.8
3.8
4580
7200
Ext
20
3.8
3.8
4590
7200
Ext
48
3.8
3.8
4604
7200
Snet
41
3.8
3.8
4608
7200
Snet
42
3.8
3.8
4609
10000
Snet
42
3.8
3.8
4618
7200
Snet
43
3.8
3.8
4619
15000
Snet
43
3.8
3.8
4636
7200
Snet
44
3.8
3.8
4637
10000
Snet
44
3.8
3.8
4638
7200
Snet
44
3.8
3.8
4672
15000
Snet
45
3.8
3.8
46144
15000
Snet
53
3.8
3.8
BF07255B2C
15000
FCSA
53
3.8
3.8
BF0725754B
15000
FCSA
53
3.8
3.8
Using MeasTCM
Table 5 DISKFACTOR Model, Speed, Controller, Subtype and Seek Times (continued)
Disk Model
Number
Rotational Speed
Controller
Subtype
Read Seek Time
(ms)
Write Seek Time
(ms)
BF07258243
15000
FCSA
53
3.8
3.8
BF14658244
15000
FCSA
53
3.8
3.8
BF0725A476
15000
FCSA
53
3.8
3.8
BF1465A477
15000
FCSA
53
3.8
3.8
BF3005A478
15000
FCSA
53
3.8
3.8
BF072D6186
15000
FCSA
53
3.8
3.8
BF146DA47C
15000
FCSA
53
3.8
3.8
BF300DA482
15000
FCSA
53
3.8
3.8
BF450DA483
15000
FCSA
53
3.8
3.8
BF072DAJZN
15000
FCSA
53
3.8
3.8
BF146DAJZP
15000
FCSA
53
3.8
3.8
BF300DAJZQ
15000
FCSA
53
3.8
3.8
BF450DAJZR
15000
FCSA
53
3.8
3.8
BF600DAJZT
15000
FCSA
53
3.8
3.8
BF036574C9
15000
FCSA
53
3.8
3.8
BF07258222
15000
FCSA
53
3.8
3.8
BF14658227
15000
FCSA
53
3.8
3.8
BF0725A692
15000
FCSA
53
3.8
3.8
BF1465A693
15000
FCSA
53
3.8
3.8
BF146DA47A
15000
FCSA
53
3.8
3.8
BF300DA47B
15000
FCSA
53
3.8
3.8
BF300D6188
15000
FCSA
53
3.8
3.8
BF450D6189
15000
FCSA
53
3.8
3.8
BF300DASTH
15000
FCSA
53
3.8
3.8
BF450DASTK
15000
FCSA
53
3.8
3.8
BF600DASTL
15000
FCSA
53
3.8
3.8
DG072BB975
10000
CLIM
51
4.0
4.4
DG146BB976
10000
CLIM
51
4.0
4.4
DH072BB978
15000
CLIM
51
2.58
3.01
DG0146BAHZP
10000
CLIM
51
4.0
4.4
DG0300BAHZQ 10000
CLIM
51
4.0
4.4
DG0146BALVN
10000
CLIM
51
4.0
4.4
DG0300BALVP
10000
CLIM
51
4.0
4.4
DG0146FAMWL
10000
CLIM
51
4.0
4.4
EG0146FAWHU
10000
CLIM
51
4.0
4.4
DG0300FAMWN 10000
CLIM
51
4.0
4.4
CNTLFILE File Format
49
Table 5 DISKFACTOR Model, Speed, Controller, Subtype and Seek Times (continued)
Disk Model
Number
50
Controller
Subtype
Read Seek Time
(ms)
Write Seek Time
(ms)
EG0300FAWHV 10000
CLIM
51
4.0
4.4
DH0072BALWL
15000
CLIM
51
2.58
3.01
DH0146BALWN
15000
CLIM
51
2.58
3.01
DH0072FAQRD
15000
CLIM
51
2.58
3.01
EH0072FAWJA
15000
CLIM
51
2.58
3.01
DH0146FAQRE
15000
CLIM
51
2.58
3.01
EH0146FAWJB
15000
CLIM
51
2.58
3.01
DG072BAAJA
10000
CLIM
51
4.0
4.4
DG146BAAJB
10000
CLIM
51
4.0
4.4
DG0146BAMYQ 10000
CLIM
51
4.0
4.4
DG0300BAMYR
10000
CLIM
51
4.0
4.4
DG0146FARVU
10000
CLIM
51
4.0
4.4
DG0300FARVV
10000
CLIM
51
4.0
4.4
EG0146FAWJC
10000
CLIM
51
4.0
4.4
EG0300FAWJD
10000
CLIM
51
4.0
4.4
EH0072FARWC
15000
CLIM
51
2.58
3.01
EH0146FARWD
15000
CLIM
51
2.58
3.01
EG0300FBDBR
10000
CLIM
51
4.0
4.4
EG0600FBDBU
10000
CLIM
51
4.0
4.4
DH072BAAKN
15000
CLIM
51
2.58
3.01
DG072BABCE
10000
CLIM
51
4.0
4.4
DG146BABCF
10000
CLIM
51
4.0
4.4
DG0146BARTP
10000
CLIM
51
4.0
4.4
DG0300BARTQ
10000
CLIM
51
4.0
4.4
EG0146FARTR
10000
CLIM
51
4.0
4.4
EG0300FARTT
10000
CLIM
51
4.0
4.4
EH0072FARUA
15000
CLIM
51
2.58
3.01
EH0146FARUB
15000
CLIM
51
2.58
3.01
EG0300FBDSP
10000
CLIM
51
4.0
4.4
EG0600FBDSR
10000
CLIM
51
4.0
4.4
EG0900FBLSK
10000
CLIM
51
3.8
3.94
EG0900FCHHV
10000
CLIM
51
3.8
3.94
EG0600FBLSH
10000
CLIM
51
4.0
3.94
EG0600FCHHU
10000
CLIM
51
4.0
3.94
EH0300FBQDD
15000
CLIM
51
3.5
3.3
EG0300FCHHR
10000
CLIM
51
4.0
3.94
Using MeasTCM
Rotational Speed
Table 5 DISKFACTOR Model, Speed, Controller, Subtype and Seek Times (continued)
Disk Model
Number
Rotational Speed
Controller
Subtype
Read Seek Time
(ms)
Write Seek Time
(ms)
EG0300FBLSE
10000
CLIM
51
4.0
3.94
EG0300FBVFL
15000
CLIM
51
3.5
3.3
EG0300FBQDD
15000
CLIM
51
3.5
3.3
EH0300FCBVC
15000
CLIM
51
3.5
3.3
EH0146FBQDC
15000
CLIM
51
3.0
3.3
EH0146FCBV
15000
CLIM
51
3.0
3.3
EH0146FCBVB
15000
CLIM
51
3.0
3.3
15000
CLIM
51
3.0
3.3
15000
CLIM
50
NA
NA
EH0146FAWJB
1
EO0200FBRVV
1
Supported only on H-series and J-series machines.
NOTE: For XP or P9500 disk models, the read and write seek times specified does not have any
impact on calculations, and it is ignored. These values are basically placeholders to fulfill syntactical
requirements of MeasTCM. MeasTCM internally uses hardcoded power values for calculations.
As of SPR T6042^ABD, read-seek time is hardcoded as 02.58 and write-seek 03.01 for XP or
P9500 disks. The syntax for DISKFACTOR is designed for common use by various disk types (JBOD,
SAS, SCSI, and so on). Syntactically read-seek is required for DISKFACTOR. So, for XP or P9500
disks, seek time with a value in the form XX.YY which is less than 10.00 fulfills the requirements.
The hard coding mechanism is only for XP or P9500 disk arrays, as they are merely an array of
disks put together. For all other disk types, user provided values work fine and used for calculations.
Examples
•
This example changes the rpm of disk 4608 to 10000, the disk controller type to Ext (the read
seek time is 3.8):
DISKFACTOR 4608 10000 Ext 42 03.80
•
This example changes the read seek time of disk BF07255B2C to 4.0, rpm to 10000 and
the disk controller type to CLIM:
DISKFACTOR BF07255B2C 10000 CLIM 53 04.00
•
This example creates a new disk model number with the parameters specified:
DISKFACTOR 4610 7200 MFC 80 02.50 02.80
ACTUALDISK42 Entry
Two disk model numbers (4608 and 4609) can be associated with subtype 42. Therefore,
ACTUALDISK42 is used to specify which of the two is in use.
The syntax follows:
ACTUALDISK42 m
where:
m
is the actual disk model number (4608 or 4609) associated with the subtype 42.
NOTE: Measure may not display the disk model number correctly. Physical checking of disk
model number used during measurement is recommended.
CNTLFILE File Format
51
ACTUALDISK43 Entry
Two disk model numbers (4618 and 4619) can be associated with subtype 43. Therefore,
ACTUALDISK43 is used to specify which of the two is in use.
The syntax follows:
ACTUALDISK43 m
where:
m
is the actual disk model number (4618 or 4619) associated with the subtype 43.
NOTE: Measure may not display the disk model number correctly. Physical checking of disk
model number used during measurement is recommended.
ACTUALDISK44 Entry
Three disk model numbers (4636, 4637, and 4638) can be associated with subtype 44. Therefore,
ACTUALDISK44 is used to specify which of the three is in use.
The syntax follows:
ACTUALDISK44 m
where:
m
is the actual disk model number (4636, 4637, and 4638) associated with the subtype 44.
NOTE: Measure may not display the disk model number correctly. Physical checking of disk
model number used during measurement is recommended.
ACTUALDISK50 Entry
Effective with SPR T6042H01^ABE and later, SSD disks which are of subtype 50 is supported.
ACTUALDISK50 is used to specify the SSD disk which is in use.
CLIM is the default controller for all SSD disk models.
The syntax follows:
ACTUALDISK50 m [w]
where:
m
is the actual disk model number associated with the subtype 50.
[w]
specifies the write cache enable (WCE) option. This is an optional entry. Allowed values are
ON and OFF. If not specified, by default OFF is used.
NOTE: SSD disks does not have any moving parts. Therefore, rotational speed, read seek time,
and write seek time are not applicable.
Table 5 (page 48) lists the disks supported by TCM along with their model numbers, rotational
speeds, controllers, and subtypes.
NOTE: Measure may not display the disk model number correctly. Physical checking of disk
model number used during measurement is recommended.
ACTUALDISK51 Entry
Effective with SPR T6042H01^ABE and later, SAS disks are associated with subtype 51. Therefore,
ACTUALDISK51 is used to specify which SAS disk is in use.
CLIM is the default controller for all SAS disks models.
52
Using MeasTCM
The syntax follows:
ACTUALDISK51 m [w]
where:
m
is the actual disk model number associated with the subtype 51.
[w]
specifies the write cache enable (WCE) option. This is an optional entry. Allowed values are
ON and OFF. If not specified, by default OFF will be used.
Table 5 (page 48) lists the disks supported by TCM, with their model numbers, rotational speeds,
controllers, subtypes, read and write seek times.
NOTE: Measure may not display the disk model number correctly. Physical checking of disk
model number used during measurement is recommended.
ACTUALDISK52 Entry
Effective with SPR T6042H01^ABE and later, two new P9500 disk arrays that belong to the HP
XP disks family are associated with subtype52: Models AV482A and AV483A which are P9500
disk array are supported along with XP24KRG5A and XP24KRG5B.
Where,
XP24KRG5A specifies the XP24K RAID5 (3D+1P) array group.
XP24KRG5B specifies the XP24K RAID5 (7D+1P) array group.
AV482A specifies the P9500 146GB 6G SAS 15k rpm dual port hard drive.
AV483A specifies the P9500 300GB 6G SAS 15k rpm dual port hard drive.
Therefore, ACTUALDISK52 is used to specify which of the XP family disks are in use.
The syntax follows:
ACTUALDISK52 m
where:
m
is the actual disk model number associated with subtype 52.
NOTE: Measure may not display the disk model number correctly. Physical checking of disk
model number used during measurement is recommended.
ACTUALDISK53 Entry
The ACTUALDISK53 entry is associated with disks of subtype 53 and is used to specify which disk
is in use.
The syntax follows:
ACTUALDISK53 m
where:
m
is the actual disk model number associated with the subtype 53.
NOTE: Measure may not display the disk model number correctly. Physical checking of disk
model number used during measurement is recommended.
CNTLFILE File Format
53
Constraints with ACTUALDISK42, ACTUALDISK43, ACTUALDISK44, ACTUALDISK50,
ACTUALDISK51, ACTUALDISK52, ACTUALDISK53
A situation might arise, for example, where the measure data file might have both 4608 and 4609
disk types associated with the same subtype 42, but with different performance.
In that case, ACTUALDISK42 4608 or ACTUALDISK42 4609 can be used, converting the disks
of that subtype into a single disk model number, although some loss of accuracy occurs because
of the conversion.
Process Category (PCAT) Statements
One or more PCAT statements and one TITLE statement are used to define a process category.
Category numbers are arbitrary and serve only to link PCAT statements to a TITLE statement. The
category number can be any 2-digit number from 00 through 97. These numbers link the statement
to a category name in a TITLE statement and also link multiple PCAT statements into one process
category description.
The syntax follows:
PCATnn B,C,D $E $F,G,H I,J
where:
nn
is the category number for aggregation, a number between 00 and 97, which identifies one
of a set of counters used to summarize interval detail information.
B
is the node name (* means any).
C
is the CPU number (* means any).
D
is the PIN number (* means any).
$E
is the process name ($???????? or * means any).
$F
is the program volume name ($???????? or * means any).
G
is the program subvolume name ($???????? or * means any).
H
is the program file name ($???????? or * means any).
I
is the userid group (* means any).
J
is the userid user (* means any).
In general, you should define these categories:
54
•
One category that includes all disk processes (except audit disk processes). Disk processes
are assigned to one category only.
•
If the system is TMF-audited, one TMF category that includes the audit disk processes. (The
default file assumes an audit disk name of $AUDIT.)
•
One category for each major server class.
Using MeasTCM
•
One category for each set of TCPs (or other requesters) that are dedicated to one or more
major transactions.
•
One category for each set of line handlers that are dedicated to one or more major transactions.
Figure 8 (page 56) shows an excerpt from the template file and shows typical process categories
for an application:
CNTLFILE File Format
55
Figure 8 PCAT Template File
! TMF processes
PCAT01 *,*,4 *
PCAT01 *,*,* $audit
PCAT01 *,*,* $tmp
PCAT01 *,*,* *
PCAT01 *,*,* *
$system.sys??.osimage
$audi $system.sys??.*
$tmp $system.sys??.*
$system.sys??.tmf*
$system.sys??.backout
*,*
*,*
*,*
*,*
*,*
! TMF monitor
! audit disk
! $TMP
! >=D30 TMF
! backout process >D30
! Requester (PATHWAY) processes
PCAT02 *,*,* *
$system.system.pathtcp2
PCAT02 *,*,* *
$system.system.pathmon
PCAT02 *,*,3 $zl?? $system.sys??.osimage
PCAT02 *,*,* $zl?? $system.sys??.ROUT
PCAT02 *,*,* $zacs $system.sys??.BC
PCAT02 *,*,* $zp?? $system.sys??.PB
PCAT02 *,*,* $zcs?? $system.sys??.CS
*,*
*,*
*,*
*,*
*,*
*,*
*,*
! PATHWAY TCP
! PATHWAY monitor
! PATHWAY linkmon
! Linkmon >= D40
! Broadcst Manager
! Process Broker
! Configuration
! MEASURE subsystem
PCAT03 *,*,* *
PCAT03 *,*,* *
PCAT03 *,*,* *
PCAT03 *,*,* *
$system.sys??.meascom
$system.sys??.measctl
$system.sys??.measfh
$system.sys??.measmon
*,*
*,*
*,*
*,*
! Disk processes other than audit
PCAT04 *,*,* $system $system.sys??.osimage
PCAT04 *,*,* $data* $system.sys??.osimage
PCAT04 *,*,* $data* $system.sys??.TSYSDP2
*,*
*,*
*,*
! Other system processes
PCAT05 *,*,* *
$system.sys??.osimage
PCAT05 *,*,* *
$system.sys??.*
PCAT05 *,*,* *
$system.system.*
*,*
*,*
*,*
! Server processes
PCAT06 *,*,* *
*,*
$data??.obj.*
! OSS processes
PCAT07 *,*,* $ZMSGQ $system.sys??.ZMSGQ
PCAT07
PCAT07
PCAT07
PCAT07
PCAT07
PCAT07
PCAT07
PCAT07
PCAT07
PCAT07
PCAT07
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
$ZPMON $system.sys??.OSSMON
$ZFM?? $system.sys??.OSSFM
$ZLS??
$system.sys??.OSSLS2
$ZPLS?? $system.sys??.OSSLS
*
$system.sys??.NS
$ZPP??
$system.sys??.OSSPS
$ZSP??
$system.sys??.OSSSP
$ZTA?? $system.sys??.OSSTA
$ZTT??
$system.sys??.OSSTH
*
$system.sys??.OSSTTY
*
$system.sys??.TELSERV
! SQLMP Processes
56
Using MeasTCM
*,* ! Message Queue Servers
*,* ! OSS Monitor
*,* ! File Manager
*,* ! Local Server2
*,* ! Local Server
*,* ! Name Server
*,* ! Pipe Server
*,* ! OSP Server
*,* ! Transport Agent
*,* ! Terminal Helper
*,* ! OSSTY Processes
*,* ! Telnet Server Process
PCAT08
PCAT08
PCAT08
PCAT08
PCAT08
PCAT08
PCAT08
PCAT08
PCAT08
PCAT08
PCAT08
PCAT08
PCAT08
PCAT08
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*,*,*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
! SQLMX Processes
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
PCAT09 *,*,* *
$system.system.sqlci
$system.system.sqlci2
$system.system.sqlcat
$system.system.sqlcomp
$system.system.audserv
$system.system.sqlesp
$system.system.sqlespmg
$system.system.statsrv
$system.system.sqlutil
$system.system.Goaway
$system.sys??.initdll
$system.sys??.recgen
$system.sys??.sortprog
$system.zdtload2.dataload
$system.system.MXTOOL
$system.system.MXCMP
$system.system.MXAUDSERV
$system.system.MXRTDSRV
$system.system.MXESP
$system.system.MXUDR
$system.ztempl.ZMXSTMPL
$system.zmxtools.MXVQP
$system.zmxtools.T0607ET
$system.zmxtools.T0607SET
$system.zmxtools.T0610SET
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
*,*
Effective with SPR T6042H01^ABE and later:
•
The four final PCAT02 Pathway processes support TS/MP
•
The PCAT08 entries support SQL/MP
•
The PCAT09 entries support SQL/MX
The complete syntax for the PCAT entries is included in the control file and illustrated in Figure 9
(page 57).
Figure 9 PCAT Entry
Note the separation between the parts in the PCAT statement. The general rule is that there is no
space when there is a comma, and vice versa. The same is true for the TITLE and TXN statements.
Wild Cards
The process name and program (object file) parameters can contain wild-card characters in any
or all positions. The wild-card character * (asterisk) is used to mean any sequence of zero or more
characters, and the ? (question mark) is used to mean any single character (or no character).
CNTLFILE File Format
57
A process is potentially selected by a category if its attributes (PIN, program file name, and so on)
match all the fields in at least one of the category’s PCAT statements. A process is only “potentially
selected” because it might match PCAT statements in several categories.
A process is selected by a PCAT statement if it matches all specifiers in the statement (an AND
relationship).
A process is selected by a Category (that is, a TITLE statement) if it matches any of the PCAT
statements associated with the TITLE (an OR relationship).
PCAT Example
The following example describes a process category called PCAT03 that includes all audit disk
activity. Its node name, CPU, and process ID number are universal (indicated by the asterisk). Its
process name must be $audit. The program volume name is $system.sysnn.osimage. Its user group
ID and user ID are universal.
PCAT03 *,*,*
$audit $system.sys??.osimage
*,*
! audit disk
The parameters within each PCAT statement are defined from the most restrictive to the least
restrictive as you move from left to right. The selection criteria, in the order of most restrictive to
least restrictive, are the process ID parameters, process name, object file, and user group and user
ID numbers. For data to be filtered by a PCAT statement, it must satisfy all parameters in the
statement. For data to be filtered by a group of PCAT statements for the same process category
(such as all PCAT01 statements), the data must satisfy any one of those statements.
Resolving Multiple Category Matches
If a process is potentially selected by multiple categories, it is assigned to the most restrictive of
the matches. Restrictiveness is tested by examining the fields of the matching PCAT statements from
left to right:
•
Alphanumeric characters are more restrictive than question mark (?) wild cards.
•
Question mark (?) characters are more restrictive than asterisk (*) wild cards.
Figure 10 (page 59) shows that every process is assigned to only one category by resolving multiple
category matches through a series of sort questions.
To illustrate how a process would be categorized in the control file, consider a process with the
following parameters:
process-name = $SYSTEM
program-filename = $SYSTEM.SYS00.OSIMAGE
Although these parameters satisfy PCAT statements for categories 4 and 5 in the template control
file, the process is aggregated to category 4, because that category is the most restrictive of the
two. Here are the PCAT statements for categories 4 and 5:
! Disk
!
PCAT04
PCAT04
PCAT04
processes other than audit
*,*,* $system
*,*,* $data*
*,*,* $data*
$system.sys??.osimage
$system.sys??.osimage
$system.sys??.TSYSDP2
*,*
*,*
*,*
! Other system processes
!
PCAT05 *,*,* *
$system.sys??.osimage
PCAT05 *,*,* *
$system.sys??.*
PCAT05 *,*,* *
$system.system.*
*,*
*,*
*,*
If the process uses process name $STUFF, it would be aggregated to category 5 because it specifies
the wild card (*) as the process name and specifies $SYSTEM.SYS??.OSIMAGE as the program
filename.
58
Using MeasTCM
Unspecified Data
To ensure that no data is omitted, MeasTCM automatically summarizes all data that does not satisfy
any other criteria in the file into category 98 with the default name of _OTHER and type O.
All Discopen data that cannot be linked to process data goes into category 99, with the default
name of _ERROR and type O.
Figure 10 Multiple Category Matches
TITLE Statements
TITLE statements name a process category. The syntax for TITLE entries is:
TITLEnn U,V
nn
is the category number for aggregation, a number between 00 and 97, which identifies one
of a set of counters used to summarize interval detail information.
U
is a one-character process category type code.
V
is a one to eight character process category description.
The category type has a predefined meaning to TCM and must be one of the following:
CNTLFILE File Format
59
Table 6 TITLE Entry with Category Type and Description
Title Entry
Process
Category Type Process Category Description
TITLE01
T
TMF (including audit disk processes)
TITLE02
R
Requester
TITLE03
F
Measure
TITLE04
D
Disk (excluding audit disk processes)
TITLE05
O
System
TITLE06
S
Server
TITLE07
O
OSS
TITLE08
R
SQLMP
TITLE09
R
SQLMX
Effective with SPR T6042H01^ABE and later, OSS, SQLMP and SQLMX process categories are
added to template control file.
File Defaults
The template control file aggregates processes running on any system into eight categories as
follows. The default statements contain no restrictions on user ID numbers.
NOTE: The categories in the template control file are provided as a starting point. They do not
necessarily represent categories appropriate for your particular application.
TXN Entries
Table 7 Category Number, Name, and Description
Category Number Category Name
Description
01
tmf
All processes related to TMF, including audit disk processes
02
requestr
All Pathway TCPs and monitors
03
measure
All processes related to Measure
04
disc
All the application’s disk processes, excluding any audit disks
05
system
All other NonStop processes
06
server
All server processes with program file name $DATA??.OBJ.*
07
oss
All processes related to OSS
08
sqlmp
All processes related to SQL/MP
09
sqlmx
All processes related to SQL/MX
The TXN entries have a transaction type code and a transaction name. TXN entries are required
if you have any batch transactions. They are optional if you have OLTP transactions only.
! TXN W,Z
!
! where:
W
!
Z
TXN X,bigtrans
60
Using MeasTCM
1 character transaction type code
transaction name (up to 20 chars)
The one-character transaction type code can be one of the following:
•
X for an OLTP transaction
•
B for a batch transaction
•
Q for a query transaction
NOTE: Do not include a space between the one-character transaction type code and the
transaction name. Including a space between them will cause an error.
The transaction name can be up to 20 characters.
If you do not specify TXN entries, TCM uses the name of the Server (S type) process categories as
the default, and the TXN type is assumed to be X.
If you do not want to use the defaults (for instance, if you have batch transactions), you must list
all transaction names and their codes.
The maximum number of transactions that can be modeled is 40.
Running MeasTCM to Create CSV Files
Once you have edited the control file, MeasTCM has the information it needs to summarize the
specified Measure data and create the CSV files for downloading to TCM on the workstation.
To process the data, run MeasTCM. The length of processing time depends on the amount of
Measure data being summarized, the number of process categories defined, and the priority given.
During run time, MeasTCM creates these files:
•
If you specify a report to be made, an intermediate file might be created if FastSort needs
one. This file is automatically deleted when processing finishes.
•
The CSV files required by TCM.
Messages appear to inform you of the processing status. If a specified control file does not
exist, MeasTCM terminates with a completion message indicating that the control file does
not exist.
NOTE:
HP reserves the right to change the format of the CSV file without notice.
Running MeasTCM
To run MeasTCM:
1. Set the optional EXECUTION-LOG parameter:
> [ PARAM EXECUTION-LOG { Tandem-file-name } ]
{
define-file }
The EXECUTION-LOG parameter must be set when you run MeasTCM with the NOWAIT
option. (See Step 2.) The parameter value controls the destination of the MeasTCM
informational messages and messages issued by the COBOL85 runtime library routines. If
there is no EXECUTION-LOG parameter, messages are sent to the home terminal.
2.
Run MeasTCM by entering the following command. This example assumes that MeasTCM is
installed in the $SYSTEM.SYSTEM sub-volume.
2> MEASTCM [ / NOWAIT / ] cntlfile
cntlfile is the name of your control file.
If MeasTCM is not installed in the $SYSTEM.SYSTEM subvolume, specify RUN and enter the
fully qualified file name of the MEASTCM program:
2> RUN $DATA.ATTG.MEASTCM [ / NOWAIT / ] cntlfile
Running MeasTCM to Create CSV Files
61
MeasTCM Syntax
MeasTCM has the following syntax:
[ RUN ] MEASTCM / [ run-option [ , run-option ] ] / cntlfile
RUN
is the TACL RUN command. Do not specify RUN if MeasTCM is installed in the
$SYSTEM.SYSTEM subvolume.
run-option
is one of the following. This list describes commonly used RUN options. For a complete list of
RUN options, see the TACL Reference Manual.
CPU cpu-number
specifies the number of the CPU in which MeasTCM is to run. cpu-number is an integer in
the range of 0 through 15. If you omit this option, MeasTCM runs in the same processor
as TACL. (If you omit the CPU option and a $CMON process exists, $CMON might specify
a CPU other than the one in which the current TACL process is running. For more information
about $CMON, see the Guardian Programmer’s Guide.)
NAME [ $process-name ]
specifies the name you are assigning to MeasTCM. Specify the $processname as an
alphanumeric string of 1 to 5 characters, the first of which must be a letter. For network
access, the name must be no more than four characters. If you omit this parameter, the
MeasTCM process is not named and has only a CPU number and process ID.
NOWAIT
specifies that TACL does not wait while the program runs. TACL returns a command input
prompt after sending the startup message to the new process. If you omit this option, TACL
pauses while MeasTCM runs. Use this option to run MeasTCM in background mode for a
batch environment.
PRI priority
specifies the run priority of the MeasTCM process. Specify priority as an integer in the
range of 1 to 199. Processes with higher numbers are executed first. If you omit this option,
MeasTCM runs at a priority of 1 less than that of the TACL process. If a $CMON process
exists and you omit the PRI option, $CMON might specify a priority other than 1 less than
your TACL process. For more information about $CMON, see the Guardian Programmer’s
Guide.
cntlfile
specifies the name of your control file.
Example
A sample RUN command follows:
1> MEASTCM cntlfile
Run Summary Report
After execution, MeasTCM displays a Run Summary Report, as shown in Figure 11 (page 63).
The Run Summary Report is also listed at the end of the Process Category Audit report if you
requested one. The report shows:
62
•
The Measure input file summary (including the start and stop times, the system name and the
intervals, and any optional advisory messages for each Measure data file specified)
•
The user-specified CSVLO and CSVHI values, if any, and the actual low and high values
•
The number of CSV files you requested and the actual number of CSV files generated
•
The start and stop time for which data was extracted from the Measure file, the name of the
CSV file, and the percentage linkage for each CSV file generated
Using MeasTCM
Figure 11 Run Summary Report
MeasTCM
Run Summary
24-JUN-1993 16:34:10
Measure Data File Summary:
-------------------------1 Measure file name: $DATA17.TCMTEST1.MDATA1 System: \LILLI
From time: 1991/09/17;10:00:00 To Time: 1991/09/17;12:00:00 Int.(Secs): 1200
2 Measure file name: $DATA03.TCMTEST1.MDATA2 System: \BELGIUM
From time: 1991/09/17;10:00:00 To Time: 1991/09/17;12:00:06 Int.(Secs): 1200
CSVLO and CSVHI Summary:
-----------------------Requested Time Range: CSVLO = 1991/09/17;10:20:00 CSVHI = 1991/09/17;11:40:00
Actual Time Range: CSVLO = 1991/09/17;10:20:00 CSVHI = 1991/09/17;11:40:00
CSV Output file Summary:
-----------------------Number of CSV data files possible: 4
Requested number of CSV data files: MAX
Actual number of CSV data files: 4
CSV File
From
CSV File
From
CSV File
From
CSV File
From
Name:
time:
Name:
time:
Name:
time:
Name:
time:
CSVDA001 % Discopens linked:
1991/09/17;10:20:00 To Time:
CSVDA002 % Discopens linked:
1991/09/17;10:40:00 To Time:
CSVDA003 % Discopens linked:
1991/09/17;11:00:00 To Time:
CSVDA004 % Discopens linked:
1991/09/17;11:20:00 To Time:
92.0
1991/09/17;10:40:00
92.8
1991/09/17;11:00:00
92.7
1991/09/17;11:20:00
92.8
1991/09/17;11:40:00
Using the Process Category Audit Report
You can use the Process Category Audit (PCAT) report to check the accuracy of the control file in
aggregating processes and discopen activity to process categories. If the aggregation does not
seem reasonable based on the report, review the PCAT statements in the control file and revise
the file if needed.
The report lists the processes aggregated into each process category as defined by the MeasTCM
control file. For each process, the report shows the number of CPU busy seconds and the number
of seconds the process was in the time boundaries set by the MeasTCM control file. In addition,
the report calculates the total CPU busy seconds for each process category.
Figure 12 (page 64) shows an excerpt of a sample Process Category Audit report. The Process
Category Audit report also contains the Figure 11 (page 63). If you have generated multiple CSV
files, the Process Category Audit report contains a set of audit reports, one for each CSV file
generated
Checking Category 98
Check the contents of the process category that contains all the remaining processes not aggregated
to other categories (_OTHER). If this category contains a unusually high number of unexpected
processes, consider performing one or all of these options:
•
Edit the control file to create a new category to accommodate these processes
•
Modify the existing categories to include this activity
Using the Process Category Audit Report
63
Figure 12 Process Category Audit Report
Process category audit report, application MDATA1
Measurement window: from 2002/09/17;10:20:00 to 2002/09/17;10:40:00
CSV Data file: CC20C001
Pcat
System
Program file name
Process CP PIN Busy secs Res secs
$VIRTUAL \BELGIUM $SYSTEM SYS00 OSIMAGE $VIRTUAL 0
1
.559 1200.00
1
1
.627 1199.95
2
1
.664 1199.92
3
1
.585 1199.94
\LILLI
$SYSTEM SYS01 OSIMAGE $VIRTUAL 0
1
.000 1199.99
1
1
.000 1199.99
2.437
DISC
\BELGIUM $SYSTEM SYS00 OSIMAGE $ADMIN
2
6
27.579 1199.89
33
1.307 1199.89
34
.299 1199.89
3
6
1.931 1199.94
33
.008 1199.93
34
.008 1199.93
$ADMIN1 2 10
.038 1199.89
41
.009 1199.89
42
.011 1199.89
3 10
1.145 1199.94
41
.105 1199.91
42
.002 1199.91
$CE
2
7
59.216 1199.89
35
3.149 1199.89
36
.930 1199.89
3
7
1.684 1199.94
35
.009 1199.93
36
.008 1199.91
$DATA
0 12
57.629 1200.00
35
9.855 1200.00
36
2.164 1200.00
1 12
6.349 1199.95
35
.008 1199.95
36
.009 1199.95
$SA
0 10
58.080 1200.00
31
.992 1199.98
32
.287 1199.99
1 10
.769 1199.95
31
.008 1199.95
32
.010 1199.95
$SYSTEM 0
9
78.885 1200.00
29
5.472 1199.98
30
2.069 1199.98
1
9
3.653 1199.95
29
.010 1199.95
30
.008 1199.95
$TANDEM 2
8
35.089 1199.89
37
.337 1199.89
38
.003 1199.89
3
8
.440 1199.94
37
.008 1199.91
64
Using MeasTCM
4 Getting Started With TCM
This chapter provides some guidelines to help you start working with TCM. It also describes the
TCM Initial menu, explains how TCM handles security issues, how to access TCM online help, and
how to load TCM models created by other users.
Guidelines
Before you start using TCM, the following guidelines can help you use the application effectively.
TCM Users
TCM has three levels of users:
•
The capacity planner has access to basic commands and Performance model screens.
•
The TCM administrator defines the apportionment methods.
•
The super user can modify almost any TCM screen or field and should understand Excel and
TCM internal structure.
TCM Online Help
Online help is available for all fields in TCM. To get help for a field, first position the cursor on
that field by pointing and clicking with a mouse or by using the arrow keys. Next, select Help,
TCM Help or press F1. For more information on the TCM help facility, see “Online Help” (page 71).
Selecting Ribbons, Tabs and Options
To select ribbons, tabs and options, either:
•
Point and click with a mouse
•
Hold down the Alt key and type the underlined letter that represents the tab option you want
TCM Status
To view the current status of any command you are executing or the complete calculation of the
calculating cell percentage, watch the TCM status bar in the lower left corner of your monitor.
Moving From Screen to Screen
To move between screens within TCM, select the name of the screen you want to view from the
Find tab. Separate worksheets are available for every screen in the Performance model.
Getting Started With Sample Data
To help you get started with TCM, use the sample performance data included with the product.
From the TCM Initial menu, you can choose to demonstrate either a Workload Apportionment
(WA) model or a Performance model.
Creating a Folder for Your Model
Before you begin working with TCM, you should have some knowledge of the TCM folder and file
structure.
Create a new folder for each application or set of applications you model using TCM. Figure 13
(page 67) shows a typical TCM folder structure. Custom folders are not required to be under the
Guidelines
65
TCM distribution folder, but this architecture is recommended. Each folder should include all the
files associated with the application:
•
Performance data files downloaded from the NonStop host system.
•
WA models and Performance models you create for that application to serve as templates
•
Apportionment tables associated with each model
•
WA models and Performance models created when you load sample data into the template
models
•
A capacity history database that organizes all the apportioned performance data for the
application
TCM File Names
Your TCM file names must follow the rules of your workstation operating system with these additional
guidelines:
•
TCM file names cannot have embedded spaces.
•
TCM file names cannot have apostrophes (’).
Figure 13 (page 67) shows the TCM folder structure.
66
Getting Started With TCM
Figure 13 TCM Folder Structure
TCM Initial Menu
The TCM Initial menu gives you several choices. Descriptions of these choices follow.
TCM Initial Menu
67
Workload Apportionment Options
Use the Workload Apportionment (WA) options to apportion sample data from processoriented
to transaction-oriented information before doing what-if analysis by using the Performance model.
Demonstrate Option
When you choose the Demonstrate option, TCM displays an apportioned WA model that you can
use for practice. You can make changes in the sample model, but you cannot save the changes.
Create a New WA Model Option
When you choose the Create a New WA Model option, you create a new model from your own
CSV data. You are prompted to select the CSV data to load into the new model. You also need
to apportion the data.
Work With an Existing Model Option
When you choose Work with an Existing WA Model, you can review a WA model that was
previously created as well as the history of the model. You can also load multiple samples into an
apportioned model and create several models to be part of a model set. A model set is a group
of models that use the same apportionment method but different CSV data.
Loading TCM Models Created by Other Users
If you want to load a TCM model created by another user, do not open the workload apportionment
table (.WWA file) or the performance model (.WPM file) as you would normally do for a model
that you created.
To load a TCM model created by another user:
68
Getting Started With TCM
1.
From the “TCM Initial Menu” (page 67), select Work with an Existing WA Model or Work
with an Existing Performance Model and then click OK.
The Open PM Model or Open WA Model dialog box appears.
2.
3.
4.
If you want to view all possible Workload Apportionment models, type *.SWA in the Model
to Open field. Type *.SPM to see all possible Performance models.
Select a file from the list or enter the file name you want to open, including its .SWA or .SPM
extension.
Click OK. TCM loads the model file (rather than the Excel workspace file).
Performance Model Options
After you have worked with the WA model and created an apportionment method that is reasonable,
you can use the Performance model to answer what-if questions about system capacity and the
performance of your application. For more information on determining whether an apportionment
method is reasonable, see “Checking an Apportionment Method” (page 83).
Demonstrate Option
When you choose the Demonstrate option, TCM displays a Performance model that you can use
for practice. You can make changes in the sample model, but you cannot save the changes.
Create a New Performance Model Option
When you select Create a New Performance Model, you are prompted to select the WA model
to load from a list of available WA models.
Work with an Existing Performance Model Option
When you select Work with Existing Performance Model, you can review or modify an existing
Performance model. You can also use an existing Performance model to add new baseline data
if you want to retain your what-if conditions but change the baseline data.
TCM Expert Option
TCM Expert provides a way to do capacity planning when you have limited knowledge of the
application design or architecture. To access the Expert features of TCM, click the TCM Expert
button. When you click this button, TCM adds the TCM Expert tab to the WA model tabs. For a
description of TCM Expert, see Chapter 10: “Using TCM Expert”.
Security
TCM has security features to prevent you from unintentionally corrupting algorithms or sample
data. Password-protected user authorization levels are built into the product to:
•
Restrict access to commands that are particularly crucial in the modeling process.
•
Restrict modification of specific fields in TCM models. Only highlighted fields in TCM can be
directly modified. Most of the fields are protected and cannot be changed. Authorization
levels are used to control the number of highlighted fields in the model. User modifiable and
nonmodifiable fields are a different color.
User Authorization Levels
TCM has three authorization levels associated with the three types of TCM users.
Capacity Planner
The capacity planner is the most restricted authorization level in TCM. It is not password-protected.
It provides access only to the basic TCM commands, enabling you to define and analyze alternative
capacity management approaches using existing custom models.
Security
69
If you entered an incorrect, blank, or null password, your authorization level changes to capacity
planner.
TCM Administrator
The TCM administrator is the second-highest level. It is password-protected. TCM administrators
can do everything that capacity planners can do, and can also perform TCM administrative
functions, such as creating apportionment tables.
The default password is “admin.” This password is not case-sensitive, and both the WA and
Performance models have the same default passwords.
Super User
The super user is the highest, most unrestricted level in TCM. It is also passwordprotected. Super
users can do everything that TCM administrators can do, and can also enter the Excel program
and remove the protected status of fields in TCM models. Because the ability to modify any field
makes it easier to corrupt a model inadvertently, users with this authorization level must exercise
caution when working with unprotected models.
The default password is “super.” This password is not case-sensitive, and both the WA and
Performance models have the same default passwords.
Changing Authorization Levels
To change authorization levels:
1. Open a WA model or a Performance model.
2. Either:
3.
•
Select Options > Change Authorization Level. The TCM Password dialog box appears.
•
Click the User Authorization Level button located at the top left corner. The TCM Password
dialog box appears.
At the prompt, enter the password for the new authorization level if one has been set. TCM
calculates the values to reflect the changes.
The default password for the administrator authorization level is “admin”. The default password
for the super authorization level is “super”. The default passwords are not case-sensitive, and
both the WA and Performance models have the same default passwords.
4.
Click OK.
When you enter the appropriate password, TCM changes your authorization to the level that
corresponds with the password you entered.
Passwords
The distribution version of TCM contains the preassigned passwords for the top two authorization
levels: TCM administrator (“admin”) and super user (“super”). Both the WA and Performance
models have the same default passwords.
You can establish separate passwords for both the WA and Performance model at the two
authorization levels. That is, you can have four separate passwords:
•
TCM administrator WA password
•
TCM administrator PM password
•
Super-user WA password
•
Super-user PM password
For example, you can change the TCM administrator WA password to “banana,” the TCM
administrator PM password to “pumpkin,” the superuser WA password to “squash,” and the
70
Getting Started With TCM
superuser PM password to “orange.” Only the TCM administrator and superuser authorization
levels can change the default passwords.
CAUTION: If multiple users will be working with TCM, the default passwords should be changed
to maintain system security.
Changing Passwords
To change passwords:
1. Log on as an administrator or super user.
2. Open a WA model or a Performance model.
3. Select Options > Change Password. The Change TCM Password dialog box appears.
4. Enter your old password (or the default password) in the Old Password field.
5. Enter the new password you want to use in the New Password field.
6. Click OK. A dialog box confirms the change.
Online Help
TCM offers online, context-sensitive help messages that provide information on any field in the WA
model or Performance model.
Getting Help for a Specific Field
To get help for a specific field:
1. Select the field about which you want more information.
2. Either:
•
Select Help > TCM Help.
•
Press the F1 function key.
Getting Help for Function Keys
For help on commands available with the Function Keys, select Help > Function Keys. For a list of
TCM function keys and their meanings, press the Shift key and F1 function key simultaneously.
For information about the TCM environment, select About Help. TCM then displays its version
number, its copyright date, the operating system environment, the version of Excel, the amount of
total and available memory, and whether a math coprocessor is present.
Customizing Help Messages
If you have a help compiler, you can change the text of any help message to customize it. The text
for TCM help messages is contained in three files: tcmhpm.txt for the Performance model, tcmtxt.hwa
for the WA model, and tcmtxt.hxp for TCM Expert.
To customize help messages:
1. Use any text editor installed on your workstation to open the help file (tcmhpm.txt, tcmtxt.hwa,
or tcmtxt.hxp).
2. Locate the name of the field with the help message you want to change by scrolling through
the file. The names of all fields are preceded by asterisks (*).
3. Edit the text and save the file.
4. Convert the revised file to a format understandable to Microsoft Windows.
Online Help
71
5 Creating a WA Model
This chapter describes how to create a customized Workload Apportionment (WA) model for a
new application (or set of applications). It is assumed in the following instructions that a Measure
sample has been collected on the NonStop host system, and that a performance sample has been
generated by MeasTCM, downloaded to the PC, and loaded into TCM. This chapter also includes
a sample WA model for a non- Pathway application.
For detailed information on selecting menus and menu items on the WA model screens, see
“Workload Apportionment Ribbon” (page 126).
Overview
You use the Workload Apportionment (WA) model to translate process category performance data
collected and summarized on the NonStop host system into transaction-oriented performance data
that can be measured in terms of CPU and disk consumption. To perform its work, the WA model
uses apportionment tables that specify how CPU and disk consumption should be charged to
transactions and how to compute the number of transactions.
The WA model is used to update the Capacity History database so that the capacity planner can
effectively track transaction-based performance data and check apportionment methods for
reasonableness. A model can be viewed as reasonable if CPU and disk demands per transaction
are relatively constant across many performance samples (CSV files) with varying transaction mixes
and throughput levels.
After you apportion performance data using the WA model, you can load it into the TCM
Performance model for more analysis. For more information about this process, see Chapter 6:
“Creating a Performance Model”.
Apportionment Tables
The TCM WA model uses two tables to determine how to apportion process category performance
data to transactions. These tables are contained in a file with an .AWA extension. The first table
is called the Apportionment Weights table. It indicates how to apportion the CPU and disk seconds
of process categories to transactions. The second table is called the Transaction Count table. It
specifies how to count transactions (how to compute the number of transactions in a performance
sample from the number of messages that process categories receive, send, or both).
Together, these two tables completely describe the apportionment method that TCM uses. Defining
these tables is a major step in creating a WA model.
In general, TCM makes the following assumptions when creating default apportionment tables
based on the performance data sample you have loaded:
•
The transaction count for a specific transaction equals the sum of the messages received by
its servers.
•
The CPU and disk seconds consumed by process categories are spread evenly (on a
per-transaction basis) across all transactions. In other words, if transactions Txn1 and Txn2
both use the TCP1 requester, the WA model assumes that they both consume the same amount
of TCP1 resources per transaction unless you indicate otherwise. This assumption applies for
nondisk categories only.
NOTE: Because Measure provides DISOPEN information, TCM accurately apportions disk activity
without requiring any additional input in the apportionment tables.
Example of an Apportionment Weights Table
The Apportionment Weights table is a matrix of process categories (rows) versus transactions
(columns). The weighting factors are relative. That is, the important information is the ratio of the
72
Creating a WA Model
numbers in a given row. The numbers can be decimal fractions, such as 0.5. The numbers in one
row have no effect on any of the other rows. The best way to read the table is across.
In the following table, the CPU and disk consumption cost of the linehandler category is spread
equally (on a per-transaction basis) between Withdrawal and Deposit. Deposit Server is charged
entirely to Deposit. TCP is charged to Withdrawal and Deposit with relative weights of 2 and 1,
respectively. TCP must do twice as much work for a Withdrawal transaction as for a Deposit
transaction.
Withdrawal
Deposit
Line handler
1
1
Deposit Server
0
1
TCP
2
1
The following guidelines apply to disk and TMF process categories:
•
All transaction values for the single disk process category (type D category) in the
Apportionment Weights table should be 1.
•
All transaction values for the single TMF process category (type T category) should be 1 for
audited transactions or 0 for nonaudited transactions.
If all transaction values for any category are 0, an error message appears because the process
category CPU and disk seconds must be allocated to a transaction.
TCM Expert
You can use the TCM Expert feature to create the Apportionment Weights table automatically. For
more information, see “Generating Expert Apportionment Weights” (page 183).
Example of a Transaction Count Table
The starting point for transaction count analysis is the process flow diagram. Arrows indicate a
transaction’s path through the process categories. Each transaction has its own set of arrows.
Figure 14 (page 73) shows a sample process flow diagram.
Figure 14 Process Flow Diagram
The Transaction Count table for this example calculates the transaction counts for Deposit and
Withdrawal:
•
Rows correspond to process categories.
•
Below each transaction are Rcv and Send columns.
•
Table entries are coefficients (multipliers) for category Rcv/Send counts.
Apportionment Tables
73
The Rcv/Send counts for each transaction name are multiplied by the user-entered coefficients and
summed to produce a transaction count. In the example, the number of Deposit transactions is set
equal to 1 times the messages received by the Deposit category.
The following guidelines apply to the Transaction Count table:
•
Entries can be positive or negative.
•
Entries can be decimal fractions, such as 0.5.
•
Transaction counts are calculated as a sum of Send/Receive message counts multiplied by
the entries in the two columns below the transaction name.
For example, if there are 2 sends from the Deposit category for each Deposit transaction, you
would enter 0.5 in the table rather than a 1. Transaction counts are computed by multiplying
message counts by the numbers in the table. Therefore, two messages per transaction requires
0.5 in the table, not 2.
•
Most entries of the Transaction Count table are zero (0). This scenario is typical of real world
situations. To count transactions, you usually do not have to trace every interprocess message.
You need only identify the places where a simple relationship exists between category message
traffic and transaction counts.
The Transaction Count table for the example follows:
Once created, the TCM administrator can modify the default apportionment tables to create one
or more apportionment methods that are well suited to the particular application. The tables are
then saved as part of your WA model, which you can use to apportion a variety of performance
data samples.
Transaction Count Table Versus Transaction Count File
CAUTION: Modifying these values is not recommended. Edit these protected cells carefully in
order not to overwrite some of the default formulas.
74
Creating a WA Model
NOTE: TCM enables you to modify specific cells in the WA workbook. TCM returns an error "To
modify a protected cell, first remove protection using the Unprotect Sheet command (Review tab,
Changes group)" when you try to edit any of the values in protected cells of the WA model
workbook. Only TCM administrators are able to unprotect and edit admin cells. To edit the protected
cells:
1. Change the Authorization level to "super" using the Options->Change Authorization Level
button.
2. Enable the Excel default tabs using the Options-->Enter Excel button. After changing the
authorization level to "super" the "Enter Excel" choice is enabled (Options is grayed out for
non-super authorization levels).
3. Enter your changes: TCM now allows you to edit the protected cells in the WA model.
4. Return to the TCM custom ribbon using the Home->Enter TCM button. This takes you back into
TCM and the Excel default tab is hidden again.
You can create a Transaction Count file instead of using the counts in the Transaction Count table.
This feature is useful if you know how many transactions your application processes. For example,
you might be able to create a simple program to parse your application’s statistics or log file to
determine the number of transactions that your application processes. Alternately, you can use
Measure user-defined counters to determine the number of transactions processed by your
application. You can create the file on the NonStop host system and download the file to the custom
folder, or you can create the file directly on the PC.
When TCM loads a CSV file, it checks to see if the corresponding Transaction Count file exists. If
the Transaction Count file exists, TCM uses the Transaction Count file for the transaction counts
and uses the Transaction Count table if any transaction counts are missing in the Transaction Count
file. Thus, you can use both a Transaction Count table and Transaction Count files. If you use both,
the values in the Transaction Count files supersede any values in the Transaction Count table.
For example, suppose your application has 20 transactions, and you have counts for 8 of the
transactions. You can use Transaction Count files to indicate the counts for these 8 transactions.
You should not put blanks in the Transaction Count files. For the 12 transactions not listed in the
Transaction Count files, TCM uses the Transaction Count table for the counts.
Transaction Count File Naming Convention
Transaction Count file names are patterned after the CSV file name. The Transaction Count file
has the same name as the CSV file except the extension is .TCF instead of .CSV. For example, the
CSV file EXAMPLE1.CSV would be EXAMPLE1.TCF. The Workload Apportionment model uses the
counts in the Transaction Count file instead of its generated formulas to calculate the number of
transactions. When you load category data, TCM automatically detects if you have a Transaction
Count file and loads it.
Transaction Count File Format
The Transaction Count file has the following format:
TXNCNT
txn-name-1, txn-cnt-1, comment text
txn-name-2, txn-cnt-2, comment
For example, the following Transaction Count file is valid:
TXNCNT
BIG, 500, You have 500 transactions of type BIG
ST1, 10, You have 10 ST1 transactions
Blank lines are not allowed in the file. To enter comments, enter a comma following the transaction
count number and type the comment.
If a Transaction Count file exists in the custom model folder, TCM uses the Transaction Count file.
If no .TCF file exists, TCM uses the Transaction Count table.
Apportionment Tables
75
WA Model Flowchart
Figure 15 (page 76) outlines the major steps involved in creating a WA model. This section
describes each of these steps.
Figure 15 Creating a WA Model
Loading Performance Data Into TCM
TCM uses performance data samples and models as a basis for its capacity planning. Before you
can model systems with TCM, you must download sample performance data to your PC and load
the data into TCM.
Downloading Performance Data Samples
To create models using TCM, the sample performance data must be collected from the NonStop
host system using Measure and formatted by MeasTCM.
Once the sample performance data has been summarized by MeasTCM in a CSV file, you need
to download it from the host to the workstation and load it into TCM.
To download performance data samples to the PC, follow the download procedure you normally
use in Windows. All CSV files for the same application or set of applications should be kept in the
76
Creating a WA Model
same folder, and all CSV files must have the extension .CSV. TCM detects any truncated data and
issues an error message.
NOTE:
All CSV files must have the extension .CSV.
Loading Samples Into TCM
To load a sample into TCM:
1. From the “TCM Initial Menu” (page 67), select Create a New WA Model.
The Specify Custom Directory dialog box appears.
2.
Specify the custom folder location of your CSV files.
Select the custom folder of your CSV files and double-click the custom folder name. When you
double-click on name, TCM updates this name in the custom folder field of the dialog box and
also makes this folder the location of your working session.
3.
Click OK to close the dialog.
You can now begin using TCM Expert.
4.
5.
Select a CSV file and click OK.
•
If an Apportionment Weights table exists for the model, TCM loads the CSV file and
displays the unapportioned data in the Category Demand Report screen.
•
If no Apportionment Weights table is available for the selected model, a warning dialog
advises you that TCM cannot apportion the model because no apportionment table exists
in your custom folder. Click OK. The TCM Password dialog box appears. Log on as TCM
administrator or super user and click OK. (For more information about this step, see
“Changing Authorization Levels” (page 70).) TCM generates a default apportionment
table for the model and displays the unapportioned data in the Category Demand Report
screen.
At this point, the performance sample has been loaded into the distribution WA model, and
a new WA model has been created with the name of the downloaded file and an .SWA
extension. However, this new model has not yet been customized for your particular application.
The Category Demand Report shows aggregate values for each category defined in MeasTCM,
totalled over all processes in the category:
•
Messages received
•
Messages sent
•
CPU busy time
•
Cache hits
•
Cache misses
•
Disk read busy time
•
Disk write busy time
You are now ready to apportion the data and create a WA model to obtain transaction information.
Modifying the Apportionment Weights Table
TCM automatically generates the application-specific default Apportionment Weights table and
Transaction Count table when you create a new WA model. A sample default Apportionment
Weights table appears in Figure 16 (page 78).
Modifying the Apportionment Weights Table
77
Figure 16 Workload Apportionment Weights Table
The default Apportionment Weights tables created by TCM provide an excellent starting point for
fine tuning the WA model to your application’s particular architecture. However, to customize the
WA model to best reflect an application’s characteristics, the TCM administrator might need to
modify these tables. The tables also need to be modified if you want to experiment with more than
one apportionment method for your application or if you want to change an existing apportionment
method because of changes in the application’s architecture.
The procedure for modifying a model’s apportionment tables is the same whether you are modifying
the default tables of a new model or changing the tables of an existing model.
To modify the Workload Apportionment Weights table:
1. Open a WA model if one is not already open.
2. Select Options > Change Authorization Level and log on as an administrator or superuser. For
more information about this step, see “Changing Authorization Levels” (page 70).
3. Select Find > Apportionment Weights. If this option is unavailable, select Calculate Now from
the Options tab to update the table. Then select Find > Apportionment Weights. The Workload
Apportionment Weights table appears.
4. Select Options > Unprotect Admin Fields to unprotect the Workload Apportionment Weights
table so you can change its entries. (They are normally protected against modification.)
The entries that you can modify are highlighted.
5.
6.
7.
8.
Change the entries in the Apportionment Weights table to best reflect your application’s
characteristics. These entries indicate the relative weights to be assigned to transactions when
the CPU and disk seconds process categories are apportioned.
When you are done, select Options > Protect Admin Fields to protect the apportionment tables.
Although this step is optional, it is good practice. It safeguards your data from unintentional
corruption.
Select Options > Calculate Now to update the table.
If you want to save the file, select Save or Save As under the File tab. See “Saving the Tables”
(page 79).
Modifying the Transaction Count Table
This procedure describes how to modify the default Transaction Count table. The Transaction Count
table tells TCM how to map category message counts to transaction counts. In many cases, you
can derive the number of messages sent or received by a process category or some combination
of categories.
78
Creating a WA Model
NOTE: You can use a Transaction Count file instead of a Transaction Count table to count
transactions processed by your application. For information on the Transaction Count file, see the
subsection “Transaction Count Table Versus Transaction Count File” (page 121).
If you are using a Transaction Count file, each entry in the Transaction Count table can be zero
(0).
1. Open a WA model.
2. Log on as an administrator or super user. For more information about this step, see “Changing
Authorization Levels” (page 70).
3. Select Find > Transaction Count Table. If this option is unavailable, select Options > Calculate
Now to update the table. Then select Transaction Count Table under the Find tab again. The
Transaction Count table appears. Figure 17 (page 79) shows a default Transaction Count
table.
Figure 17 Default Transaction Count Table
4.
5.
6.
7.
8.
Select Options > Unprotect Admin Fields to unprotect the Transaction Count Table so you can
change its entries. (They are normally protected against modification.)
Change the entries in the Transaction Count table to best reflect your application’s
characteristics.
When you finish, select Options > Protect Admin Fields to protect the apportionment tables.
Although this step is optional, it is good practice. It safeguards your data from unintentional
corruption.
Select Options > Calculate Now to update the table.
If you want to save your modifications to the file, select Save or Save As under the File tab.
See “Saving the Tables” (page 79) in the next section.
Saving the Tables
If you do not save the apportionment tables, they are automatically saved when you save the entire
model. However, it is recommended that you save the tables as soon as they are created.
To save the tables:
Modifying the Transaction Count Table
79
1.
Save the modified apportionment tables by selecting Save or Save As under the Find tab.
The Save As option allows you to change the name of the apportionment tables.
2.
3.
4.
5.
If you chose Save, the TCM Save dialog box appears. Choose the menu item you want and
click Continue.
•
Select Workload > Apportionment Model files to save everything that is open in this
session.
•
Select Apportionment Tables to save the apportionment tables. This option is available
only when apportionment tables are open in the current session.
•
Select Capacity History to save the capacity history file. This option is available only when
capacity history files are open in the current session.
TCM saves the files.
If you select Save As, the TCM Save As dialog box appears. Select the appropriate option
and click Continue.
•
Select Workload > Apportionment Model files to save everything that is open in this
session. (Skip this step if Workload Apportionment Model files do not appear.)
•
Select Apportionment Tables to save the apportionment tables. This option is available
only when apportionment tables are open in the current session.
•
Select Capacity History to save the capacity history file. This option is available only when
capacity history files are open in the current session.
In the TCM Save As dialog box, enter a new name to replace the default name displayed
and then click Yes.
Default file names contain the first eight characters of the name of your application, or model,
with an .AWA extension. The file is saved with an .AWA extension in your folder. For example,
in the tutorial’s Example application, the apportionment tables file is named EXAMPLE.AWA.
6.
TCM saves the files.
Reviewing Apportionment Results
Once the apportionment formulas have been generated, you can review the apportioned data to
check how well the apportionment method works. (To determine the reasonableness of the method,
however, you need to create several models for a variety of performance data samples. For more
information, see “Checking an Apportionment Method” (page 83).) You can also update the
Capacity History database to maintain a historical record of your apportioned data.
To review apportionment results:
80
Creating a WA Model
1.
2.
Check that the CPU and disk apportionments per transaction are in line with what you would
expect. For example, you need to validate your apportionment method if your results show 2
seconds of CPU time for a transaction that you expect uses 500 milliseconds of CPU time.
From the Find menu, select CPU, Disk Read, or Disk Write, under the Work Apportionment
option, to view each apportionment in detail. Figure 18 (page 81) shows a sample CPU
Workload Apportionment screen.
Figure 18 CPU Workload Apportionment Screen
3.
Select Find > Workload Summary to get a summary of transaction costs in terms of time.
Figure 19 (page 81) shows a sample Workload Summary screen.
Figure 19 Workload Summary Screen
Updating the Capacity History Database
Once you have created a WA model, update the Capacity History database so you can track
your apportionment methods and samples.
To update the Capacity History database, select History > Update History.
Figure 20 (page 82), Capacity History Screen shows a sample Capacity History screen after it
was updated with the default apportionment tables created for the EXAMPLE1 performance sample.
The Mix column shows the percentage of transactions in the sample. This information is useful for
validation.
Updating the Capacity History Database
81
Figure 20 Capacity History Screen
Saving a WA Model
Save a model as a template for apportioning additional performance samples by saving the model’s
apportionment tables and formulas. Create a new model if the apportionment method has been
changed for an existing model or customized for one or more applications for the first time.
To save a Workload Apportionment model with its existing name:
1. Select File > Save.
2. The TCM Save dialog box appears. Select the option you want and click Continue.
3.
4.
•
Select Workload > Apportionment Model files to save everything that is open in this
session.
•
Select Apportionment Tables to save the apportionment tables. This option is available
only when apportionment tables are open in the current session.
•
Select Capacity History to save the capacity history file. This option is available only when
a capacity history file is open in the current session.
TCM saves the files.
To exit the WA model, select File > Exit.
To save a Workload Apportionment model with a different name:
1. Select File > Save As.
2. The TCM Save As dialog box appears. Select the appropriate option and click Continue.
3.
•
Select Workload > Apportionment Model files to save everything that is open in this
session.
•
Select Apportionment Tables to save the apportionment tables. This option is available
only when apportionment tables are open in the current session.
•
Select Capacity History to save the capacity history file. This option is available only when
capacity history files are open in the current session.
In the TCM Save As dialog box, enter a new name to replace the default name displayed
and then click Yes.
Default file names contain the first eight characters of the name of your application or new
apportionment tables file with a .WWA extension. The file is saved with a .WWA extension
in your folder. For example, in the tutorial’s Example application, the model file is named
EXAMPLE.WWA. The WA spreadsheet is saved in a file with an .SWA extension.
4.
5.
82
TCM saves the files.
To exit the WA model, select File > Exit.
Creating a WA Model
Checking an Apportionment Method
Once an apportionment method has been created by modifying either the default apportionment
tables of a new model or the apportionment tables of an existing model, and the apportionment
formulas have been generated, you need to analyze the results to determine the reasonableness
of the method.
In general, an Apportionment Weights table can be viewed as reasonable if CPU and disk demands
per transaction are relatively constant across many performance samples with varying transaction
mixes and throughput levels. The requirement for a variety of transaction mixes is crucial. If mixes
do not vary, any apportionment method will appear to be reasonable but might not be.
To make sure a method is reasonable, first save a model for each apportionment method and
follow the steps in “Updating History With Several Examples” (page 83).
Because checking an appropriate apportionment method requires several performance samples,
the following procedure is based on the assumption that you have already collected these samples
on the NonStop host system using Measure and processed them using MeasTCM. The number of
samples should be at least 4 to 5 times the number of defined transactions. For example, if your
application has 3 transactions named Withdrawal, Deposit, and Customer Update, collect at least
12 to 15 samples. The samples should have different transaction mixes and be at varying utilizations.
Updating History With Several Examples
Creating additional WA models involves loading additional performance data samples into your
WA model for apportioning. This process allows you to apportion a variety of data samples to
determine the reasonableness of the apportionment method. Creating additional models allows
you to update the Capacity History database with many samples, to select appropriate samples
for modeling, and to create baseline data for input to the Performance model.
The following procedure results in one or more saved, apportioned WA models with an updated
history:
1. To download performance data samples to the PC, follow the download procedure you
normally use in Windows. All CSV files for the same application or set of applications should
be kept in the same folder, and all CSV files must have the extension .CSV. TCM detects any
truncated data and issues an error message.
2. If you are already in the WA model, load a CSV file into the current model. (See page “Loading
a CSV Sample Into a WA Model” (page 241).)
If you are at the “TCM Initial Menu” (page 67):
1. Select Work With Existing Model. The Open WA Model dialog box displays the available
WA models.
2. Log on as an administrator or super user. For more information about this step, see “Changing
Authorization Levels” (page 70).
3. From the Models field, select an existing apportioned model to use as a template for all the
new WA models that you want to create.
4. Click Update History and Display List of CSV Files. Then click Open.
The Create New WA Model dialog box appears.
5.
Select the CSV file or files to load and click OK.
When you are finished, each data sample will have a corresponding sample WA model in
the folder.
To update history with several examples:
1. Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box appears.
2.
Select a custom folder and click OK.
Checking an Apportionment Method
83
3.
4.
5.
6.
7.
8.
From the Expert tab to the TCM Expert Parameters, enter in Check History Over Last the number
of months required to cover all dates when the samples were taken.
Select Expert Update History with Selected CSVs. The Update History with Selected CSV Files
dialog box appears. By default, the CSV files that have not yet been used to update capacity
history appear in the Selected CSV Files list.
Select a History database from the History Database list. Select from the list of History files,
keep the default History name, or enter a new name.
Select an apportionment table from the Apportionment Table list. Select from the list of
apportionment tables or keep the apportionment table name.
If you want, you can remove CSV files from the list or add them to it to update capacity history:
•
To select a CSV file, click a file name in the Unselected CSV Files field and then click
Add. The file name appears in the Selected CSV File list.
•
To clear a CSV file, click the file name in the Selected CSV File list and click Remove.
The file name appears in the Unselected CSV File list.
•
To get information on a specific CSV file, select a CSV file name in the Selected CSV
Files list and click CSV Info.
Click Update History.
TCM Expert updates capacity history and shows the updated file.
If TCM Expert finds inconsistent transaction costs in the capacity history, it reports this
information to you in a dialog.
For more information, see “Updating Capacity History With Selected CSV Files” (page 186).
Analyzing Capacity History
The Capacity History database is a valuable tool in determining the reasonableness of the
apportionment method. From it, the capacity planner can analyze the apportioned data in each
sample model and eliminate unrepresentative sample models, as well as identify the apportionment
method that yields the most consistent CPU and disk demands.
To analyze capacity history:
1. Open a Workload Apportionment model.
2. Select Find Capacity History, Database. The Capacity History screen appears.
If the model has more than one Capacity History database, the Find Capacity History dialog
box appears. Select a Capacity History file from the Select field and click Find. The Capacity
History screen appears.
3.
4.
Analyze the historical variance of the CPU and disk demands for the sample data. Delete or
ignore unrepresentative date samples, which might have been taken when data communications
lines were inoperative or during CPU failures.
•
To delete records, select at least one delete criterion in a highlighted field and then select
History > Delete History.
•
To sort records, select History > Sort History, click the Sort by Transaction or Sort by
Sample button, and then click OK.
Select the apportionment method that yields relatively consistent CPU and disk demands across
all the representative samples.
Non-Pathway Example
The following example describes an apportionment method for a non-Pathway automated teller
machine (ATM) application.
Three major transaction types are: ATM, Non-ATM, and Foreign. An ATM transaction is a transaction
in which a bank customer performs an ATM function on an ATM that belongs to the bank. A
84
Creating a WA Model
Non-ATM transaction is a transaction in which a bank customer performs an ATM function on an
ATM that belongs to another bank. The Foreign transaction is a transaction in which another bank’s
customer performs an ATM function on an ATM.
Transactions enter the system at either the Device Handler or the Gateway Interface. A Router
sends all transactions to Authorization. From Authorization, they return to the Router and are sent
to Host Interface or Gateway Interface. In either case, they return to Router, visit Authorization
again, are routed back to the point of entry, and depart from the system. Figure 21 (page 85)
shows a process flow diagram for this application.
Figure 21 Process Flow Diagram for a Non-Pathway Application
In Figure 22 (page 85), arrows indicate one Send and one Receive in each direction except for
the arrows from the Router to the Authorization. These arrows (for all three transactions) indicate
two Sends and two Receives in each direction.
Figure 22 Exact Paths for All Transactions
ATM: Device Handler → Router → Authorization → Router → Host
Interface → Router → Authorization → Router → Device Handler
Non-ATM: Gateway Interface → Router → Authorization → Router
→ Host Interface → Router → Authorization → Router → Gateway
Interface
Foreign: Device Handler → Router → Authorization → Router →
Gateway Interface → Router → Authorization → Router → Device
Handler
Performance data for all these categories is collected on an HP system using Measure and is
summarized using MeasTCM. An Other category contains everything else.
Non-Pathway Example
85
In each category, the per-transaction demand is estimated to be the same for all transaction types.
Workload Apportionment Weights Table
The Workload Apportionment Weights table for the application follows:
Workload Apportionment Weights Table
Category Name
Type
ATM
Non-ATM
Foreign
Host
S
1
1
0
Gate
R
0
1
1
Device Handler
R
1
0
1
Router
O
1
1
1
Authorization
O
1
1
1
Other
O
1
1
1
Transaction Count Table
The Transaction Count table for this non-Pathway application follows:
Transaction Count Table
Transactions →
ATM
Non-ATM
Foreign
Category Name
Type
Rcv
Send
Rcv
Send
Rcv
Send
HOST
S
0
0
0
0
–1
0
GATE
R
–1
0
0
0
0
0
DH
R
0
0
–1
0
0
0
ROUT
O
0
0
0
0
0
0
AUTH
O
0.5
0
0.5
0
0.5
0
OTHER
O
0
0
0
0
0
0
NOTE: The Transaction Count table is not necessarily unique. Frequently, there are several ways
to set up the Transaction Count table to achieve correct transaction counts. Several acceptable
alternate Transaction Count tables could be made for this example.
86
Creating a WA Model
6 Creating a Performance Model
This chapter describes how to create a Performance model (PM) for your application or set of
applications. The Performance model enables you to ask questions about system performance
under changing circumstances, such as transaction rates, response time constraints, and CPU type.
As a capacity planner, you often have a number of options regarding the system’s response to
increased workload. For example, you can add hardware to reduce CPU utilization and improve
response time. Or you can leave hardware unchanged and tolerate longer response times.
With the Performance model, you can explore possibilities by imposing constraints on the modeling
process. You can impose constraints on either hardware configuration or performance factors. For
instance, you can ask what will happen to response time if the average transaction rate doubles
but the hardware configuration remains the same. Or you can ask what is the lowest-cost
combination of CPUs and disk drives that will maintain an average response time below two
seconds.
Because the TCM Performance model bases its estimates on selected baseline data, it is important
to select a representative but conservative WA model for the Performance model to use as its input.
To select a representative model, analyze capacity history and discard samples with inconsistent
CPU and disk demands.
Creating a New Performance Model
In the following procedure, it is assumed that you have checked the WA model for the application
for reasonableness and that you have selected a representative WA model as the basis for your
analysis. For more information about checking the WA model for reasonableness, see “Checking
an Apportionment Method” (page 83).
To load the baseline data to create a new Performance model:
1. Launch TCM. The “TCM Initial Menu” (page 67) appears.
2. Select Create a New Performance Model and click OK.
The Specify Custom Directory dialog appears.
3.
4.
Specify a custom folder and click OK.
The Create New Performance Model dialog box appears. Select whether to load the
Performance model from a WA model or a CSV file and one of:
•
A WA baseline file (when loading from a WA model)
•
A CSV file and an apportionment method
When you click the WA Model button, the WA Baseline File list appears, and the Using
Apportionment field is disabled. When you click CSV File, CSV files are shown instead
of WA Baseline files, and the Using Apportionment field is active.
Creating a New Performance Model
87
5.
When you are finished, click OK.
TCM performs the necessary calculations and then displays the Capacity Baseline—Actual
screen. You are now ready to model scenarios. Figure 23 (page 89) shows a sample Capacity
Baseline—Actual screen.
If TCM encounters an unknown CPU in the WA model or CSV source file during calculation,
it recalculates the sheet and saves the new file. To ensure proper Performance Model
recalculation, however, you must enter the new CPU type into the CPU Conversion Factors
screen.
88
Creating a Performance Model
Figure 23 Capacity Baseline—Actual Screen
Working With an Existing Performance Model
1.
2.
3.
Start TCM. The “TCM Initial Menu” (page 67) appears.
Select Work with an Existing Performance Model and click OK.
The Open PM Model dialog box appears so you can specify which Performance model to
open and optionally which WA model to load into that Performance model. Select:
•
The custom folder.
•
Which model to open–either from a list of available Performance models in the selected
custom folder or by entering the name directly into the Model to Open field. These are
the most common ways to load a Performance model.
If you want to bring new WA data into the Performance model, use the remaining options
to specify the WA model you want to load into the Performance model. Choose one or
more of the following:
◦
WA baselines to load.
◦
Whether to Exit When Done. (This opens the Performance model, loads the WA
baseline if one was chosen, automatically saves the new model, and exits without
displaying the newly created Performance model.)
◦
Whether to display a list of WA baselines.
Working With an Existing Performance Model
89
WARNING! In the Excel 2003 version of TCM, the Custom Directory name text
may appear corrupt.
4.
When you finish, click Open.
TCM shows the Capacity Baseline—Actual screen. You are now ready to model scenarios.
Figure 23 (page 89) shows a sample Capacity Baseline—Actual screen.
Modifying the Planning Unit
Often a capacity planner needs to model transaction throughputs in units other than transactions
per second (TPS). The planning unit for throughput can be changed by entering another value in
the Planning Unit field on the Capacity Baseline—Actual screen. You can model transactions in
seconds, minutes, hours, days, or months.
To modify the planning unit:
1. Select the highlighted Planning Unit field on the Capacity Baseline—Actual screen.
2. Enter the new unit of time (sec, min, hour, day, month) and press Return.
3. Select Options > Calculate Now (function key F9). To finish entering your data, you must press
Return before selecting Calculate Now or pressing a function key.
90
Creating a Performance Model
Modifying Percentile Response Times
TCM can provide the following results for OLTP transactions: average, 90th, 95th, or 99th percentile.
The default is average. If you change from the default (average) to percentile response times, TCM
uses percentile response time for OLTP transactions in all screens of the Performance model.
For example, if the response time is 1 second and average response time is selected, the average
response time of transactions is 1 second. If 90th percentile is selected, 90 percent of the transactions
have a response time of less than or equal to 1 second.
To change to a different response time method:
1. Open a Performance model.
2. Select Options > Select Response Time Method. The Select Response Time Method dialog box
appears.
3. Select the response time method you want (Average is the default) and click OK.
4. A confirmation dialog appears. Click OK to dismiss it.
Using the Consumption Model
The TCM Consumption model is used primarily to predict the number of CPUs and logical disk
volumes required for a given scenario. The capacity planner can specify any of the following
parameters:
•
Target online CPU or disk utilization or both expressed in average percentages
•
Target online host response time in seconds (either average or percentile)
•
Target batch response time
•
Planned online throughputs in transactions per second, minute, hour, day, or month
•
Planned CPU and disk type
•
Number of CPUs, logical disk volumes or both
•
Planned number of transactions per task for batch transactions
To use the Consumption model:
1. Open a Performance model.
2. Select Consumption model. The Consumption model appears. Figure 24 (page 91) shows a
sample Consumption model screen.
Figure 24 Consumption Model Screen
Using the Consumption Model
91
Actual data based on the workload-apportioned Measure data appears in the Actual column.
Default constraints appear in the Constraint column. The configuration recommended by TCM
appears in the Plan column.
3.
4.
Enter constraints in the input fields in the Constraint column and other highlighted cells. Then
press Return.
After entering all of the changes you want into the highlighted input fields, press Return. Then
select Options > Calculate Now. To finish entering your data, you must press Return before
selecting Calculate Now or pressing a function key.
TCM calculates all the values in the Plan column to support the given constraints.
About the Results
As a starting point TCM recommends a reasonable combination of CPUs and disks at an estimated
minimum cost. For a definitive solution you must analyze your system environment and budgetary
constraints to determine the optimal combination of CPUs and disks. If this analysis shows it is
impossible to support a given workload within your constraints, TCM flags the Plan or Constraint
fields corresponding to the unachievable constraints.
Using the Planning Timeline Model
The TCM Planning Timeline model is used to examine host response times and throughputs over
six user-specified planning periods. You can specify several growth scenarios including:
•
Throughput growth rate for OLTP transactions (Rate column) starts from the second column.
The first column is the actual for the Basic Sample Data for the Consumption model.
•
Number of transactions per tasks growth rate for batch transactions (Rate column)
•
Number of CPUs, disks or both over time
•
CPU and disk type
You can display the results of the Planning Timeline model in a chart and print the chart. Default
behavior from the Planning Timeline line propagates to the right from column 2. The user can
define behavior changes.
To use the Planning Timeline model:
1. Open a Performance model.
2. Choose Find > Planning Timeline. The Planning Timeline model appears. Figure 25 (page 93)
shows a sample Planning Timeline model.
92
Creating a Performance Model
Figure 25 Planning Timeline Model Screen
3.
After entering all of the changes into the highlighted input fields, press Return. Then select
Options Calculate Now. To finish entering your data, you must press Return before selecting
Calculate Now. TCM calculates the values to reflect the changes.
Throughput Trending
You can use the Planning Timeline model to have TCM calculate throughput growth rate (or
transaction per task growth rate) based on the existing trend in the history database.
To calculate throughput trending:
1. Open a Performance model.
2. Select Update Timeline Trends. The Update Timeline Trend dialog box appears.
Using the Planning Timeline Model
93
3.
4.
5.
6.
Select the transaction whose trend you want to measure from the Transaction list.
If you want, modify the range of dates in the history database by entering new dates in the
From and To fields. The default is the entire history database. Those dates are displayed in
the fields.
Click OK.
Select Options > Calculate Now.
Use the transaction trend in the historical database to update the Planning Timeline screen.
A notation that the transaction rate is based on historical trend is displayed in red.
To Generate a Timeline Chart
To generate a Timeline Chart:
1. Open a Performance model.
2. Select Options > Calculate Now to update the Performance model data.
3. Select Chart Create > Timeline Chart. The Timeline Chart dialog box appears.
4. Select Transaction (to chart) and click OK. The Timeline Plot dialog box appears.
The host response time and the throughput data from the Planning Timeline model are then
plotted on the screen. Figure 26 (page 95) and Figure 27 (page 95) show sample Planning
Timeline Model charts.
94
Creating a Performance Model
Figure 26 Planning Timeline Model Chart for Average Online Transaction
Figure 27 Planning Timeline Model Chart for Batch Transaction
Using the Planning Timeline Model
95
Printing Charts
TCM creates its charts in black and white. TCM automatically produces the chart to be printed on
a black and white printer.
To print a chart:
1. Create a chart of the Planning Timeline model.
2. Update the Performance model data by selecting Options > Calculate Now.
3. Once the chart appears on the screen, select Print option under the Print tab.
Saving the Model
To save the Performance model with its existing name:
1. Select File > Save As.
2. A dialog box containing a list of files in the Excel session appears.
3. To save the model in a location other than the TCM custom directory, click the Browse button
next to the Performance model name.
4. Ensure that the check box next to the Browse button of the Performance model is checked.
Click Save to save the model.
To save the Performance model with a different name:
1. Select File > Save As.
2. A dialog box containing a list of files in the Excel session appears.
3. Type a new name (except TCM.spm) for the model.
4. To save the model in a location other than the TCM custom directory, click Browse.
5. Ensure that the check box next to the PM model name is checked. Click Save to save the model
under the different name.
NOTE: Any Timeline charts created in the TCM session are saved as a part of the Performance
Model.
Deleting Transactions or Applications
As a TCM administrator, you can use TCM to model what happens to a system if an application
or certain transactions of an application are moved to another system. For instance, if you have
both online and batch applications running on the same system, you might want to estimate the
effect of moving batch activity to its own system.
Although you can accomplish the same results with different methods using the options of TCM,
one method is recommended. Collect all Measure statistics on the current system and then create
a WA model that apportions the Measure data to transactions. Make sure there are no Z categories
and that no Measure data is ignored.
To model the removal of an application or a transaction, simply zero out the application’s or
transaction’s throughput (or transactions per task). By doing this, you basically nullify the effect of
the application or transaction on the system. To zero out the application’s or transaction’s throughput,
type zero (0) in the Plan column for the appropriate transactions in the Consumption model and
select Options > Calculate Now. To finish entering your data, you must press Return before selecting
Calculate Now or pressing a function key.
Merging Performance Models
Refer to “Merge Performance Models” (page 169).
96
Creating a Performance Model
7 Modeling Batch Workloads
TCM uses a multiple priority closed queueing model to predict task response time and transaction
throughput for batch transactions. It is assumed that OLTP transactions have higher priority than
batch transactions and that batch transactions do not interfere with OLTP activity. System resources
that are not used for processing OLTP transactions are left for batch use. TCM uses the remaining
system resources to calculate the CPU and disk seconds for processing batch transactions and then
takes the sum of CPU and disk seconds as batch response time. For a more detailed explanation
of the batch formula that TCM uses, see Appendix D: “TCM Response Time Formulas”.
This chapter:
•
Describes the assumptions made about batch transactions
•
Defines batch terms
•
Explains the differences in modeling batch transactions in MeasTCM, the WA model, and the
Performance model
•
Explains how to calibrate batch response time to observed response time
Assumptions
TCM makes the following assumptions about batch transactions:
•
Batch transactions run at a lower priority than OLTP transactions. While increased online
activity interferes with the response time of batch activity, increased batch activity does not
interfere with the response time of online transactions.
•
Batch activity in the disk process does not interfere with OLTP activity at all. Mixed workload
enhancement (its use or disuse) has no effect on this assumption.
•
Batch transactions do not use system resources uniformly. With OLTP activity, TCM assumes
that transactions are spread evenly across CPUs and disks. With batch activity, you can define
how batch activity should be allocated to your system resources. To model batch transactions
accurately, you must understand how batch applications run on your system.
•
Process categories run in parallel across CPUs, but that run in series within CPUs.
For example, Tape Read and DB Update are process categories in a batch application. Tape
Read and DB Update run one after the other; that is, sequentially. DB Update runs at the same
time in two separate CPUs. Tape Read uses 100 CPU seconds. DB Update uses 300 CPU
seconds but occurs simultaneously in two CPUs, so its net CPU seconds is 300/2 = 150 CPU
seconds for response time. The total response time needed by Tape Read and DB Update is
100 (Tape Read) + 150 (DB Update) = 250 CPU seconds. Figure 28 (page 98) illustrates
this example.
Assumptions
97
Figure 28 Batch Applications
Transaction Types
TCM uses three transaction types: batch, online, and query. In TCM, a batch transaction is roughly
equivalent to the common terms batch job and workload. The batch transaction can have multiple
tasks. Batch transactions have the following characteristics:
•
Long job duration—Batch transactions can last several hours and can include processing of
several tasks, each of which includes hundreds or thousands of transactions.
•
Low priority—Batch transactions have lower priority than online transactions and do not
normally interfere with the response time of online transactions.
•
Significant disk activity—Batch transactions can process hundreds or thousands of smaller
transactions. Each of these smaller transactions can have disk activity.
•
Little or no terminal interaction—Batch transactions require little or no operator intervention
and can be run during nonpeak periods such as at night or on weekends.
•
Closed system—A batch transaction processes a series of smaller transactions (records)
sequentially with no delay between them.
The completion of the processing of one transaction (record) immediately starts the processing of
the next. The following diagram shows a simple batch transaction or workload. Within the workload
is a closed box representing a task. Within that task are 3,000 transactions to be processed in
the batch workload. The moment one of these 3,000 transactions completes, the next one is started.
A given batch workload has only one active transaction in the system at a time.
98
Modeling Batch Workloads
In contrast to the batch transaction or workload is the online transaction. The online transaction or
workload is an open system. In contrast to batch transactions, the interval time of consecutive OLTP
transactions is random.
Although batch and online transactions are very different, query transactions are modeled as batch
or online transactions, depending on the CPU demand of the query transaction. Large demand
queries are modeled as batch. Small demand queries are modeled as OLTP.
Batch Examples
Consider the following examples of batch transactions.
International Bigbank runs a batch application that updates credit card balances nightly. The
application has a single batch transaction. The batch transaction updates International Bigbank’s
database consisting of 10,000 credit card records. The batch application processes an average
of 10,000 transactions per night. In this case, TCM has one batch transaction for the application.
That batch transaction has one task, and that single task has 10,000 smaller transactions.
Mighty Manufacturing company has a batch application called Shipping Orders. The application
currently has 20 tasks. Each task includes all the shipping orders received during that half of the
day, typically 10 orders in the morning and 15 orders in the afternoon. In this case, TCM has one
batch transaction for the application. Because all of these orders are the same shipping order
transaction, we can model them as one type of batch transaction — the shipping order transaction.
Within TCM, we can indicate that it is a batch transaction composed of 2 tasks, each task with
an average of 12.5 smaller transactions per task:
Transaction Types
99
However, if Mighty Manufacturing Company processed shipping orders in the morning and
inventory analysis in the afternoon, these would be classified as two different batch transactions,
each with one or more tasks. The purpose of defining multiple tasks for a batch transaction is so
that TCM can estimate the response time and throughput per task.
Differences in Modeling Batch Transactions
When you model batch transactions in TCM, you need to modify your procedures in MeasTCM
and TCM slightly. This subsection highlights only the differences in the procedures.
Running MeasTCM
When you create a control file for your MeasTCM run, you must identify your transaction as a
batch transaction by using the TXN keyword. This excerpt of a MeasTCM control file identifies a
batch transaction:
!**********************************************************************
! Syntax for TXN entries
! ---------------------!
! TXN W,Z
!
! where:
W
1 character transaction type code
!
Z
transaction name (up to 20 chars)
TXN B,creditcard
The TXN keyword is followed by the one-character transaction type code: B for batch, X for OLTP,
or Q for query. For batch or query transactions, you must include the code because OLTP (type X)
is the default.
The transaction name can be up to 20 characters. If you do not specify a transaction name, TCM
uses the name of the Server (type S) process category as the default.
Every transaction type in your model must be identified with the TXN keyword. The following
example includes both batch and online transactions:
!**********************************************************************
! Syntax for TXN entries
! ---------------------!
! TXN W,Z
!
! where:
W
1 character transaction type code
!
Z
transaction name (up to 20 chars)
TXN B,creditcard
TXN X,bigtrans
TXN X,smalltrans
Creating a WA Model
After you have run MeasTCM and created several CSV files for your samples, you are ready to
load the CSV file into TCM to create a WA model. Once you have loaded the CSV file, check to
ensure that batch transactions are correctly identified as type B in the Workload Apportionment
screen. If your batch transactions are not correctly labeled as type B, rerun your Measure sample
with MeasTCM and be sure to specify the batch transactions and any others with the TXN keyword.
Figure 29 (page 101) shows the Workload Apportionment screen for the Demo model included
with TCM.
100 Modeling Batch Workloads
Figure 29 Workload Apportionment Screen
Notice that the batch transaction, CustUpdt, is labeled as B. The online transactions, Withdrawal
and Deposit, are labeled as X.
Number of Tasks
In your batch transaction, you can have multiple tasks. In the Mighty Manufacturing example
earlier, the Shipping Orders batch workload has two tasks. If your transaction has multiple tasks,
you need to modify the #Tasks field for the batch transaction in the Workload Apportionment
screen:
1. Open a WA model.
2. Log on as an administrator or super user. For more information about this step, see “Changing
Authorization Levels” (page 70).
3. Move to a Workload Apportionment screen.
4. Choose the Unprotect Admin Fields option from the Options tab. TCM highlights the fields that
you can modify.
5. In the #Tasks field for your batch transaction enter the correct number of tasks in your batch
transaction and press Return. To finish entering your data, you must press Return before
selecting Calculate Now or pressing a function key.
6. Select Options > Protect Admin Fields.
7. Select Options > Calculate Now to update the table. TCM recalculates values based on your
changes.
8. If you want to save the file, select Save or Save As from the File tab.
Workload Detail by Category
The Workload Detail by Category screen in the WA model has one field that pertains to batch
transactions: tunable CPU.
You can change this field from its default value either in the Apportionments Weights or Transaction
Count screen of the WA model or in the Actual or Plan Detail Baseline by Category screens in the
Performance model. It is recommended that you use the Performance model screens to modify these
fields if needed. For more information on CPU tunability, see “CPU Tunability” (page 103).
Creating a Performance Model
You need to evaluate three batch parameters in the Performance model and decide whether to
change them from their default values. These batch parameters are:
•
Number of batch CPUs
•
Hardware utilization thresholds for CPU and disk
Differences in Modeling Batch Transactions
101
•
Calculate batch response times with completed jobs removed from system
•
CPU tunability
The first three parameters, Number of Batch CPUs, and Hardware utilization thresholds for CPU
and Disk, and Calculate Batch response times with completed jobs removed from system are found
on the TCM Parameters screen. The last field is found on the Actual or Plan Baseline Detail by
Category screen in the Performance model.
The fourth is not a parameter but a column. For more information about CPU tunability, see “CPU
Tunability” (page 103).
Number of Batch CPUs
The Number of Batch CPUs field indicates the number of CPUs available for batch activity. The
parameter has no effect on OLTP. OLTP processing is always assumed to take place on all CPUs.
It is assumed that both batch and OLTP activity occur in a batch CPU. The default is All, which
means batch activity can run in all CPUs in the system.
Change this field if you limit batch activity to run in a subset of the CPUs in your system. For
instance, if batch activity occurs in CPUs 5 and 6 only, change the Number of Batch CPUs to 2.
Only two CPUs are available for batch activity, and all CPUs are used for OLTP transactions.
All users can modify the Number of Batch CPUs field in the TCM Parameters screen. Figure 31
(page 104) shows a sample TCM Parameters screen.
Hardware Utilization Thresholds for CPU and Disk
The Hardware Utilization Thresholds fields indicate the system resources available for batch
transactions. The default is 100 percent for CPU utilization and 50 percent for disk utilization.
When batch activity is running in a CPU, the CPU can run at 100 percent utilization. When batch
activity is running in a disk, TCM assumes the disk can run at no more than 50 percent utilization.
You need to evaluate both of the default values and determine hardware utilization thresholds
appropriate to your system. For example, if you observe that your disks run at no greater than 40
percent busy, change the disk utilization threshold to 40 percent.
Calculate Batch Response Times With Completed Jobs Removed From System
The Calculate Batch Response Times With Completed Jobs Removed From System field indicates
how TCM should calculate batch response times. The default is TRUE. When the field is set to TRUE,
completed batch jobs are effectively removed from the system. The remaining jobs speed up
because fewer active jobs are sharing the CPU and Disk resources. When the field is set to FALSE,
completed batch jobs are not removed from the system. In this case, TCM treats all batch jobs as
though they restart when completed and assumes that all batch jobs are running simultaneously,
no matter how long they actually take.
All users can modify the Calculate Batch response times with completed jobs removed from the
system field in the TCM Parameters screen. Figure 30 (page 103) shows a sample TCM Parameters
screen.
102 Modeling Batch Workloads
Figure 30 TCM Parameters Screen
CPU Tunability
The CPU Tunability field can be specified for each process category. It is used only for batch activity
and is ignored for OLTP activity. It indicates whether a process category runs in one or all available
batch CPUs. The default is N (no) for process categories that participate in batch transactions only.
N (no) indicates batch transactions are assigned to run in only one CPU. The default is Y (yes) for
process categories that participate in at least one OLTP transaction. Yes indicates that batch
transactions are spread evenly across all available batch CPUs.
TMF always defaults to nontunable because it is assumed that the major portion of its work is done
by one audit disk process.
In the Demo model included with TCM, the Tape Read and Cust Update categories are not tunable.
That is, they run in only one CPU. In contrast, the FastSort category is tunable. It runs in all CPUs
that are available to batch transactions.
The TCM administrator can modify this field on the Actual or Plan Baseline Detail by Category
screen.
You can modify the Tunable CPU field in the Plan Baseline Detail by Category screen. Figure 31
(page 104) shows a sample Plan Baseline Detail by Category screen.
Differences in Modeling Batch Transactions 103
Figure 31 Plan Baseline Detail by Category Screen
Consumption Model
You can modify two batch-related fields in the Consumption model screen—#Txns per Task and
Avg Batch Resp Time Constraint. Figure 32 (page 104) shows a sample Consumption model screen.
Figure 32 Consumption Model Screen
The batch response time is the time to perform one task. Thus, if you increase the #Txns per Task
field, the (task) response time increases. Conversely, if you decrease the #Txns per Task field, the
batch response time also decreases.
104 Modeling Batch Workloads
Modify the Avg Batch Resp Time Constraint field if you want TCM to estimate the number of CPUs
and disks required to ensure that average batch response time does not exceed the constraint,
and that all other constraints are also met. For example, if the average batch response time should
not exceed five minutes, enter one of the following in this field:
0h5m
5m
The syntax for the Avg Batch Resp Time is:
[ number h ] [ number m ] [ number s]
number
is any nonnegative integer; for example, 0, 1, or 45.
h
specifies hours.
m
specifies minutes.
s
specifies seconds.
Planning Timeline Model
The Planning Timeline model shows the number of transactions per task for batch transactions
(instead of throughput for online transactions) and average response time for the task. Figure 33
(page 105) shows a sample Planning Timeline model screen.
Figure 33 Planning Timeline Model Screen
Calibrating Batch Response Time
If you observe the actual response time of batch transactions that you run on your system and want
TCM to adjust its predicted response time accordingly, you can use the Calibrate Batch Response
Time option. Any TCM user can perform this function, regardless of security level.
Calibrating Batch Response Time 105
To calibrate Batch Response Time:
1. Open a Performance model.
2. Select Update > Calibrate Batch Response Time. The Calibrate Batch Response Time dialog
box appears.
3. Select the batch transaction name to calibrate from the list.
4. Enter the observed response time in the Calibrate Batch Response Time dialog box or accept
the defaults. You can enter hours, minutes, and seconds.
5. Click OK.
TCM adjusts its estimated response times in the Performance model by factors that reflect observed
response times.
Uncalibrate Transaction
You can reverse the calibration process and revert to the TCM predicted response times.
To uncalibrate Batch Response Time:
1. Open a Performance model.
2. Select Update > Calibrate Batch Response Time. The Calibrate Batch Response Time dialog
box appears.
3. Click the Uncalibrate Transaction check box.
4. Click OK.
TCM reverses the calibration process and reverts to the TCM predicted response times.
106 Modeling Batch Workloads
8 Workload Apportionment Model
This chapter describes the screens and menus of the Workload Apportionment model.
To move from one screen to the next, select the name of the screen you want to view from the Find
menu.
The WA model consists of the following major screens:
•
Category Demand Report—provides a summary of the performance data for process categories
as summarized by MeasTCM on the NonStop host system. (See Chapter 3: “Using MeasTCM”.)
Performance data is loaded using the Load Category Data option on the Update tab or
specified when the WA model is first created.
•
Workload Apportionment—is used to apportion the CPU and disk seconds consumed by
process categories to transactions. The three screens in this area are: CPU, Disk Read, and
Disk Write.
•
Workload Summary—summarizes the results of Workload Apportionment and displays the
CPU and disk seconds for each transaction. In addition, it indicates the fixed consumption
per second.
•
TCM Parameters—is used to set various parameters for the WA model and to change default
process category priorities.
•
Apportionment Weights Table—is used to define the way in which process category
performance data should be apportioned to transactions. This table is created and modified
only by users with a TCM administrator or superuser authorization level.
•
Transaction Count Table—is used to define how TCM should calculate the number of
transactions from process category performance data. The table specifies how to compute the
number of transactions from the number of messages received, sent or both by process
categories. This table is created and modified only by users with a TCM administrator or
superuser authorization level.
Instead of using the Transaction Count table to compute the number of transactions, you can
use a Transaction Count file. For more information, see “Transaction Count Table Versus
Transaction Count File” (page 121).
•
Workload Detail by Category—shows detailed information about process categories, CPU
consumption by transaction, category priority, disk process priority queuing, and CPU tunability.
•
Capacity History—is a database used to archive and organize apportionment data from the
WA model. Capacity history is organized as an Excel database and presents information that
is useful to the capacity planner for tasks such as verifying transaction consistency, trend
analysis, and selection of representative samples.
Each of the screen descriptions shows a sample screen and describes the significant rows and
columns.
Data Source
The source of the data for the WA model is the process category performance data collected on
the NonStop host system using Measure and summarized by MeasTCM. The MeasTCM file is
created on the NonStop host system and downloaded to the PC.
To download performance data samples to the PC, follow the download procedure you normally
use in Windows. Keep all CSV files for the same application or set of applications in the same
folder. All CSV files must have the extension .CSV.
To load the downloaded performance data into TCM, specify the performance data when you
create a new WA model or choose Load Category Data option from the Update tab.
Data Source 107
Category Demand Report
The Category Demand Report screen summarizes the performance data for process categories
collected on the NonStop host system. To load the data, select Create a New WA Model from the
TCM Initial menu or Load Category Data from the Update tab. The data on this screen is used as
input for the Workload Apportionment component of the model.
As Figure 35 (page 110) shows, the top portion of the screen displays summarized data for each
type of process category, such as server (S), requester (R), and disk (D) processes. The bottom
portion displays detailed performance data for each process category as defined by MeasTCM
on the NonStop host system. Figure 34 (page 108) shows a sample Category Demand Report
screen.
Figure 34 Category Demand Report Screen
Significant Rows
1.
Application—Modifiable by TCM administrators only
Application is the user-defined name for the application (or set of applications) being modeled.
The application name is defined in MeasTCM on the NonStop host system but can be
overwritten by the TCM administrator if preferred.
2.
Category File—Not directly modifiable
Category File is the name of the CSV file that was loaded into the WA model. This file was
created by MeasTCM on the NonStop host system and downloaded to the workstation. It has
a file extension of .CSV. If TCM detects an invalid CSV file format, an error message appears
when the Load Category Data option is selected. A CSV file is considered invalid if its first
field does not have a node name or a value of I01.
3.
Interrupts—Not directly modifiable
Interrupts are the total number of interrupt seconds measured on the NonStop host system by
Measure during the time period of the sample window. These seconds are apportioned to the
CPU seconds of all the process categories according to their relative number of messages
received and sent.
108 Workload Apportionment Model
Significant Columns
4.
Cat Name—Modifiable by TCM administrators only
Cat Name is the name of the process category defined in MeasTCM on the NonStop host
system. (See “Process Category (PCAT) Statements” (page 54).) Up to 100 categories are
supported by MeasTCM.
5.
Type—Not directly modifiable
Type is the type of a process category as defined in MeasTCM on the NonStop host system.
The maximum number of categories is 100 (including Other and Error).
The process category type consists of one of the following characters:
S
Server process—this category type grows with throughput.
R
Requester process—this category type grows with throughput.
D
Disk process—this category holds all nonaudited disk processes. There is only one process with this
category type.
T
TMF processes—this category holds all TMF-related processes, including the audit disk. TMF-related
processes must be identified in the Process Category Control File. For more information, see
“Customizing Your Process Category Control File” (page 33).
L
Line-handler process—this category type grows with throughput.
O
Other—this category type grows with throughput.
F
Fixed—this category includes system overhead that does not vary with throughput.
Z
Ignored processes (appropriate interrupt and disk activity to be omitted)—this category is ignored
and is used for activities that you do not expect to occur in the future. Use this category with caution
because you might unintentionally undersize a system.
Table 8 TITLE Entry with Category Type and Description
Title Entry
Process
Category Type Process Category Description
TITLE01
T
TMF (including audit disk processes)
TITLE02
R
Requester
TITLE03
F
Measure
TITLE04
D
Disk (excluding audit disk processes)
TITLE05
O
System
TITLE06
S
Server
TITLE07
O
OSS
TITLE08
R
SQLMP
TITLE09
R
SQLMX
CPU Workload Apportionment Screen
The CPU Workload Apportionment screen shows the apportionment of the CPU consumed by
process categories to transactions. Figure 35 (page 110) shows a sample CPU Workload
Apportionment screen.
CPU Workload Apportionment Screen 109
Figure 35 CPU Workload Apportionment Screen
Significant Rows
1.
CPU Config—Not directly modifiable
CPU Config is the actual CPU configuration that was measured for the sample. The configuration
includes the number of CPUs, type and the IPU information. For single core CPUs, the IPU field
would contain "NA". If the sample was measured on an HP NonStop system running the G06
RVU, the suffix G06 is displayed next to the CPU type.
The WA model permits only one CPU type to perform its calculations. If the sample was
measured on a mixed system (using NSR-W and NSR-G processors, for example), CPU seconds
are normalized by MeasTCM to one CPU type, as specified in the MeasTCM control file on
the NonStop host system. For this reason, the number of CPUs might be fractional if the sample
was measured on a mixed system.
2.
Fixed CPU Seconds—Not directly modifiable
Fixed CPU Seconds is the total number of CPU seconds consumed per second by process
categories of type F (fixed). This number is not included in the CPU and disk consumption of
individual transactions, but does affect the total CPU and disk utilizations. Define a category
as type F if its CPU and disk consumption do not increase as throughput increases, such as
during asynchronous data communications polling activity or the running of Measure.
3.
Apportionment—Not modifiable
Apportionment indicates the apportionment method used by the WA screen. The apportionment
method name is the name of the apportionment table file (without the .AWA extension) that
was used to generate the apportionment formulas when Workload Apportionment was selected
from the Update tab.
Significant Columns
4.
Txn Name—Modifiable by the TCM administrator
Txn Name is the name of the transaction as defined on the NonStop host system using
MeasTCM. In MeasTCM, you can specify the transaction names for each transaction in the
application or applications being modeled. You can specify up to 40 transactions. For more
information, see “Customizing Your Process Category Control File” (page 33).
If no transaction names are specified in MeasTCM, TCM assumes that each server category
(type S) represents a transaction and uses the corresponding server category names as
transaction names.
The TCM administrator can modify the transaction names.
5.
First Unlabeled Column—Not directly modifiable
The first unlabeled column shows the type of a transaction: X for OLTP transactions, B for batch
transactions, or Q for query transactions.
110
Workload Apportionment Model
6.
Second Unlabeled Column—Not directly modifiable
The second unlabeled column indicates Aud if the transaction is audited but is left blank
otherwise. A transaction is considered audited if it has a nonzero entry in the TMF process
category in the Apportionment Weights table.
7.
# Tasks—Modifiable by the TCM administrator
# Tasks shows the number of tasks on the NonStop host system during the time period of the
sample window. This number applies to batch transactions only.
8.
# Txns—Not directly modifiable
# Txns shows the number of transactions on the NonStop host system during the time period
of the sample window. This number is computed according to the user-specified Transaction
Count table, which specifies how to calculate the number of transactions from the number of
messages received, sent or both by the process categories, or is input through the Transaction
Count file. For more information, see “Transaction Count Table” (page 119) and the “Transaction
Count Table Versus Transaction Count File” (page 121).
9.
CPU Seconds per Transaction—Not modifiable
CPU Seconds per Transaction is the apportioned number of CPU seconds consumed per
transaction. The Avg On-line row contains the (weighted) average of CPU seconds for each
online transaction. The Avg Batch row contains the (weighted) average of CPU seconds for
each Batch transaction.
The WA model distinguishes between CPU seconds consumed by the various processes of a
transaction, such as the server, requester, disk, TMF, line handler, interrupts, and other
processes.
CPU seconds are apportioned to transactions according to the user-specified Apportionment
Weights table described later in this section. In addition, the disk process component of CPU
seconds is apportioned according to the relative number of disk cache hits and disk cache
misses for each process category.
Disk Read Workload Apportionment Screen
The Disk Read Workload Apportionment screen shows the apportionment of the disk read seconds
consumed by process categories to transactions. Figure 36 (page 111) shows a sample Disk Read
Workload Apportionment screen.
Figure 36 Disk Read Workload Apportionment Screen
Significant Rows
1.
Disk Config—Not directly modifiable
Disk Config is the actual disk configuration that was measured for the sample, as determined
by MeasTCM on the NonStop host system. The configuration includes the number of logical
Disk Read Workload Apportionment Screen
111
disk volumes, their configuration type, their write cache (WCE) configuration status and TMF
audit trail count. Valid disk write cache configuration status can be:
Enabled
WCE enabled for disks that support WCE
Disabled
WCE disabled for disks that support WCE
NA
NA for disks that do not support WCE
For audited disk configurations, valid TMF audit trails can be between 1 and 16. For unaudited
configurations, it is NA (not applicable). The WA model assigns an Aud disk configuration
type if there are any audited transactions. If none are audited and the number of logical and
physical disks are equal, it assigns an Unmirr disk type. Otherwise, the WA model assigns
an Unaud disk type.
2.
Fixed Read Sec—Not directly modifiable
Fixed Read Sec is the total number of CPU seconds consumed per second by process categories
of type F (fixed). This number is not included in the CPU and disk consumption of individual
transactions but does affect the total CPU and disk utilizations. Define a category as type F if
its CPU and disk consumption do not increase as throughput increases, such as during
asynchronous data communications polling activity or the running of Measure.
3.
Apportionment—Not directly modifiable
Apportionment indicates the apportionment method used by the WA screen. The apportionment
method name is the name of the apportionment table file (without the .AWA extension) that
was used to generate the apportionment formulas when Workload Apportionment was selected
from the Update menu.
Significant Columns
4.
Txn Name—Modifiable by the TCM administrator
Txn Name is the name of the transaction as defined on the NonStop host system using
MeasTCM. In MeasTCM, you can specify the transaction names for each transaction in the
application or applications being modeled. You can specify up to 40 transactions.
If no transaction names are specified in MeasTCM, TCM assumes that each server category
(type S) represents a transaction and uses the corresponding server category names as
transaction names.
5.
First Unlabeled Column—Not directly modifiable
The first unlabeled column shows the type of a transaction, either X for OLTP transactions, B
for batch transactions, or Q for query transaction.
6.
Second Unlabeled Column—Not directly modifiable
The second unlabeled column indicates Aud if the transaction is audited but is left blank
otherwise. A transaction is considered audited if it has a nonzero entry in the TMF process
category in the Apportionment Weights table.
7.
# Tasks—Modifiable by the TCM administrator
# Tasks is the number of tasks on the NonStop host system during the time period of the sample
window. This number applies to batch transactions only.
8.
# Txns—Not directly modifiable
# Txns is the number of transactions on the NonStop host system during the time period of the
sample window. This number is computed according to the user-specified Transaction Count
table, which specifies how to calculate the number of transactions from the number of messages
received, sent or both by the process categories, or is input through the Transaction Count
112
Workload Apportionment Model
file. For more information, see “Transaction Count Table” (page 119) and the “Transaction
Count Table Versus Transaction Count File” (page 121).
9.
Read Seconds per Transaction—Not modifiable
The apportioned number of disk read and disk write seconds consumed per transaction. The
Average Txn column contains the (weighted) average of disk seconds for each transaction.
Disk seconds are the number of seconds spent doing physical disk access, including seeks.
Seek seconds are apportioned by MeasTCM on the NonStop host system according to the
relative number of reads and writes performed.
The WA model distinguishes between disk seconds consumed by the various processes of a
transaction, such as the server, requester, disk, TMF, line handler, and other processes.
Disk read and write seconds are apportioned to transactions according to the userspecified
Apportionment Weights table.
Disk Write Workload Apportionment Screen
The Disk Write Workload Apportionment screen shows the apportionment of the disk write seconds
consumed by process categories to transactions. Figure 37 (page 113) shows a sample Disk Write
Workload Apportionment screen.
Figure 37 Disk Write Workload Apportionment Screen
Significant Rows
1.
Disk Config—Not directly modifiable
Disk Config is the actual disk configuration that was measured for the sample, as determined
by MeasTCM on the NonStop host system. The configuration includes the number of logical
disk volumes, their configuration type, their write cache (WCE) configuration status and TMF
audit trail count. Valid disk write cache configuration status can be:
Enabled
WCE enabled for disks that support WCE
Disabled
WCE disabled for disks that support WCE
NA
NA for disks that do not support WCE
The WA model assigns an Aud disk configuration type if there are any audited transactions.
If none are audited and the number of logical and physical disks are equal, it assigns an
Unmirr disk type. Otherwise, the WA model assigns an Unaud disk type.
2.
Fixed Write Sec—Not directly modifiable
Fixed Write Sec is the total number of CPU seconds consumed per second by process categories
of type F (fixed). This number is not included in the CPU and disk consumption of individual
transactions but does affect the total CPU and disk utilizations. A category should be defined
Disk Write Workload Apportionment Screen
113
as type F if its CPU and disk consumption do not increase as throughput increases, such as
during asynchronous data communications polling activity or the running of Measure.
3.
Apportionment—Not directly modifiable
Apportionment indicates the apportionment method used by the WA screen. The apportionment
method name is the name of the apportionment table file (without the .AWA extension) that
was used to generate the apportionment formulas when Workload Apportionment was selected
from the Update menu.
Significant Columns
4.
Txn Name—Modifiable by the TCM administrator
Txn Name is the name of the transaction as defined on the NonStop host system using
MeasTCM. In MeasTCM, you can specify the transaction names for each transaction in the
application or applications being modeled. You can specify up to 40 transactions.
If no transaction names are specified in MeasTCM, TCM assumes that each server category
(type S) represents a transaction and uses the corresponding server category names as
transaction names.
5.
First Unlabeled Column—Not directly modifiable
The first unlabeled column shows the type of a transaction: X for OLTP transactions, B for batch
transactions, or Q for query transactions.
6.
Second Unlabeled Column—Not directly modifiable
The second unlabeled column indicates Aud if the transaction is audited but is left blank
otherwise. A transaction is considered audited if it has a nonzero entry in the TMF process
category in the Apportionment Weights table.
7.
# Tasks—Modifiable by the TCM administrator
# Tasks is the number of tasks on the NonStop host system during the time period of the sample
window. This number applies to batch transactions only.
8.
# Txns—Not directly modifiable
# Txns is the number of transactions on the NonStop host system during the time period of the
sample window. This number is computed according to the user-specified Transaction Count
table, which specifies how to calculate the number of transactions from the number of messages
received, sent or both by the process categories, or is input through the Transaction Count
file. For more information, see “Transaction Count Table” (page 119) and the “Transaction
Count Table Versus Transaction Count File” (page 121).
9.
Write Seconds per Transaction—Not modifiable
Write Seconds per Transaction are the apportioned number of disk write seconds consumed
per transaction. The Average Txn column contains the (weighted) average of disk seconds for
each transaction. Disk seconds are the number of seconds spent doing physical disk access,
including seeks. Seek seconds are apportioned by MeasTCM on the NonStop host system
according to the relative number of reads and writes performed.
The WA model distinguishes between disk seconds consumed by the various processes of a
transaction, such as the server, requester, disk, TMF, line handler, and other processes.
Disk read and write seconds are apportioned to transactions according to the userspecified
Apportionment Weights table.
Workload Summary Screen
The Workload Summary screen summarizes the results of Workload Apportionment and displays
the apportioned CPU, disk read, and disk write seconds for each transaction. The data on this
114
Workload Apportionment Model
screen is used as input for the TCM Performance model described in Chapter 6: “Creating a
Performance Model”.
Unlike the Workload Apportionment screens that show CPU, disk read, and disk write information
on separate screens, the Workload Summary screen displays all the information on one screen.
Figure 38 (page 115) shows a sample Workload Summary screen.
Figure 38 Workload Summary Screen
Significant Rows
1.
CPU Config—Not directly modifiable
CPU Config is the name of the actual CPU and the HP product version that was measured for
the sample, as determined by MeasTCM on the NonStop host system, such as NSR-GG06
with NA for IPU count. Valid CPU types are listed on the CPU conversion factor screen in the
TCM Performance Model.
2.
Disk Config—Not directly modifiable
Disk Config is the actual disk configuration that was measured for the sample, as determined
by MeasTCM on the NonStop host system. The configuration includes the number of logical
disk volumes, their configuration type, their write cache (WCE) configuration status and TMF
audit trail count. Valid disk write cache configuration status can be:
Enabled
WCE enabled for disks that support WCE
Disabled
WCE disabled for disks that support WCE
NA
NA for disks that do not support WCE
The WA model assigns an Aud disk configuration type if there are any audited transactions.
If none are audited and the number of logical and physical disks are equal, it assigns an
Unmirr disk type. Otherwise, the WA model assigns an Unaud disk type.
Significant Columns
3.
#Txns per Task
The #Txns per Task column shows the number of transactions per task. This parameter applies
to batch transactions only. For OLTP transactions, this parameter is always 1.
4.
Mix
The Mix column shows the transaction mix in percentage for the sample used.
Workload Summary Screen
115
WA Model TCM Parameters Screen
You can use the Workload Apportionment model TCM Parameters screen to change the default
process priorities and to set the Disk Process Apportionment Factors, History File Name, and Default
Process Priorities parameters for the WA model. Figure 39 (page 116) shows a sample TCM
Parameters screen for a Workload Apportionment model.
Figure 39 Workload Apportionment Model TCM Parameters Screen
Significant Rows
1.
Disk Process Apportionment Factors—Modifiable by the TCM administrator
Disk Process Apportionment Factors are the factors used to apportion the CPU seconds
consumed by the disk process based on cache hits and misses. These factors are used when
you select Workload Apportionment from the Update menu. The default settings assume that
a cache miss requires twice the CPU time as a cache hit.
2.
History File Name—Directly modifiable
History File Name is the file name of the Capacity History database. The default file name
consists of the first eight characters of the application name with an .HST extension, but you
can overwrite it.
3.
Query Transaction OLTP-> Batch Response Time CPU Pathlength Threshold—Directly modifiable
Query Transaction OLTP-> Batch Response Time CPU Pathlength Threshold specifies the point
at which a query transaction is considered either an OLTP or a batch transaction. The default
setting is 2 seconds. Small demand queries taking less than two seconds are considered OLTP
transactions. Large demand queries taking longer than two seconds are considered batch
transactions. Any TCM user can modify this parameter.
116
Workload Apportionment Model
Significant Columns
4.
Type—Not modifiable
The Type column shows the process category types.
5.
S
Server process—this category type grows with throughput.
R
Requester process—this category type grows with throughput.
D
Disk process—this category holds all nonaudited disk processes. There is only one process with
this category type.
T
TMF processes—this category holds all TMF-related processes, including the audit disk.
TMF-related processes must be identified in the Process Category Control File. For more
information, see “Customizing Your Process Category Control File” (page 33).
L
Line-handler process—this category type grows with throughput.
O
Other—this category type grows with throughput.
F
Fixed—this category includes system overhead that does not vary with throughput, for example,
Measure or some data polling or operator commands such as FUP.
Z
Ignored processes (appropriate interrupt and disk activity to be omitted)—this category is ignored
and is used for activities that you do not expect to occur in the future. Use this category with
caution because you might unintentionally undersize a system.
Priority—Modifiable by the TCM administrator
Priority is the process priority assigned as the default for each type.
Workload Apportionment Weights Table
The TCM administrator uses the Workload Apportionment Weights table to specify how TCM
should apportion the CPU and disk seconds of process categories to the appropriate transactions.
The table defines the relative weights to be given to each transaction (on a per-transaction basis)
in apportioning category consumption. If you already have an apportioned model, an .AWA file
exists in your custom folder, and you can access the Apportionment Weights table by choosing
Apportionment Weights from the Find tab. If the .AWA file does not exist in your custom folder,
the Apportionment Weights and Transaction Count Table options are unavailable on the Find tab.
Figure 40 (page 117) shows a sample Workload Apportionment Weights table.
Figure 40 Workload Apportionment Weights Table
Workload Apportionment Weights Table
117
Significant Row
1.
User-Supplied Transaction Names—Not directly modifiable
The name of the transaction as it appears on the Workload Apportionment screens. Transaction
names are either initially defined on the NonStop host system using MeasTCM (see “TXN
Entries” (page 60)) or named by default in TCM by server category (type S), but they can be
overwritten on the Workload Apportionment screens by the TCM administrator.
Significant Columns
2.
Cat Name—Not directly modifiable
Cat Name is the category name of all process categories as they appear on the Category
Demand report. These categories appear in rows in the Apportionment Weights table. The
table indicates how the CPU and disk seconds consumed by these categories are to be allocated
to each transaction.
3.
Type—Modifiable by the TCM administrator
Type is the type of process category, as defined in MeasTCM on the NonStop host system.
The category type consists of one of the following characters:
4.
S
Server process
R
Requester process
D
Disk process (including all nonaudited disk processes)
T
TMF processes (including all audit disk processes)
L
Linehandler process
O
Other
F
Fixed (system overhead that does not vary with throughput)
Z
Ignore these categories (appropriate interrupt and disk activity to be omitted)
Tunable CPU—Modifiable by the TCM administrator
Tunable CPU indicates, for batch transactions only, whether all process category activity occurs
in one or multiple CPUs. It is ignored for online transactions. The process category CPU activity
is either monolithic or spread evenly across all CPUs that are available for batch activity. The
default is Y (yes) for categories that participate in at least one OLTP transaction. The default
is N (no) for categories that participate only in batch transactions.
For example, in the Demo model included with TCM, the Tape Read and Cust Update
categories are not tunable. That is, they are assigned to run in specific CPUs. However, the
FastSort category is tunable. It runs in all CPUs.
After the WA model recalculates the tunable CPU values in Figure 41 (page 119) they will be
reflected in the Workload detail by Category screen.
5.
Expert Flag—Modifiable by the TCM administrator
Expert Flag shows whether TCM Expert generates a value for the process category. The default
for the TMF (T), Disk (D), Fixed (F), and Ignore (Z) process categories is N (no). The default is
also N for server categories whose names exactly match the transaction names because a
process category that has the same name as a server is assumed to have all activity for that
server. The default value for all other process categories is Y (yes).
6.
Transaction—Modifiable by the TCM administrator
The TCM administrator uses the Transaction columns to indicate the relative weights with which
the CPU, disk read, and disk write seconds of a category should be apportioned to transactions.
A default version of the table is created by selecting Workload Apportionment from the Update
tab and selecting Create Default Apportionment Tables from the dialog box that appears or
118
Workload Apportionment Model
by selecting Calculate Now from the Options tab (if no table exists). For categories other than
server, the default table assumes that category demand is spread evenly (on a per-transaction
basis) across all transactions. For server categories whose names match a transaction name,
the default table assumes that category demand is 1 for the transaction with the matching
name and 0 for all others.
In some cases, however, a transaction might consume more of a certain resource per transaction
than another transaction does. For example, in a Pathway system, the requesters for transactions
Txn 1 and Txn 2 might use the same TCP, but Txn 1 might be a heavy requester and Txn 2 a
light requester. In this case, the TCM administrator would modify the relative weights in the
default Apportionment Weights table to reflect the difference.
Transaction Count Table
The Transaction Count table is used by the TCM administrator to specify how the WA model should
compute the number of transactions measured by Measure during the time period of the sample
window on the NonStop host system. TCM calculates transaction counts from the entries in this
table, the number of messages received, sent or both by process categories into transaction counts.
Figure 41 (page 119) shows a sample Transaction Count Table. For more information, see “Example
of a Transaction Count Table” (page 73).
Figure 41 Transaction Count Table
Significant Columns
1.
Cat Name—Not directly modifiable
Cat Name is the category name of all process categories as they appear on the Category
Demand report. The table is used to indicate how the CPU and disk seconds consumed by
these categories are to be allocated to each transaction.
2.
Type—Modifiable by the TCM administrator
The type of process category, as defined in MeasTCM on the NonStop host system. The
category type consists of one of the following characters:
S
Server process
R
Requester process
D
Disk process (including all nonaudited disk processes)
Transaction Count Table
119
3.
T
TMF processes (including all audit disk processes)
L
Linehandler process
O
Other
F
Fixed (system overhead that does not vary with throughput)
Z
Ignore these categories (appropriate interrupt and disk activity to be omitted)
Tunable CPU—Modifiable by the TCM administrator
This column indicates, for batch transactions only, whether all process category activity occurs
in one or multiple CPUs. It is ignored for online transactions. The process category CPU activity
is either monolithic or spread evenly across all CPUs that are available for batch activity. The
default is Y (yes) for categories that participate in at least one OLTP transaction. The default
is N (no) for categories that participate only in batch transactions.
For example, in the Demo model included with TCM, the Tape Read and Cust Update
categories are not tunable. That is, they are assigned to run in specific CPUs. However, the
FastSort category is tunable. It runs in all CPUs.
4.
Expert Flag—Modifiable by the TCM administrator
This column shows whether TCM Expert generates a value for the process category. The default
for the TMF (T), Disk (D), Fixed (F), and Ignore (Z) process categories is N (no). The default is
also N for server categories whose names exactly match the transaction names because a
process category that has the same name as a server is assumed to have all activity for that
server. The default value for all other process categories is Y (yes).
5.
Rcv and Sends—Modifiable by the TCM administrator
The Rcvs and Sends refer to the receives to or sends from process category, not the receives
to or sends from transaction. The entries in the table are multipliers of the process category
receives or sends. To compute the number of transactions, the entries listed in the two columns
below the transaction name are multiplied by the appropriate number of sends or receives of
the associated process category and the resultant products are added together. Therefore,
the zero entries provide no contribution. Negative numbers can be entered in the table.
For example, in the following table, the number of Txn1 transactions is equal to the number
of messages received by the Cat1 process category. (This is a common situation when Cat1
is the Pathway server class for Txn1.) In addition, the number of Txn2 transactions is equal to
half of the number of messages received by Cat2, minus the messages sent by Cat1.
Txn1
Txn2
Rcv
Send
Rcv
Send
Cat1
1
0
0
-1
Cat2
0
0
.5
0
Cat3
0
0
0
0
The Transaction Count table is used by the TCM administrator to indicate how to compute the
number of transactions from the number of messages received, sent or both by process
categories.
A default version of the table is automatically created when the user creates WA model.
Alternately, default version of the table can be created by selecting Workload Apportionment
from the Update menu and selecting Create Default Apportionment Tables from the dialog
box that appears. The table assumes that the transaction count for a specific transaction is
equal to the sum of the messages received by the server categories that participate in that
transaction. For more information see “Example of a Transaction Count Table” (page 73).
120 Workload Apportionment Model
For example, in a Pathway application, the default table would assume that the number of
transactions is equal to the number of messages received by its Pathway server class.
Although the default algorithm is frequently accurate, in some cases it will need to be modified.
A value of zero in the matrix indicates that messages received (or sent) by the category should
not be counted as transactions. A value of n indicates that the WA model should multiply by
n the number of messages received (or sent) by the category in calculating the number of
transactions.
TCM issues a warning if the transaction count matrix contains all zeros for any transaction.
Maximum Transactions
The maximum number of transactions that can be modeled is 40. Procedures for creating and
modifying the Transaction Count table are similar to the procedures for creating and modifying
the Apportionment Weights table. For details, see “Workload Apportionment Weights Table”
(page 117).
Transaction Count Table Versus Transaction Count File
You can create a Transaction Count file to compute the number of transactions instead of using
the counts in the Transaction Count table. This feature is useful if you know how many transactions
are processed by your application.
For example, you might be able to create a simple program to parse your application’s statistics
or log file to determine the number of transactions processed by your application. Alternately, you
can use Measure user-defined counters to determine the number of transactions processed by your
application. You can create the file on the NonStop host system and download the file to the custom
folder, or you can create the file directly on the PC.
When TCM loads a CSV file, it checks to see if the corresponding Transaction Count file exists. If
the Transaction Count file exists, TCM uses the Transaction Count file for the transaction counts
and uses the Transaction Count table if any transaction counts are missing in the Transaction Count
file. Thus, you can use both a Transaction Count table and Transaction Count files. If you use both,
the values in the Transaction Count files supersede any values in the Transaction Count table.
For example, suppose your application has 20 transactions, and you have counts for 8 of the
transactions. You can use Transaction Count files to indicate the counts for these 8 transactions.
You should not put blanks in the Transaction Count files. For the 12 transactions not listed in the
Transaction Count files, TCM uses the Transaction Count table for the counts.
Transaction Count File Naming Convention
You create a Transaction Count file with a name patterned after the CSV file name. The Transaction
Count file has the same name as the CSV file except the extension is .TCF instead of .CSV.
For example, the CSV file EXAMPLE1.CSV would become Transaction Count file EXAMPLE1.TCF.
The Workload Apportionment model uses the counts in the Transaction Count file instead of its
generated formulas to calculate the number of transactions. When you load category data, TCM
automatically detects when you have a Transaction Count file and loads it.
Transaction Count File Format
The Transaction Count file has the following format:
TXNCNT
txn-name-1, txn-cnt-1, comment text
txn-name-2, txn-cnt-2, comment text
For example, a valid Transaction Count file follows:
TXNCNT
BIG, 500, You have 500 transactions of type BIG
ST1, 10, You have 10 ST1 transactions
Transaction Count Table
121
You cannot have any blank lines in the file. To enter comments, enter a comma following the
transaction count number and type the comment.
Using Process Pairs
If a process category has process pairs, the process category is not a good choice to be used in
the Transaction Count table because checkpoints to the backup process are included in the count
for messages received.
Workload Detail by Category Screen
The Workload Detail by Category screen shows detail about the process categories (also known
as workloads) as well as the application model. Figure 42 (page 122) shows a sample Workload
Detail by Category screen.
Figure 42 Workload Detail by Category Screen
122
Workload Apportionment Model
Significant Row
1.
Disk Process Priority Queuing—Modifiable by the TCM administrator
Disk Process Priority Queuing shows whether disk process priority queuing is to be applied.
Disk process priority queuing is also known as Mixed Workload Enhancement (MWE) and is
provided for all applications running on NonStop systems using C30 or later product versions
of the operating system. If disk process priority queuing is set to TRUE, the disk process runs
at the priority of its calling process instead of at a higher priority. The value is set according
to the CSV file produced by MeasTCM.
Disk Process Priority Queuing for batch transactions is always set to TRUE because TCM
assumes that applications on pre-C30 systems adequately controlled batch activity so that it
did not interfere with online transactions.
Significant Columns
2.
Tunable CPU—Not directly modifiable
To change these tunable CPU values, change them in the Tunable CPU column. (See Figure 41
(page 119).) After TCM recalculates these tunable CPU values, the Workload Detail by Category
screen is updated.
Tunable CPU indicates, for batch transactions only, whether all process category activity occurs
in one or multiple CPUs. It is ignored for online transactions. The process category CPU activity
is either monolithic or spread evenly across all CPUs that are available for batch activity. The
default is Y (yes) for categories that participate in at least one OLTP transaction. The default
is N (no) for categories that participate only in batch transactions.
For example, in the Demo model included with TCM, the Tape Read and Cust Update
categories are not tunable. That is, they are assigned to run in specific CPUs. However, the
FastSort category is tunable. It runs in all CPUs.
3.
Priority—Modifiable by the TCM administrator
This column shows the priority assigned to each of the process categories. Interrupts always
have the highest priority.
Changing Process Category Priorities
The Performance model uses process category priority data to calculate response times by using
a priority queueing algorithm. To change specific individual process category priorities, use the
Workload Detail by Category screen in the WA model. You must be the TCM administrator or a
super user to change the individual priorities.
To change process category priorities in the WA model:
1. Open a WA model.
2. Select Options > Change Authorization Level and log on as an administrator or super user.
For more information about this step, see “Changing Authorization Levels” (page 70).
3. Select Find > Workload Detail by Category. Figure 43 (page 124) shows a sample Workload
Detail by Category screen.
4. Select Options > Unprotect Admin Fields. The entries that you can modify are highlighted.
5. Enter the customized priorities in the Priority column for the process categories that you want
to change and press the Return key. To finish entering your data, press Return and then select
Calculate Now or press a function key.
6. Choose Options > Protect Admin Fields.
7. Choose Options > Calculate Now.
8. To save the model, select Save or Save As from the File tab.
Workload Detail by Category Screen
123
Capacity History Screens
The Capacity History screens–Database, TrendCharts, and MixCharts–are used to archive and
organize apportioned performance data for a particular application or set of applications. The
information in the Capacity History database is valuable in assisting the capacity planner in such
crucial activities as:
•
Checking the reasonableness of an apportionment method for a custom WA model
•
Choosing a representative performance sample as a baseline for the TCM Performance model
•
Projecting trends based on historical data in the Performance model
•
Performing database queries against historical data
•
Creating historical charts
The Capacity History screens display summary performance information for each transaction in a
given application (or set of applications) across multiple performance samples. The database can
also store data for several different apportionment methods, so the capacity planner can easily
examine the effect of different apportionment methods on several historical samples.
Capacity planners can search the database by selecting Search from the History menu. Figure 43
(page 124) shows part of a sample Capacity History database screen.
NOTE: A given Capacity History screen is restricted to only one application (the name defined
in the MeasTCM control file on the host), but it can contain the results of more than one
apportionment method if needed.
Figure 43 Capacity History Database Screen
Significant Rows
1.
Application—Not directly modifiable
Application is the user-specified name of the application or set of applications that is being
modeled. It is also the application name that appears on the Category Demand report of the
WA model. This name is specified when MeasTCM is executed on the NonStop host system.
(See “Customizing Your Process Category Control File” (page 33).) All the historical data on
the Capacity History screen pertains to this application. (An error message appears if you
select Update History from the History menu for a sample with a different application name.)
2.
Search Criteria—Modifiable by the user
Search Criteria is a collection of fields in which you can enter values before selecting Search
History or Delete History from the History menu. You can specify several database criteria to
124
Workload Apportionment Model
perform such operations as finding all samples where the throughput of transaction Txn 1 is
greater than 10 transactions per second.
3.
History Data—Not directly modifiable
History Data is the historical sample data as apportioned by the WA model. This data is
loaded by selecting Update History from the History tab and cannot be modified. Performance
data is sorted by apportionment method and transaction type in descending date sequence.
Significant Columns
4.
App’t—Not directly modifiable
App’t is the apportionment method that was used in the WA model to compute the sample
performance data from the MeasTCM process category data. Because Capacity History can
be updated with data from more than one apportionment method, the same sample could
appear more than once, each occurrence being generated with a different apportionment
method.
5.
Mix—Not directly modifiable
This column shows the percentage mix of transactions in the sample used. Carefully note the
mix. The mix of transactions must vary for your model to be reasonable.
History Charts
The Chart History command creates two types of History charts from the History file, Trend charts
and Mix charts. Trend charts and Mix charts are placed on worksheets named TrendCharts and
MixCharts, respectively, in the History file workbook.
The Chart History command is available whenever a History file is in the session. If a History file
currently appears, the Chart History command applies to the displayed History file. Otherwise
TCM performs a TCM Find to the History file if there is only one History file in the current session.
If more than one History file is open in the current session, you are prompted to select one from a
list, after which TCM performs a TCM Find to the selected History file. The Chart History command
then applies to this History file.
To create a Trend chart or a Mix chart:
1. Open a Workload Apportionment model.
2. Open a History database:
3.
4.
•
If a History database already exists, open it.
•
If a History database does not exist, select History Update History to create a History
database. The History database must exist before TCM can create a chart.
Choose History Chart History.
•
If the History file contains data for more than one apportionment method, TCM prompts
you to select the apportionment method you want to use when creating the History charts.
•
If TrendCharts, MixCharts or both are already part of the History file, the History Chart
Overwrite Warning dialog box appears. To create new Trend charts and Mix charts (the
existing ones are deleted automatically), click both boxes. This action is recommended.
Clearing either check box causes TCM to not overwrite that Chart sheet. When you finish
making your selections, click OK.
When the History Charts dialog box appears, choose a chart size: 1/4 screen, 1/2 screen
(horizontal), 1/2 screen (vertical), 2/3 screen (the default), or Full screen. Then click OK.
TCM creates the requested History charts in the specified size. Progress messages appear in
Excel's status bar at the bottom of the screen while the History charts are being created.
History Charts
125
To select a worksheet either:
•
Click its sheet tab at the bottom of the screen
•
Use the TCM Find command to find it
The TCM Find command can find the Trend charts or Mix charts (if present) as well as the
History database.
Trend Chart
The TrendCharts worksheet has one Trend chart for each transaction name in the History data.
Each Trend chart has two plot areas, one in the top half and one in the bottom half. The top half
plots the CPU Seconds per Transaction. The bottom half plots the TPS rate (if OLTP), or the
Transactions per Task rate (if Batch), and a best-fit linear trend line. Sample dates are on the x-axis
and apply to both halves of the chart.
The Trend chart is designed so you can easily see how transaction rates change over time from
sample to sample and how the corresponding transaction cost (CPU time per transaction) varies
by sample. If a reasonable apportionment scheme was used when adding the data to the History
file, the transaction cost will not vary too much from sample to sample and should not be a function
of the sample transaction throughput rate.
The Capacity Planner can use the transaction rate trend line from the Trend chart to estimate future
expected transaction rates for samples beyond those that occur in the History file. The Performance
model already allows for automated linear trend estimation of transaction throughput rates. These
History Trend charts make it easier for you to see and work with these existing rate trends in
graphical form.
Mix Chart
The MixCharts worksheet contains one Mix chart for every sample in the History data. Each Mix
chart is a 3-D pie chart showing the percentage of CPU activity each named transaction consumed
during that data sample. This data is plotted from the Mix column of the History data.
Workload Apportionment Ribbon
The WA model tabs are listed at the top of the screen in a ribbon. To select tabs and their options,
you can either point and click with a mouse, or enter commands from the keyboard. In addition,
you can select some of the most common commands by pressing a function key.
File Tab
The File tab is used to perform common operations on Workload Apportionment files, such as
opening or closing a model.
Open (F5)
The Open option opens apportionment tables or a Capacity History database. A dialog box then
displays a list of the history databases or apportionment tables that are in the current folder.
Save (F6)
The Save option saves all the WA model files, a selected apportionment table, or a Capacity
History database.
Save As
The Save As option allows you to save all the WA model files, a selected apportionment table, or
a Capacity History database with a different file name.
126
Workload Apportionment Model
Close (SF5)
The Close option allows you to close all the WA model files, a selected apportionment table, or
a Capacity History database. If you close the WA model, you return to the TCM Initial menu.
Delete
The Delete option allows you to delete any file on the workstation. If you select this option, it gives
you a list of all the files in the current folder of the same type as the file you are viewing. For
example, if you are looking at an apportionment table, you will get a list of all apportionment
table files in the current folder. Select the file you want to delete and then click Delete. After
confirmation, the file is deleted.
Exit (SF6)
The Exit option ends the TCM session and returns you to Windows.
Find Tab
The Find tab, which can be selected by pressing function key F7, lists the available Workload
Apportionment model screens that can be displayed.
If more than one screen of the selected type is open, a dialog displays the available choices. For
example, if two apportionment tables are open, a list of the tables that are currently open from
which you can choose appears.
Screens that are not open in your current session appear dimmed on the tab.
Update Tab
The Update tab lists all the update operations that you can perform on a Workload Apportionment
model. Access to some options is limited to users with a TCM administrator or super-user
authorization level.
NOTE: After you use one of the options on the Update tab, you need to use the Calculate Now
option from the Options tab (F12) to see the effect on the TCM screens.
Load Category Data (F3)
The Load Category Data option loads selected performance data into the Workload Apportionment
model. The data must already have been captured on the NonStop host system using Measure,
and the CSV file created by MeasTCM must have been downloaded to the PC. After you select
this option, a dialog prompts you to specify the file names you want to access, and whether to
display a list of .CSV files or to update history. If you select the Display List of .CSV Files option,
a second dialog box appears with a list of the files in the current folder with .CSV extensions. You
can select the appropriate sample file from this list or enter another name.
Workload Apportionment (SF10)
The Workload Apportionment option is used to create default apportionment tables and to change
current apportionment tables. Only users with a TCM administrator or superuser authorization level
have access to this option.
Find Tab
127
If you select Create Default Apportionment Tables, TCM assumes that the name of the apportionment
tables you are working with is the same as the name of the apportionment method on the Workload
Apportionment screen (with a file extension of .AWA). If this table name is not correct, enter the
file name in the appropriate area of the dialog box. To apply these changes, click OK.
If you select Change Current Apportionment Tables, a list of apportionment methods in the current
folder appears. Select the name of an existing apportionment method. Selecting this option causes
the Workload Apportionment model to use the selected method. To reapportion the existing model,
click OK.
History Tab
The History tab provides options for working with the Capacity History database of a WA model.
Update History (F10)
The Update History option adds summary performance information from the WA model to the
Capacity History database. The file name of the database has an .HST extension and appears on
the TCM Parameters screen in the History File Name field.
Search History (F11)
The Search History option searches the Capacity History database for entries that satisfy
user-specified search criteria. Before selecting this option, you need to specify one or more search
criteria in the fields labeled Search Criteria on the Capacity History screen.
NOTE: You cannot select WA options until you press the Escape key to end the search. For more
information about Excel databases, refer to the Microsoft Excel Reference Manual.
Delete History
The Delete History option allows the TCM administrator to purge selected records from the Capacity
History database. To delete records, enter the deletion criteria in the Search Criteria fields on the
Capacity History screen. After a warning message, all records that satisfy the criteria are deleted
128
Workload Apportionment Model
from the database. This option is useful for deleting all history data for an old apportionment
method.
Sort History
The Sort History option is used to sort the Capacity History data by transaction name or by sample
name. It is available only when there is a Capacity History (.HST) file in the current session.
To sort Capacity History data:
1. Select History > Sort History.
2. When the Sort History dialog box appears, click the button for the sort method.
3.
•
To see how much a transaction varies by sample, select Sort by Transaction.
•
To see a chronological list of data, select Sort by Sample.
Click OK.
For online help about the Sort History dialog box, click the Help button in the Sort History dialog
box.
Chart History
The Chart History command creates two types of History charts from the History file, Trend charts,
and Mix charts. Trend charts and Mix charts are placed on worksheets named TrendCharts and
MixCharts, respectively, in the History file workbook. To select a worksheet, click its sheet tab at
the bottom of the screen or find it using the TCM Find command.
Display Tab
The Display tab is used to specify what information TCM displays and how it is displayed.
Display (or Undisplay) Scratch Areas
The Display (Undisplay) Scratch Areas option allows you to view several areas of the model that
are hidden during normal use. These hidden areas contain valuable scratch data for the proper
operation of the model and data that could be helpful to you if you want to understand the model’s
structure and formulas. Once selected, the option toggles to Undisplay Scratch Areas, which you
can select to return the screens to their normal appearance.
Change Display Fonts
The Change Display Fonts option changes the fonts that TCM uses to display its data. TCM supports
four font characteristics: Normal, Bold, Italic, and Title. You are prompted to select the font
characteristics for each font.
For more information, refer to the Microsoft Excel documentation.
Show Value (Control-V)
The Show Value option shows the current field value up to 15 decimal places.
Display Tab
129
Print Tab
The Print tab is used to print the screens of a model.
Print (F8)
The Print option prints one or more screens in the current model. A dialog box lists the names of
the screens that you can choose to print and provides two print options.
130 Workload Apportionment Model
Select Draft Quality to print the screen using your printer’s built-in character set. This option does
not provide high-quality output, but it does offer fast printing.
Select Preview to display an image of the printed page on the PC monitor before it is actually
printed. This option is useful for checking that the page layout is correct for your particular printer
configuration before you print the screen.
If you have added notes to the screen by using the Notepad feature on the Options menu, the
notes are printed first on a separate page.
Page Setup
The Page Setup option defines the printing preferences for the page, margins, headers, footers,
and sheet. TCM provides a default page setup that can be modified using this option. For more
detail, refer to the section on file page setup in the Microsoft Excel documentation. Printing in
landscape mode generally provides better looking output for most TCM screens.
Print Tab
131
The scope of the Page Setup command is as follows:
•
Page Setup changes for a WA screen are applied to all WA model screens.
•
Page Setup changes for the Apportionment Weights table are applied to the Transactions
Counts table and vice versa.
•
Page Setup changes for a sheet of the History workbook are applied only to that worksheet.
Change Printer Fonts
The Change Printer Fonts option changes the fonts that TCM uses to print its data. Because of the
difference between printers and monitors, different fonts are frequently required for printing and
displaying data.
TCM comes with a default printer font setting that might not be appropriate for your specific
requirements. It is recommended that you select Preview from the Print option to ensure that your
printer fonts are appropriate to your needs before printing a screen.
NOTE: The fonts you select with this option are used only when TCM prints a screen. To select
the fonts used in the screen display, use the Change Display Fonts option on the Display menu.
Printer Setup
The Printer Setup option lets you specify the printer you want to use and how it should be configured.
For more information, refer to the section on file printer setup in the Microsoft Excel documentation.
Options Tab
The Options tab provides options for working with a model and for ensuring the model’s security.
Change Authorization Level (SF7)
The Change Authorization Level option changes your authorization level, provided you have a
valid password. Users with a TCM administrator or superuser authorization level have access to
more TCM options than users with a capacity planner authorization level. For more information
on TCM security and authorization levels, see “Security” (page 69).
Undo Entry
The Undo Entry option allows you to reverse the last action you performed, if possible.
Notepad (SF2)
The Notepad option allows you to attach notes to a selected screen in the model. A dialog box
provides room for a 5-line note, which you can edit by typing over, for the selected screen. Use
the Tab key to move between notes and the Enter key to complete a note.
NOTE:
page.
If you print a screen that has notes attached to it, the notes are printed first on a separate
Calculate Now (F12)
The Calculate Now option instructs TCM to calculate any changes you have made to the screens.
Unprotect (or Protect) Admin Fields
The Unprotect (Protect) Admin Fields option, which toggles between Unprotect and Protect, allows
users with a TCM administrator or super-user authorization level to modify more fields in the model.
When you select Unprotect Admin Fields, you can modify values in the highlighted fields. When
you select Protect Admin Fields, no field reserved for TCM administrators or super users can be
modified, preventing inadvertent corruption of data.
132
Workload Apportionment Model
Change Password
The Change Password option changes the TCM passwords that control access to TCM administrator
and superuser authorization levels. The default password for the TCM administrator level is “admin.”
The password for the superuser level is “super.” To enhance TCM security, modify the default
passwords. This option is available only to users with a TCM administrator or superuser authorization
level.
After you select this option, a dialog box prompts for both the existing and new (replacement)
passwords. For more information regarding TCM passwords, see “Passwords” (page 70).
Enter Excel (F4)
The Enter Excel option, available only to users with a superuser authorization level, allows you to
access the standard Excel ribbon so you can execute any Excel commands you want. You can use
non-TCM spreadsheets when you are in Excel, but be sure to close any spreadsheets that are not
part of a normal TCM session before returning to TCM.
Returning to TCM from Excel
If you enter Excel from TCM and want to return to TCM from Excel, select Enter TCM from the Excel
Home tab or press Shift-F4.
Expert Tab
The TCM Expert tab provides options to generate a Workload Apportionment Weights table,
update history with selected samples, create a default Transaction Count table, pick the best sample,
and view or modify TCM Expert parameters. This tab is available only if you selected the TCM
Expert option on the initial TCM tab.
For more information on these options, see Chapter 10: “Using TCM Expert”.
Generate Expert Apportionment Weights
The Generate Expert Apportionment Weights option generates a Workload Apportionment Weights
table and updates a History file automatically. A dialog box provides fields for you to enter the
name of the history file. If one does not exist, TCM creates it. The field labeled Apportionment
Table File enables you to select an existing Transaction Count table and provides the name for the
Apportionment Weights table that TCM Expert generates. In addition, you can add or remove the
CSV files to be used in the generation from this dialog box.
Data Splitting
TCM Expert uses the statistical concept of data splitting to give you a higher confidence level in
its results. When TCM Expert generates apportionment weights, it uses 2/3 of the CSV files selected.
TCM Expert does not use the other 1/3 of the CSV files selected but reserves those CSV files as a
test sample for consistency. When TCM Expert updates the history file, it uses all of the CSV files
selected and at that time tests all of the samples for consistency. If TCM Expert finds inconsistencies,
it reports this information in a dialog box.
If you are a TCM super user, the dialog box shows Percent of Selected CSVs used to generate. (If
you are not a TCM super user, the dialog box does not show this field.) This field shows the
percentage of CSV files out of all the selected CSV files from which TCM Expert generates the
Apportionment Weights table. The default is 67 percent. If you have too few samples to make an
accurate Apportionment Weights table, you might want to increase this percentage. By increasing
this percentage, you have a better chance of getting an accurate Apportionment Weights table,
but you reduce the confidence level of the results.
Expert Tab
133
Update History With Selected CSVs
The Update History With Selected CSVs option enables you to update a History file with selected
CSV files. If TCM Expert finds inconsistent transaction costs, it reports this information to you in a
dialog box.
Create Default Transaction Count Table
The Create Default Transaction Count Table option enables you to create a default Transaction
Count table based on a selected CSV file. It also checks for transaction cost consistency in the
History file.
To create a default Transaction Count table:
1. Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box appears.
2.
3.
4.
Specify a custom folder and click OK.
Log on as an administrator or super user. For more information about this step, see “Changing
Authorization Levels” (page 70).
If you do not have an existing Apportionment Weights table or Transaction Count table, select
TCM Expert > Create > Default Transaction Count Table.
The Default Transaction Count Table dialog box appears. TCM Expert provides a default
Transaction Count table name and selects a CSV file from which to generate the default table.
Click OK to accept the defaults or choose a different name and CSV file and then click OK.
5.
If you have a type T (TMF) process category defined in the selected CSV file, the Create Default
Apportionment Tables dialog displays.
Using your knowledge of the application, you can select which transactions are audited (or
not audited) by placing them in the appropriate list. When the default Apportionment Weights
table is created, audited transactions are indicated by a 1 for any type T process category.
Unaudited transactions will be indicated by a 0.
6.
7.
8.
Click OK. TCM Expert generates a default Transaction Count table and Apportionment Weights
table and displays the newly generated “Transaction Count Table” (page 119).
Examine the default Transaction Count table. If you want to make changes:
a. Select Options > Unprotect Admin Fields.
b. Enter the corrected values.
c. Select Options > Protect Admin Fields.
Examine the default Apportionment Weights table. To navigate to that table, select Find >
Apportionment Weights Table.
TCM displays the default “Workload Apportionment Weights Table” (page 117).
9.
For process categories for which you have specific application knowledge, you might want
to override the default Expert Flag and enter your own numbers. The Expert Flag indicates
whether TCM Expert should generate a value for the process category. The default for the
TMF (T), Disk (D), Fixed (F), and Ignore (Z) process categories is N (no). The default is also N
for server categories whose names exactly match the transaction names. The default value for
all other process categories is Y.
If you want to override Expert’s calculations for any category marked with a Y (yes):
a. Select Options > Unprotect Admin Fields. TCM makes modifiable fields shaded.
b. Type an N in the Expert Flag column of the category you want to override and enter the
values you think are correct under the transaction columns.
c. Select Options > Protect Admin Fields.
134
Workload Apportionment Model
Pick Best CSV Sample
Use the Pick Best CSV Sample option to select the most representative CSV file from all the available
CSV files. When you select Pick Best CSV Sample, the Pick Best CSV Sample dialog box appears.
Select a History file from the available files and click OK. TCM Expert computes the average CPU
seconds for each transaction, assigns a weight to each transaction, and then picks the most
representative sample across all samples.
TCM Expert selects the best sample. Add screen capture for the Pick Best CSV Sample dialog box.
Click Don’t Create to close the dialog box. Click Create to have TCM automatically load this load
sample into a new Performance model.
TCM Expert Parameters
The TCM Expert Parameters option enables you to view or change the global TCM Expert
parameters.
Check History Over Last Field
The Check History Over Last field specifies the exact time period parameters. This field specifies
the time range, which is used in three situations:
•
The time range that is checked for transaction cost consistency when Generate Expert is
executed.
•
The time range that is checked for transaction cost consistency when Update History with
Selected CSV Samples is executed.
•
The time range that is used when the Pick Best Sample option is selected.
The default time period is six months.
Cache Miss Factor
The Cache Miss Factor field specifies the relative CPU cost to the disk process of a cache miss as
compared with a cache hit. The default settings assume that a cache miss costs twice as much as
a cache hit. Only a TCM administrator or superuser can modify this factor.
Expert Tab
135
CPU Pathlength Threshold
The CPU Pathlength Threshold field specifies the point at which a query transaction is considered
either an OLTP or batch transaction. The default setting is two seconds.
Small demand queries taking less than two seconds are considered OLTP transactions, and large
demand queries taking longer than two seconds are considered batch transactions. Any TCM user
can modify this factor.
Help Tab
The Help tab provides information about the TCM fields, function keys, and operating environment.
TCM Help (F1)
TCM Help displays context-sensitive help messages about the currently selected field.
Exiting Help
To exit Help, select Exit from the File tab of the Help window or click outside the Help window.
Function Keys (SF1)
The Function Keys option lists all the TCM function keys and their meanings. You can also access
this function by pressing SF1.
About
The About option displays information about the TCM environment.
136
Workload Apportionment Model
9 The Performance Model
The Performance model is used to answer what-if questions about baseline sample data that has
already been computed in the Workload Apportionment model of TCM. You can analyze estimated
throughputs, host response times, and the number of CPUs and logical disk volumes required to
support different user-defined scenarios. The Performance model also provides presentation-quality
charts for reporting estimated performance results.
This section describes the screens and menus of the Performance model.
Performance Model Components
The Performance model is composed of two submodels that examine apportioned data: the
Consumption model and the Planning Timeline model. These models are represented as two of the
thirteen screens that make up the Performance model. The Performance model consists of the
following main screens:
•
•
Capacity Baseline Actual—a screen that summarizes the source data for the Performance
model. It has the same data as in the WA model, but it is modifiable. This data is used in the
following components of the Performance model:
◦
Consumption model
◦
Planning Timeline model
Consumption Model—a model used to compute the number of CPUs and disks required to
accommodate one or more performance targets, or vice versa, including:
◦
Target host response time for online transactions
◦
Target CPU utilization, disk utilization, or both for online transactions
◦
Target host response time for batch transactions
◦
Planned OLTP throughputs
◦
Planned batch transactions per task
◦
CPU device type
◦
Disk configuration type (such as audited and nonaudited)
◦
Disk write cache configuration (such as enabled and disabled/NA)
◦
Number of CPUs
◦
Number of logical disk volumes and number of TMF audit trails
•
Disk Factors—a screen used to view disk model number, rotational speed (rpm), controller,
disk read seek time and write seek time.
•
Planning Timeline—a model used to examine transaction rates and host response times over
six user-specified planning intervals. Several growth scenarios can be specified, including:
◦
Throughput growth
◦
Number of CPUs, disks, or both over time
◦
CPU type
◦
Disk configuration type
Performance Model Components
137
◦
Disk write cache configuration
◦
Number of TMF audit trails required
•
TCM Parameters—used to set various parameters for the Performance model.
•
CPU Conversion Factors—used to set factors that represent the relative CPU speeds assumed
for the application or set of applications in the model.
•
Baseline Detail by Category Actual—shows detailed information about process categories,
CPU consumption by transaction, category priority, disk process priority queuing, and CPU
tunability.
•
Baseline Detail by Category Plan—used to view detailed characteristics about process
categories. The screen defaults to the actual data but is modifiable.
•
Charts—provides presentation-quality charts of the data in the Planning Timeline model.
•
Capacity History Database—a database used to archive and organize apportionment data
from the WA model. Capacity history is organized as an Excel database and presents
information that is useful to the capacity planner for such tasks as apportionment validation,
trend analysis, and selection of representative samples. This screen is available for read-only
access in the Performance model.
•
Capacity History TrendChart—The Trend chart is designed so you can easily see how transaction
rates change over time from sample to sample and how the corresponding transaction cost
(CPU time per transaction) varies by sample. If a reasonable apportionment scheme was used
when adding the data to the History file, the transaction cost will not vary much from sample
to sample and should not be a function of the sample transaction throughput rate.
•
Capacity History MixChart—3-D pie charts that show the percentage of CPU activity for each
named transaction consumed during a data sample.
•
TCM User Customization screen—used to change the appearance of the TCM screens. The
user can change the Display/Printer font properties, the background colors, and the font color
of the Manually overwritten cells.
Each of the screen descriptions shows a sample screen and describes the significant rows and
columns.
Data Source
The source of the data for the Performance model is the Workload Summary and Workload Detail
screens in the WA model or their equivalent. To load data into the Performance model, either:
•
Select Create a New Performance model from the “TCM Initial Menu” (page 67). TCM prompts
you to pick either an .SWA file or a CSV and associated .AWA file from your custom folder.
•
From the TCM Expert tab, select Create Pick Best Sample. TCM loads the best sample into a
new Performance model.
NOTE: Although the WA model is the usual data source for the Performance model, you can
also directly add, change, or delete transaction data in the Performance model by selecting Add
Transaction, Delete Transaction, Add Category, or Delete Category from the Update tab. For
example, do this to model theoretical transactions for which no Measure data exists.
Navigation
To move from one screen to the next in the Performance model, select the name of the screen you
want to view from the Find tab or from a tab at the bottom of the screen.
To go to the User Customization screen, select the Customize TCM command from the Options
tab.
138
The Performance Model
Screen Descriptions
Help is available for fields on all the Performance model screens by selecting the field you want
information about and selecting Help > TCM Help.
The Read-only (protected) and User-modifiable (unprotected) fields of the screens have different
background colors for easy identification. The default background of the Read-only fields is brown,
and that of the User-modifiable fields is yellow.
In the Consumption Model, Planning Timeline Model, CPU Factors, Disk Factors, and Plan Baseline
Detail by Category screens, whenever the formula of any Usermodifiable cell is overwritten with
a value, the font of that cell becomes bold and takes on the color of the text 'Manual Overwrite
Font ColorIndex' in the User Customization screen. The Default Manual Overwrite color is blue.
Therefore, if you can easily see where custom changes have been made.
The significant rows and columns of each screen are described in the following sections.
Capacity Baseline—Actual Screen
This screen summarizes the source data for the Performance model. It has the same data as the
WA model.
This screen is used as the baseline from which the Performance model algorithms derive the
projections used in the Consumption and Planning Timeline models.
The throughput and cost in CPU and disk seconds for each transaction are summarized. Similar
information is shown for the average (weighted) transaction as well as for consumption that is
fixed. The fixed category is used for activity that does not increase as throughput increases (for
example, some types of asynchronous data communication polling or the HP Measure product).
Figure 44 (page 139)Figure 9-1 shows a sample Capacity Baseline–Actual screen.
Figure 44 Capacity Baseline—Actual Screen
Screen Descriptions
139
Significant Rows
1.
Application—Not directly Modifiable
Application is the user-defined name of the application as it appears in the associated WA
model.
2.
Sample File—Not directly Modifiable
Sample File is the file name of the associated WA model.
3.
Sample Date—Not directly Modifiable
Is the creation date of the input file which used to work with the performance model.
4.
Planning Unit—Modifiable by the user
Planning unit is the unit of transaction rate.
In some cases, you will want to use a larger throughput unit than the TCM default of transactions
per second. The value in the Planning Unit field can be Second, Minute, Hour, Day, or Month.
If you enter Day, for example, all Performance model throughputs appear as transactions per
day. The axis on the charts (see “Planning Timeline Model Chart” (page 163)) are also adjusted
to reflect the new unit. An error message appears in a nearby field if an incorrect planning
unit is entered.
5.
Apportionment—Not directly Modifiable
Apportionment is the name of the apportionment method used in the associated WA model.
6.
CPUs—Modifiable by the TCM administrator
This row lists the number and type of the CPUs in the sample. For a list of valid CPUs, refer
the CPU Factors screen. (See Figure 49 (page 152).)
7.
SW Release—Modifiable by the TCM administrator
SW Release is a changing in RVU number. Whenever the TCM administrator or super user
modifies the CPU type, the value of SW Release is automatically set to the latest intended RVU
for which this CPU type is supported in the CPU Factors screen.
8.
Disks—Modifiable by the TCM administrator
Disks is the number of disks.
9.
Disk Config—Modifiable by the TCM administrator
Disk Config is the number and configuration type for all logical disk volumes in the sample.
A list of valid disk configuration types is shown on the TCM Parameters Screen. (See Figure 48
(page 151).)
10. TMF Audit Trails—Modifiable by the TCM administrator
TMF audit trails depict the number of audit trails used in the sample. The value for the TMF
audit trail can be between 1 and 16 for audit disk configuration. For unaudited disk
configuration, it is not applicable.
11. Disk Write Cache—Modifiable by the TCM administrator
Disk Write Cache specifies if the write cache enable (WCE) option is ENABLED or DISABLED.
For disks that support WCE, the default value is DISABLED. For disks that do not support WCE,
this field is NA (not applicable).
12. Physical Disks—Not directly modifiable
Physical Disks is number of physical disks in the system.
140 The Performance Model
Significant Columns
13. Txn Name—Modifiable by TCM Administrator
Txn Name is the name of the transactions as shown in the Workload Summary screen of the
Baseline WA model.
14. Type—Not directly modifiable
Type indicates the type of transaction. X indicates an online (OLTP) transaction, B indicates a
batch transaction, and Q indicates a query transaction. When the Scratch Areas appear, the
first Type column shows the source transaction type X, B, or Q, and the adjacent column shows
whether the transaction is being modeled as type X or B.
15. Unlabeled Column—Not directly modifiable
The unlabeled column indicates Aud if the transaction is audited but is left blank otherwise.
A transaction is considered audited if it has a nonzero entry in the TMF process category in
the Apportionment Weights table.
16. TPS (or TPH, TPD, or TPM)—Not directly modifiable
TPS, TPH, TPD or TPM indicates the average number of transactions per second, hour, day,
or month and applies to OLTP transactions (type x) only. The TPS is computed from the number
of transactions and the size of the sample window. When the Scratch Areas are visible, the
first TPS column shows the throughput in transactions per second, and the second shows
throughput in the units you select (for example, transactions per hour).
17. #Txns per Task—Not directly modifiable
#Txns per Task applies to batch transactions only. It is the number of subtransactions within
the batch task or transaction itself.
18. CPU Sec—Not directly modifiable
CPU Sec is the apportioned number of CPU seconds (adjusted to include interrupt seconds)
consumed per transaction as shown in the Workload Summary screen of the Baseline WA
model. The Average Txn row contains the (weighted) average of CPU seconds for each
transaction.
19. Disk Sec—Not directly modifiable
The apportioned number of disk read and disk write seconds consumed per transaction as
shown in the Workload Summary screen of the Baseline WA model. The Average Txn column
contains the (weighted) average of disk seconds or each transaction. When you select Display
Scratch Areas from the Display tab, this section expands to show more detailed information.
Consumption Model Screen
The Consumption model calculates the number of CPUs and disks required to achieve acceptable
performance as defined by the capacity planner. The model also estimates host response times,
utilizations, and maximum throughputs.
In the Consumption model, you define acceptable performance by defining the rules the model
should use in developing its planned, or estimated, performance and the requirements of the system.
To do this, specify constraints for items such as host OLTP response time, device utilizations, and
the number of CPUs, disks, or both. Within these constraints, the Consumption model determines
the number of CPUs and disks required and the expected performance characteristics of the
application under study.
When one or more of the constraints is not achievable, a warning message appears with an
asterisk (*) displayed next to the unachievable constraint.
You can also specify planned transaction throughputs that are different from the actual throughputs.
In addition, super users can change the CPU or disk seconds per transaction in the Plan column
to investigate the effect of possible changes in the processing requirements of a given transaction.
Consumption Model Screen
141
Figure 45 (page 142) shows a sample Consumption model.
Figure 45 Consumption Model
Significant Rows
1.
Number—Constraint modifiable
Number is the actual, constrained, and planned number of CPUs and disks required to achieve
the performance specified by the constraints you set. The number of devices is for a well-tuned
system. If the system is not well-tuned, more CPUs, disks, or both could be required.
NOTE:
2.
TCM does not model disk space.
Processor Type and SW Release—Constraint modifiable
Processor type is the actual, constrained, and planned CPU types. SW Release is the NSK
release for the selected Processor Type. The user can select one of the values from the
drop-down lists that appear when these fields are clicked. Whenever the user selects a CPU
type, the value of the SW Release is automatically set to the latest NSK release for which this
CPU type is supported.
Valid CPU types and NSK releases are listed in the CPU Conversion Factors screen.
CPU seconds are scaled if the planned CPU type differs from the actual CPU type.
3.
Disk Model—Constraint modifiable
Disk Model is the actual, constrained, and planned Disk Model number.
The user can select one of the values from the drop-down lists that appear when the Disk
Model field is clicked.
Valid Disk Model numbers are listed in the Disk Factors screen.
4.
Disk Config—Constraint modifiable
Disk Config is the configuration type for all logical disk volumes in the sample. Valid Disk
configuration types are listed in the scratch areas of the TCM Parameters screen.
5.
Disk Write Cache—Constraint Modifiable
Disk Write Cache is the actual, constrained, and planned Write Cache Configuration for the
selected Disk Model. Disk Write Cache specifies if the write cache enable (WCE) option is
ENABLED or DISABLED. For disks that support WCE, the default value is DISABLED. For disks
that do not support WCE, this field is NA (not applicable). Whenever the user selects a Disk
142
The Performance Model
model, the value of the Disk Write Cache is automatically set to the default write cache value
corresponding to the selected Disk model.
6.
TMF audit trails—Constraint Modifiable
TMF audit trails depict the number of audit trails used in actual measurement. The value for
the TMF audit trail constraint field can be between 1 and 16. The number of audit trails
required for planned data is based on the TMF seconds required for planned transactions
and the audit write ceiling value for each audit trail and type of audit trail configuration
(mirrored, unmirrored or serial).
7.
Avg Online Util—Constraint modifiable
Avg Online Util is the average percentage utilization of actual and planned CPUs and disks
for online transactions. These utilization values cannot exceed the values in the Constraint
fields, if values are entered. To enter a utilization percentage in a Constraint field, type any
whole number between 1 and 99.
8.
Avg Online Resp Time—Constraint modifiable
Avg Online Resp Time is the host response time for the actual and planned average transaction
for online transactions. You can enter the maximum chosen value for the estimated host response
time in the Constraint field. This field is particularly useful if a known host response time
requirement for the average (90, 95, or 99%) transaction must not be exceeded. If a value
is entered, the Consumption model estimates the number of CPUs and disks so that the estimated
host response time for the average (90, 95, or 99%) transaction is below this value, if possible.
Use the Select Response Time Method on the Options tab to set the type of response time
wanted. Note that the average (90, 95, or 99%) online response time is a weighted average
of the individual OLTP transactions average (90, 95, or 99%) response times.
9.
Avg Batch Resp Time—Constraint modifiable
Avg Batch Resp Time is the host response time for the actual and planned average transaction
for batch transactions. You can type the maximum desired value for the estimated host response
time in the Constraint field. This field is particularly useful if a known host response time
requirement for the average batch transaction must not be exceeded. If a value is entered,
the Consumption model estimates the number of CPUs and disks so that the estimated host
response time for the average batch transaction is below this value, if possible. Note that the
average batch response time is an unweighted average of the individual response times of
the batch transactions. Batch times longer than 999 hours (41.625 days) are displayed as
999 hours.
10. Sample File—Not directly modifiable
The input file name used to work with performance model.
11. Sample Date—Not directly modifiable
Is the creation date of the input file which used to work with the performance model.
12. Disk Partitions — Disk partitions are the actual, constrained, and planned partition configuration
for SSD disks. Disk partition specifies whether the SSD disk is partitioned or not. If partitioned,
it also specifies the number of partitions. For non SSD disks, this field is NA (not applicable).
Whenever the user selects the SSD model, the value of the disk partition is automatically set
to one, and enables users to select values from 1 to 8.
Consumption Model Screen
143
Significant Columns
13. Txn Name—Modifiable by TCM Administrator
Txn Name is the name of the transactions as shown in the Workload Summary screen of the
Baseline WA model.
14. Txn per Sec (or Hour, Day, or Month)—Plan modifiable
Txn per Sec is the actual and planned transaction rates for each transaction in the model
expressed in the user-defined planning unit (transactions per second, minute, hour, day, or
month). The value in the Average Online Txn field shows the total transaction rate. If you do
not want to include a transaction in your what-if analysis, type zero (0) for the planned
transaction rate. For batch transactions, it shows the resulting throughput given the transactions
per task and the TCM calculated response time.
The Max field shows the maximum throughput achievable for each transaction, given the
planned number of devices, their constraining utilizations, and the average response time
constraint.
15. Txns per Task—Plan modifiable
Txns per Task is the number of transactions per task and applies to batch transactions only.
16. CPU Seconds—Modifiable through the Change Transaction option of the Update tab
CPU Seconds is the actual and planned consumption, or cost, per transaction in CPU seconds
(also referred to as the CPU demand) for each transaction. Fixed CPU seconds are not included
in the CPU demand for individual transactions. The value in the Average Txn field shows the
CPU demand for a weighted average OLTP transaction or the unweighted average of the
batch transaction.
Users with a TCM administrator or superuser authorization level can modify the planned CPU
seconds (by using the Change Transaction option of the Update tab) to examine the effect of
possible changes in the CPU seconds consumed by a given transaction.
144 The Performance Model
17. Disk Seconds—Modifiable through the Change Transaction option of the Update tab
Disk Seconds is the actual and planned consumption, or cost, per transaction in disk seconds
for each transaction.
18. Avg Resp Time—Not directly modifiable
Avg Resp Time is the host response time for each transaction and the average or specified
percentile transaction. This number includes both CPU and disk response times. It does not
include communication line time and therefore is not end-to-end. Expected OLTP response
times for CPUs are calculated using a standard M/M/1 with priority queueing model. Expected
OLTP response times for disks are calculated with the M/U/1 model. Total OLTP host response
time in a system is the sum of the CPU response time and disk response time. The actual
average response time, as well as the plan, are estimates based on queueing theory and are
not measured directly.
Batch transaction response time is calculated using a multiple priority closed queueing model
and is always the average response time. Specified percentile response times apply only to
OLTP. For more information, see “Modifying Percentile Response Times” (page 91), Chapter 7:
“Modeling Batch Workloads”, and Appendix D: “TCM Response Time Formulas”.
Waited writes of any TXN are either all audited or all not audited. If audited, TMF Audit trails
will give the number of audit trails required. If not audited, writes are either serial or parallel
on all mirrored disks.
The demand numbers used to compute host response time do not include the demand for fixed
categories, it is assumed that transactions do not wait for fixed activity to complete. However,
fixed consumption is included in the utilization figures.
The average transaction response time is the expected host response time for the (weighted)
average OLTP transaction or the unweighted average batch transaction. The value in the Plan
Average Response Time field for the average transaction must be less than or equal to the
number in the Plan Average Response Time target field described previously, if one has been
entered. For individual transaction types, these fields reflect the expected host response time
for that type of actual or planned transaction.
Disk response time depends on the disk configuration type (audited, nonaudited, unmirrored,
or serial). For response time formulas that TCM uses, see Appendix D: “TCM Response Time
Formulas”.
Planning Timeline Model Screen
The Planning Timeline model is used to examine the impact of various upgrade scenarios and is
integral to the capacity planning process. It examines the changes in CPU and disk utilization
levels and host response times for eight time periods as throughputs, numbers of CPUs and disks,
and types of CPU and disk configurations vary. This model is useful for capacity planning when
specific changes to hardware configuration, transaction throughputs, or both are anticipated or
proposed.
Each Planning Timeline model shows eight scenarios. The first column shows the Actual sample
data from the Consumption model. The user can select either the first plan scenario data (second
column) from either the Actual data or the Plan data of the Consumption model. The default shows
the Actual Data. The remaining scenarios are all related to the planned scenario in the second
column. Each throughput level is incrementally higher than the one prior by the percentage specified
in the Rate column. Figure 46 (page 146) screen.
Planning Timeline Model Screen
145
Figure 46 Planning Timeline Model
CAUTION: Modifying a field erases the formula it originally contained. If you typed over data
in a field, erasing the formula originally contained in the field, you can use the Refresh Formulas
option on the Update tab to reinitialize the formulas in the screen.
Significant Rows
1.
Time Increment—Directly Modifiable
Time Increment is the number of months between adjacent periods in the planning timeline.
The initial default time increment is six months.
2.
Default Growth Rate—Directly Modifiable
Default Growth Rate is the default growth rate for each period. If you enter a percent sign (%)
in the adjacent cell on the right, the growth rate is expressed as a percentage. Otherwise,
throughput is incremented in absolute transactions. For example, if a default annual rate of
500 is specified in a batch transaction, throughput is incremented by an annual rate of 500
tasks for each time period.
3.
Planning Dates—Directly Modifiable
These fields default to the dates established by the Time Increment field but can be changed
to any text string that describes your planning scenario, such as fiscal quarter dates and project
milestones.
4.
# CPUs and CPU Type—Directly Modifiable
# CPUs and CPU Type are the chosen number and type of CPUs for any of the Scenario dates
in the Planning Timeline model. Whenever you selects a CPU type, the value of the SW Release
is automatically set to the latest RVU for which this CPU type is supported. Valid CPU types
are listed on the CPU Conversion Factors screen. Initially, the first column values match the
actual number and type of CPUs, as shown in the first date column in the series. Columns 2
through 8 initially match the Actual data, or the Plan data from the Consumption Model
depending on the value of the First Plan Scenario From Consumption Model button. When
you type over any value, the new value automatically propagates to the fields on the right. If
you enter a CPU Type that is not listed in the CPU Conversion Factor screen, a red "?Bad
CPU" value appears in the row between the top and bottom sections of the screen when you
press Calculate Now (F9).
146
The Performance Model
5.
# Disks, Disk Model, and Config—Directly Modifiable
#Disks, Disk Model and Config are the desired number, Model, configuration of disks for any
of the Scenario dates in the Planning Timeline model. Valid disk model numbers are listed in
the Disk Factors screen. Valid disk configuration types are listed in the scratch areas of the
TCM Parameters screen. Initially, the first column values match the actual number and model
of disks, as shown in the first date column in the series. Columns 2 through 8 initially match
the Actual data, or the Plan data from the Consumption Model depending on the value of the
First Plan Scenario From Consumption Model button. When you type over any value, the new
value automatically propagates to the fields on the right. If you enter a disk model number
that is not listed in the Disk Conversion Factor screen, a red "?Bad Disk Model" value appears
in the row between the top and bottom sections of the screen when you press Calculate Now
(F9).
NOTE:
6.
TCM does not model disk space.
Disk Write Cache—Directly Modifiable
Disk Write Cache is the desired write cache configuration for any of the Scenario dates in
the Planning Timeline model. Valid Write Cache configurations are listed in the scratch areas
of the TCM Parameters screen. Initially, the first column values match the actual configuration
as shown in the first date column in the series. Columns 2 through 8 initially match the Actual
data, or the Plan data from the Consumption Model depending on the value of the First Plan
Scenario From Consumption Model button. When you type over any value, the new value
automatically propagates to the fields on the right.
7.
TMF audit trails—Directly Modifiable
TMF Audit Trails is the desired number of TMF audit trails for any of the Scenario dates in the
Planning Timeline model. For audit disk configurations, TMF trails can be between 1 and 16.
For unaudited configurations it is NA (not applicable). Initially, the first column values match
the actual configuration as shown in the first date column in the series. Columns 2 through 8
initially match the Actual data, or the Plan data from the Consumption Model depending on
the value of the First Plan Scenario From Consumption Model button. When you type over
any value, the new value automatically propagates to the fields on the right.
8.
Total Online TPS—Not Directly Modifiable
Total TPS, TPH, TPD, or TPM is the planned throughput for each transaction in userspecified
planning units (transactions per second, hour, day, or month) for each time period.
9.
Avg Online Resp Time—Not Directly Modifiable
Avg Online Resp Time is the estimated host response time for each transaction, given its
throughput and excluding communications line time, for each time period.
10. Avg Batch Resp Time—Not Directly Modifiable
Avg Batch Resp Time is the estimated host response time for each transaction, given its
throughput and excluding communications line time, for each time period. This result is based
on the multiple Priority Closed Queueing model. For more information, see Chapter 7:
“Modeling Batch Workloads”, and Appendix D: “TCM Response Time Formulas”.
11. TPS (TPM or TPH)—Directly Modifiable
TPS, TPM or TPH is the throughput for each transaction for each time period. To predict host
response times and utilizations for a specific transaction for a specific date, simply type over
the value in the appropriate field. Type zero (0) in the field if you do not want to include that
transaction in the model’s projections. Throughput amounts to the right of the modified field
automatically increment according to the specified rate.
Planning Timeline Model Screen
147
12. #Txns—Not Directly Modifiable
#Txns is the number of transactions per task if a batch transaction. This number can be trended
using the Timeline Trends option of the Update menu.
13. Disk Partitions — Disk partitions are the actual, constrained, and planned partition configuration
for SSD disks. Disk partition specifies if the SSD disk is partitioned or not. If partitioned, it also
specifies the number of partitions. For non SSD disks, this field is NA (not applicable).
Whenever the user selects the SSD model, the value of the disk partition is automatically set
to one, and enables users to select values from 1 to 8.
Significant Columns
14. Txn Name—Modifiable by TCM Administrator
Txn Name is the name of the transactions as shown in the Workload Summary screen of the
Baseline WA model.
15. Rate—Directly Modifiable
Rate is the rate at which planned throughput will grow for each transaction, expressed as
percentages or absolute planning units. You can use these fields to override the value in the
Default Growth Rate field (the value which they initially contain) when the expected transaction
growth rates of some transactions are different from others. This number can be a percentage
or absolute number of transactions. Instead of estimating the growth rate, you can have TCM
use the historical trend. This feature is called throughput trending. For more information, see
“Update Tab” (page 165).
To do throughput trending with the Planning Timeline model:
a. Select Update Timeline Trends.
b. Highlight the transaction to trend and optionally type the start and end dates.
c. Click OK.
The transaction trend is used to update the Planning Timeline screen. If you are using a
color monitor, the trend appears in red.
TCM Parameters Screen
The TCM Parameters screen is used to set parameters for the TCM Performance model. These
parameters can be modified by users with a TCM administrator or superuser authorization level.
Figure 47 (page 149) shows a sample TCM Parameters screen.
148
The Performance Model
Figure 47 TCM Parameters Screen
Significant Rows
1.
Number of Batch CPUs—Directly Modifiable
Number of Batch CPUs is the number of CPUs assigned to batch transactions. The default is
All. For more information on this parameter, see “Number of Batch CPUs” (page 102).
2.
Maximum CPU Utilization—Directly Modifiable
Maximum CPU Utilization is the percentage of CPU that is available for batch activity. The
default is 100 percent. For more information on this parameter, see “Hardware Utilization
Thresholds for CPU and Disk” (page 102).
3.
Maximum Disk Utilization—Directly Modifiable
Maximum Disk Utilization is the percentage of disk that is available for batch activity. The
default is 50 percent. For more information on this parameter, see “Hardware Utilization
Thresholds for CPU and Disk” (page 102).
4.
Calculate Batch response times with completed jobs removed from the system—Directly
Modifiable
This option determines how batch jobs are handled. When this option is set to TRUE, batch
jobs are removed from the system when they complete. The remaining jobs then speed up
because the CPU and disk resources are shared by fewer active jobs. When this option is set
TCM Parameters Screen
149
to FALSE, TCM assumes that all batch jobs restart when completed. No matter how long batch
jobs actually take, they are all considered to be running simultaneously all of the time. The
default value is TRUE.
5.
Query Transaction OLTP-> Batch response Time CPU pathlength threshold—Directly Modifiable
This option is the point at which a query transaction is considered either an OLTP or batch
transaction. The default setting is two seconds. Small demand queries taking less than two
seconds are considered OLTP transactions. Large demand queries taking longer than two
seconds are considered batch transactions. Any TCM user can modify this parameter.
6.
Audit Write Ceiling—Directly Modifiable
Audit Write Ceiling is the maximum number of audit writes per second. The model provides
a default value, but a TCM administrator or super user can modify it if a more appropriate
value is available.
7.
# Commits per Txn—Directly Modifiable
# Commits per Txn is the number of TMF transactions in a business transaction. A business
transaction is sometimes made of more than one TMF transaction. That is, it has more than
one begin-end transaction statement pair. Its value affects TCM response time estimates.
NOTE:
8.
This field applies to all audited transactions in the model. Its default value is one.
Audit Disk Configuration—Directly Modifiable
Audit Disk Configuration is the assumed disk configuration for audit disk. The specified
configuration must be one of the following: Mirr (mirrored), Unmirr, (unmirrored) or Serial.
9.
Response Time Gamma Factor—Directly Modifiable
It is the Disk Rotation Factor, that is, Number of Disk Rotations per Second. One quarter of
the time it takes to do a rotation is added in as part of the Response Time formulas for parallel
writes. This extra factor is needed because parallel writes never occur truly simultaneously,
one disk taking slightly longer than the other.
CPU Factors Screen
The CPU Factors screen is used to set the CPU conversion factors used by the Performance model
and to add new CPU types, RVUs and factors to model systems with theoretical CPU types (along
with their IPU count). Figure 48 (page 151) shows a sample CPU Factors screen.
150
The Performance Model
Figure 48 CPU Factors Screen
The leftmost column contains the names of the supported processor types in TCM. The first row
contains the RVUs. The table contains the conversion factors for different configurations of CPU
types and RVUs.
The rightmost column contains the IPU count for multi-core processors and this field is not applicable
for single core CPUs.
When the CPU configuration types differ, the model's planned CPU consumption is estimated from
the actual CPU consumption using these factors. A new CPU type or RVU can be added to the
blank fields in the table. You must be either a TCM administrator or a superuser to change the
values in this screen.
If the available fields are less than the number of new CPU types and RVUs to be added, you can
overwrite the factor, processor, and RVU names of some existing unused CPU type and RVU pair.
To restore the original table, select the Refresh Formulas command from the Update tab and then
select the CPU Conversion Factors screen.
Disk Factors Screen
This screen lists the disks for TCM, with their model numbers, rotational speeds, controllers, disk
read seek time and write seek time. Figure 49 (page 152) shows a sample Disk Factors screen.
Disk Factors Screen
151
Figure 49 Disk Factors Screen
152
The Performance Model
Disk Factors Screen
153
154 The Performance Model
NOTE: Although RPM, read seek, and write seek times are mentioned in the disk factor sheet,
they are not considered in the actual calculation of SSD disk values, as these three parameters are
not applicable for SSD disks.
Users can add a new disk in the blank rows at the end of the table. You must be either a TCM
administrator or a super user to change the values in this screen. If the available fields are less
than the number of new disks to be added, you can overwrite some of the unused existing entries.
To restore the original table, use the Refresh Formulas command from the Update tab.
Actual Baseline Detail by Category Screen
The Actual Baseline Detail by Category screen is used to view detailed characteristics about process
categories. This screen cannot be modified. Figure 50 (page 155) shows a sample Actual Baseline
Detail by Category screen.
Figure 50 Actual Baseline Detail by Category Screen
Significant Rows
1.
Txn Type—Not Directly Modifiable
Online transactions are Txn Type X. Batch transactions are Txn Type B.
2.
Total CPU Secs—Not Directly Modifiable
Total CPU Secs is the number of CPU seconds used by the transaction type.
Significant Columns
3.
Cat Name—Not Directly Modifiable
Cat Name lists the category names of all process categories as they appear on the Category
Demand Report. These categories are appear in rows in the Apportionment Weights table.
Actual Baseline Detail by Category Screen
155
The table is used to indicate how the CPU and disk seconds consumed by these categories
are to be allocated to each transaction.
4.
Type—Not Directly Modifiable
Type is the type of a process category, as defined in MeasTCM on the NonStop host system.
The category type consists of one of the following characters:
5.
S
Server process
R
Requester process
D
Disk process (including all nonaudited disk processes)
T
TMF processes (including all audit disk processes)
L
Line handler process
O
Other
F
Fixed (system overhead that does not vary with throughput)
Z
Ignore these categories (appropriate interrupt and disk activity to be omitted)
Tunable CPU—Not Directly Modifiable
Tunable CPU applies to batch transactions only. Y indicates that batch transactions are spread
evenly across all available batch CPUs. N indicates that batch transactions are assigned to
run in only one CPU.
6.
Fixed CPU Sec—Not Directly Modifiable
The total number of CPU seconds consumed per second by process categories of type F (fixed).
This number is not included in the CPU and disk consumption of individual transactions, but
does affect the total CPU and disk utilizations. A category should be defined as type F if its
CPU and disk consumption do not increase as throughput increases, such as during
asynchronous data communications polling activity or the running of Measure.
7.
Priority—Not Directly Modifiable
Priority is the priority of the process category.
8.
CPU Seconds Per Transaction—Not Directly Modifiable
CPU Seconds Per Transaction are the CPU seconds allocated to each transaction by process
category.
9.
Not shown. CPU Sec and DP CPU Sec Tables—Not Directly Modifiable
The CPU Sec and DP CPU Sec tables are visible only when you select the Display Scratch
Areas option. The values in these tables are the CPU seconds and DP CPU seconds allocated
to each transaction by the process category. Total CPU seconds per transaction is the sum of
the corresponding values in these two tables.
Plan Baseline Detail by Category Screen
The Plan Baseline Detail by Category screen is used to view or modify detailed characteristics
about process categories.
You can view the Detail CPU seconds in the units of the Actual CPU in the Consumption Model or
scaled to reflect the Plan CPU in the Consumption Model. To use this feature, select the appropriate
button and then select Calculate Now (F9). Figure 51 (page 157) shows a sample Plan Baseline
Detail by Category screen.
156
The Performance Model
Figure 51 Plan Baseline Detail by Category Screen
Significant Rows
1.
Txn Type—Not Directly Modifiable
Online transactions are Txn Type X, batch transactions are Txn Type B, and query transactions
are Txn Type Q.
2.
Total CPU Secs—Not Directly Modifiable
Total CPU Secs is the number of CPU seconds used by the transaction type.
Significant Columns
3.
Cat Name—Not Directly Modifiable
Cat Name is the category names of all process categories as they appear on the Category
Demand Report. These categories are placed in rows in the Apportionment Weights table.
The table is used to indicate how the CPU and disk seconds consumed by these categories
are to be allocated to each transaction.
4.
Type—Not Directly Modifiable
Type is the type of a process category, as defined in MeasTCM on the NonStop host system.
The category type consists of one of the following characters:
S
Server process
R
Requester process
D
Disk process (including all nonaudited disk processes)
T
TMF processes (including all audit disk processes)
L
Line-handler process
O
Other
Plan Baseline Detail by Category Screen
157
5.
F
Fixed (system overhead that does not vary with throughput)
Z
Ignore these categories (appropriate interrupt and disk activity to be omitted)
Tunable CPU—Directly Modifiable
Tunable CPU applies to batch transactions only. Y indicates batch transactions are spread
evenly across all available batch CPUs. N indicates batch transactions are assigned to run in
only one CPU. For more information, see “CPU Tunability” (page 103).
6.
Fixed CPU Sec Actual/Plan—Directly Modifiable
The Fixed CPU Sec Actual/Plan column is visible only when you select the Display Scratch
Areas option. The total number of CPU seconds consumed per second by process categories
of type F (fixed) is not included in the CPU and disk consumption of individual transactions,
but it does affect the total CPU and disk utilizations. Define a category as type F if its CPU
and disk consumption do not increase as throughput increases, such as during asynchronous
data communications polling activity or the running of Measure.
7.
Priority—Directly Modifiable
Priority is the priority of the process category.
8.
CPU Seconds—Not Directly Modifiable
CPU Seconds is the CPU seconds allocated to each transaction by process category.
9.
Not shown. CPU Sec and DP CPU Sec Tables—Directly Modifiable
The CPU Sec and DP CPU Sec tables are visible only when you select the Display Scratch
Areas option. The values in these tables are the CPU seconds and DP CPU seconds allocated
to each transaction by the process category. Total CPU seconds per transaction is the sum of
the corresponding values in these two tables.
You can modify these values by overwriting the cells. For example, TCM Plan transaction costs
contain "Smart Cell Updating." If you change a formula to a value, TCM changes the entry
formula that yields the desired value, but will scale as necessary, depending on Plan CPU
type.
Capacity History Screens
The Capacity History screens–Database, TrendCharts, and MixCharts–are used to archive, organize,
and visualize apportioned performance data for a particular application or set of applications.
The information in the Capacity History database helps the capacity planner in such crucial activities
as:
•
Checking the reasonableness of an apportionment method for a custom WA model
•
Choosing a representative performance sample as a baseline for the TCM Performance model
•
Projecting trends based on historical data in the Performance model
•
Performing database queries against historical data
•
Creating historical charts
The Capacity History screens display summary performance information for each transaction in a
given application (or set of applications) across multiple performance samples. The database can
also store data for several different apportionment methods, so the capacity planner can easily
examine the effect of different apportionment methods on several historical samples.
Capacity History Database Screen
Capacity planners can search the database by selecting Search from the History tab. Figure 52
(page 159) shows part of a sample Capacity History database screen.
158
The Performance Model
NOTE: A given Capacity History screen is restricted to only one application (the name defined
in the MeasTCM control file on the host) but can contain the results of more than one apportionment
method.
Figure 52 Capacity History Database Screen
Significant Rows
1.
Application—Not directly modifiable
Application is the user-specified name of the application or set of applications that is being
modeled. It is also the application name that appears on the Category Demand report of the
WA model. This name is specified when MeasTCM is executed on the NonStop host system.
(See “Customizing Your Process Category Control File” (page 33).) All the historical data on
the Capacity History screen pertains to this application. (An error message appears if you
select Update History from the History tab for a sample with a different application name.)
2.
Search Criteria—Modifiable by the user
Search Criteria is a collection of fields in which you can enter values before selecting Search
History or Delete History from the History tab. You can specify several database criteria to
perform such operations as finding all samples where the throughput of transaction Txn 1 is
greater than 10 transactions per second.
3.
History Data—Not directly modifiable
History Data is the historical sample data as apportioned by the WA model. To load this data,
select Update History from the History tab. The data cannot be modified. Performance data
is sorted by apportionment method and transaction type in descending date sequence.
Significant Columns
4.
App’t—Not directly modifiable
App’t is the apportionment method that was used in the WA model to compute the sample
performance data from the MeasTCM process category data. Because Capacity History can
be updated with data from more than one apportionment method, the same sample could
appear more than once, each occurrence being generated with a different apportionment
method.
5.
Mix—Not directly modifiable
This option shows the percentage mix of transactions in the sample used. Carefully note the
mix. To be reasonable, the mix of transactions must vary for your model.
Capacity History Screens
159
Capacity History Trend Charts Screen
The TrendCharts sheet has one Trend chart for each transaction name in the History data. Each
Trend chart has two plot areas, one in the top half and one in the bottom half. The top half plots
the CPU Seconds per Transaction. The bottom half plots the TPS rate (if OLTP), or the Transactions
per Task rate (if Batch) and a best-fit linear trend line. Sample dates are on the x-axis and apply
to both halves of the chart.
The Trend chart is designed so you can easily see how transaction rates change over time from
sample to sample and how the corresponding transaction cost (CPU time per transaction) varies
by sample. If a reasonable apportionment scheme was used when adding the data to the History
file, the transaction cost will not vary much from sample to sample and should not be a function
of the sample transaction throughput rate.
The Capacity Planner can use the rate trend line for the trend chart's transaction to estimate future
expected transaction rates for samples beyond those that occur in the History file. The Performance
model already allows for automated linear trend estimation of transaction throughput rates. These
History Trend charts can make it easier for you to see and work with the existing rate trends in
graphical form. For information on creating a Trend chart, see “History Charts” (page 125).
Capacity History Mix Chart Screen
The MixCharts worksheet contains one Mix chart for every sample in the History data. Each Mix
chart is a 3-D pie chart showing the percentage of CPU activity each named transaction consumed
during that data sample. This data is plotted from the Mix column of the History data. For information
on creating a Mix chart, see “History Charts” (page 125).
TCM User Customization Screen
The TCM User Customization screen allows users to modify the appearance of the TCM screens.
Figure 53 (page 161) shows the TCM User Customization screen.
To display this screen, select the Customize TCM option from the Options tab. To return to the TCM
model, click the Return to Model button at the top of this screen.
160 The Performance Model
Figure 53 TCM User Customization Screen
Descriptions of five modifiable features of the TCM screens follow, along with the method to change
them:
•
Font color of Manually overwritten cells
When the formula of any user-modifiable cell is overwritten with a value, in either the
Consumption Model, Planning Timeline model, CPU Factors screen, Disk Factors screen, or
Detail Plan screen, the font of that cell becomes bold and takes on the color of the text Manual
Overwrite Font ColorIndex in the User Customization screen.
To change this color, enter a value between 0 and 56 in the Value field. As soon as you
change the value, the font color of the text in the sample cell on the right changes to reflect
the entered value.
TCM User Customization Screen
161
The default value of this property is 5 (blue). Values less than 0 or greater than 56 are changed
to the default value of 5.
•
Background color of Read Only cells
The read-only protected cells of the TCM screens have the background color represented by
the sample cell of the Read-Only cells feature of the User Customization screen.
To change this feature, double-click the Read-Only cells label in the Feature column, select a
color from the color palette that appears and click OK. The sample cell immediately changes
to the selected color. The default is brown.
•
Background color of User Modifiable cells
The user-modifiable unprotected cells of the TCM screens have the background color represented
by the sample cell of the User-Modifiable cells feature of the User Customization screen.
To change this feature, double-click the User-Modifiable cells label in the Feature column,
select a color from the color palette that appears and click OK. The sample cell immediately
changes to the selected color. The default is yellow.
•
Screen Display font properties
The Screen Display Fonts table lists the font properties of the Normal, Bold, Italic and Title
fields of the TCM screens. Font properties listed in the table are: Name, Size, Bold, Italic,
Underline, Strikethrough, and ColorIndex.
To change these properties:
◦
Double-click the Screen Display Fonts label in the Feature column. A dialog box appears.
◦
Select one or more of the font types: Normal, Bold, Italic, or Title. Click OK.
◦
Select the font properties from the Format Font dialog box that appears.
The table is immediately updated to reflect the changes.
•
Screen Printer Font properties
The Screen Printer Fonts table lists the font properties of the Normal, Bold, Italic, and Title
fields of the TCM screens, which are used only during the printing of these screens. Font
properties listed in the table are: Name, Size, Bold, Italic, Underline, Strikethrough, and
ColorIndex.
To change these properties:
1. Double-click the Screen Printer Fonts label in the Feature column. A dialog box appears.
2. Select one or more of the font types: Normal, Bold, Italic or Title. Click OK.
3. Select the font properties from the Format Font dialog box that appears.
The table is immediately updated to reflect the changes.
Restoring Default Properties
To reset the default properties, click the Set Defaults button at the top right corner of the screen.
You are prompted to select the feature that has to be set to default.
Performance Model Charts
Throughputs and host response times in the Planning Timeline model can be plotted as charts by
selecting Create from the Chart tab. From the dialog box that appears, select the transaction you
want to plot.
162
The Performance Model
To customize a chart, select Customize from the Chart tab. A chart tools context-sensitive tab
displays Excel’s chart formatting options for changing the chart type and text and graphic elements.
You can customize the chart in a number of ways:
•
Double-click to view the chart formatting dialog, which allows you to set attributes such as
borders, line styles, patterns, and colors.
•
Select any attached text and drag it to a new location on the chart.
To go to another screen, select the Find tab or the screen tabs at the bottom. For complete
information about customizing charts, see the Microsoft Excel online help.
Planning Timeline Model Chart
The Planning Timeline chart plots throughput and host response time using planning dates on the
horizontal axis, as shown in Figure 54 (page 163) and Figure 55 (page 164). With this chart, you
can weigh the performance impact of a proposed HP NonStop system configuration against
expected throughput growth over the same time period.
Figure 54 Planning Timeline Model Chart for Average Online Transaction
Performance Model Charts 163
Figure 55 Planning Timeline Model Chart for Batch Transaction
Performance Model Ribbons
The Performance model options are listed under tabs in the ribbon. Select tabs, options, and choices
in dialog boxes in the same way as in the Work Apportionment (WA) model.
File Tab
The File tab is used to perform common operations on performance model files, such as opening
or closing a model.
Open (F4)
The Open option opens a Capacity History database. A dialog box then displays a list of files that
are in the current folder.
Save/Save As (F5)
The Save/Save As option allows you to save all the Performance model files, history files and any
other non-TCM file that is open in the session under the same name or a different name. You cannot
save the TCM User Customization file under a different name.
Close (SF4)
The Close option allows you to close the currently active file (could be the PM model file, the History
file, or any other non-TCM file).
Return to the TCM Initial Menu (SF3)
The Return to the TCM Initial Menu option returns you to the “TCM Initial Menu” (page 67).
164 The Performance Model
Exit TCM (SF5)
The Exit TCM option ends the TCM session and returns you to Windows.
Find Tab
The Find tab, which you can select by pressing function key F7, lists the Performance model screens
that you can display.
If no charts are open in the current session, the Chart menu item is disabled to indicate that the
option is not available.
If the history database has not been opened, the Capacity History items are disabled.
Update Tab
The Update tab contains all the update operations that can be performed on a Performance model.
Access to some options is limited to users with a TCM administrator or super-user authorization
level.
NOTE: After you use one of the options on the Update tab, you need to use the Calculate Now
option on the Options tab (F9) to see the effect on the TCM screens.
Load Baseline Data (F3)
The Load Baseline Data option loads selected performance data from a WA model or a CSV file
into the Performance model. After you select this option, a list of the WA baseline files or CSV files
appears. You can select the appropriate file from this list or type another name.
The Create New Performance Model dialog box appears. Select whether to load the Performance
model from a WA model or a CSV file and one of the following:
•
WA baseline file (when loading from a WA model)
•
CSV file and an apportionment method
When you select the WA Model button, the WA Baseline File list appears and the Using
Apportionment field is unavailable. When you select CSV File, CSV files appear instead of
WA Baseline files, and the Using Apportionment field is available.
Find Tab
165
Refresh Formulas
The Refresh Formulas option reinitializes all the formulas or those you select through a dialog box.
Use it to refresh the formulas if you typed over a lot of information while doing what-if exercises.
166 The Performance Model
Timeline Trends
The Timeline Trends option opens the history file for the application if it is not already in the current
screen. The Update Timeline Trend dialog box appears:
Update Tab
167
After the dialog box appears, choose the transaction to trend and optionally the start and end
dates. Then click OK. The data is modified to show the trend in the Planning Timeline model. TCM
uses a linear regression based on historical data to project the data. This option requires at least
10 Measure samples and a confidence level of 95 percent.
Calibrate Batch Response Time
The Calibrate Batch Response Time option is used to calibrate the response times for a batch
transaction to actual observed response times.
To calibrate Batch response times:
1. Open a Performance model.
2. Select Update > Calibrate Batch Response Time. The Calibrate Batch Response Time dialog
box appears.
3. Select the batch transaction name to calibrate from the list.
4. Type the observed response time in the Calibrate Batch Response Time dialog box or accept
the default values. You can enter hours, minutes, and seconds.
5. Click OK.
TCM changes the Performance model according to your observed response time instead of
TCM estimated response times.
168 The Performance Model
Merge Performance Models
As a TCM administrator or superuser, you can merge two Performance models into one model or
add transactions from one Performance model to another Performance model. These features are
useful for modeling the impact of combining two applications in a single system. The models you
are merging must have the same version and the same VPROC date.
1. Select Work with an Existing Model from the “TCM Initial Menu” (page 67) and click OK.
The Open PM Model dialog box appears.
2.
Choose the model to open and click OK.
The selected Performance model opens.
3.
4.
5.
Log on as a TCM administrator or super user. For more information about this step, see
“Changing Authorization Levels” (page 70).
Select Update > Merge Model. The Merge Performance Models dialog box appears.
From the list, select the model to merge with the current Performance model.
To work with a different Performance model than the one currently open, click Cancel to close
the Merge Performance Models dialog box. Select Close from the File tab. Then select from
the TCM Initial > Work with an Existing Performance Model and open the desired model.
6.
7.
8.
9.
Accept the default name of merged model or type a new name (other than TCM.spm) in the
Name of the Merged Model field.
Click the All Transactions button to merge all transactions, or click the Selected Transaction
button to specify the transaction to merge. Then click OK.
If you click All Transactions, the Merge Configuration dialog box appears. Accept the defaults
or make any desired changes, and click OK. TCM merges the Performance models and
displays the newly merged model. If you click Selected Transaction, the Merge Transaction
List dialog box appears. Specify the transaction to merge from the Merge Transaction list and
click OK.
The Merge Configuration dialog box appears. Accept the defaults or make any desired
changes. Then click OK.
Update Tab
169
TCM merges the Performance models and displays the Capacity Baseline–Plan of the merged
model.
170
The Performance Model
TCM merges the Performance models and displays the Capacity Baseline—Actual of the merged
model.
Update Tab
171
Add Transaction
The Add Transaction option adds a new, user-defined transaction to the Performance model that,
typically, was not apportioned using a WA model. For example, if you have estimates of CPU and
disk demands for a new transaction for which no Measure data yet exists, you can use this option
to define the transaction.
After you select this option, a dialog requests the name of the transaction to add. It also asks for
the corresponding CPU and application disk seconds per transaction and whether the transaction
is audited or not. The disk seconds requested are application disk seconds and exclude seconds
attributed to TMF. If the transaction is audited, TCM assigns default values to the TMF disk read
and write seconds for the transactions. These values can be examined, modified, or both using
the Change Transaction option on the Update tab.
172
The Performance Model
The transaction’s activity is allocated entirely to a category of the same name and is added to both
the actual and plan baseline screens.
Add Similar Transaction
The Add Similar Transaction option adds a transaction similar to an existing transaction in the
model. Enter New Transaction Name and select one of the existing transactions in the model.
Select Add. You must perform a Calculate in order for TCM screens to be properly updated with
the newly added transactions.
Update Tab
173
Delete Transaction
The Delete Transaction option deletes an existing transaction, and the category of the same name
if you want, from a Performance model. After you select this option, a list of the transactions in the
Performance model appears. To delete a transaction, select its name from the list and click Delete.
Add Category
The Add Category option adds a process category to the Performance model.
Delete Category
The Delete Category option deletes a category from the Performance model.
Display Tab
The Display tab is used to specify what information TCM displays and how it is displayed.
Show Gridlines
Displays gridlines on the current screen. Once selected, the option toggles to Remove Gridlines,
which removes the gridlines from the display.
Zoom In
Zooms in on the current screen to make it larger. Once selected, the option toggles to Zoom Out,
which returns the screen to its original state.
Display Scratch Areas
The Display Scratch Areas option allows you to view several areas of the model that are hidden
during normal use. These hidden areas contain valuable scratch data for the operation of the model
and data that can be helpful if you want to understand the model’s structure and formulas. Once
selected, the option toggles to Hide Scratch Areas, which returns the screens to their normal
appearance.
Show Headings
The Show Headings option displays spreadsheet headings of the current screen. Once selected,
the option toggles to Remove Headings, which removes the spreadsheet headings of the current
screen.
Change Display Fonts
The Change Display Fonts option changes the fonts that TCM uses to display its data. TCM supports
four font characteristics: Normal, Bold, Italic, and Title. You are prompted to select the font
characteristics for each font.
For more information, refer to the Microsoft Excel documentation.
Show Value (Control-V)
The Show Value option shows the current field value up to 15 decimal places.
174
The Performance Model
Widen Column
The Widen Column option widens the selected column.
Narrow Column
The Narrow Column option narrows the selected column.
Print Tab
The Print tab is used to print the screens of a Performance model.
Print (F6)
The Print option prints one or more screens in the current model. A dialog box lists the names of
the screens that you can choose to print and provides two print options.
Print Tab
175
Select Draft Quality to print the screen using your printer’s built-in character set. This option does
not provide high-quality output, but it does offer fast printing.
Select Preview to display an image of the printed page on the PC monitor before printing. This
option is useful for checking that the page layout is correct for your particular printer’s configuration
before you print the screen.
If you have added notes to the screen by using the Notepad feature on the Options menu, the
notes are printed first.
Page Setup
The Page Setup option defines the printing preferences for the page, margins, headers, footers,
and sheet. TCM provides a default page setup that can be modified using this option. Printing in
landscape mode generally provides better looking output for most TCM screens. For more
information, refer to the section on file page setup in the Microsoft Excel online help.
The scope of the Page Setup command is as follows:
176
•
Page Setup changes for a Performance Model screen are applied to all Performance Model
screens.
•
Page Setup changes for a Performance Model chart are applied only to that chart.
•
Page Setup changes for a sheet of the History workbook are applied only to that worksheet.
The Performance Model
Change Printer Fonts
The Change Printer Fonts option changes the fonts that TCM uses to print its data. Due to the
difference between printers and monitors, different fonts are frequently required for printing and
displaying data.
TCM comes with a default printer font setting that might not be appropriate for your specific
requirements. It is recommended that you select Preview from the Print option to ensure that your
printer fonts are appropriate to your needs before printing a screen.
NOTE: The fonts you select with this option are used only when TCM prints a screen. To select
the fonts used in the screen display, select the Change Display Fonts option from the Display tab.
Printer Setup
The Printer Setup option lets you specify the printer you want to use and how it should be configured.
For more information, refer to the section on file printer setup in the Microsoft Excel online help.
Options Tab
The Options tab provides various options for working with a Performance model and for ensuring
the model’s security.
Change Authorization Level (SF6)
The Change Authorization Level option changes your authorization level, if you have a valid
password. Users with a TCM administrator or superuser authorization level have access to more
TCM options than users with a capacity planner authorization level. For more information on TCM
security and authorization levels, see “Security” (page 69).
Calculate Now (F9)
The Calculate Now option instructs TCM to calculate any changes you made to the screens. When
batch response times are being calculated, the Excel status bar displays messages showing how
many batch transactions are currently in the model being solved and how many iterations have
been completed while searching for the current solution.
Undo Entry
The Undo Entry option allows you to reverse the last action you performed if possible.
Notepad (SF2)
The Notepad option allows you to attach notes to a selected screen in the model. A dialog box
provides room for a 5-line note, which can be edited by typing over, for the selected screen. Press
the Tab key to move between notes and press the Enter key to complete a note.
NOTE:
page.
If you print a screen that has notes attached to it, the notes are printed first on a separate
Select Response Time Method
The Select Response Time Method option allows you to select the response time method. The default
is average. You can also select 90th, 95th, or 99th percentile response time. For example, if the
response time is 1 second and average response time is selected, the average response time of
transactions is 1 second. If 90th percentile is selected, 90 percent of the transactions have a
response time of less than or equal to 1 second.
Options Tab 177
Change Password
The Change Password option changes the TCM passwords that control access to TCM administrator
and superuser authorization levels. The default password for the TCM administrator level is “admin.”
The password for the superuser level is “super.” To enhance TCM security, the default passwords
should be modified. This option is available only to users with a TCM administrator or superuser
authorization level.
After you select this option, a dialog box prompts for both the existing and new (replacement)
passwords. For more information regarding TCM passwords, see “Passwords” (page 70).
Customize TCM
The Customize TCM option displays the TCM User Customization worksheet, which allows you to
customize the appearance of the TCM screens. To return to TCM, select Return to Model on the
TCM User Customization screen.
Chart Tab
The Chart tab is used to create and customize Performance model charts.
Create Timeline Chart (F8)
The Create Timeline Chart option plots a Planning Timeline model chart. (For information about
using the charts, see “Planning Timeline Model Chart” (page 163).)
After you select Create Timeline Chart option, a list of transactions in the Performance model
appears. Select the transaction (or average transaction) you want to plot. You can modify models
while simultaneously updating the chart. When you finish, click OK. For more information on
positioning, sizing, and switching between Excel windows, see the Microsoft Excel online help.
Customize
The Customize option enables all of Excel’s chart formatting commands so that you can change
the default format and customize the chart in whatever way you desire. Refer to the section on the
charts in the Microsoft Excel online help for more details.
Help Tab
The Help tab provides information about the TCM fields, function keys, and operating environment.
TCM Help (F1)
The TCM Help option displays context-sensitive help messages about the currently selected field.
Exiting Help
To exit Help, select Exit from the File tab in the Help window.
Function Keys (SF1)
The Function Keys option lists all the TCM function keys and their meanings. You can also access
this function by pressing SF1.
178
The Performance Model
About
The About option displays information about the TCM environment.
Help Tab
179
10 Using TCM Expert
TCM Expert is a feature of TCM that enables you to do the following:
•
Automatically generate Apportionment Weights table from sample data
•
Update capacity history with selected samples
•
Create a default Transaction Count table
•
Pick the most representative sample
•
View and modify TCM Expert parameters
TCM Expert provides a way to do capacity planning when you have limited knowledge of the
application design or architecture. When you bring CSV data into TCM Expert, TCM Expert warns
you if the collected data is inconsistent with the current model and advises you when you should
generate a new apportionment scheme.
The TCM Expert tab enables you to access all TCM Expert features. You can use TCM Expert with
CSV files to generate an Apportionment Weights table automatically. However, you must still use
an existing Transaction Count table or transaction count files. If you do not have an existing
Transaction Count table or transaction count files, you must generate the default Transaction Count
table and modify it according to your application needs.
CSV Sample Data Required
TCM Expert needs to have enough CSV sample data to do its work. Depending on the quality of
your data, you might need at least 4 to 5 times the number of defined transaction names. For
example, if your model has two transactions, you would need at least 8 to 10 CSV samples for
the best results. The more CSV files, the better.
The CSV samples you collect should be independent of one another. Thus, the CSV samples should
have varying transaction mixes. To get independent CSV samples, you might have to take several
measurements. For instance, to get 12 independent samples, you might have to take 12 1-hour
intervals over a 12-hour period. For other applications, you might take measurements at the same
time but over a 12-day period to get 12 independent samples. In an automatic teller machine
(ATM) application, for example, you will get different transaction mixes on a traditional pay day
(such as the 1st or 16th of the month) versus another day. You would also get a different transaction
mix on a Friday when customers want to withdraw money for the weekend or the day before a
holiday.
CSV files should cover periods when the different transaction rates are not correlated. As part of
its analysis, TCM looks for linear relationships in the counts in your CSV sample data. For example,
if there are always twice as many withdrawal transactions as deposit transactions, the data is not
suitable for TCM Expert analysis. In this case, retake your CSV samples during different periods
when the established relationship is not as strong or is nonexistent.
If TCM detects any undesirable correlations, your CSV samples are not independent. A dialog box
appears describing the established linear relationship. However, you can continue if you want. If
you decide to continue with your original data and TCM Expert comes up with reasonable
apportionment weights, be aware that the results depend on the established linear relationship
continuing.
Data Splitting
TCM Expert uses the statistical concept of data splitting to give you a higher confidence level in
its results. When TCM Expert generates apportionment weights, it uses two-thirds of the CSV files
selected. TCM Expert does not use the other third of the CSV files selected but reserves those CSV
files as a test sample for consistency. When TCM Expert updates the capacity history, it uses all
180 Using TCM Expert
of the CSV files selected and at that time tests all of the CSV samples for consistency. If TCM Expert
finds inconsistencies, it reports this information in a dialog box.
If you are a TCM super user, the Generate TCM Expert Apportionment Weights dialog box shows
the percent of selected CSVs used to generate the data.
If you are not a TCM super user, the dialog box does not show this field. This field shows the
percentage of CSV files out of all the selected CSV files that TCM Expert uses to generate the
Apportionment Weights table. The default is 67 percent. If you have too few CSV samples to make
an accurate Apportionment Weights table, you might want to increase this percentage. By increasing
this percentage, you have a better chance of getting an accurate Apportionment Weights table,
but you reduce the confidence level of the results.
Generating an Apportionment Weights Table for CSV Files
The following procedure shows how to use TCM Expert to generate an Apportionment Weights
table for your CSV files. This procedure assumes you are initially at the capacity planner
authorization level and that you have authorization to be a TCM administrator.
Before you use TCM Expert, you should have:
•
A custom folder that contains your CSV files (sample data)
•
An existing Transaction Count table or transaction count files unless you decide to generate
a default Transaction Count table
Getting Started With TCM Expert
To use TCM Expert:
CSV Sample Data Required
181
1.
Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box appears.
2.
Specify the custom folder location of your CSV files.
Highlight the custom folder of your CSV files and double-click the custom folder name. When
you double-click the name, TCM updates this name on the custom folder field of the dialog
box and also makes this the location of your working session.
3.
Click OK to close the dialog box.
You can now begin using TCM Expert.
Creating a Default Transaction Count Table and Workload Apportionment
Weights Table
To create a default Transaction Count table:
1. Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box appears.
2.
3.
Specify a custom folder and click OK.
If you do not have an existing Apportionment Weights table or Transaction Count table, select
Expert > Create Default Transaction Count Table.
A dialog box similar to the following appears:
TCM Expert provides a default Transaction Count table name and selects a CSV file from
which to generate the default table.
Click OK to accept the defaults or select a different name and CSV file.
4.
If you have a type T (TMF) process category defined in the selected CSV file, the Create Default
Apportionment Tables Audited Transaction dialog box appears.
Using your knowledge of the application, you can select which transactions are audited (or
not audited) by placing them in the appropriate list. When the default Apportionment Weights
table is created, audited transactions will be indicated by a 1 for any type T process category.
Unaudited transactions are indicated by a 0.
182
Using TCM Expert
5.
6.
7.
Click OK. TCM Expert generates a default Transaction Count table and Apportionment Weights
table and displays the newly generated “Transaction Count Table” (page 119).
Examine the default Transaction Count table. If you want to make changes:
a. Select Options > Unprotect Admin Fields.
b. Enter the corrected values.
c. Select Options > Protect Admin Fields.
Examine the default Apportionment Weights table. To navigate to that table, select Find >
Apportionment Weights Table.
TCM displays the default “Workload Apportionment Weights Table” (page 117).
8.
You might want to override the default Expert Flag for process categories for which you have
specific application knowledge and enter your own numbers. The Expert Flag indicates whether
TCM Expert should generate a value for the process category. The default for the TMF (T),
Disk (D), Fixed (F), and Ignore (Z) process categories is N (no). The default is also N for server
categories whose names exactly match the transaction names. The default value for all other
process categories is Y.
If you want to override Expert’s calculations for any category marked with a Y (yes):
a. Select Options > Unprotect Admin Fields. The modifiable fields are dimmed.
b. Type an N in the Expert Flag column of the category you want to override and enter the
values you believe are correct in the transaction columns.
c. Select Options > Protect Admin Fields.
Generating Expert Apportionment Weights
To use TCM Expert to generate an Apportionment Weights Table:
1. Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box appears.
2.
3.
4.
Specify a custom folder and click OK.
Log on as an administrator or super user. For more information about this step, see “Changing
Authorization Levels” (page 70).
Select Expert > Generate Expert Apportionment Weights.
The Generate Expert Apportionment Weights dialog box appears.
Generating Expert Apportionment Weights 183
From this dialog box, you can do the following:
a. From the History Database list, select or enter the name of the Capacity History database
that will be updated automatically after the weights are generated. The Capacity History
database is created if it does not already exist.
b. To select a name for the source of the transaction counts, select an apportionment table
file. If you have transaction count files, TCM Expert automatically identifies them. If
transaction count files are present, they override a Transaction Count table if both are
present. If you have neither a Transaction Count table nor transaction count files, you
must create a default table. For more information, see “Creating a Default Transaction
Count Table and Workload Apportionment Weights Table” (page 182).
If you are a TCM super user, the field “Percent of Selected CSVs used to generate” is
shown. If you are not a TCM super user, this field is hidden. The default is 67 percent.
This percentage is the percent of CSV files randomly selected by TCM Expert to generate
the apportionment weights.
c.
d.
To select the CSV sample data files to be used, highlight the files. Click and select either
the Remove or Add buttons. Press the Shift key while clicking the file names to select a
contiguous set of files. Press the Control key while clicking the file names to add or remove
a highlighted file from those selected.
To get information about a CSV file before you decide whether to use it, select the CSV
file name and click the CSV Info button. The CSV Info dialog displays.
The Number of Transactions field shows the total number of transactions of the type
selected in the Transaction field. The Transaction Mix field shows the percentage of
transactions in the CSV data of this transaction type.
184 Using TCM Expert
You can also select a different transaction or Transaction Count table from the lists in the
dialog box. As you change the selected transaction or Transaction Count table, TCM
updates the information in the dialog box to reflect your selections. When you finish
entering changes, click OK to enter the changes and close the dialog box.
5.
Once you complete the fields in the Generate Apportionment Weights dialog box, click
Generate.
TCM Expert generates an Apportionment Weights table, and a confirmation dialog box
appears.
6.
7.
Click OK or press Enter to dismiss the confirmation dialog box.
•
If TCM Expert has too few CSV files, a dialog box reports this fact, and TCM Expert stops.
•
If TCM Expert does not have enough CSV files or wrong transaction counts, a transaction
list appears to show the transactions that TCM Expert does not have consistent costs on.
•
If TCM Expert finds that the CSV files are not compatible with the AWA files, the
Incompatible CSV List dialog box appears:
•
If TCM Expert finds CSV files that are correlated, a linear relationship dialog box appears:
•
If TCM Expert finds transactions that do not occur in any of your CSV files, TCM Expert
puts question marks (?) in the Apportionment Weights table and does not include these
transactions in its analysis.
Examine the Apportionment Weights table generated by TCM Expert:
Generating Expert Apportionment Weights 185
To override TCM Expert’s calculations for any category marked with a Y:
a. Select Options > Unprotect Admin Fields. Modifiable fields are dimmed.
b. Type an N in the Expert Flag column of the category you want to override and enter the
values you believe are correct under the transaction columns. To finish entering your data,
you must press Return before selecting Calculate Now or pressing a function key.
c. Select Options > Protect Admin Fields.
d. Select TCM Expert > Generate Expert Apportionment Weights and generate again.
TCM automatically updates capacity history using the automatically generated
Apportionment Weights table.
Updating Capacity History With Selected CSV Files
The Update Capacity History with Selected CSV Files option is available so that you can update
capacity history using any Apportionment Weights table (whether TCM Expert generated it
automatically or you manually generated it). If you use TCM Expert to generate the Apportionment
Weights table, TCM Expert already has automatically updated capacity history, and you need not
use this option.
To update capacity history with selected CSV files:
1. Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box appears.
2.
3.
4.
5.
6.
Specify a custom folder and click OK.
Select Expert > TCM Expert Parameters. Enter in Check History Over Last enough months to
cover all of the dates when the samples were taken.
Select Expert > Update History with Selected CSVs. The Update History with Selected CSV
Files dialog box appears. By default, CSV files that have not yet been used to update capacity
history appear in the Selected CSV Files list.
Select a History database from the History Database list. You can select from the list of History
files, keep the default History name, or enter a new name.
Select an apportionment table from the Apportionment Table pull-down list. You can select
from the list of apportionment tables or keep the apportionment table name.
186 Using TCM Expert
7.
8.
If you want, you can remove or add CSV files from the list to update capacity history:
•
To select CSV file, select a file name in the Unselected CSV Files field, and then click
Add. The file name appears in the Selected CSV File list.
•
To clear a CSV file, click the file name in the Selected CSV File list and click Remove.
The file name appears in the Unselected CSV File list.
•
To get information on a specific CSV file, select a CSV file name in the Selected CSV
Files list and click CSV Info.
Click Update History.
TCM Expert updates capacity history and displays the updated file.
If TCM Expert finds inconsistent transaction costs in the capacity history, it reports this
information to you in a dialog box.
For more information, see “Updating Capacity History With Selected CSV Files” (page 186).
Picking the Best CSV Sample and Loading It Into the Performance Model
To have TCM Expert pick the most representative CSV file and load it into the Performance model:
1. Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box appears.
2.
Specify the custom folder location of your CSV files.
Select the custom folder of your CSV files (you can use the arrow keys or the mouse to move
to the correct folder) and double-click the custom folder name. When you double-click the
Picking the Best CSV Sample and Loading It Into the Performance Model
187
name, TCM updates this name in the custom folder field of the dialog box and also makes
this the location of your working session.
3.
4.
Click OK to close the dialog box.
Select TCM Expert > Pick Best CSV Sample.
The Pick Best CSV Sample dialog box appears.
5.
Select the Capacity History file from which to pick the CSV sample and click OK.
TCM Expert picks the best CSV sample.
6.
If you want to load this CSV sample into the Performance model, click Create.
TCM loads the CSV sample into the Performance model and displays the Capacity Baseline
Plan for the CSV sample. You are now in the Performance model and have left TCM Expert.
Viewing or Changing Expert Parameters
To view the global parameters for TCM Expert, select TCM Expert > TCM Expert Parameters.
To change the global parameters for TCM Expert:
1. Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box appears.
2.
3.
Specify a custom folder and click OK.
Select TCM Expert > TCM Expert Parameters.
The TCM Expert Parameters dialog box appears.
4.
Accept the default Capacity History time period (six months) or specify a new one.
This field specifies the time range that is used in three situations:
•
The time range that is checked for transaction cost consistency when you select Generate
Expert.
•
The time range that is checked for transaction cost consistency when you select Update
History with Selected CSV Samples.
•
The time range that is used when you select Pick Best Sample.
The default time period is six months.
5.
If you are logged on as an administrator (with the access level of system administrator or
higher), accept the default Cache Miss Factor or specify a new one.
The Cache Miss Factor specifies the relative CPU cost to the disk process of a cache miss as
compared with a cache hit. The default settings assume that it takes twice as much CPU time
to get data off the disk than to get data from cache (memory). That is, a cache miss costs twice
as much as a cache hit. A TCM administrator or superuser can modify this factor.
6.
Accept the default CPU Pathlength Threshold or specify a new one.
The CPU Pathlength Threshold field specifies the point at which a query transaction is considered
either an OLTP or batch transaction. The default setting is two seconds. Small demand queries
taking less than two seconds are considered OLTP transactions, and large demand queries
taking longer than two seconds are considered batch transactions. Any TCM user can modify
this factor.
7.
Click OK. TCM Expert uses the new parameters.
188 Using TCM Expert
A TCM File Names
Distribution Folder for the PC Using Excel 2003
The TCM files are in Excel spreadsheet format unless otherwise stated:
File Name
Description
1TCM.MWA
Excel macro sheet for the WA model.
1TCM.MXP
Excel macro sheet for TCM Expert.
DEMO.AWA
Sample WA model for the Demo model.
DEMO.HST
Sample history file for the Demo model.
DEMO2301.CSV
Sample CSV file.
EXAMPLE1.CSV
Performance sample data (in Comma Separated Values format).
EXAMPLE2.CSV
Performance sample data (in Comma Separated Values format).
README.TXT
ASCII text format file that contains detailed and timely notes regarding TCM
installation and other topics.
SOFTDOC.TXT
Online documentation for new features and fixed and remaining problems for
TCM for the current RVU.
TCM.AWA
Template for the WA apportionment tables.
TCM.HST
Template for the WA capacity history database.
TCM.ICO
Sample icon for TCM.
TCM.PXP
A spreadsheet template file used internally by TCM Expert.
TCM.SPM
Performance model spreadsheet for the distribution model.
TCM.SWA
WA spreadsheet for the distribution model.
TCM.XLB
Excel Toolbar file with no toolbars.
TCM.XLM
Excel macro file used by TCM.XLS.
TCM.XLS
The file that launches TCM. Double-click this file to start TCM.
TCM.EXE
File containing all TCM distribution files for the PC in compressed (WINZIP)
format.
TCMNT. XLA
The add in file for TCMNT.XLS.
TCMNT.XLS
Excel workbook containing Visual BASIC code.
TCMPM32.DLL
32-bit dynamic-link library (DLL) that contains response time algorithms and
other routines for the Performance model.
TCMUSER.XLS
The User Customization file.
TCMWA32.DLL
32-bit dynamic-link library (DLL) that contains apportionment algorithms and
other routines for the WA model.
TCMXP32.DLL
32-bit dynamic-link library (DLL) that contains TCM Expert algorithms.
TCMHPM.TXT
Help file for the Performance model in text format.
TCMTXT.HWA
Help file for the WA model in text format.
TCMTXT.HXP
Help file for TCM Expert in text format.
TCMHPM.CHM
Performance model help file for the PC in Windows format.
TCMHWA.CHM
WA help file for the PC in Windows format.
TCMHXP.CHM
TCM Expert help file for the PC in Windows format.
VPROC.XLM
Program that tells you which version of TCM was used in making the file.
template.wwa
Template workspace file for WA model used by TCM internally.
Distribution Folder for the PC Using Excel 2003 189
Distribution Folder for the PC Using Excel 2007
The TCM files are in Excel spreadsheet format unless otherwise stated:
File Name
Description
1TCM.MWA
Excel macro sheet for the WA model.
1TCM.MXP
Excel macro sheet for TCM Expert.
DEMO.AWA
Sample WA model for the Demo model.
DEMO.HST
Sample history file for the Demo model.
DEMO2301.CSV
Sample CSV file.
EXAMPLE1.CSV
Performance sample data (in Comma Separated Values format).
EXAMPLE2.CSV
Performance sample data (in Comma Separated Values format).
README.TXT
ASCII text format file that contains detailed and timely notes regarding TCM
installation and other topics.
SOFTDOC.TXT
Online documentation for new features and fixed and remaining problems for
TCM for the current RVU.
TCM.AWA
Template for the WA apportionment tables.
TCM.HST
Template for the WA capacity history database.
TCM.ICO
Sample icon for TCM.
TCM.PXP
A spreadsheet template file used internally by TCM Expert.
TCM.SPM
Performance model spreadsheet for the distribution model.
TCM.SWA
WA spreadsheet for the distribution model.
TCM.XLB
Excel Toolbar file with no toolbars.
TCM.XLAM
Excel macro file used by TCM.XLSM.
TCM.XLSM
The file that launches TCM. Double-click this file to start TCM.
TCM7.EXE
File containing all TCM distribution files for the PC in compressed (WINZIP)
format.
TCMNT.XLAM
The add in file for TCMNT.XLSM.
TCMNT.XLSM
Excel workbook containing Visual BASIC code.
TCMPM32.DLL
32-bit dynamic-link library (DLL) that contains response time algorithms and
other routines for the Performance model.
TCMUSER.XLSM
The User Customization file.
TCMWA32.DLL
32-bit dynamic-link library (DLL) that contains apportionment algorithms and
other routines for the WA model.
TCMXP32.DLL
32-bit dynamic-link library (DLL) that contains TCM Expert algorithms.
TCMHPM.TXT
Help file for the Performance model in text format.
TCMTXT.HWA
Help file for the WA model in text format.
TCMTXT.HXP
Help file for TCM Expert in text format.
TCMHPM.CHM
Performance model help file for the PC in Windows format.
TCMHWA.CHM
WA help file for the PC in Windows format.
TCMHXP.CHM
TCM Expert help file for the PC in Windows format.
VPROC.XLAM
Program that tells you which version of TCM was used in making the file.
190 TCM File Names
Custom Folder
File Name
Description
application-name.HST
Capacity history database for the modeled application or applications.
custom.PXP
An internal file, one per custom folder, that contains detailed diagnostic and
results information beyond that displayed in the history file or the .AWA file.
method-name.AWA
WA apportionment tables for the modeled application or applications.
sample-name.TCF
Transaction count file for your application. You can use a Transaction count
file instead of using the Transaction count table of the WA model for counting
transactions processed by your application.
model-name.SPM
Performance model spreadsheet for the modeled application or applications.
model-name.SWA
WA spreadsheet for the modeled application or applications.
model-name.WPM
Workspace for the performance model; a special Excel file that automatically
opens all necessary performance model files.
model-name.WWA
Workspace for the WA model; a special Excel file that automatically opens
all necessary WA files.
sample-name.CSV
Downloaded performance category data from MeasTCM.
Custom Folder
191
B MeasTCM Error Messages
MeasTCM generates three types of error messages:
•
COBOL85 run-time diagnostic messages. For an explanation of these messages, see the
COBOL85 Manual.
•
MeasTCM termination messages. These messages indicate normal or abnormal termination
of MeasTCM. A list of these messages follows. The number preceding each message is the
corresponding termination-info parameter.
•
Informational messages. These messages are for your information only and do not have
message numbers.
MeasTCM Termination Messages
0
MeasTCM normal termination
Cause
MeasTCM completed all work successfully and then terminated.
Effect
The program terminates.
Recovery
Informational message only; no corrective action is needed.
1
GETSTARTUPTEXT logic error
Cause
A logic error occurred during execution of the COBOLLIB SMU routine GETSTARTUPTEXT.
Effect
The program abends. A process snapshot file is created. CSV files are not created.
Recovery
Report this error to your HP analyst.
2
Control file COBOLASSIGN error n
Cause
Error number n occurred during execution of the COBOLLIB routine COBOLASSIGN. If n = 1,
an invalid syntax for the control file name was specified at MeasTCM run time. If n > 1, a
MeasTCM internal error occurred.
Effect
The program terminates. No CSV files are produced.
Recovery
If n = 1, rerun MeasTCM specifying the correct control file name. If n > 1, report this error to
your HP analyst.
5
Missing APPL entry in control file
Cause
The required entry APPL is missing in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
192 MeasTCM Error Messages
Recovery
Edit the MeasTCM control file and add an APPL entry defining the application name.
6
More than one CSVDATA entry in control file
Cause
The MeasTCM control file contains more than one CSVDATA entry.
Effect
The program terminates. No CSV files are produced.
Recovery
The MeasTCM control file can only contain one CSVDATA entry. Edit the control file and remove
all but one CSVDATA entry.
7
More than one CSVLO entry in control file
Cause
The MeasTCM control file contains more than one CSVLO entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove all but one CSVLO entry.
8
CSVLO date/time must be unsigned numeric
Cause
The date, time, or both specified in the CSVLO entry contains nonnumeric values.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the specification for the lower time boundary in the
CSVLO entry.
9
More than one CSVHI entry in control file
Cause
The MeasTCM control file contains more than one CSVHI entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove all but one CSVHI entry.
10
CSVHI date/time must be unsigned numeric
Cause
The date, time, or both specified in the CSVHI entry contains nonnumeric values.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the specification for the upper time boundary in the
CSVHI entry.
MeasTCM Termination Messages
193
11
More than one APPL entry in control file
Cause
The MeasTCM control file contains more than one APPL entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove all but one APPL entry.
12
Missing APPL parameter in control file
Cause
The APPL keyword in the MeasTCM control file is not followed by an application name.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and add an application name following the APPL keyword.
15
Invalid type for process category n
Cause
The MeasTCM control file contains an invalid type specification for process category n.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and look for the TITLE entry corresponding to process category
n. Change the type parameter to a valid value.
16
Invalid name for process category n
Cause
The MeasTCM control file contains an invalid name specification for process category n.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and look for the TITLE entry corresponding to process category
n. Enter a valid name. The names _OTHER and _ERROR are reserved for MeasTCM internal
use.
17
Duplicate process category name n
Cause
The name defined for process category n in the MeasTCM control file has already been assigned
to another process category.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and check that each process category has a unique name.
18
194
MeasTCM Error Messages
Process category number out of range n
Cause
One of the PCAT entries in the MeasTCM control file contains a process category number n that
is larger than 97.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the process category number. It must be an unsigned
integer between 00 and 97.
19
Missing TXN parameter in control file
Cause
The MeasTCM control file contains one or more TXN entries without a corresponding transaction
type and name.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and check that each TXN keyword is followed by a transaction
type and name.
20
Duplicate transaction name name
Cause
The MeasTCM control file contains two or more TXN entries with the same transaction name
name.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and check that each TXN keyword is followed by a unique
transaction name.
21
Invalid keyword text
Cause
The MeasTCM control file contains an invalid keyword text.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove the line containing the invalid keyword.
22
CSVHI parameter <= CSVLO parameter
Cause
The value specified for CSVHI in the MeasTCM control file is smaller than or equal to the value
specified for CSVLO.
Effect
The program terminates. No CSV files are produced.
MeasTCM Termination Messages 195
Recovery
Edit the MeasTCM control file and specify a valid time window using CSVLO (lower boundary)
and CSVHI (upper boundary).
23
PCAT entry contains nonnumeric process category number text
Cause
One of the PCAT entries in the MeasTCM control file contains a nonnumeric process category
number text.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the process category number. It must be an unsigned
integer between 00 and 97.
24
CSV file COBOLASSIGN error n
Cause
Error number n occurred during execution of the COBOLLIB routine COBOLASSIGN. If n = 1,
then invalid syntax for the file name was specified in the CSVDATA entry of the MeasTCM control
file. If n > 1, an internal MeasTCM error occurred.
Effect
The program terminates. No CSV files are produced.
Recovery
If n = 1, edit the MeasTCM control file and correct the file name in the CSVDATA entry. If n >
1, report this error to your HP analyst.
25
CSVLO COMPUTETIMESTAMP error n
Cause
The date/time specified in the CSVLO entry is incorrect. The value n represents the error mask
returned by the COMPUTETIMESTAMP procedure.
Effect
The program abends and creates a process SAVEABEND file. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the specification for the lower time boundary in the
CSVLO entry. If n > 63, report this error to your HP analyst.
26
CSVHI COMPUTETIMESTAMP error n
Cause
The date/time specified in the CSVHI entry is incorrect. The value n represents the error mask
returned by the COMPUTETIMESTAMP procedure.
Effect
The program abends and creates a process SAVEABEND file. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the specification for the upper time boundary in the
CSVHI entry. If n > 63, report this error to your HP analyst.
27
CONVERTTO required if mixed CPU types are present
196
MeasTCM Error Messages
Cause
The measurement data files contain CPU entity records showing mixed CPU types and the
CONVERTTO entry is not present in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and add a CONVERTTO entry defining what the output CPU type
should be.
28
No control file specified
Cause
No control file was specified at MeasTCM run time.
Effect
The program terminates. No CSV files are produced.
Recovery
Rerun MeasTCM specifying the name of the control file as the startup message's parameter
string.
29
Incompatible Guardian 90 version
Cause
There was an attempt to run MeasTCM on an incompatible product version of Guardian 90.
Effect
The program terminates. No CSV files are produced.
Recovery
Check the MeasTCM documentation to find out which operating system product version or
versions can be used. Change the product version of MeasTCM, the operating system, or both
accordingly.
30
Unsupported Measure data file version
Cause
The product version of the one of the Measure data files under consideration is not supported
by this product version of MeasTCM.
Effect
The program terminates. No CSV files are produced.
Recovery
Check the MeasTCM documentation to verify which measurement data file product versions are
supported.
31
Invalid Measure data file name
Cause
The Measure data file name following one of the keywords MEASURE in the MeasTCM control
file is invalid.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the Measure data file name.
MeasTCM Termination Messages
197
32
Duplicate Measure data file name
Cause
Two or more Measure entries in the MeasTCM control file specify the same Measure data file
name.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove the duplicate Measure entries.
33
Invalid node name for process category n
Cause
One of the PCAT entries of process category n contains an invalid node (system) name
specification.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the node name spelling. It must be equivalent to an
asterisk (*) or contain up to eight characters starting with a backslash (\).
34
Invalid CPU number for process category n
Cause
One of the PCAT entries of process category n contains an invalid CPU number specification.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the CPU number. It must be equivalent to an asterisk
(*) or an unsigned integer between 0 and 15.
35
Invalid PIN for process category n
Cause
One of the PCAT entries of process category n contains an invalid PIN specification.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the PIN. It must be equivalent to an asterisk (*) or an
unsigned integer between 0 and 255.
36
Invalid process name for process category n
Cause
One of the PCAT entries of process category n contains an invalid process name specification.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the process name. Wild-card characters asterisk (*)
and question mark (?) are allowed.
198 MeasTCM Error Messages
37
Invalid program file name for process category n
Cause
One of the PCAT entries of process category n contains an invalid program file name
specification.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the program file name. It must be of the form
volume.subvolume.filename. Wild-card characters asterisk (*) and question mark (?) are
allowed.
38
Invalid user ID group number for process category n
Cause
One of the PCAT entries of process category n contains an invalid user ID group number
specification.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the user ID group number. It must be equivalent to an
asterisk (*) or an unsigned integer between 0 and 255.
39
TITLE entry contains nonnumeric process category number text
Cause
One of the TITLE entries in the MeasTCM control file contains a nonnumeric process category
number text.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the process category number. It must be an unsigned
integer between 00 and 97.
40
No corresponding PCAT entry for TITLE n
Cause
The MeasTCM control file contains a TITLE entry for process category n and there is no
corresponding PCAT entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and delete the TITLE entry or add the corresponding PCAT entry
or entries.
41
More than one TITLE entry for process category n
Cause
The MeasTCM control file contains more than one TITLE entry for process category n.
MeasTCM Termination Messages 199
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and check that each process category has only one corresponding
TITLE entry.
42
Invalid user ID user number for process category n
Cause
One of the PCAT entries of process category n contains an invalid user ID user number
specification.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the user ID user number. It must be equivalent to an
asterisk (*) or an unsigned integer between 0 and 255.
43
More than one REPORT entry in control file n
Cause
The MeasTCM control file contains more than one REPORT entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and check that no more than one REPORT entry is specified.
44
Missing REPORT parameter in control file
Cause
The REPORT keyword in the MeasTCM control file is not followed by a process name.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and either add a Spooler collector process name (including location
if desired) following the REPORT keyword or remove the REPORT entry completely.
45
TITLE entries must come after PCAT entries
Cause
One or more PCAT entries follow TITLE entries in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and move all the TITLE entries after the last PCAT entry.
46
TITLE entry missing for process category n
Cause
The MeasTCM control file contains PCAT entries for process category n but no corresponding
TITLE entry.
200 MeasTCM Error Messages
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and either add a TITLE entry for process category n or delete all
the PCAT entries for that process category.
47
Missing CSVDATA parameter in control file
Cause
The CSVDATA keyword in the MeasTCM control file is not followed by a file name.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and either add a file name following the CSVDATA keyword, or
remove the CSVDATA entry completely.
48
Invalid Measure MEASFH file name
Cause
The file name of the Measure file handling program following one of the keywords MEASURE
in the MeasTCM control file is invalid.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the MEASFH file name.
49
Error during MEASOPEN n
Cause
Error n occurred during execution of the Measure callable procedure MEASOPEN.
Effect
The program abends. A saveabend is created. No CSV files are produced.
Recovery
For an explanation of the error codes, refer to the Measure Reference Manual. To find out if the
Measure file is valid, try to open the Measure file from MEASCOM. If it is, check that the
MEASURE entry in the MeasTCM control file is syntactically correct. Make sure that the measure
file and measfh file values are fully qualified and match those in the MEASCOM command used
to open the Measure file.
50
Error during MEASCLOSE n
Cause
Error n occurred during execution of the Measure callable procedure MEASCLOSE.
Effect
The program abends. A saveabend is created. The CSVs should have been created. If requested,
the audit report should also be available.
Recovery
For an explanation of the error codes, refer to the Measure Reference Manual.
51
Error during MEASGETVERSION n
MeasTCM Termination Messages 201
Cause
Error n occurred during execution of the Measure callable procedure MEASGETVERSION.
Effect
The program abends. A process snapshot file is created. No CSV files are produced.
Recovery
For an explanation of the error codes, refer to the Measure Reference Manual.
52
Error during MEASREAD_DIFF_ n
Cause
Error n occurred during execution of the Measure callable procedure MEASREAD_DIFF_.
Effect
The program abends. A saveabend is created. Part of the CSV files might have been created
but will be incomplete. If requested, the audit report might also have been partially created.
Recovery
For an explanation of the error codes, refer to the Measure Reference Manual.
53
Measure Disk record allocation error n times
Cause
Entity overflow errors were detected in the Measure files during processing for disk records. n
specifies the number of DISC entities ignored because of the Measure error.
Effect
MeasTCM ignores the invalid DISC entries. The CSVs files and audit report are created if
requested.
Recovery
None needed. If the number of invalid entries is too high, take another measurement with a
smaller total time or with fewer intervals and try MeasTCM again.
54
Internal table overflow text
Cause
An overflow occurred on one of the MeasTCM internal tables.
Effect
The program abends. A saveabend is created. No CSV files are produced.
Recovery
Report this error to your HP analyst.
55
Measure Process record allocation error n times
Cause
Entity overflow errors were detected in the Measure files during processing for process records.
n specifies the number of process entities ignored because of the Measure error.
Effect
MeasTCM ignores the invalid process entries. The CSVs files and audit report are created if
requested.
Recovery
None needed. If the number of invalid entries is too high, take another measurement with a
smaller total time or with fewer intervals and try MeasTCM again.
202 MeasTCM Error Messages
56
Internal error text
Cause
A MeasTCM internal error occurred.
Effect
The program abends. A saveabend is created. No CSV files are produced.
Recovery
Report this error to your HP analyst.
57
Too many Measure data files
Cause
Too many Measure data files are specified in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
Recovery
“Features and Functions” (page 29) shows the maximum number of Measure data files that can
be handled in one session. Reduce the number of Measure data files by combining Measure
entities in one file.
58
Too many PCAT entries
Cause
The MeasTCM control file contains too many PCAT entries.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the control file and eliminate some PCAT entries using wild-card characters in other PCAT
entries. If you cannot reduce the number of entries, contact Software Support.
59
Too many transactions
Cause
The MeasTCM control file contains too many TXN entries.
Effect
The program terminates. No CSV files are produced.
Recovery
Check the MeasTCM documentation for the maximum number of transaction definitions. Edit the
MeasTCM control file and delete one or more TXN entries.
60
Different Measure data file versions for the same system
Cause
Two or more Measure data files have been collected on the same system but show different
product versions.
Effect
The program terminates. No CSV files are produced.
Recovery
Check that all Measure data files belonging to the one system contain data that was collected
at the same time.
MeasTCM Termination Messages 203
61
Too many disk volumes
Cause
The total number of disk volumes defined in the Measure data files exceeds the maximum currently
allowed by MeasTCM.
Effect
The program terminates. No CSV files are produced.
Recovery
Reduce the number of disk volumes by limiting the number of systems under study. If you cannot
reduce the number of disk volumes, contact the GCSC.
62
Too many processes
Cause
The total number of processes in the current system exceeds the maximum currently allowed by
MeasTCM.
Effect
The program terminates. No CSV files are produced.
Recovery
Reduce the number of processes defined by narrowing down the time window (CSVHI-CSVLO)
in the MeasTCM control file. If you cannot reduce the number of entries, contact the GNSC.
63
Measure Discopen record allocation error n times
Cause
1. Entity overflow errors were detected in the Measure files during processing for discopen
records. n specifies the number of discopen entities ignored because of the Measure error.
2. Entity overflow errors were detected in the Measure files during processing for discopen
total records.
Effect
1. MeasTCM ignores the invalid discopen entries. The CSVs files and audit report are created
if requested.
2. The program abends. A process snapshot file is created. CSV files are not created.
Recovery
1. None needed. If the number of invalid entries is too high, take another measurement with
a smaller total time or with fewer intervals and try MeasTCM again.
2. Take another measurement with a smaller total time or with fewer intervals and try MeasTCM
again.
64
Invalid report file name
Cause
The file name following the keyword REPORT in the MeasTCM control file is invalid.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the report file name. It should correspond to a valid
Spooler collector process name that can be qualified.
65
Spooler collector COBOLASSIGN error n
204 MeasTCM Error Messages
Cause
Error number n occurred during execution of the COBOLLIB routine COBOLASSIGN. If n = 1,
the syntax for the file name specified in the REPORT entry of the MeasTCM control file was
invalid. If n > 1, there was an internal MeasTCM error occurred.
Effect
The program terminates. No CSV files are produced.
Recovery
If n = 1, edit the MeasTCM control file and check that the REPORT entry refers to a valid local
Spooler collector process name. If n > 1, report this error to your HP analyst.
66
Error during COBOL85^SPECIAL^OPEN n
Cause
An error occurred during execution of the CBL85UTL routine COBOL85^SPECIAL^OPEN. If n
= 4, then the file name specified in the REPORT entry of the MeasTCM control file does not
correspond to a Spooler collector process. If n = 5, then an operation error occurred while
opening the file name specified in the REPORT entry of the MeasTCM control file. Otherwise,
an MeasTCM internal error occurred.
Effect
The program terminates. No CSV files are produced.
Recovery
If n = 4, edit the MeasTCM control file and correct the REPORT entry. If n = 5, check the attributes
of the Spooler collector process or change the file name in the REPORT entry. Otherwise, report
this error to your HP analyst.
67
Error during COBOL85^SET^SORT^PARAM^VALUE n
Cause
An error occurred during execution of the COBOL85 routine
COBOL85^SET^SORT^PARAM^VALUE.
Effect
The program abends. A saveabend is created. No CSV files are produced.
Recovery
Check that the correct product version of FastSort is installed on your system. If this is the case,
report this error to your HP analyst.
68
Measure data contains unsupported CPU type n
Cause
One of the Measure CPU entity records show a CPU type of n, which this version of MeasTCM
does not supported.
Effect
The program abends. A saveabend is created. No CSV files are produced.
Recovery
Check if this CPU type is valid and obtain an updated product version of MeasTCM if necessary.
69
Invalid transaction type n
Cause
The MeasTCM control file contains an invalid transaction type specification text.
MeasTCM Termination Messages 205
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and look for the TXN entry with the corresponding transaction
type. Change the type parameter to a valid value.
70
Invalid CSV file name
Cause
The CSV data file name following the keyword CSVDATA in the MeasTCM control file is invalid.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the CSV data file name.
71
Error in purging CSV file n
Cause
File-system error n occurred during an attempt to purge the existing CSV data file.
Effect
The program terminates. No CSV files are produced.
Recovery
Verify the meaning of the file-system error code and correct accordingly.
72
Error in creating CSV file n
Cause
File-system error n occurred during an attempt to create the CSV data file.
Effect
The program terminates. No CSV files are produced.
Recovery
Verify the meaning of the file-system error code and correct accordingly.
73
Invalid application name in control file.
Cause
The MeasTCM control file contains an invalid application name.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and check that the application name starts with an alphabetic
character.
74
More than one CONVERTTO entry in control file
Cause
The MeasTCM control file contains more than one CONVERTTO entry.
Effect
The program terminates. No CSV files are produced.
206 MeasTCM Error Messages
Recovery
Edit the MeasTCM control file and remove the erroneous CONVERTTO entry or entries.
75
Invalid CONVERTTO parameter in control file
Cause
The parameter following the CONVERTTO keyword in the MeasTCM control file does not
represent a valid processor type.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the CONVERTTO parameter.
77
Invalid CPUPOWER type parameter in Control file
Cause
The CPU TYPE value (first parameter) for the CPUPOWER keyword is not correct for the CPU
TYPE.
Effect
The program terminates. No CSV files are produced.
Recovery
Correct the value of the first parameter for this keyword.
78
Invalid CPUPOWER factor parameter in Control file
Cause
The CPUPOWER value (second parameter) for the CPUPOWER keyword is not in the correct
format, is not numeric, or is zero.
Effect
The program terminates. No CSV files are produced.
Recovery
Correct the value of the second parameter for this keyword.
79
Invalid Measure data file(s)
Cause
The specified Measure data file or files are not valid given the other parameters specified in the
MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
Recovery
Check the MeasTCM control file for CSVLO and CSVHI values, the start and stop times of the
Measure data files specified. For further information, check the run summary produced.
80
CSVHI earlier than actual start time
Cause
The user-specified CSVHI is earlier than the start time of the first Measure data file specified.
Effect
The program terminates. No CSV files are produced.
MeasTCM Termination Messages 207
Recovery
Correct the value of CSVHI so that it is later than the start time of the first Measure data file.
81
CSVLO later than actual stop time
Cause
The user-specified CSVLO is later than the latest stop time across all Measure data files specified.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file so that the value of CSVLO is earlier than the latest stop time.
82
Duplicate NUMCSVS keyword detected
Cause
More than one NUMCSVS keyword entry exists in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove all but one NUMCSVS keyword entry.
83
Invalid NUMCSVS parameter; should be numeric
Cause
The NUMCSVS parameter in the MeasTCM control file has an alphanumeric value other than
* or ALL.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and enter a nonzero integer for the NUMCSVS parameter.
84
Invalid NUMCSVS parameter; should not be zero
Cause
The NUMCSVS parameter in the MeasTCM control file has the value zero.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and enter a nonzero integer for the NUMCSVS parameter.
85
CPUFACTOR - Guardian Type must be G, H or J
Cause
A Guardian Type other than G, H or J was entered.
Effect
The program terminates. No CSV files are produced.
Recovery
Enter Guardian Type G, H or J.
86
208 MeasTCM Error Messages
Essential CPU data missing. CPU=nn
Cause
The Measure data is incomplete. CPU number nn is missing.
Effect
The program terminates. No CSV files are produced.
Recovery
Rerun Measure. Include all CPUs (CPU*).
87
Entity overflow has occured.
Cause
A MEASURE entity overflow error occurred during the MeasTCM processing.
Effect
MeasTCM ignores the entities affected by the overflow. A count of the number of entities is kept
and given in a separate message. The CSV files and audit report are produced if requested.
Recovery
None. If the number of entities ignored is too large, take another measurement with a smaller
total time or with fewer intervals and try again.
88
Input CONTROL FILE does not exist.
Cause
The MeasTCM control file was not specified on the command line.
Effect
The program terminates. No CSV files are produced.
Recovery
Specify the MeasTCM control file on the command line. For more information, see Chapter 3:
“Using MeasTCM”.
89
NSK-version required as second CONVERTTO parameter.
Cause
In the control file, the second parameter (NonStop Kernel version) was not specified for the
CONVERTTO factor. This NonStop kernel is necessary if the first parameter, the processor type,
does not match that of any of the Measure data files.
Effect
The program terminates. No CSV files are produced.
Recovery
In the control file, add the second parameter for the CONVERTTO factor. This parameter is a
three-lettered entity. The list of allowable values is included in the sample control file CNTLFILE.
90
CONVERTTO NSK-version (Param 2) incompatible for CPU-type (Param 1).
Cause
In the control file, the second parameter of CONVERTTO (NonStop Kernel version) is not
compatible with the first parameter (CPU type). This second parameter is necessary if the first
parameter, the processor type, does not match that of any of the Measure data files.
Effect
The program terminates. No CSV files are produced.
MeasTCM Termination Messages 209
Recovery
In the control file, alter the second parameter for the CONVERTTO factor. This parameter is a
three-lettered entity. The list of allowable values is mentioned in the sample control file CNTLFILE.
91
Invalid DISKPOWER type parameter in control file.
Cause
In the MeasTCM control file, one or more than one of the DISKFACTOR keyword parameters is
incorrect.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the DISKFACTOR parameter or parameters.
92
Controller not available for DISK type.
Cause
One of the Measure Disk entity records contains a controller of type n, which this version of
MeasTCM does not support.
Effect
The program terminates. A saveabend is created. No CSV files are produced.
Recovery
Check if this controller type is valid and obtain an updated product version of MeasTCM if
necessary.
93
More than one DISKCONVERTTO entry in control file.
Cause
The MeasTCM control file contains more than one DISKCONVERTTO entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove the erroneous DISKCONVERTTO entry or entries.
94
Invalid DISKCONVERTTO parameter in control file.
Cause
The first parameter following the DISKCONVERTTO keyword in the MeasTCM control file does
not represent a valid disk type.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the DISKCONVERTTO first parameter.
95
DISKCONVERTTO required if mixed DISK types are present.
Cause
Measure data file contains mixed disk types.
Effect
The program terminates. No CSV files are produced.
210
MeasTCM Error Messages
Recovery
Edit the MeasTCM control file and add a DISKCONVERTTO entry defining the output disk type.
96
Measure data contains unsupported DISK type.
Cause
One of the Measure Disk entity records show a disk subtype of n, which this version of MeasTCM
does not support.
Effect
The program terminates. A saveabend is created. No CSV files are produced.
Recovery
Check if this disk subtype is valid and obtain an updated product version of MeasTCM if
necessary. Workaround: Use the DISKFACTOR keyword in the control file to run MeasTCM
successfully for generating a CSV file.
97
More than one ACTUALDISK42 entry in control file.
Cause
The MeasTCM control file contains more than one ACTUALDISK42 entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove the erroneous ACTUALDISK42 entry or entries.
98
More than one ACTUALDISK43 entry in control file.
Cause
The MeasTCM control file contains more than one ACTUALDISK43 entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove the erroneous ACTUALDISK43 entry or entries.
99
More than one ACTUALDISK44 entry in control file.
Cause
The MeasTCM control file contains more than one ACTUALDISK44 entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove the erroneous ACTUALDISK44 entry or entries.
100
Invalid ACTUALDISK42 parameter in control file.
Cause
The parameter following the ACTUALDISK42 keyword in the MeasTCM control file does not
represent a valid disk of subtype 42.
Effect
The program terminates. No CSV files are produced.
MeasTCM Termination Messages
211
Recovery
Edit the MeasTCM control file and correct the ACTUALDISK42 parameter.
101
Invalid ACTUALDISK43 parameter in control file.
Cause
The parameter following the ACTUALDISK43 keyword in the MeasTCM control file does not
represent a valid disk of subtype 43.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the ACTUALDISK43 parameter.
102
Invalid ACTUALDISK44 parameter in control file.
Cause
The parameter following the ACTUALDISK44 keyword in the MeasTCM control file does not
represent a valid disk of subtype 44.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the ACTUALDISK44 parameter.
103
Disk Subtype is 42. ACTUALDISK42 keyword required.
Cause
The measurement data file or files contain disk entity records for disks of subtype 42, and the
ACTUALDISK42 entry is not present in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and add an ACTUALDISK42 entry defining the disks of subtype
42.
104
Disk Subtype is 43. ACTUALDISK43 keyword required.
Cause
The measurement data file or files contain disk entity records for disks of subtype 43, and the
ACTUALDISK43 entry is not present in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and add an ACTUALDISK43 entry defining the disks of subtype
43.
105
Disk Subtype is 44. ACTUALDISK44 keyword required.
Cause
The measurement data file or files contain disk entity records for disks of subtype 44, and the
ACTUALDISK44 entry is not present in the MeasTCM control file.
212
MeasTCM Error Messages
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and add an ACTUALDISK44 entry defining the disks of subtype
44.
106
More than one ACTUALDISK53 entry in control file.
Cause
The MeasTCM control file contains more than one ACTUALDISK53 entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove the erroneous ACTUALDISK53 entry or entries.
107
Invalid ACTUALDISK53 parameter in control file.
Cause
The parameter following the ACTUALDISK53 keyword in the MeasTCM control file does not
represent a valid disk of subtype 53.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the ACTUALDISK53 parameter.
108
Disk Subtype is 53. ACTUALDISK53 keyword required.
Cause
The measurement data file or files contain disk entity records for disks of subtype 53, and the
ACTUALDISK53 entry is not present in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and add an ACTUALDISK53 entry defining the disks of subtype
53.
109
DISKCONVERTTO write cache status must be ON or OFF.
Cause
The second parameter following the DISKCONVERTTO keyword in the MeasTCM control file
does not represent a valid write cache status.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the DISKCONVERTTO second parameter representing
write cache status.
110
More than one ACTUALDISK51 entry in control file.
MeasTCM Termination Messages
213
Cause
The MeasTCM control file contains more than one ACTUALDISK51 entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove the erroneous ACTUALDISK51 entry or entries.
111
Invalid ACTUALDISK51 parameter in control file.
Cause
The parameter following the ACTUALDISK51 keyword in the MeasTCM control file does not
represent a valid disk of subtype 51.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the ACTUALDISK51 parameter.
112
Disk Subtype is 51. ACTUALDISK51 keyword required.
Cause
The measurement data file or files contain disk entity records for disks of subtype 51, and the
ACTUALDISK51 entry is not present in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and add an ACTUALDISK51 entry defining the disks of subtype
51.
113
Invalid read seek time parameter for DISKFACTOR keyword in control file.
Cause
The disk read seek time (fifth parameter) for the DISKFACTOR keyword is not in the correct
format; it is not a positive number between 01.00 to 09.99.
Effect
The program terminates. No CSV files are produced.
Recovery
Correct the value of the read seek time parameter for this keyword.
114
Invalid write seek time parameter for DISKFACTOR keyword in control
file.
Cause
The disk write seek time (sixth parameter) for the DISKFACTOR keyword is not in the correct
format; it is not a positive number between 01.00 to 09.99.
Effect
The program terminates. No CSV files are produced.
Recovery
Correct the value of the write seek time parameter for this keyword.
115
214
MeasTCM Error Messages
Invalid or Blank IPU count parameter in CPUFACTOR Keyword.
Cause
The IPU count value (fifth parameter) for the CPUFACTOR keyword is not in the correct format;
it is not numeric.
Effect
The program terminates. No CSV files are produced.
Recovery
Correct the value of the IPU count parameter for this keyword.
116
Invalid parameter for NUMTMFTRAIL Keyword.
Cause
The parameter following the NUMTMFTRAIL keyword in the MeasTCM control file does not
contain a valid numeric between 1 and 16.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the NUMTMFTRAIL parameter.
117
More than one ACTUALDISK52 entry in control file.
Cause
The MeasTCM control file contains more than one ACTUALDISK52 entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove the erroneous ACTUALDISK52 entry or entries.
118
Invalid ACTUALDISK52 parameter in control file.
Cause
The parameter following the ACTUALDISK52 keyword in the MeasTCM control file does not
represent a valid disk of subtype 52.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and correct the ACTUALDISK52 parameter.
121
Measure data contains XP disk (subtype 52). DISKCONVERTO SAS disk
necessary.
Cause
•
The measurement data file or files contain disk entity records for disks of subtype 52, and
the DISKCONVERTTO keyword is not present in the MeasTCM control file.
•
The measurement data file or files contain disk entity records for disks of subtype 52, and
the first parameter of the DISKCONVERTTO keyword does not contain a disk of subtype
51 in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
MeasTCM Termination Messages
215
Recovery
Edit the MeasTCM control file and add a DISKCONVERTTO entry with SAS disk entry (of subtype
51).
122
Disk Subtype is 52. ACTUALDISK52 keyword required.
Cause
The measurement data file or files contain disk entity records for disks of subtype 52, and the
ACTUALDISK52 entry is not present in the MeasTCM control file.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and add an ACTUALDISK52 entry defining the disks of subtype
52.
123
More than one NUMTMFTRAIL entry in control file.
Cause
The MeasTCM control file contains more than one NUMTMFTRAIL entry.
Effect
The program terminates. No CSV files are produced.
Recovery
Edit the MeasTCM control file and remove the erroneous NUMTMFTRAIL entry or entries.
Informational Messages
The following messages are informational messages only and do not have message numbers
assigned to them.
Initializing.
Cause
MeasTCM is in its initialization phase.
Effect
Informational only.
Recovery
None
Reading control file.
Cause
MeasTCM is reading and interpreting the MeasTCM control file.
Effect
Informational only.
Recovery
None
Core processing for system system.
Cause
MeasTCM is processing the records for the specified system.
Effect
Informational only.
216
MeasTCM Error Messages
Recovery
None
Opening Measure data file measure file.
Cause
MeasTCM is opening the specified Measure file.
Effect
Informational only.
Recovery
None
Closing Measure data file(s).
Cause
MeasTCM is closing all the Measure files it had opened.
Effect
Informational only.
Recovery
None
Analyzing CPU records.
Cause
MeasTCM is processing CPU records. This message is displayed for each system found in the
Measure files.
Effect
Informational only.
Recovery
None
Writing CSV file csv file.
Cause
MeasTCM is creating the specified CSV file.
Effect
Informational only.
Recovery
None
Analyzing all Disc records.
Cause
MeasTCM is processing all of the disc records in the Measure files.
Effect
Informational only.
Recovery
None
Analyzing Process records.
Cause
MeasTCM is processing PROCESS records. This message is displayed for each system found in
the Measure files.
Informational Messages
217
Effect
Informational only.
Recovery
None
Linking Discopen records.
Cause
MeasTCM is linking the process records to the discopen records in the Measure files. This
message is displayed for each system found in the Measure files.
Effect
Informational only.
Recovery
None
Sorting data for process category audit report.
Cause
MeasTCM is sorting the data for the requested audit report. This message appears only if an
audit report was requested.
Effect
Informational only.
Recovery
None
Producing process category audit report.
Cause
MeasTCM is creating the requested audit report.
Effect
Informational only.
Recovery
None
% of the Discopens were linked.
Cause
This message shows what percentage of total Discopen activity was linked to corresponding
processes.
Effect
Informational only.
Recovery
None
Invalid Measure file; CSVHI and stop time not available.
Cause
The Measure data file was created without a specified stop time, and the user has not specified
CSVHI.
Effect
The program terminates. CSV files are not created.
Recovery
Add the CSVHI keyword entry to the MeasTCM control file or remove the Measure entry of the
invalid file from the MeasTCM control file.
218
MeasTCM Error Messages
Warning: This Measure file does not overlap previous valid file.
Cause
This Measure data file was started after the previous file ended. There is no overlap.
Effect
The CSV files will not be 100 percent precise because there is a gap in the measurement window.
Recovery
If this situation is unacceptable, re-create Measure files by using intervals instead of Measure
stops and starts.
Collection interval not available; computed as stop time - start time.
Cause
The collection interval was not specified for this Measure file.
Effect
MeasTCM calculated the interval as stop time - start time.
Recovery
None.
This CSV file has a low % linkage between processes and discopens.
Cause
The percent of linkage between the Measure PROCESS entities and DISCOPEN entities is below
90 percent.
Effect
The CSV files might be as precise as they can be.
Recovery
This situation is unacceptable. This situation might be caused by having a large number of remote
opens and not having the Measure files of the remote system. Check that you have Measure
files for all the systems affected and try MeasTCM again.
Program terminated because some Measure data files cannot be used.
Cause
MeasTCM could not continue because one or more of the Measure files could not be used.
Effect
The program terminates. CSV files are not created.
Recovery
This is a global advisory message. One or more detailed messages with the actual errors will
precede this message. Use those messages to determine the required recovery.
Stop time not available for this file; set as user-specified CSVHI.
Cause
A stop time was not specified for this Measure file.
Effect
MeasTCM uses the specified CSVHI as the stop time.
Recovery
None.
Warning: The start and stop time lies outside user-specified window.
Cause
The time range for this Measure file lies outside the window specified by CSVLO and CSVHI.
Informational Messages
219
Effect
MeasTCM does not use this Measure file.
Recovery
This situation is unacceptable. Change the values for CSVHI, CSVLO or both values in the
MeasTCM control file if the Measure file is to be included.
Warning: This file will not be used to generate CSV file(s).
Cause
MeasTCM ignores this Measure file.
Effect
MeasTCM ignores this Measure file.
Recovery
A previous message indicates why the Measure file is not used. See the recovery for that message.
User specified time window outside actual time window of data files.
Cause
The time window specified by the user as CSVLO and CSVHI is outside the actual time range
as determined by the earliest start time and latest stop time of all Measure data files.
Effect
The program terminates. CSV files are not created.
Recovery
Correct the CSVLO and CSVHI entries in the MeasTCM control file.
No valid Measure data files within user-specified time range.
Cause
No valid Measure files were found with a time range within the CSVLO and CSVHI time range.
Effect
The program terminates. CSV files are not created.
Recovery
Correct the CSVLO and CSVHI entries in the MeasTCM control file.
Warning: One or more measure file error occured.
Cause
A Measure file error occurred on the Measure data file.
Effect
MeasTCM declares the Measure file invalid and stops using it.
Recovery
The Measure file is probably full (error 45). If the resulting CSV files are not acceptable, new
Measure files are needed. Create larger Measure files, use fewer intervals, or use a smaller time
window.
Empty CSV file. No processes found.
Cause
MeasTCM could not find any process records in the Measure file for the time specified.
Effect
None. MeasTCM continues with the next Measure file.
220 MeasTCM Error Messages
Recovery
The Measure file is probably full (error 45). If the resulting CSV files are not acceptable, new
Measure files are needed. Create larger Measure files, use fewer intervals, or use a smaller time
window.
Starting processing for CSV file.
Cause
MeasTCM is processing the data needed for the specified CSV file.
Effect
Informational only.
Recovery
None.
Informational Messages 221
C TCM Menus
This appendix shows the menu items for the TCM Workload Apportionment and Performance
Model menus. You can print this appendix and use it as a job aid.
Menu Items for Excel 2003
For Workload Apportionment Model
222 TCM Menus
Menu Items for Excel 2003 223
For Performance Model
224 TCM Menus
Menu Items for Excel 2003 225
Ribbon Items for Excel 2007/2010
For Workload Apportionment Model
226 TCM Menus
Ribbon Items for Excel 2007/2010 227
For Performance Model
228 TCM Menus
Ribbon Items for Excel 2007/2010 229
D TCM Response Time Formulas
TCM uses these response time formulas for batch transactions:
TCM uses these simplified response time formulas for online transactions:
Query transactions are modeled as OLTP or batch, depending on the setting of the CPU Pathlength
Threshold field.
230 TCM Response Time Formulas
E Common TCM Procedures
This appendix gives step-by-step instructions for completing the following TCM procedures:
•
“Adding a Transaction” (page 232)
•
“Analyzing Capacity History” (page 232)
•
“Calculating Throughput Trending” (page 233)
•
“Calibrating Batch Response Time” (page 233)
•
“Changing Authorization Levels” (page 233)
•
“Changing Default Priorities” (page 234)
•
“Changing Expert Parameters” (page 234)
•
“Changing Individual Priorities” (page 235)
•
“Changing Passwords” (page 235)
•
“Checking an Apportionment Method” (page 235)
•
“Checking Category 98” (page 236)
•
“Collecting Measure Samples” (page 236)
•
“Converting TCM Models From Earlier TCM Product Versions” (page 236)
•
“Creating Additional Workload Apportionment Models” (page 236)
•
“Creating a Mix Chart” (page 237)
•
“Creating a New Workload Apportionment Model” (page 237)
•
“Creating a New Performance Model” (page 237)
•
“Creating a Trend Chart” (page 237)
•
“Customizing the MeasTCM CNTLFILE” (page 238)
•
“Customizing Help Messages” (page 238)
•
“Customizing TCM Screens” (page 238)
•
“Downloading Performance Data Samples” (page 239)
•
“Finding Product Version Information” (page 239)
•
“Generating a Timeline Chart” (page 239)
•
“Getting Help for Function Keys” (page 240)
•
“Getting Help for Specific Fields” (page 241)
•
“Loading a CSV Sample Into a WA Model” (page 241)
•
“Loading Models Created by Other Users” (page 241)
•
“Merging Performance Models” (page 242)
•
“Modifying Apportioned Data Using an .AWA File in the Current Session” (page 242)
•
“Modifying Apportioned Data Using an .AWA File Not in the Current Session” (page 243)
•
“Modifying the Percentile Response Times” (page 244)
•
“Modifying the Planning Unit” (page 244)
•
“Modifying the Transaction Count Table” (page 244)
•
“Modifying the Workload Apportionment Weights Table” (page 245)
•
“Moving Between Screens” (page 245)
•
“Picking the Best CSV Sample and Loading It Into the Performance Model” (page 245)
•
“Printing a Chart” (page 246)
231
•
“Returning to TCM From a Chart” (page 246)
•
“Running MeasTCM” (page 246)
•
“Saving Apportionment Tables” (page 247)
•
“Saving a Performance Model” (page 247)
•
“Saving a Workload Apportionment Model” (page 248)
•
“Sorting Capacity History Data” (page 248)
•
“Uncalibrating Batch Response Time” (page 249)
•
“Updating the Capacity History Database” (page 249)
•
“Updating the Capacity History Database With Selected CSV Files” (page 249)
•
“Using Online Help” (page 250)
•
“Using TCM Expert to Generate an Apportionment Weights Table for CSV Files” (page 250)
•
“Using the Consumption Model” (page 251)
•
“Using the Process Category Audit (PCAT) Report” (page 252)
•
“Using the Planning Timeline Model” (page 252)
•
“Viewing TCM Expert Parameters” (page 253)
Adding a Transaction
The Add Transaction option adds a new, user-defined transaction to the Performance model that
typically was not apportioned using a WA model. For example, if you have estimates of CPU and
disk demands for a new transaction for which no Measure data yet exists, you can use this option
to define the transaction.
To add a transaction:
1. Log on as an administrator or a super user.
2. Open a Performance model.
3. Select Update > Add Transaction. The Add Transaction dialog box appears.
4. In the Add Transaction section, select the Transaction Name, Type, Transactions per Second,
and Transaction Priority.
5. In the CPU Secs per Txn section, select the Interrupt CPU Secs per Txn, Application CPU Secs
per Txn, and Disk Process CPU Secs per Txn.
6. In the Application Disk Seconds section, select Read Secs per Txn and Write Secs per Txn.
7. If the transaction is audited, click the Audited check box. If the transaction is not audited, leave
the check box unchecked. If the transaction is audited, TCM assigns default values to the TMF
disk read and write seconds for the transactions.
8. Click Add.
The transaction’s activity is allocated entirely to a category of the same name and is added to both
the actual and plan baseline screens.
To examine or modify these values, select Update > Change Transaction.
For more information, see “Add Transaction” (page 172) and “Add Similar Transaction” (page 173).
Analyzing Capacity History
The Capacity History database is a valuable tool in determining the reasonableness of the
apportionment method. From it, the capacity planner can:
•
analyze the apportioned data in each sample model and eliminate unrepresentative sample
models
•
identify the apportionment method that yields the most consistent CPU demands
To analyze capacity history:
232 Common TCM Procedures
1.
2.
Open a Workload Apportionment model.
Find the Capacity History database. If it is not accessible, open the desired history file. The
Capacity History screen appears.
3. Analyze the historical variance of the CPU and disk demands for the sample data, ignoring
or deleting unrepresentative data samples that might have been taken when data
communications lines were inoperative or during CPU failures.
4. Select the apportionment method that yields relatively consistent CPU and disk demands across
all the representative samples.
For more information, see “Updating the Capacity History Database” (page 81).
Calculating Throughput Trending
Calculating throughput trending is the same as calculating throughput growth rate and transaction
per task growth rate. You can use the Planning Timeline model to have TCM calculate throughput
growth rate (or transaction per task growth rate) based on the existing trend in the history database.
To calculate throughput trending:
1. Open a Performance model.
2. Select Update > Timeline Trends. The Update Timeline Trend dialog box appears.
3. Select the desired transaction to trend from the Transaction list.
4. If desired, modify the range of dates in the history database by entering new dates in the
From and To fields. The default is the entire history database. Those dates appear in the fields.
5. Click OK.
6. Select Options > Calculate Now (F9).
The transaction trend in the historical database is used to update the Planning Timeline screen.
If you are using a color monitor, the trend appears in red.
For more information, see “Throughput Trending” (page 93).
Calibrating Batch Response Time
If you observe the actual response time of batch transactions that you run on your system and want
TCM to adjust its predicted response time accordingly, you can use the Calibrate Batch Response
Time command.
To calibrate batch response time:
1. Open a Performance model.
2. Select Update > Calibrate Batch Response Time. The Calibrate Batch Response Time dialog
box appears.
3. Select the batch transaction name to calibrate from the list.
4. Type the observed response time in the Calibrate Batch Response Time dialog box or accept
the default values. You can enter hours, minutes, and seconds.
5. Make sure the Uncalibrate Transaction check box is not checked.
6. Click OK.
TCM adjusts its estimated response times in the Performance model by factors that reflect observed
response times.
For more information, see “Calibrating Batch Response Time” (page 105).
Changing Authorization Levels
Only users with a TCM administrator or superuser authorization level can create or modify the
apportionment tables (and therefore create a model).
To change authorization levels:
1. Open a model.
2. To change the authorization level either:
Calculating Throughput Trending 233
a.
b.
3.
4.
Select Options > Change Authorization Level. The TCM Password dialog box appears.
Click the User Authorization level button located at the top left corner. The TCM Password
dialog box appears.
At the prompt, enter the password for the new authorization level if one has been set up.
Otherwise, enter the default password.
The default password for the Administrator authorization level is ADMIN. The default password
for the Super authorization level is SUPER. The default passwords are not case-sensitive, and
both the WA and Performance models have the same default passwords.
Click OK.
When the appropriate password is entered, TCM changes your authorization to the level that
corresponds with the password you entered and a dialog displays the new authorization level.
If an incorrect, blank, or null password is entered, your authorization level changes to that of
capacity planner.
For more information, see “Security” (page 69).
Changing Default Priorities
To change the default process category priority, you use the TCM Parameters screen in the WA
model.
To change default priorities:
1. Open a WA model.
2. Log on as an administrator or super user.
3. Select Find > TCM Parameters.
4. Select Options > Unprotect Admin Fields.
5. Enter the customized priorities in the Priority column for the process categories that you want
to change.
6. Select Options > Protect Admin Fields.
7. Select Options > Calculate Now (F12).
8. To save the model select Save or Save As from the File tab.
For more information, see “WA Model TCM Parameters Screen” (page 116).
Changing Expert Parameters
To change the global parameters for TCM Expert:
1. Select TCM Expert from the “TCM Initial Menu” (page 67).
2. Enter or select a custom directory and click OK.
3. Select Expert > TCM Expert Parameters.
The TCM Expert Parameters dialog box appears.
4.
5.
Accept the default Capacity History time period (six months) or specify a new one.
This field specifies the time range that is used in three situations:
•
The time range that is checked for transaction cost consistency when Generate Expert is
executed
•
The time range that is checked for transaction cost consistency when Update History with
Selected CSV Samples is executed
•
The time range that is used when the Pick Best Sample option is selected
If you are logged on as an administrator or at a higher level, accept the default Cache Miss
Factor or enter a new one.
The Cache Miss Factor specifies the relative CPU cost to the disk process of a cache miss as
compared with a cache hit. The default settings assume that it takes twice as much CPU time
to get data off the disk than to get data from cache (memory). That is, a cache miss costs twice
as much as a cache hit. A TCM administrator or superuser can modify this factor.
234 Common TCM Procedures
6.
Accept the default CPU Pathlength Threshold or specify a new one.
The CPU Pathlength Threshold field specifies the point at which a query transaction is considered
either an OLTP or batch transaction. The default setting is two seconds. Small demand queries
taking less than two seconds are considered OLTP transactions, large demand queries taking
longer than two seconds are considered batch transactions. Any TCM user can modify this
factor.
7. Click OK. TCM Expert uses the new parameters.
For more information, see Chapter 10: “Using TCM Expert”.
Changing Individual Priorities
To change specific individual process category priorities, use the Workload Detail by Category
screen in the WA model.
To change individual priorities:
1. Open a WA model.
2. Make sure you are logged on as an administrator or super user.
3. Select Find > Workload Detail by Category.
4. Select Options > Unprotect Admin Fields.
5. Enter the customized priorities in the Priority column for the process categories that you want
to change.
6. Select Options > Protect Admin Fields.
7. Select Options > Calculate Now (F12).
8. To save the model, by select Save or Save As from the File tab.
For more information, see “Workload Detail by Category Screen” (page 122).
Changing Passwords
If multiple users will be working with TCM, change the default passwords to maintain system
security.
To change passwords:
1. Log on as an administrator or super user.
2. Open a WA model or a Performance model.
3. Select Options > Change Password. The Change TCM Password dialog box appears.
4. Enter your old password (or the default password) in the Old Password field.
5. Enter the new password you want to use in the New Password field.
6. Click OK. A message confirms the change.
For more information, see “Security” (page 69).
Checking an Apportionment Method
Once an apportionment method has been created (see modifying the default apportionment tables
of a new model or the apportionment tables of an existing model,) and the apportionment formulas
have been generated (see generating apportionment formulas), you need to analyze the results to
determine the reasonableness of the method.
To ensure the accuracy of the TCM modeling results, examine the reasonableness of both the
performance data sample and the method used to apportion this data. Selecting an appropriate
method involves collecting and apportioning multiple performance samples and then analyzing
the results.
Because checking an apportionment method requires several performance samples, the number
of samples should be at least 4 to 5 times the number of defined transactions. For example, if your
application has 3 transactions named Withdrawal, Deposit, and Customer Update, you should
collect at least 12 to 15 samples. The samples should have different transaction mixes and be at
varying utilizations.
Changing Individual Priorities 235
To make sure a method is reasonable, save a model for each apportionment method and follow
the steps in “Updating History With Several Examples” (page 83).
Check the workload apportionment model of your application by comparing your results from all
samples by reviewing the Capacity History file. In general, an Apportionment Weights table can
be viewed as reasonable if CPU and disk demands per transaction are relatively constant across
many performance samples with varying transaction mixes and throughput levels. The requirement
for a variety of transaction mixes is crucial. If mixes do not vary, any apportionment method will
appear to be reasonable but might not be.
For more information, see “Checking an Apportionment Method” (page 83).
Checking Category 98
When working with MeasTCM, check the contents of the process category that contains all the
remaining processes not aggregated to other categories (_OTHER). If this category contains a high
number of unexpected processes, either consider:
•
Editing the control file to create a new category to accommodate these processes
•
Modifying the existing categories to include this activity
For more information, see “Using the Process Category Audit Report” (page 63).
Collecting Measure Samples
For MeasTCM to extract and summarize Measure data, the Measure sample data must meet several
requirements. For a complete list of these requirements, see “Collecting Measure Samples”
(page 30).
Converting TCM Models From Earlier TCM Product Versions
If you open a file created with an older product version of TCM, an alert message notifies you of
the product version mismatch. TCM automatically converts the file and then renames the older file
by replacing the first letter of the file name with an underscore (_).
For example, the original file bank.HST is renamed _ank.HST, and the converted file is now named
bank.HST. A Microsoft Excel dialog box appears when the conversion is done.
Creating Additional Workload Apportionment Models
Creating additional WA models involves loading additional performance data samples into your
WA model for apportioning. This approach allows you to apportion a variety of data samples to
determine the reasonableness of the apportionment method. Creating additional models allows
you to update the Capacity History database with many samples, to select appropriate samples
for modeling, and to create baseline data for input to the Performance model. You must have at
least 10 samples to use the throughput trending feature available in the Performance model.
The following procedure results in one or more saved, apportioned WA models with an updated
history.
To create additional Workload Apportionment models:
1. To download performance data samples to the PC, follow the download procedure you
normally use in Windows. All CSV files for the same application or set of applications should
be kept in the same folder, and all CSV files must have the extension .CSV. TCM detects any
truncated data and issues an error message.
2. If you are already in the WA model, load a CSV file into the current model. (See “Loading a
CSV Sample Into a WA Model” (page 241).)
If you are at the “TCM Initial Menu” (page 67):
a. Select Work With Existing Model. The Open WA Model dialog box displays the available
WA models.
b. Select an existing apportioned model to use as a template for all the new WA models
that you want to create.
236 Common TCM Procedures
c.
d.
Click Update History and Display List of CSV Files, and then click Open.
Select the CSV file or files to load and click OK.
When you are finished, each data sample has a corresponding sample WA model in the folder.
Creating a Mix Chart
To create a Mix chart:
1. Open a Workload Apportionment model.
2. Select History > Update History.
3. Select History > Chart History.
•
If the History file contains data for more than one apportionment method, TCM prompts
you to select the desired apportionment method to use when creating the History charts.
•
4.
If TrendCharts sheets, MixCharts sheets or both are already part of the History file, the
History Chart Overwrite Warning dialog box appears. To create new Trend charts and
Mix charts (the existing ones are deleted automatically), click both checkboxes. This
approach is recommended. Clearing either check box causes TCM to not overwrite that
Chart sheet. When you finish making your selections, click OK.
When the History Charts dialog box displays, select the desired chart size: 1/4 screen, 1/2
screen (horizontal), 1/2 screen (vertical), 2/3 screen (the default), or Full screen. Then click
OK.
TCM creates the requested History charts in the specified size. Progress messages appear in
Excel's status bar at the bottom of the screen while the History charts are being created.
Creating a New Workload Apportionment Model
To create a new Workload Apportionment model:
1. Launch TCM or select Close to return to the TCM Initial menu.
2. Select Create a New WA Model from the “TCM Initial Menu” (page 67).
3. Specify a custom folder and click OK. The Create a New WA Model dialog box appears.
4. Select a CSV file and click OK.
5. TCM displays the new WA model.
Creating a New Performance Model
To create a new Performance model:
1. Launch TCM or select Close to return to the TCM Initial menu.
2. Select Create a New Performance Model from the “TCM Initial Menu” (page 67).
3. Select a custom folder and click OK. The Create New Performance Model dialog box appears.
4. Click the WA Model or CSV File button.
5. Select the WA baseline file or CSV file.
6. If you are building the new model using a CSV file, choose the apportionment from the Using
Apportionment menu.
7. Click OK.
8. TCM displays the new Performance model.
Creating a Trend Chart
To create a Trend chart:
1. Open a Workload Apportionment model.
2. Select History > Update History.
Creating a Mix Chart 237
3.
Select History > Chart History.
•
If the History file contains data for more than one apportionment method, TCM prompts
you to select the desired apportionment method to use when creating the History charts.
•
4.
If TrendCharts sheets, MixCharts sheets, or both are already part of the History file, the
History Chart Overwrite Warning dialog box appears. To create new Trend charts and
Mix charts (the existing ones are deleted automatically), click both checkboxes. This
approach is recommended. Clearing either check box causes TCM to not overwrite that
Chart sheet. When you are finished making your selections, click OK.
When the History Charts dialog box appears, select the desired chart size: 1/4 screen, 1/2
screen (horizontal), 1/2 screen (vertical), 2/3 screen (the default), or Full screen. Then click
OK.
TCM creates the requested History charts in the specified size. Progress messages appear in
Excel's status bar at the bottom of the screen while the History charts are being created.
Customizing the MeasTCM CNTLFILE
When you have completed the process flow diagram, you must translate it into process category
(PCAT) statements for MeasTCM. A template of the control file (CNTLFILE) is available in the
MeasTCM installation subvolume (ZMEASTCM). To define the process categories for your Measure
data, copy the template control file to your working subvolume and edit the file according to your
application needs. For detailed information about the CNTLFILE and its sections, see “Customizing
Your Process Category Control File” (page 33).
Customizing Help Messages
If you have a help compiler, you can change the text of any help message to customize it. The text
for TCM help messages is contained in three files: tcmtxt.hwa for the WA model, tcmhpm.txt for
the Performance model, and tcmtxt.hxp for TCM Expert. The Helpconv utility or equivalent help
compiler must be obtained from Microsoft.
To customize help messages:
1. Use any text editor installed on your workstation to open the help file (tcmtxt.hwa, tcmhpm.txt,
or tcmtxt.hxp).
2. Locate the name of the field with the help message you want to change by scrolling through
the file. The names of all fields are preceded by asterisks (*).
3. Edit the text and save the file.
4. Convert the revised file to a format understandable to Microsoft Windows.
Customizing TCM Screens
To go to this screen, select Customize TCM from the Options Menu. To return to the TCM model,
click the Return to Model button at the top of this screen.
To change the font color of Manually overwritten cells:
1. Enter a value between 0 and 56 in the Value field.
2. As soon as the value is changed, the font color of the text in the sample cell on the right
changes according to the entered value.
The default value of this property is 5 (blue). Values less than 0 or greater than 56 are changed
to the default value of 5.
To change the background color of Read Only cells:
1. Double-click the Read-Only cells label in the Feature column.
2. Select a color from the color palette that pops up and click OK.
The sample cell immediately changes to the selected color. The default is brown.
To change the background color of User-Modifiable cells:
1. Double-click the User-Modifiable cells label in the Feature column.
2. Select a color from the color palette that pops up and click OK.
238 Common TCM Procedures
The sample cell immediately changes to the selected color. The default is yellow.
To change the Screen Display font properties:
1. Double-click the Screen Display Fonts label in the Feature column. A dialog box appears.
2. Select one or more of the font types: Normal, Bold, Italic, or Title. Click OK.
3. Select the font properties from the Format Font dialog box that appears.
The table is immediately updated to reflect the changes.
To change the Screen Printer Font properties:
1. Double-click the Screen Printer Fonts label in the Feature column. A dialog box appears.
2. Select one or more of the font types: Normal, Bold, Italic, or Title. Click OK.
3. Select the font properties from the Format Font dialog box that appears.
The table is immediately updated to reflect the changes.
To restore the default properties:
1. Click the Set Defaults button at the top right corner of the screen.
2. Select the feature that has to be set to the default.
Downloading Performance Data Samples
To create models using TCM, the sample performance data must be collected from the NonStop
host system using Measure and formatted by MeasTCM. Once the sample performance data has
been summarized by MeasTCM in a CSV file, you need to download it from the host to the
workstation and load it into TCM.
To download performance data samples to the PC, follow the download procedure you normally
use in Windows. All CSV files for the same application or set of applications should be kept in the
same folder. TCM detects any truncated data and issues an error message.
NOTE:
All CSV files must have the extension .CSV.
Finding Product Version Information
You can use the Excel macro VPROC.XLM to get the product version of any TCM file. VPROC.XLM
is included in your TCM folder.
To find product version information:
1. Run VPROC.XLM.
2. Enter the name of the file.
3. VPROC responds with the product version of TCM.
4. Click OK button.
Generating a Timeline Chart
To generate a Timeline Chart:
1. Open a Performance model.
2. Select Options > Calculate Now to update the Performance model data.
3. Select Chart > Create Timeline Chart. The Timeline Chart dialog box appears.
4. Select transaction to chart and click OK. The Timeline Plot dialog box appears.
The host response time and the throughput data from the Planning Timeline model are then
plotted on the screen and show sample Planning Timeline Model charts.
Downloading Performance Data Samples 239
Getting Help for Function Keys
To get help for function keys either:
•
Select Help > Function Keys for help on commands available with the function keys.
•
Press the Shift key and the F1 function key simultaneously for a list of TCM function keys and
their meanings.
240 Common TCM Procedures
Getting Help for Specific Fields
TCM offers online, context-sensitive help messages that provide information on any field in the WA
model or Performance model.
To get help for specific fields:
1. Select the field about which you want more information. Either:
2.
3.
4.
•
Position the cursor on that field with the cursor keys.
•
Use the mouse to point to that field and click the left mouse button.
Select help. Either:
•
Select Help > TCM Help.
•
Press the F1 function key.
Use the cursor keys or the scroll bar on the right side of the message window to scroll through
long messages.
When you are finished, close the Help window by selecting File > Exit.
Loading a CSV Sample Into a WA Model
To load a CSV sample into a WA model:
1. Open a WA model.
2. Select Update > Load Category Data.
The Load Category Data dialog box appears.
3.
Do one of:
•
Type the name of the desired CSV file or files in the CSV file or files to Load field and
click OK to load the file.
•
4.
5.
Select the Display List of CSV Files checkbox and click OK to see a list of available CSV
files.
If you chose to view a list of CSV files, the Load Selected Category Data dialog box appears.
Either:
•
Enter a file name in the CSV file or files to Load field.
•
Select a file name from the CSV Files list.
Click OK.
TCM loads the selected CSV file.
Loading Models Created by Other Users
If you want to load a TCM model created by another user, or you have renamed your distribution
or custom folder, you should not open the Workload Apportionment model (.WWA file) or the
performance model (.WPM file) as you would normally do.
Because the .WWA and WPM files are pointer files containing path names, these files become
invalid when folder names or paths change. To open a model after such a change, be sure to use
the .SWA or .SPM files the first time. Once you open a .SWA or .SPM file, its new .WWA or
.WPM file is created and you can once again work with the pointer files. Other workspace files,
such as .HST or .AWA files, can be opened as part of your normal session activities and require
no special handling.
To load a TCM model created by another user or in another folder:
1. From the “TCM Initial Menu” (page 67), select Work with an Existing WA Model or Work
with an Existing Performance Model and then click OK.
The Open PM Model or Open WA Model dialog box appears.
2.
If you want to view all possible Workload Apportionment models, type *.SWA in the Model
to Open field. Type *.SPM to view all possible Performance models.
Getting Help for Specific Fields
241
3.
4.
5.
Select a file from the list or enter the file name you want to open, including its .SWA or .SPM
extension.
Click OK. TCM loads the model file (rather than the Excel workspace file).
Select File > Save to resave the model.
Merging Performance Models
As a TCM administrator or super user, you can also merge two Performance models into one model
or add transactions from one Performance model to another Performance model. This approach
is useful for modeling the impact of combining two applications in a single system. The models
you are merging must have the same version and the same VPROC date.
To merge Performance models:
1. Select Work with an Existing Model from the “TCM Initial Menu” (page 67) and click OK.
The Open PM Model dialog box appears.
2.
Select the model to open and click OK.
The selected Performance model opens.
3.
Log on as a TCM administrator or super user. For more information about this step, see
“Changing Authorization Levels” (page 70).
Select Update > Merge Model. The Merge Performance Models dialog box appears.
From the list, select the model to merge with the current Performance model.
To work with a different Performance model than the one that is currently open:
a. Click Cancel to dismiss the Merge Performance Models dialog box.
b. Select File > Close.
c. Select TCM Initial > Work with an Existing Performance Model and open the desired
model.
Accept the default name of merged model or type a new name (other than TCM.spm) in the
Name of the Merged Model field.
Click the All Transactions button to merge all transactions, or click the Selected Transaction
button to specify the transaction to merge. Then click OK.
If you select All Transactions, the Merge Configuration dialog box appears. Accept the defaults
or make any desired changes. Then click OK.
TCM merges the Performance models and displays the newly merged model.
If you chose Selected Transaction, the Merge Transaction List dialog box appears.
Specify the transaction to merge from the Merge Transaction list and click OK.
4.
5.
6.
7.
8.
9.
The Merge Configuration dialog box appears. Accept the defaults or make any desired
changes and then click OK.
TCM merges the Performance models and displays the Capacity Baseline–Plan of the merged
model.
For more information, see “Merge Performance Models” (page 169).
Modifying Apportioned Data Using an .AWA File in the Current Session
If you already have apportioned data but decide you want to modify the apportionment method,
you can modify the Apportionment Weights table of an existing model or replace it with a new
table. You must be a TCM administrator to modify apportioned data.
To modify apportioned data using an .AWA file that is in your current session:
1. Open a WA model.
2. Make sure you are logged on as an administrator or super user.
3. Select Find > Apportionment Weights.
If you have more than one .AWA file in the current session, the Find Apportionment Tables
dialog box displays the available files.
4.
Select the desired .AWA file, and then click Find.
242 Common TCM Procedures
5.
Select Options > Unprotect Admin Fields.
Cells whose values can be changed appear in blue.
6.
7.
Enter all changes into the table.
Select Options > Calculate Now (F12) to update the table.
TCM recalculates values based on your changes.
8. Select Options > Protect Admin Fields.
For more information, see “Apportionment Tables” (page 72).
Modifying Apportioned Data Using an .AWA File Not in the Current
Session
If you already have apportioned data but decide you want to modify the apportionment method,
you can modify the Apportionment Weights table of an existing model or replace it with a new
table. The procedure for modifying the Apportionment Weights table of an existing model depends
on whether the .AWA file is in your current session.
If you do not need to modify the .AWA file:
If the .AWA file you want is not in your session and you do not need to modify the .AWA file, to
load the .AWA file and apportion the data according to the .AWA file you selected:
1. Make sure you are logged on as an administrator or superuser.
2. Select Update > Workload Apportionment. The Workload Apportionment dialog box displays
two options:
3.
4.
5.
6.
•
Create Default Apportionment Tables
•
Change Current Apportionment Tables
Choose Change Current Apportionment Tables.
Accept the default apportionment table provided by TCM or choose an apportionment table
from the To: pull down list.
Click OK.
TCM loads the apportionment table into your session.
Select Calculate Now (F12) from the Options tab.
TCM apportions the data according to the table you selected.
For more information, see “Apportionment Tables” (page 72).
If you need to modify the .AWA file:
If the .AWA file is not in your session and you also need to modify the .AWA file:
1. Make sure you are logged on as an administrator or superuser.
2. Select Update > Workload Apportionment. The Workload Apportionment dialog box displays
two options:
3.
4.
5.
6.
•
Create Default Apportionment Tables
•
Change Current Apportionment Tables
Click Change Current Apportionment Tables.
Accept the default apportionment table provided by TCM or select an apportionment table
from the To: list.
Click OK.
TCM loads the apportionment table into your session.
Modify the Apportionment Weights table:
a. Select Options > Unprotect Admin Fields. Cells whose values can be changed appear in
blue.
b. Enter all changes.
Modifying Apportioned Data Using an .AWA File Not in the Current Session 243
c.
Select Options > Calculate Now (F12). TCM apportions the database according to the
table you select.
d. Select Options > Protect Admin Fields.
7. To save the modified .AWA file, select Save or Save As from the File tab.
For more information, see “Apportionment Tables” (page 72).
Modifying the Percentile Response Times
TCM can provide the following results for OLTP transactions: average, 90th, 95th, or 99th percentile.
The default is average. If you change from the default (average) to percentile response times, TCM
uses percentile response time for OLTP transactions in all screens of the Performance model.
For example, if the response time is 1 second and average response time is selected, the average
response time of transactions is 1 second. If 90th percentile is selected, 90 percent of the transactions
have a response time of less than or equal to 1 second.
To change to a different response time method:
1. Open a Performance model.
2. Select Options > Select Response Time Method. The Select Response Time Method dialog box
appears.
3. Select the desired response time method. (Average is the default.) Click OK.
4. A Microsoft Excel dialog box confirms the change. Click OK. Close the confirmation dialog
box.
Modifying the Planning Unit
Often a capacity planner needs to model transaction throughputs in units other than transactions
per second (TPS). The planning unit for throughput can be changed by entering another value in
the Planning Unit field on the Capacity Baseline—Actual screen. You can model transactions in
seconds, minutes, hours, days, or months.
To modify the planning unit:
1. Select the highlighted Planning Unit field on the Capacity Baseline—Actual screen.
2. Enter the new unit of time (sec, min, hour, day, month) and press the Return key.
3. Select Options > Calculate Now (F9). To finish entering your data, you must press Return before
clicking Calculate Now or pressing a function key.
Modifying the Transaction Count Table
The Transaction Count table tells TCM how to map category message counts to transaction counts.
In many cases, you can derive the number of messages sent or received by a process category or
some combination of categories.
NOTE: You can use a Transaction Count file instead of a Transaction Count table to count
transactions processed by your application. For information on the Transaction Count file, see
“Transaction Count Table Versus Transaction Count File” (page 121).
If you are using a Transaction Count file, all entries in the Transaction Count table can be zero
(0).
To modify the Transaction Count table:
1. Open a WA model.
2. Log on as an administrator or super user. For more information about this step, see “Changing
Authorization Levels” (page 70).
3. Select Find > Transaction Count Table. If this menu item is unavailable, select Options > Calculate
Now (F12) to update the table and then select Find > Transaction Count Table.
4. Choose Options > Unprotect Admin Fields to unprotect the Transaction Count Table so you
can change its entries. (They are normally protected against modification.)
5. Change the entries in the Transaction Count table to best reflect your application’s
characteristics.
244 Common TCM Procedures
6.
When you are done, select Options > Protect Admin Fields to protect the apportionment tables.
Although this step is optional, it is good practice because it safeguards your data from
unintentional corruption.
7. Select Options > Calculate Now (F12) to update the table.
8. If you want to save the file, choose Save or Save As from the File tab.
For more information, see “Modifying the Transaction Count Table” (page 78).
Modifying the Workload Apportionment Weights Table
The default Apportionment Weights tables created by TCM provide an excellent starting point for
fine tuning the WA model to your application’s particular architecture. However, to customize the
WA model to best reflect an application’s characteristics, the TCM administrator might need to
modify these tables. The tables also need to be modified if you want to experiment with more than
one apportionment method for your application or change an existing apportionment method due
to changes in the application’s architecture.
The procedure for modifying a model’s apportionment tables is the same whether you are modifying
the default tables of a new model or the tables of an existing model.
To modify the Workload Apportionment Weights table:
1. Open a WA model.
2. Log on as an administrator or super user
3. Select Find > Apportionment Weights. If this menu item is unavailable, select Options > Calculate
Now (F12) to update the table then select Find > Apportionment Weights. The Workload
Apportionment Weights table appears.
4. Select Options > Unprotect Admin Fields to unprotect the Workload Apportionment Weights
table so you can change its entries. (They are normally protected against modification.)
TCM highlights the fields that you can modify.
5.
6.
7.
8.
Change the entries in the Apportionment Weights table to best reflect your application’s
characteristics. These entries indicate the relative weights to be assigned to transactions when
the CPU and disk seconds process categories are apportioned.
When you are done, select Options > Protect Admin Fields to protect the apportionment tables.
Although this step is optional, it is good practice because it safeguards your data from
unintentional corruption.
Select Options > Calculate Now (F12) to update the table.
If you want to save the file, select Save or Save As from the File tab.
Moving Between Screens
To move between screens within TCM, select the name of the screen you want to view from the
Find menu, or select from the Screen tabs at the bottom.
Picking the Best CSV Sample and Loading It Into the Performance Model
You can have TCM Expert pick the most representative CSV file and load it into the Performance
model.
To pick the best CSV sample and load it into the Performance model:
1. From the “TCM Initial Menu” (page 67), select TCM Expert and click OK.
The Specify Custom Directory dialog box appears.
2.
Specify the custom folder location of your CSV files.
Select the custom folder of your CSV files and double-click the custom folder name. When you
double-click the name, TCM updates this name in the custom folder field of the dialog box
and also makes this folder the location of your working session.
3.
4.
Click OK to close the dialog.
Select TCM Expert > Pick Best CSV Sample.
The Pick Best CSV Sample dialog box appears.
Modifying the Workload Apportionment Weights Table 245
5.
Select the capacity history file from which to select the CSV sample and click OK.
TCM Expert picks the best CSV sample.
6.
To load this CSV sample into the Performance model, click Create.
TCM loads the CSV sample into the Performance model and displays the Capacity Baseline
Plan for the CSV sample. You are now in the Performance model and have left TCM Expert.
For more information, see Chapter 10: “Using TCM Expert”Section 10, Using TCM Expert.
Printing a Chart
TCM creates charts in color. Before printing a chart, check that you have updated the Performance
Model data by selecting Options > Calculate Now (F9).
To print a chart:
1. Create a chart of the Planning Timeline model.
2. Update the Performance model data by selecting Options > Calculate Now (F9).
3. Activate the chart to be printed by selecting the Find menu or the tabs at the bottom of the
window.
4. Once the chart appears on the screen, select Print > Print.
Returning to TCM From a Chart
To return to TCM from a chart, select the screen name you want to view.
Running MeasTCM
Once you have edited the control file, MeasTCM has the information it needs to summarize the
specified Measure data and create the CSV files for downloading to TCM on the workstation.
To process the data, run MeasTCM. The length of time processing takes depends on the amount
of Measure data being summarized, the number of process categories defined, and the priority
given.
During run time, MeasTCM creates these files:
•
If you specify a report to be made, an intermediate file might be created if FastSort needs
one. This file is automatically deleted when processing is finished.
•
The CSV files required by TCM.
To run MeasTCM:
1. Set the optional EXECUTION-LOG parameter:
1> [ PARAM EXECUTION-LOG { HP-file-name } ]
{ define-file }
The EXECUTION-LOG parameter must be set when you run MeasTCM with the NOWAIT
option. (See Step 2.) The parameter value controls the destination of the MeasTCM
informational messages and messages issued by the COBOL85 runtime library routines. If
there is no EXECUTION-LOG parameter, messages are sent to the home terminal.
2.
Run MeasTCM by entering the following command. This example assumes that MeasTCM is
installed in the $SYSTEM.SYSTEM subvolume.
2> MEASTCM [ / NOWAIT / ] cntlfile
cntlfile is the name of your control file.
If MeasTCM is not installed in the $SYSTEM. SYSTEM subvolume, specify RUN and enter the
fully qualified file name of the MEASTCM program:
2> RUN $DATA.ATTG.MEASTCM [ / NOWAIT / ] cntlfile
For detailed information about MeasTCM syntax, see “MeasTCM Syntax” (page 62).
246 Common TCM Procedures
Saving Apportionment Tables
If you do not save the apportionment tables, they are automatically saved when you save the entire
model. However, it is recommended that you save the tables as soon as they are created.
The Save As command allows you to change the name of the apportionment tables. The Save
command does not. You will probably want to change the name of the tables if you are modifying
the tables of an existing model rather than simply modifying the default tables of a new model.
To save Apportionment Tables with their existing names:
1. Select File > Save.
2. The TCM Save dialog box appears. Select the desired option and click Continue.
•
Select Workload Apportionment Model files to save everything that is open in this session.
•
Select Apportionment Tables to save the apportionment tables. This option is available
only when apportionment tables are open in the current session.
•
Select Capacity History to save the capacity history file. This option is available only when
a capacity history file is open in the current session.
3. TCM saves the files.
For more information, see “Saving the Tables” (page 79).
To save Apportionment Tables with a different name:
1. Select File > Save As.
2. The TCM Save As dialog box appears. Select the appropriate option and click Continue.
•
Select Workload Apportionment Model files to save everything that is open in this session.
•
Select Apportionment Tables to save the apportionment tables. This option is available
only when apportionment tables are open in the current session.
•
3.
Select Capacity History to save the capacity history file. This option is available only when
capacity history files are open in the current session.
In the TCM Save As dialog box, enter a new name to replace the default name displayed
and then click Yes.
Default file names contain the first eight characters of the name of your application, or model,
with an .AWA extension. The file is saved with an .AWA extension in your folder. For example,
in the tutorial’s Example application, the apportionment tables file is named EXAMPLE.AWA.
4. TCM saves the files.
For more information, see “Saving the Tables” (page 79).
Saving a Performance Model
You can save a Performance model with the same name or a different name.
To save the Performance model with its existing name:
1. Select Save or Save As from the File tab.
A dialog box containing a list of files in the Excel session appears.
2.
To save the model in a location other than the TCM custom directory, click the Browse button
next to the Performance Model name.
Ensure that the check box next to the Browse button of the Performance model is checked.
Click the Save button to save the model.
To save the Performance model with a different name:
Saving Apportionment Tables 247
1.
Choose Save or Save As from the File tab.
A dialog box containing a list of files in the Excel session appears. Type a new name (other
than TCM.SPM) for the model.
2.
To save the model in a location other than the TCM custom directory, click the Browse button
next to the Performance Model name.
Ensure that the check box next to the Performance Model name is checked. Click the Save
button to save the Model under the different name.
NOTE: Any Timeline Charts created in the TCM session are saved as a part of the Performance
Model.
Saving a Workload Apportionment Model
Saving a model involves saving the apportionment tables and formulas so that the model can be
used as a template for apportioning additional performance samples. Create a new model whenever
the apportionment method has been customized for a specific application (or set of applications)
for the first time or changed for an existing model.
The Save As menu item allows you to change the name of the model; the Save menu item does
not.
To save a Workload Apportionment model with its existing name:
1. Select File > Save.
2. The TCM Save dialog box appears. Select the desired option and click Continue.
•
Select Workload Apportionment Model files to save everything that is open in this session.
•
Select Apportionment Tables to save the apportionment tables. This option is available
only when apportionment tables are open in the current session.
•
3.
4.
To
1.
2.
Select Capacity History to save the capacity history file. This option is available only when
a capacity history file is open in the current session.
TCM saves the files.
To exit the WA model, select File > Exit.
save a Workload Apportionment model with a different name:
Choose File > Save.
The TCM Save As dialog box appears. Select the appropriate option and click Continue.
•
Select Workload Apportionment Model files to save everything that is open in this session.
•
Select Apportionment Tables to save the apportionment tables. This option is available
only when apportionment tables are open in the current session.
•
3.
4.
5.
Select Capacity History to save the capacity history file. This option is available only when
capacity history files are open in the current session.
In the TCM Save As dialog box, enter a new name to replace the default name displayed in
the dialog box and then click Yes.
Default file names contain the first eight characters of the name of your application or new
apportionment tables file with a .WWA extension. The file is saved with a .WWA extension
in your folder. For example, in the tutorial’s Example application, the model file is named
EXAMPLE.WWA. The WA spreadsheet is saved in a file with an .SWA extension.
TCM saves the files.
To exit the WA model, select File > Exit.
Sorting Capacity History Data
The Sort History command sorts the Capacity History data by transaction name or by sample name.
It is available only when there is a Capacity History (.HST) file in the current session.
To sort Capacity History data:
248 Common TCM Procedures
1.
2.
Select History > Sort History.
When the Sort History dialog box appears, click the button next to the desired sort method:
•
To see how much a transaction varies by sample, select Sort by Transaction.
•
To see a chronological list of data, select Sort by Sample.
3. Click OK.
You can click the Help button in the Sort History dialog box for online help about the Sort History
dialog box.
Uncalibrating Batch Response Time
To reverse the calibration process and revert to the TCM predicted response times, select the
Uncalibrate Transaction option.
To uncalibrate batch response time:
1. Open a Performance model.
2. Select Update > Calibrate Batch Response Time. The Calibrate Batch Response Time dialog
box appears.
3. Check the Uncalibrate Transaction checkbox.
4. Click OK.
TCM reverses the calibration process and reverts to the TCM predicted response times.
For more information, see “Calibrating Batch Response Time” (page 105).
Updating the Capacity History Database
Once you have created a WA model, update the Capacity History database so you can track
your apportionment methods and samples.
To update the capacity history database, select History > Update History.
For more information, see “Updating the Capacity History Database” (page 81).
Updating the Capacity History Database With Selected CSV Files
If you want to update the Capacity History database with a single CSV file, select Workload
Apportionment History > Update History.
The Update Capacity History with Selected CSV Files command is available so that you can update
capacity history with several samples using any Apportionment Weights table (whether TCM Expert
generated it automatically or you generated it manually). If you use TCM Expert to generate the
Apportionment Weights table, TCM Expert automatically updates capacity history and using this
option is not needed.
To update capacity history with selected CSV files:
1. Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box appears.
2.
3.
Specify a custom folder and click OK.
Select TCM Expert > Update History With Selected CSV Files.
The Update History With Selected CSV Files dialog box appears. By default, CSV files that
have not yet been used to update capacity history appear in the Selected CSV Files list.
4.
5.
6.
7.
Select a capacity history database from the History Database list.
Select an apportionment table from the Apportionment Table list.
To get information on a specific CSV file, select the CSV file name and click CSV Info.
To select a CSV file, select a file name in the Unselected CSV Files field and then click Add.
The file name appears in the Selected CSV File list.
Uncalibrating Batch Response Time 249
8.
9.
To clear a CSV file, select the file name in the Selected CSV File list and click Remove. The
filename appears in the Unselected CSV File list.
Click Update History.
TCM Expert updates capacity history and shows the updated file.
If TCM Expert finds inconsistent transaction costs in the capacity history, it reports this
information to you in a dialog box.
Using Online Help
TCM offers online, context-sensitive help messages that provide information on any field in the WA
model or Performance model.
To use online help:
1. Select the field about which you want more information. Either:
2.
3.
4.
•
Position the cursor on that field with the cursor keys.
•
Use the mouse to point to that field and left-click.
To select help either:
•
Select Help > TCM Help.
•
Press the F1 function key.
Use the cursor keys or the scroll bar on the right side of the message window to scroll long
messages.
When you are finished, close the Help window by selecting File > Exit in the Help window
or clicking outside the Help window.
Using TCM Expert to Generate an Apportionment Weights Table for CSV
Files
To use TCM Expert to generate an Apportionment Weights Table for CSV files:
1. Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box appears.
2.
3.
Select a custom folder and click OK.
Select TCM Expert > Generate Expert Apportionment Weights.
If you are at the capacity planner authorization level, TCM displays the TCM password dialog
box. Log on as an administrator or superuser. Enter the TCM administrator or superuser
password. (The defaults are “admin” and “super” respectively.) Click OK.
The Generate Expert Apportionment Weights dialog box appears.
From this dialog box, you can:
a. Select or enter the name of the capacity history that is updated automatically after the
weights are generated. The capacity history is created if it does not already exist.
b. Select a name for the source of the transaction counts by selecting an apportionment
table file. If you have transaction count files, TCM Expert automatically identifies them.
If transaction count files are present, they override a Transaction Count table if both are
present. If you do not have either a Transaction Count table or transaction count files,
you must create a default table. For more information, see “Creating a Default Transaction
Count Table and Workload Apportionment Weights Table” (page 182).
TCM Expert uses the name entered in the Apportionment Table file as the output for
placing its resulting apportioned weights. In the preceding example dialog box, DEMO
is both the name of the Transaction Count Table and the Apportionment Weights Table
(.AWA file).
If you are a TCM super user, the field Percent of Selected CSVs used to generate appears.
If you are not a TCM super user, this field is hidden. The default is 67 percent. This
percentage is the percent of CSV files randomly selected by TCM Expert to generate the
apportionment weights.
250 Common TCM Procedures
c.
d.
Select the CSV sample data files to be used by selecting the files and clicking either the
Remove or Add buttons. To select multiple files press the Shift or Control keys while clicking
the file names. Press the Shift key to select a contiguous set of file or files. Use the Control
key to add or remove a highlighted file.
If you want to get information about a CSV file before you decide whether to use it, select
the CSV file name and click the CSV Info button. The CSV Info dialog box appears.
The Number of Transactions field shows the total number of transactions of the type
selected in the Transaction field. The Transaction Mix field shows the percentage of
transactions in the CSV data of the transaction type selected in the Transaction field.
From this dialog box, you can also select a different transaction or Transaction Count
table. As you change the selected transaction or Transaction Count table, TCM updates
the information in the dialog box of your choice.
4.
Once you have completed the fields in the Generate Apportionment Weights dialog box, click
Generate.
TCM Expert generates an Apportionment Weights table and a confirmation dialog box
appears.
5.
Click OK or press Enter to close the confirmation dialog box.
•
If TCM Expert has too few CSV files, a dialog box reports this fact, and TCM Expert stops.
•
If TCM Expert does not have enough CSV files or has wrong transaction counts, a
transaction list shows the transactions that TCM Expert does not have consistent costs on.
•
If TCM Expert finds that the CSV files are not compatible with the .AWA files, an
incompatible CSV list dialog box appears.
•
If TCM Expert finds CSV files that are correlated, a linear relationship dialog box appears.
•
6.
If TCM Expert finds transactions that do not occur in any of your CSV files, TCM Expert
displays question marks (?) in the Apportionment Weights table and does not include
these transactions in its analysis.
Examine the Apportionment Weights table generated by TCM Expert.
To override TCM Expert’s calculations for any category marked with a Y:
a. Select Options > Unprotect Admin Fields. TCM makes modifiable fields available.
b. Type an N in the Expert Flag column of the category you want to override and enter the
values you believe are correct under the transaction columns.
c. Reprotect admin fields.
d. Go to Step 1 and generate again.
TCM automatically updates capacity history using the automatically generated Apportionment
Weights table.
Using the Consumption Model
The TCM Consumption model is used primarily to predict the number of CPUs and logical disk
volumes required for a given scenario. The capacity planner can specify any of the following
parameters:
•
Target online CPU utilization, disk utilization or both expressed in average percentages
•
Target online host response time in seconds (either average or percentile)
•
Target batch response time
•
Planned online throughputs in transactions per second, hour, day, or month
•
Planned CPU and disk type
•
Number of CPUs and/or logical disk volumes, or both
•
Planned number of transactions per task for batch transactions
To use the Consumption model:
Using the Consumption Model
251
1.
2.
Open a Performance model.
Select Consumption model. The Consumption model appears.
Actual data based on the workload-apportioned Measure data appears in the Actual column.
Default constraints appear in the Constraint column. The configuration recommended by TCM
appears in the Plan column.
3.
Enter constraints in the input fields in the Constraint column and other selected cells. Then
press Return.
After entering all the changes you want in the input fields, press Return and then select Options
> Calculate Now (F12). If you select Calculate Now before pressing Return, TCM displays the
Save As dialog box for you to save the new model.
TCM calculates all the values in the Plan column to support the given constraints.
4.
For more information, see “Using the Consumption Model” (page 91).
Using the Process Category Audit (PCAT) Report
You can use the Process Category Audit report to check the accuracy of the control file in
aggregating processes and discopen activity to process categories. If the aggregation does not
seem reasonable based on the report, review the PCAT statements in the control file and revise
the file if needed.
The report lists the processes aggregated into each process category as defined by the MeasTCM
control file. For each process, the report shows the number of CPU busy seconds and the number
of seconds the process was in the time boundaries set by the MeasTCM control file. In addition,
the report calculates the total CPU busy seconds for each process category.
Figure 13 (page 67) shows an excerpt of a sample Process Category Audit report. For more
information, see “Using the Process Category Audit Report” (page 63).
Using the Planning Timeline Model
The TCM Planning Timeline model is used to examine host response times and throughputs over
eight user-specified planning periods. Several growth scenarios can be specified, including:
•
Throughput growth rate for OLTP transactions (Rate column) starts from the second column.
The first column is the Actual for the Basic Sample Data for the Consumption model. The First
Plan Scenario (second column) can be either the Actual Sample Data of the Consumption
Model or the Plan Data of the Consumption Model, depending on the button at the top right
corner of the Planning Timeline screen.
•
Number of transactions per tasks growth rate for batch transactions (Rate column)
•
Number of CPUs and/or disks over time
•
CPU and disk type
You can display the results of the Planning Timeline model in a chart and print the chart. Default
behavior from the Planning Timeline line propagates to the right from column 2. You can define
behavior changes.
To use the Planning Timeline model:
1. Open a Performance model.
2. Select Find > Planning Timeline. The Planning Timeline model appears. Figure 26 (page 95)
shows a sample Planning Timeline model.
3. After entering all of the changes in the selected input fields, press Return and then select
Options > Calculate Now. You must press Return before selecting Calculate Now. TCM
calculates the values to reflect the changes.
For more information, see “Using the Planning Timeline Model” (page 92).
252 Common TCM Procedures
Viewing TCM Expert Parameters
1.
Select TCM Expert from the “TCM Initial Menu” (page 67).
The Specify Custom Directory dialog box opens.
2.
3.
Specify a custom folder and click OK.
Select Expert > TCM Expert Parameters.
The TCM Expert parameters appear.
Viewing TCM Expert Parameters 253
Glossary
accelerated mode
The operational environment in which Accelerator-generated RISC instructions execute.
application
A set of processes that execute an end-user business function on an HP NonStop system. These
processes are assigned to categories, and the application is given a name in the MeasTCM control
file.
Apportionment Weights table
A table that defines the way in which process category performance data should be apportioned
to transactions. This table is created and modified only by users with a TCM administrator or
super-user authorization level.
batch transaction
A workload that processes several transactions at once. Batch transactions have the following
characteristics: long job duration, low priority, significant disk activity, little or no terminal interaction,
and work within a closed system.
Capacity Baseline
A Performance model screen that summarizes the source data for the model. It shows each defined
transaction in terms of CPU, disk read, and disk write seconds.
Capacity History
A database used to archive and organize apportionment data from the WA model. Capacity
History is organized as a Microsoft Excel database and presents information that is useful to the
capacity planner for such tasks as apportionment validation, trend analysis, and selection of
representative samples.
Category Demand report
A Workload Apportionment (WA) model report that provides a summary of the performance data
for process categories as summarized by MeasTCM on the NonStop host system.
Consumption model
A component of the Performance model used to compute the number of CPUs and disks required
to accommodate one or more user-defined targets, including target host response time; target CPU,
disk utilization or both; planned throughputs; CPU device type; and disk configuration type (such
as audited and nonaudited). The Consumption model also computes utilizations, response times,
and maximum throughput given other specified constraints.
CPU conversion factors
A set of factors that represent the relative CPU speeds assumed for the application or set of
applications in the Performance model. The Performance model uses these factors when the planned
CPU type is different from the actual CPU type.
254 Glossary
custom folder
A folder where the performance data samples, custom models, and sample models for the
application or set of applications under study reside. It is recommended that a different custom
folder be established for each set of applications under study.
Disk Factors
A screen used to view disk model number, rotational speed (rpm), and controller.
distribution folder
The folder where the TCM distribution files are located.
Distribution model
The set of template files distributed with TCM and installed by the user. TCM custom models are
constructed using the Distribution model. The Distribution model is composed of the Distribution
WA model and the Distribution Performance model located in the distribution folder.
Expert
A feature that enables you to generate a workload apportionment weights table without detailed
knowledge of your applications. The Expert menu provides five options: generate Expert
apportionment weights, update history with selected CSV samples, create default transaction count
table, pick the best CSV sample, and view or modify Expert parameters.
MeasTCM
The interface between Measure on the NonStop host system and the capacity planning tool TCM
on the PC. MeasTCM runs under TACL on the NonStop host system, summarizes the performance
data collected by Measure, and formats this data for use by TCM.
MeasTCM control file
The MeasTCM file that defines the criteria for summarizing Measure processes into process
categories. Process category information is translated into transaction-oriented performance
information by TCM.
Measure
A performance monitoring product that runs on the operating system. You can use Measure to
collect and examine system performance data.
model
A group of files (typically in a custom folder) that contains a list of transaction names for a given
application, CPU seconds, disk seconds, and transactions per second for each named transaction.
model set
A group of WA models that use the same Apportionment Weights table and Transaction Count
table but have different CSV data.
native mode
See “TNS-R native mode” (page 256).
custom folder 255
online transaction
A workload that processes one transaction at a time, as opposed to a batch transaction, which
processes several transactions at once.
performance data sample
Performance information collected on the NonStop host system for a particular application or set
of applications to be modeled. Performance data is collected using Measure, summarized using
MeasTCM, and then downloaded to the PC. TCM uses the raw performance data as input to its
modeling process.
Planning Timeline model
A component of the Performance model used to examine transaction rates and host response times
over six user-specified planning intervals.
PM model
The Performance model component of TCM. The Performance model is used to answer questions
regarding baseline data that has already been apportioned in the WA model. The Performance
model is composed of three submodels: the Consumption model and the Planning Timeline model.
process category
Summarized performance data for any collection of the CPU, Process, Disk, and Discopen Measure
entities as defined in the MeasTCM process category control file.
query transaction
A transaction that is modeled as a batch or online transaction, depending on the CPU demand of
the query transaction. Large demand queries are modeled as batch. Small demand queries are
modeled as OLTP.
TCM
The Tandem Capacity Model; the name of the entire workstation-based capacity planning tool.
TCM requires Microsoft Excel and Windows to run, but Excel and Windows are not considered
part of TCM.
TCM parameters
A screen in the Workload Apportionment (WA) model and the Performance model used to set
various parameters.
TNS mode
The operational environment in which TNS instructions execute.
TNS-R native mode
The operational environment in which native-compiled RISC instructions execute.
Transaction Count file
A file used instead of the Transaction Count table. This feature is useful if you know how many
transactions are processed by your application. For example, you might be able to create a simple
program to parse your application’s statistics or log file to determine the number of transactions
processed by your application. Alternately, you can use Measure user-defined counters to determine
the number of transactions processed by your application. You can create the file on the NonStop
256 Glossary
host system and download the file to the custom folder, or you can create the file directly on the
PC.
Transaction Count table
A table that defines how TCM should calculate the number of transactions from process category
performance data. The table specifies how to compute the number of transactions from the number
of messages process categories that receive, send, or both. This table is created and modified only
by users with a TCM administrator or superuser authorization level.
WA model
The Workload Apportionment component of TCM. The WA model is used to apportion process
category performance data (as collected on the NonStop host system using MeasTCM) into
transaction-oriented performance data. Data apportioned by the WA model can be loaded into
the Performance model for making capacity planning projections.
workload apportionment
The allocation of the CPU and disk read and write seconds, consumed by process categories, to
transactions.
Workload Summary
A Workload Apportionment (WA) model screen that summarizes the results of workload
apportionment and displays the CPU and disk seconds for each transaction. It also indicates the
fixed consumption per second.
Transaction Count table 257
Index
Symbols
# Commits per Txn field, 150
# CPUs and CPU Type field, 146
# Disks and Disk Type field, 147
# Tasks field, 111, 112, 114
# Txns field, 111, 112, 114
#Txns field, 148
#Txns per Task field, 115, 141
.AWA file extension, 72
A
Actual Baseline Detail by Category screen, 155
ACTUALDISK42 entry
control file, 51
ACTUALDISK43 entry
control file, 52
ACTUALDISK44 entry
control file, 52
ACTUALDISK50 entry
control file, 52
ACTUALDISK51 entry
control file, 52
ACTUALDISK52 entry
control file, 53
ACTUALDISK53 entry
control file, 53
additional WA models
creating, 236
administrators
TCM user, 20
analysis
what-if, 23
APPL entry
control file, 41
application entry
control file, 41
Application field, 108, 124, 140, 159
applications
deleting, 96
apportioned data
modifying, 242
apportionment
methods, 23
model results, 80
Apportionment field, 110, 112, 114, 140
apportionment formulas
checking, 235
apportionment method
checking, 83
apportionment metiod
non-Pathway example, 84
apportionment model
creating additional models, 83
saving, 248
updating history, 83
258 Index
apportionment tables
.AWA file extension, 72
defined, 72
saving, 79, 247
Apportionment Weights Table, 107, 183
Apportionment Weights table, 181
modifying, 245
apportionment weights table, 72
modifying, 77
App’t field, 125, 159
architecture, 19
assumptions, 19
Audit Disk Configuration field, 150
audit report
MeasTCM, 63
Audit Write Ceiling field, 150
authorization level
changing, 233
authorization levels
changing, 70
for users, 69
Avg Batch Resp Time field, 143, 147
Avg Online Resp Time field, 143, 147
Avg Online Util field, 143
Avg Resp Time field, 145
B
baseline
defined, 23
Baseline Detail by Category Actual screen, 138
Baseline Detail by Category Plan screen, 138
batch models, 31
batch response time
calibrate, 105
calibrating, 233
uncalibrate, 106
batch transaction
assumptions, 97
examples, 99
mixed workload, 97
modeling, 97
modeling differences, 100
priorities, 97
running process categories, 97
system resources, 97
tasks, 101
types, 98
C
Calculate Batch response times field, 149
Capacity Baseline Actual screen, 137
Capacity Baseline—Actual screen, 88, 139
of merged model, 171
capacity history
analyzing, 232
capacity history data
sorting, 248
Capacity History Database, 138
Capacity History database, 84
updating, 81, 249
Capacity History Database screen, 158
Capacity History Mix Chart screen, 160
Capacity History MixChart, 138
Capacity History screen, 107, 124
Capacity History screens, 158
Capacity History Trend Charts screen, 160
Capacity History TrendChart, 138
capacity planners
TCM user, 20
capacity planning process
description, 21
Cat Name field, 109, 118, 119, 155, 157
category 98 (_OTHER)
checking, 236
category 98 (other)
control file, 63
Category Demand Report, 107
Category Demand Report screen, 108
Category File field, 108
Chart History command, 125
Charts, 138
charts
printing, 246
CNTLFILE see process category control file
components, 19
MeasTCM, 29
Consumption model
predicting scenarios, 251
usage, 91
Consumption Model screen, 104, 137, 141
control file
ACTUALDISK42 entry, 51
ACTUALDISK43 entry, 52
ACTUALDISK44 entry, 52
ACTUALDISK50 entry, 52
ACTUALDISK51 entry, 52
ACTUALDISK52 entry, 53
ACTUALDISK53 entry, 53
APPL entry, 41
category 98 (other), 63
CNTLFILE, 33
CONVERTTO entry, 41
CPUFACTOR entry, 42
CSVDATA entry, 44
CSVLO and CSVHI entries, 40
customizing, 33
DISKCONVERTTO entry, 45
DISKFACTOR entry, 47
environmental entries, 40
example RUN command, 62
format, 40
MEASURE entry, 40
NUMCSVS entry, 44
NUMTMFTRAIL entry, 45
OTHER category, 63
process category (PCAT) statements, 54
REPORT entry, 44
SSDDISKFACTOR entry, 46
template, 33
TITLE statements, 59
CONVERTTO entry
control file, 41
CPU
batch, 102
tunability, 103
utilization thresholds, 102
CPU Config field, 110, 115
CPU Conversion Factors screen, 138
CPU Factors screen, 150
CPU Sec and DP CPU Sec Tables field, 156, 158
CPU Sec field, 141
CPU Seconds field, 144, 158
CPU Seconds Per Transaction field, 156
CPU Seconds per Transaction field, 111
CPU Workload Apportionment screen, 109
CPUFACTOR entry
control file, 42
CPUs field, 140
CSV file, 29
CSV files
creating, 61
CSV sample
loading, 241
CSV sample data
requirements, 180
CSVDATA entry
control file, 44
CSVLO and CSVHI entries
control file, 40
D
data source
Performance model, 138
Workload Apportionment (WA) model, 107
data splitting, 180
Default Growth Rate field, 146
Default Transaction Count table
creating, 182
demonstrate option
WA model, 68
disk
process category type, 60
utilization thresholds, 102
Disk Config field, 111, 113, 115, 140, 142
Disk Factors screen, 137, 151
Disk Model field, 142
Disk process, 109
Disk Process Apportionment Factors field, 116
Disk Process Priority Queuing field, 123
Disk Read Workload Apportionment screen, 111
Disk Sec field, 141
Disk Seconds field, 145
Disk Write Cache field, 140, 142, 147
Disk Write Workload Apportionment screen, 113
259
DISKCONVERTTO entry
control file, 45
DISKFACTOR entry
control file, 47
Disks field, 140
Display Scratch Areas, 141
E
error messages, 192
EXECUTION-LOG parameter
MeasTCM, 61
Expert Flag field, 118, 120
Expert option, 69
F
features, 18
fields
getting help, 241
file defaults, 60
file structure, 66
files
CNTLFILE, 33
transaction count, 75
Fixed CPU Sec Actual/Plan field, 158
Fixed CPU Sec field, 156
Fixed CPU Seconds field, 110
Fixed process, 109
Fixed Read Sec field, 112
Fixed Write Sec field, 113
function keys
getting help, 240
G
Generate TCM Expert Apportionment Weights dialog box,
181, 183
getting started, 65
global parameters
changing, 234
Guardian Performance Analyzer (GPA), 22
H
hardware utilization thresholds
for CPU and disk, 102
help messages, 250
customizing, 238
History Data field, 125, 159
History File Name field, 116
I
Incompatible CSV List dialog box, 185
individual process category priorities
changing, 235
Initial Menu, 67
installing
MeasTCM, 26
TCM, 25
Interrupts field, 108
260 Index
L
Line-handler process, 109
M
Maximum CPU Utilization field, 149
Maximum Disk Utilization field, 149
maximum transactions for modeling, 121
MeasTCM
batch transaction guidelines, 100
components and architecture, 29
description, 29
features, 29
files, 29
OSS pathnames support, 29
running, 61, 246
syntax, 62
TXN keyword, 100
usage, 30
Measure, 22
configuring, 30
entities, 29
intervals, 30
multiple samples, 30
multiple sessions and HP nodes, 29
performance data, 29
process category type, 60
samples, 30
MEASURE entry
control file, 40
Mix chart, 126
mix chart
creating, 237
Mix field, 115, 125, 159
models
batch, 31
converting, 27
loading, 28
merging, 242
online, 31
WA reasonable check, 32
models created by others
loading, 241
multiple category matches, resolving, 58
N
NonStop SQL/MP, 19
Number field, 142
number of batch CPUs, 102
Number of Batch CPUs field, 149
NUMCSVS entry
control file, 44
NUMTMFTRAIL entry
control file, 45
O
online help
customizing, 71
for function keys, 71
for specific field, 71
how to access, 65
online models, 31
order of parameters
process category statements, 58
OSS
process category type, 60
OTHER category
control file, 63
P
passwords
changing, 235
PCAT statements, 54
percentile response times
modifying, 91, 244
performance data
downloading, 76
loading, 76
loading samples, 77
Measure, 29
Performance Model
About option, 179
Add Category option, 174
Add Similar Transaction option, 173
Add Transaction option, 172
Calculate Now option, 177
Change Authorization Level option, 177
Change Display Fonts option, 174
Change Password option, 178
Change Printer Fonts option, 177
Chart tab, 178
Create Timeline Chart option, 178
Customize option, 178
Customize TCM option, 178
Delete Category option, 174
Delete Transaction option, 174
Display gridlines option, 174
Display menu, 174
Display Scratch Areas option, 174
Function Keys option, 178
Help tab, 178
Narrow Column option, 175
Notepad option, 177
Options tab, 177
Page Setup option, 176
Print option, 175
Printer Setup option, 177
Remove gridlines option, 174
Select Response Time Method option, 177
Show Headings option, 174
Show Value option, 174
Undo Entry option, 177
Widen Column option, 175
Zoom option, 174
Performance model
answer what-if questions, 69
batch parameters, 101
components, 137
create new, 69
creating, 87, 237
data source, 138
Demonstrate option, 69
loading baseline data, 87
process category priorities, 123
saving, 96, 247
work with existing, 69
performance model
defined, 19
Performance model charts, 162
Performance Model ribbons
Calibrate Batch Response Time, 168
Close, 164
Exit TCM, 165
File, 164
Find, 165
Load Baseline Data, 165
Merge Performance Models, 169
Open, 164
Refresh Formulas, 166
Return to the TCM Initial tab, 164
Save/Save As, 164
Timeline Trends, 167
Update, 165
Performance model screen
Baseline Detail by Category Actual, 138
Baseline Detail by Category Plan, 138
Capacity Baseline Actual, 137
Capacity History Database, 138
Capacity History MixChart, 138
Capacity History TrendChart, 138
Charts, 138
Consumption Model, 137
CPU Conversion Factors, 138
Disk Factors, 137
Planning Timeline, 137
TCM Parameters, 138
TCM User Customization, 138
performance samples
collecting, 22
number required, 22
Physical Disks field, 140
Plan Baseline Detail by Category screen, 103, 156
Planning Dates field, 146
Planning Timeline model
examining host response times, 252
usage, 92
Planning Timeline Model chart
batch transaction, 163
online transaction, 163
Planning Timeline Model screen, 105
Planning Timeline model screen, 145
Planning Timeline screen, 137
planning unit
modifying, 90, 244
Planning Unit field, 140
Priority field, 117, 123, 156, 158
process category
defined, 31
261
example, 58
process category (PCAT) statements, 54
wild card, 57
Process Category Audit report
checking accuracy of control file, 252
MeasTCM, 63
process category priority
changing, 234
process category statements
order of parameters, 58
process category type
disk, 60
Measure, 60
OSS, 60
requester, 60
server, 60
SQLMP, 60
SQLMX, 60
system, 60
TITLE statements, 59
TMF, 60
process category types, 109, 117, 118
process flow diagram, 21
process flow diagrams
guidelines, 33
process pairs, 122
processor speed, 19
Processor Type and SW Release field, 142
Q
Query Transaction OLTP-> Batch Response Time CPU
Pathlength Threshold field, 116
Query Transaction OLTP-> Batch response times field, 150
R
Rate field, 148
Rcv and Sends field, 120
Read Seconds per Transaction field, 113
reasonableness check, 31
REPORT entry
control file, 44
requester
process category type, 60
Requester process, 109
resolving multiple category matches, 58
response time
uncalibrating, 249
Response Time Gamma Factor field, 150
response times
percentile, 91
ribbons, tabs and options, 65
RUN command
MeasTCM, 62
Run Summary Report
MeasTCM, 62
S
Sample Date field, 140, 143, 148
Sample File field, 140, 143
262 Index
samples
collecting, 22
downloading, 239
independent, 180
loading, 241
Measure, 30
number required, 31
picking and loading best CSV files, 187
picking the best, 245
varying transaction mixes, 180
screen
Apportionment Weights Table, 107
Baseline Detail by Category Actual, 138
Baseline Detail by Category Plan, 138
Capacity Baseline Actual, 137
Capacity History, 107
Capacity History Database, 138
Capacity History MixChart, 138
Capacity History TrendChart, 138
Category Demand Report, 107
Charts, 138
Consumption Model, 137
CPU Conversion Factors, 138
Disk Factors, 137
Planning Timeline, 137
TCM Parameters, 107, 138
TCM User Customization, 138
Transaction Count Table, 107
Workload Apportionment, 107
Workload Detail by Category, 107
Workload Summary, 107
screens
customizing, 238
navigating, 245
Search Criteria field, 124, 159
security features, 69
server
process category type, 60
Server process, 109
SQL applications
modeling, 19
SQLMP
process category type, 60
SQLMX
process category type, 60
SSDDISKFACTOR entry
control file, 46
step-by-step instructions, 231
super users
TCM user, 21
SW Release field, 140
synchronizing Measure samples, 30
system
process category type, 60
system configuration and application
analysis of, 21
system requirements, 25
T
TACL, 29
TCM
Expert option, 69
file structure, 66
getting started, 65
Initial Menu, 67
passwords, 70
security, 69
status, 65
user levels, 65
TCM description, 18
TCM Expert
Cache Miss Factor field, 135
Check History Over Last field, 135
CPU Pathlength Threshold field, 136
data splitting, 133
functions, 180
generating an Apportionment Weights Table for CSV
files, 250
getting started, 181
overriding calculations, 186
viewing and changing parameters, 188
viewing parameters, 253
Workload Apportionment Weights table, 133
TCM files
Excel 2003, 189
Excel 2007, 190
TCM Initial Menu, 87
TCM Parameters screen, 102, 107, 116, 138, 148
TCM procedures
common, 231
TCM User Customization screen, 138, 160
template
control file, 33
throughput trending
calculating, 233
Time Increment field, 146
Timeline Chart
generating, 94
printing, 96
timeline chart
generating, 239
TITLE statements, 59
category type, 59
TMF
process category type, 60
TMF Audit Trails field, 140
TMF process, 109
Total CPU Secs field, 155, 157
Total Online TPS field, 147
TPS (or TPH, TPD, or TPM) field, 141
TPS (TPM or TPH) field, 147
transaction
adding, 232
batch, 21
OLTP, 21
query, 21
transaction count
file format, 75
file naming conventions, 75
Transaction Count file
compute number of transactions, 121
file format, 121
naming conventions, 121
Transaction Count Table, 107
Transaction Count table, 86, 119, 121
modifying, 244
transaction count table
described, 75
example, 73
modifying, 78
Transaction field, 118
transactions
batch, 97, 99
deleting, 96
Trend chart, 126
creating, 237
tunability
CPU, 103
Tunable CPU field, 118, 120, 123, 156, 158
tuning your system, 22
TXN entries
control file, 60
Txn Name field, 110, 112, 114, 141, 144, 148
Txn per Sec (or Hour, Day, or Month) field, 144
Txn Type field, 155, 157
Txns per Task field, 144
Type field, 109, 117, 118, 119, 141, 156, 157
U
Unlabeled Column field, 141
unspecified data, 59
Update Capacity History with Selected CSV Files option,
186
Update Timeline Trend, 93
User-Supplied Transaction Names field, 118
users
TCM, 20
V
version
finding, 239
version of TCM
converting, 236
versions
finding with VPROC.XLAM, 27
softdoc for recent, 25
VPROC.XLAM, 27
W
WA model
reasonable check, 32
wild cards
process category (PCAT) statements, 57
workload apportionment, 18
see also apportionment
Workload Apportionment (WA) model
263
create new, 68
creating, 100, 237
customizing, 72
data source, 107
defined, 19
load CSV file, 100
major steps to create, 76
options, 68
saving, 82
work with existing, 68
Workload Apportionment (WA) model screen
Apportionment Weights Table, 107
Capacity History, 107
Category Demand Report, 107
TCM Parameters, 107
Transaction Count Table, 107
Workload Apportionment, 107
Workload Detail by Category, 107
Workload Summary, 107
Workload Apportionment ribbons
About option, 136
Calculate Now option, 132
Change Authorization Level option, 132
Change Display Fonts option, 129
Change Password option, 133
Change Printer Fonts option, 132
Chart History tab, 129
Close tab, 127
Create Default Transaction Count Table option, 134
Delete History tab, 128
Delete tab, 127
description, 126
Display (or Undisplay) scratch areas, 129
Display tab, 129
Enter Excel option, 133
Exit tab, 127
File tab, 126
Find tab, 127
Function Keys option, 136
Help tab, 136
History tab, 128
Load Category Data tab, 127
Notepad option, 132
Open tab, 126
Options tab, 132
Page Setup option, 131
Pick Best CSV Sample option, 135
Print tab, 130
Printer Setup option, 132
returning to TCM from Excel, 133
Save As tab, 126
Save tab, 126
Search History tab, 128
Show Value option, 129
Sort History tab, 129
TCM Expert Parameters option, 135
TCM Expert tab, 133
Undo Entry option, 132
Unprotect (Protect) Admin Fields option, 132
264 Index
Update History tab, 128
Update History With Selected CSVs option, 134
Update tab, 127
WA tab, 127
Workload Apportionment screens, 107
Workload Apportionment Weights table, 86, 117, 185
Workload Detail by Category screen, 107, 122
WA model, 101
Workload Summary screen, 107, 114
Write Seconds per Transaction field, 114

The Benefits of Traditional Chinese Medicine for Cosmetics

The Irish College of Traditional Chinese Medicine (ICTCM)

Attach Supporting Documents via TCM 09/15/2014

Clinic Article - Acupuncture.pages

Technology Centre Mongstad (TCM)

Download - PayDay Software Systems

TCM - WellCare

Jake Fratkin – Integrating Functional Medicine with a TCM Practice

TRICOR mass flow meter - KEM Küppers Elektromechanik GmbH

BACHELOR OF TRADITIONAL CHINESE MEDICINE (HONS)