Try TT Now

All Gateways

Operator ID

Overview

 

Many exchanges require identification of the trader responsible for submitting an order. To meet this requirement, TT Gateway 7.17 supports the use of an Operator ID for exchanges where trader identification is required on manually and/or automatically submitted order actions. If configured, the Operator ID is sent to the exchange instead of the TT Username.

 

To populate Operator IDs in the TT User Setup database after an upgrade to TT Gateway 7.17, refer to Using the Operator ID Assistant .

 
 

Exchanges Requiring Trader Identification

 

The following exchanges require trader identification on all submitted order actions:

 
    • CME
 
    • ICE
 
    • CFE
 
    • NYSE Liffe
 
    • NYSE Liffe US
 
    • MX
 
    • Eurex
 
    • BrokerTec
 
    • eSpeed
 
    • LSE
 
    • NASDQ OMX
 
    • NFX
 
 

TT Gateways Requiring an Operator ID

 

To meet the exchange requirement for identifying users, the following TT Gateways 7.17 (unless otherwise noted) require an Operator ID:

 
    • CME Gateway
 
    • ICE Gateway
 
    • CFE Gateway
 
    • NYSE Liffe Gateway
 
    • NYSE Liffe US Gateways 7.16.9 or higher
 
    • MX Gateway
 
    • Eurex Gateways 7.16.9 or higher
 
    • BrokerTec Gateway
 
    • eSpeed Gateway
 
    • LSE Gateway
 
    • NASDAQ OMX Gateway
 
    • NFX Gateway
 
 

Configuring Operator IDs

 

The Operator ID is configured on a per TT Username/per Member-Group-Trader ID/ per TT Gateway basis using TT User Setup 7.4.8 or higher.

 

In TT User Setup, you can configure the Operator ID field in the Gateway Logins window for a new or existing user, or the User’s Gateway Login Attributes shown below. An Operator ID must be configured for each exchange trader and TTORD trader gateway login for TT Gateways that require an Operator ID.

 
 
Note

The value configured as the Operator ID must be that of an exchange-provided trader/user ID or a user-defined ID that is registered at the exchange.

 
 
 

Configuring Operator IDs for ICE

 
 
Note

For ICE, clients running TT User Setup 7.17.60 will still be prompted to enter an Operator ID. If this is an issue, upgrade to 7.17.61 or later, which removes this requirement for ICE Gateway logins. If the Operator ID field is blank, Tag 116 will be automatically populated with Username|Username (i.e., the ’Username’ defined in TT User Setup).

 
 

In TT User Setup, Operator IDs for ICE Gateway logins must be configured in the following format: Direct Trader ID|Proxy Trader ID.

 
 
Note

Be sure to include the "|" character between the Direct Trader ID and Proxy Trader ID when configuring Operator IDs for ICE in TT User Setup. ICE requires this character in Tag 116 for order routing.

 
 

In the User’s Gateway Login Attributes window, Direct Trader IDs appear in the Exch Trader column, and trader IDs appear in the Trader column. These values will be the same for Direct Traders. Otherwise, the Trader column contains the Proxy (TTORD) Trader ID.

 

For example, if a user’s Exch Trader column is set to "01" and the Trader column for the user’s Proxy (TTORD) trader ID is set to "TT_TRADER44", the Operator ID field should be configured as "01|TT_TRADER44". Refer to the following example:

 

 

These TT trader ID values map to Tag 116 as follows: Direct Trader ID = Routing Trader ID (Tag 116 left); Proxy Trader ID = Authorized Trader ID (Tag 116 right).

 
 

Routing the Operator ID to the Exchange

 

When a user logs in to the TT Gateway and submits an order, the gateway maps the Operator ID to the required Exchange API message field to identify the user. All orders submitted by a user to the TT Gateway include the Operator ID(s) associated with their Username’s exchange trader/direct trader and TTORD gateway logins.

 

The following table shows the Operator ID-to-Exchange API mapping done by TT Gateways.

 
Operator ID-to-Exchange API Mapping
TT Gateway Requiring an Operator ID Operator ID configured in TT User Setup Exchange API field populated with the Operator ID
CME Trader ID FIX Tag 50
ICE Direct Trader ID|Proxy Trader ID (e.g., 01|TT_TRADER44) FIX Tag 116
CFE Trader ID FIX Tag 50
BVMF Desk or DMA Trader ID FIX Tag 448
NYSE Liffe Member ITM (Any optional user-defined value up to 16 characters) FIX Tag 526 (Secondary Client Order ID)
NYSE LIffe US Registered Trader ITM szTraderCardRef (Trader Card Reference)
MX Trader ID TraderId
Eurex User ID FIX Tag 50
BrokerTec Trader ID user_id_s field in the trading code structure
eSPeed Trader ID FIX Tag 50
LSE Trader ID TraderId
NASDAQ OMX SenderSubId (exchange-provided credential) FIX Tag 50
NFX SenderSubId (exchange-provided credential)|Authorized Trader ID (user-defined). The pipe "|" must be entered. Example: FIX8|aking FIX Tag 50 | Tag 448
Note: The "Trader ID" in the Operator ID column indicates the "T" of the exchange trader or TTORD trader gateway login (MGT).

Routing Rules

 

With the exception of Eurex and ICE (refer to ICE Routing Rules), TT Gateways populate the Exchange API field with one of the following values based on which value is received first from the client trading application:

 
    • SenderSubID (FIX Adapter Tag 50)
 
    • Operator ID for the Monitoring Username
 
    • Monitoring Username
 
    • Operator ID for the Username
 
    • Username
 
    • Exchange Trader ID
 

If an API originates an order, the CFE Gateway appends _API to the Operator ID or the Username. If an automated system submits the order, _ATSI is appended.

 

For Eurex, the Eurex Gateway downloads Operator IDs from TT User Setup at startup to login traders and route orders to the exchange’s new trading architecture. The gateway does not consume the Operator ID sent from the client trading applications.

 
 

ICE Routing Rules

 

The ICE Gateway populates Tag 116 with either the SenderSubID, Operator ID, or Username, but the rules vary based on whether an Operator ID is present on the order sent to the gateway.

 

If an Operator ID and SenderSubID are both present on an order action, the SenderSubID replaces the right side of the Operator ID when the gateway populates Tag 116 (see the following example).

 
  Example Operator ID and SenderSubID both present on an order  
 

SenderSubID=XYZ

 

Operator ID=ABC|DEF

 

Tag 116=ABC|XYZ

 

If only the Operator ID is present, it’s sent as Tag 116 (see the following example).

 
  Example Operator ID only  
 

SenderSubID=<empty>

 

Operator ID=ABC|DEF

 

Tag 116=ABC|DEF

 

If only the SenderSubID is present on the order (no Operator ID), the gateway sends it as the right side of Tag 116 along with the Username instead of the Operator ID as shown in the following example.

 
  Example SenderSubID only (No Operator ID)  
 

SenderSubID=XYZ

 

Username=JTRADER

 

Tag 116=JTRADER|XYZ

 

If neither the SenderSubID or Operator ID are present, the ICE Gateway populates both sides of Tag 116 with the Username as shown in the following example.

 
  Example No Operator ID or SenderSubID  
 

SenderSubID=<empty>

 

Username=JTRADER

 

Tag 116=JTRADER|JTRADER

 
 
 

Troubleshooting

 
 
Note

The "Operator ID" written in the TT Gateway Send_Recv logfiles and audit files indicates which value was sent to the exchange as a trader identifier, and is not necessarily the Operator ID configured in TT User Setup.

 
 

To troubleshoot suspected order routing errors due to a missing or incorrectly configured Operator ID:

 
    1. For CME, CFE, ICE, BVMF, and MX Gateways: go to the <root dir>ttlogfiles directory and open the latest send_recv logfile (e.g., CME-A_PROD_P16000_CME_send_recv_2014-02-18).

      In addition, you can also check the Operator ID column in the converted audit files for these TT Gateways.

       
 
    1. Refer to the following table to locate the message tag for the Operator ID routed to the exchange.
      Operator ID-to-Exchange API Mapping in Send_Recv logfile
      TT Gateway requiring an Operator ID Exchange API field populated with the Operator ID in the Send_Recv logfile
      CME 50=
      ICE 116=
      CFE 50=
      BVMF 448=
      MX (See Notes below)
      eSPeed 50=
      Notes:
        • For BVMF, the 448 tag is sent three times (Operator ID, Firm ID, Sender Location) per Send message. The first 448 tag on the Send line is the Operator ID.
       
        • MX displays the Operator ID in position 8-15 of the Send message, and position 30-37 of the Recv message.
       
 
    1. For NYSE LIffe, NYSE LIffe US, BrokerTec, and Eurex Gateways: go to <root drive>:ttauditfiles and run the audit_convert utility on a selected *.cba file. Open the converted file in Excel and check the Operator ID column.
 

Interpreting the Logfiles and Audit Files

 

In the Send_Recv logfiles and audit files, an "Operator ID" refers to one of the following values based on the gateway’s routing rules (refer to Routing Rules):

 
    • SubUserId
 
    • Operator ID of the Monitoring Username
 
    • Monitoring Username
 
    • Operator ID of the Username
 
    • Username
 
    • Exchange Trader ID
 
 

Examples: Operator ID in Send_Recv logfiles

 

Refer to the following examples when using the Send_Recv logfiles to identify what trader identifier was sent to the exchange.

 
  Example CME Gateway; Operator ID=P16x, Username=TRADER1  
 

| 18.02.2014 09:48:24.050 | 8=FIX.4.2� 9=00098 35=0� 49=P16000N� 56=CME 34=000005257 369=000005085 50=P16X� 52=20140218-15:48:24.050� 57=G� 142=US,IL� 10=233

 
  Example BVMF Gateway, no Operator ID configured, Username=TTB (DMA trader)  
 

Send | 19.02.2014 13:43:10.395 | 8=FIX.4.4 �9=00211�35=D� 49=TRTT17 �56=BVMF �34=000000777� 52=20140219-19:43:10.39 5�1=00102�581=39� 11=5O 38=10� 40=2 44=11.14 54=2� 55=DI1F15� 60=20140219-19:43:10.395 �453=3 448=TTB 447=D�4 52=36 448=188 447=D 452=7� 448=BVMF� 447=D 452=54� 10=078

 
  Example MX Gateway, Operator ID=0126EA1, Username=ABC  
 

Send | 07.02.2014 12:17:40.000 | OE1117400126EA1 000000010OO710LB000000014001500000...

 
 
 

Changing the Operator ID on Working Orders

 

Users can change the Operator ID on a selected parent or child working order using the Update User functionality in X_TRADER® 7.17. When the Update User button is selected, a request is sent to the TT Gateway to change the Operator ID associated with the order.

 

Depending on the exchange rules, the TT Gateway will either indicate the change in ownership of the working order immediately or wait for the next action to be performed (e.g., re-quote) before processing the change.

 

If it allows the update to go to the exchange, the TT Gateway does the following:

 
    • Updates the Monitoring Username field in X_TRADER and other client trading applications to display the Username of the trader (monitoring user) claiming the order.
 
    • Sends the Operator ID update to the exchange. Depending on the exchange rules, the TT Gateway may wait to send the Operator ID update to the exchange until it receives the next order action (e.g., re-quote) for the selected order.
 
    • When the exchange acknowledges the update, the gateway changes the Operator ID of working orders in X_TRADER and client trading applications to indicate that the monitoring user owns the order.
        • For orders submitted by an automated trading system (e.g., Synthetic SE), the Operator ID is changed for both the parent and child orders
       
        • For re-quotes or other subsequent order actions, these actions are sent to the exchange with the updated Operator ID.
       
 
    • If the change request is rejected by the TT Gateway, the Operator ID value remains the same; that is, it’s the Operator ID of the Username that originally submitted the order.
 

The Operator ID may also be changed when passing orders to another user for order monitoring. For more details about how order passing is supported in the TT system, refer to Order Passing Support, and refer to the X_TRADER Online Help.