Tandem Capacity Model (TCM) Manual

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.
158 The Performance Model