Tandem Capacity Model (TCM) Manual

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 100) shows the Workload Apportionment screen for the Demo model included
with TCM.
Differences in Modeling Batch Transactions 99