Try TT Now

NYSE Liffe Gateway

Debugging Parameters

Overview

The following information can assist your TAM in diagnosing issues that may arise with the TT Gateway. You should only use the information below with the assistance of TT personnel.

Warning

The information in this section should only be used by your TAM or TT personnel to aid with diagnosing issues.

You can configure the TT Gateway to record all messages between the Order Server and the exchange. When properly configured, the TT Gateway creates a separate send and receive .dat file for each enabled Order Session. The files are added to the <root drive>:ttdatfile directory.

Note

Guardian can not automatically collect the enhanced send and receive log files. You must manually collect these files independent of all other log files.

Parameter

The enhanced send/receive logging uses the following parameter:

Debugging Parameter

Parameter

Description

LogSendReceive

Sets whether a particular Order Server creates enhanced send and receive log files. This parameter has two available values:

  • 0: The Order Server does not create enhanced send and receive log files.
  • 1: The Order Server creates enhanced send and receive log files.

To record all Order Sessions, add LogSendReceive=1 to the [OrderServer] section of the hostinfo.cfg file.

Warning

This parameter should be used by your TAM or TT personnel to aid with diagnosing issues.

Only enable this parameter with the assistance of TT personnel.

Recording Global versus Individual

When recording globally (i.e., setting LogSendReceive=1 in the [OrderServer] section), you can exclude a particular Order Session by setting LogSendReceive=0 in the [OrderServerSession_X] section.

In addition, you may record individual Order Sessions by setting LogSendReceive=1 to those [OrderServerSession_X] sections only.

Converting the logfiles

TAMs can convert the datfiles from binary to text format using the binlog_converter.exe tool. Use the following command to convert the .dat files:

binlog_converter.exe -f log.dat > log.txt

where log.dat equals the original file and log.txt equals the name of the converted file.

Resetting the Sequence Number

TAMs may use the following command line parameter to force a reset of the startup sequence number sent to the exchange:

orderserver.exe -r sessionName1=0;sessionName2=0

where sessionName equals the unique identifier (i.e., X) of the [OrderServerSession_X] listed in the hostinfo.cfg file.

Warning

The information in this section should only be used by your TAM or TT personnel to aid with diagnosing issues.

You may use the following values to populate teh LastSequenceNumber in the logon message to the exchange:

  • 0 = Replay every message previously sent by the Exchange
  • -1 = Do not replay any message but continue from the last known transmitted sequence plus one
  • N > 0 = Rewind to this number plus one and retransmit from that point up to the current sequence number

You may also use this command for all order sessions by not including the sessionName.

Example Resetting the Sequence Number

For example, if you have two sessions named [OrderServerSession_EQT] and [OrderServerSession_FIN], the following commands will reset the sequence number:

orderserver.exe -r EQT=0;FIN=0

-or-

orderserver.exe -r=0