A Customer TTSTATS file, normally named using the TapeTrack Customer-ID, contains the statistics extracted from the TapeTrack Journal for a selected billing period.

Example filename:

US01.ttstats

The file is created by TMSS10LogStatsExtractDB and processed by TMSS10LogStatsProcess.

The TTSTATS file provides the operational quantities used to calculate billing items, including storage and movement activity. It does not contain the complete billing configuration. Customer descriptions, package assignments, rates, rounding and other calculations are supplied separately by the Customer Description Map, Package Map and Billing Rules.

The Customer TTSTATS file transfers customer activity from the TapeTrack Journal into the billing calculation process. Each Customer-ID has its own ttstats file, containing statistics for all activity within the set date range.

The Customer TTSTATS file is created by TMSS10LogStatsExtractDB. This utility reads the TapeTrack Journal database and creates an extract file for each Customer containing activity within the selected date range.

For example, an extraction containing the following Customers may create:

TTSTATS files should be generated from the Journal for the correct billing period. Reusing a file from another period may result in missing, duplicated or incorrect charges.

TTSTATS files can be stored in any directory accessible to the account running the billing process. For ease of administration, it is recommended that each billing period has a separate input directory.

Example Windows location:

C:\Program Files\TapeTrack\TapeTrack Framework Server\var\billing\2026-07\US01.ttstats

Example Linux location:

/var/tapetrack/billing/2026-07/US01.ttstats

A billing directory may be arranged as:

billing
├── config
│   ├── customer_map.txt
│   ├── package_map.txt
│   ├── default.ttsdef
│   └── tapetrack.xslt
├── input
│   ├── US01.ttstats
│   └── US02.ttstats
└── output
    ├── Billing_US01.xml
    └── Billing_US02.xml

The location of the TTSTATS file is supplied to TMSS10LogStatsProcess using the -i argument.

A TTSTATS file is a TapeTrack statistics extract generated from Journal activity.

The file may contain statistical records relating to:

• Storage quantities.
• Onsite and offsite activity.
• Volume movements.
• Deliveries and collections.
• Repository activity.
• Other operational events recorded in the Journal.

The exact records included depend on:

• The Customer being extracted.
• The selected date range.
• The Journal activity for that period.
• The installed TapeTrack version.
• The statistics processed by the Billing Rules.

Record Types are:

• C : TapeTrack Customer-ID
• I : Inventory Total of Media-ID
• S : Storage Total - Number of Media in that Repository
• H : High Water Mark
• M : Volume Movement to the Repository ( to Repository-ID:from Repository-ID)

US01.ttstats

CUS01
ILTO 20260816000446000015
SLTO LIBR20260816000425000015
HLTO LIBR20260816000000000015
MLTO OFFSLIBR20260816000003000010
SLTO OFFS20260816000018000015
HLTO OFFS20260816000277000015
SLTO SCRA20260816000003000015
HLTO SCRA20260816000000000015
MLTO LIBRSCRA20260816000000000010
ILTO 20260817000446000016
SLTO LIBR20260817000425000016
HLTO LIBR20260817000000000016
MLTO OFFSLIBR20260817000000000011
SLTO OFFS20260817000018000016
HLTO OFFS20260817000277000016
SLTO SCRA20260817000003000016
HLTO SCRA20260817000000000016
MLTO LIBRSCRA20260817000000000011
ILTO 00000000000446000017
SLTO LIBR00000000007300000017
HLTO LIBR00000000000000000017
MLTO OFFSLIBR00000000000016000012
SLTO OFFS00000000000236000017
HLTO OFFS00000000000277000017
SLTO SCRA00000000000046000017
HLTO SCRA00000000000000000017
MLTO LIBRSCRA00000000000001000012

Breakdown of record data: ILTO 20260816000446000015

I Inventory LTO Media type 20260816 Date YYYYMMDD 000446 Inventory 000015 Inventory record count

Breakdown of record data: MLTO LIBRSCRA20260816000003000010

M Movement LTO Media type LIBR To repository OFFS From repository Date 000003 Movement count 000010 Movement record count

TTSTATS files are generated processing files and should not normally be edited manually.

Manual changes can cause:

• Activity to be omitted.
• Quantities to be altered.
• Charges to be duplicated.
• Invalid statistics records.
• A loss of traceability to the Journal.
• Billing results that cannot be reproduced.

If the contents appear incorrect:

1. Confirm the extraction date range.
2. Review the Journal activity.
3. Correct the source data or extraction settings where appropriate.
4. Run TMSS10LogStatsExtractDB again.
5. Replace the incorrect extract with the newly generated file.
6. Reprocess the billing XML.

Check that:

• TMSS10LogStatsExtractDB completed successfully.
• The Customer had Journal activity during the selected date range.
• The output directory exists.
• The extraction account has permission to write to the output directory.
• The expected Customer-ID was included in the extraction.
• The file was not moved or archived after extraction.

Confirm that:

• The correct billing date range was selected.
• Journal records exist for the Customer.
• The correct Journal database was processed.
• The Customer-ID is correct.
• The Customer had billable activity during the period.

An empty file may be valid when the Customer had no relevant activity. It should be investigated before being excluded from billing.

Check that:

• The extraction date range is correct.
• The Journal contains the expected activity.
• The correct TTSTATS file was processed.
• The Billing Rules select the intended statistics.
• Rounding or minimum-quantity rules are being applied correctly.
• The same TTSTATS file was not processed more than once.

The raw activity may be correct while the billed quantity differs because of a Billing Rule.

For example:

Confirm that:

• The TTSTATS file was processed only once.
• The billing XML was imported into QuickBooks only once.
• The selected extraction date range does not overlap another billing period.
• Duplicate Billing Rules are not matching the same statistics.
• Previously processed files are moved to an archive directory.

• Generate a new TTSTATS file for every billing period.
• Do not manually edit generated TTSTATS files.
• Restrict write access to authorized billing administrators.
• Archive completed billing files as read-only records if required.

A TTSTATS file does not normally contain passwords or authentication details. However, it may contain Customer activity and commercially sensitive operational statistics.

Access should therefore be restricted to:

• TapeTrack administrators.
• Authorized billing staff.
• The service account running TMSS10LogStatsExtractDB.
• The service account running TMSS10LogStatsProcess.

The file should not be publicly accessible or stored in an unsecured shared directory.

• TMSS10LogStatsProcess
• Customer-ID
• Customer Description Map
• Package Map
• Billing Rules
• TapeTrack XML Stylesheet
• Billing Process
• Billing XML
• XMLQuickBooks Mapping