1.4 Evaluating Transaction Size

Use Logdump's TRANSHIST command in conjunction with other Logdump commands to determine whether or not your applications generate large transactions and to identify their relative size. TRANSHIST causes Logdump to track the size of transactions contained in a trail file or extract file in an internal history table. The transactions are ranked in descending order of size, in bytes. When the history table is full, the smallest transaction is removed to allow a larger transaction to be added to the list.

To use statistics generated by TRANSHIST, issue the following series of commands in Logdump:

Use TRANSHIST to set the size of the history table that tracks transaction size. The maximum size is 200 bytes. A value of 0 turns off the tracking.
```
TRANSHIST n
```
Use either the TRANSRECLIMIT or TRANSBYTELIMIT command to set a lower boundary for what is considered a normal sized transaction. These commands prevent normal-sized transactions from being tracked. Eliminating normal-sized transactions reduces the amount of data that must be reviewed.
```
{TRANSBYTELIMIT n bytes | TRANSRECLIMIT n records}
```

Use Logdump's COUNT command to display the statistics on transaction size, which appear at the end of the output and look like the following excerpt:

Transactions with at least 100 records or 100000 bytes
2011/02/01 09:31:24.000.000    00:00:00.000, Seq 0, RBA 13101
   Bytes/Trans .....    1168167
   Records/Trans ...       1001
   Files/Trans .....          1
2011/02/01 09:31:35.000.000    00:00:11.000, Seq 0, RBA 1205292
   Bytes/Trans .....    1168167
   Records/Trans ...       1001
   Files/Trans .....          1

Logdump scans the file(s) and reports the information.

Use Logdump's POSITION RBA command to go to each RBA listed in the COUNT output to find out the name of the table that generated the transaction. You can group these tables into their own processing group so that they do not affect processing of other tables that generate normal sized transactions.