Tandem Capacity Model (TCM) Manual

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
online transaction 255