Performing File Maintenance with TT Clean
About TT Clean
The TT FIX Adapter installs with a utility called ttclean.exe, which you can use to automatically maintain, delete, or archive files such as the TT FIX Adapter log files. The configuration file for TT Clean is located in <root_drive>:ttconfigttclean.ini. For more details on managing this utility, refer to the TT Gateways SAM Version 7.X.
Generated log files
TT FIX Adapter (and other TT processes) generate log files in the <root_drive>:ttlogfiles directory that record significant events and activities. Because these can get quite large, TT recommends that you delete or archive all log files in this directory that are more than ten days old.
TT FIX Adapter message storage
To manage order, fill, price, and fix message storage, the TT FIX Adapter uses the following .dat files (located in the ttdatfiles directory). You should delete .DAT files only if TT personnel instruct you to do so:
- FIX Adapter Dat Files (which are named Nameadapter-#.dat, where Name is the name you assigned the TT FIX Adapter and # is an integer between one and four).
- Order Session FIX logs (which are named <FIX Adapter Name>OrderSendRecv(<Order
Session Connection LocalCompId>-<FIX Client Name>)_<YYYY-MM-DD>.dat).
These logs are created for each session; the Enable debug logging
for orders setting in TT User Setup is ignored.
Caution: The order session FIX .dat file is used to service FIX client resend requests and historical fill requests. Make sure that TT Clean is not configured to delete or archive .dat files that are less than three days old or the duration of their FIX session, whichever is greater.
- Price Session FIX logs (which are named <FIX Adapter Name>PriceSendRecv(<Price Session Connection LocalCompId>-<FIX Client Name>)_<YYYY-MM-DD>.dat). These logs are created for each session; the Enable debug logging for orders setting in TT User Setup is ignored.
When TT FIX Adapter restarts after deleting the .DAT files, FIX clients must:
- Reconnect with Tag 34 (MsgSeqNum) equal to 1, because TT FIX Adapter's knowledge of any session state was erased.
- Be prepared to handle receiving duplicate fills, because the TT FIX Adapter's knowledge of the last fill ID sent to any FIX client was erased.