MB TradingFIX 6.2.6

MB Trading 1926 East Maple Avenue 1st Floor

El Segundo, CA 90245-3001

Reference Number Version 6.2.6 Last Updated 05/01/11

Table of ContentsGENERAL..................................................................................................................................................4

MBTFIX Gateway Introduction .............................................4 Connection ..............................................................4 DROP COPY Offering ......................................................5 Hours of Operation ......................................................5 Destinations ............................................................6 Client Trading Platform .................................................6 Additional Documentation ................................................6 Alerts ..................................................................6 Certification ...........................................................6

TRADING INFORMATION....................................................................................................................7 Order Types .............................................................7 GTC Orders ..............................................................7 Suspended/Pending Order Status ..........................................7 Stop Orders .............................................................7 Forex Trading ...........................................................8 Plus Orders .............................................................8 TTO Order ...............................................................8 Multi-Leg Option Orders .................................................8 Option Orders ...........................................................8 Order Group Tag .........................................................9 Trade Breaks ............................................................9 Orders via Client Trading Platform ......................................9

FIX SESSION MESSAGING.................................................................................................................10 Basic Session Information ..............................................10 Standard Header ........................................................11 Log On .................................................................11 Resend Request .........................................................12 Administrative Reject Message ..........................................12 Log Out ................................................................13 Heartbeat ..............................................................13 Test Request ...........................................................13

CLIENT/INBOUND APPLICATION MESSAGES............................................................................14 Pre-Trade Messages .....................................................14 Trading Session Status Request .....................................14 Trading Messages .......................................................15 New Order Single Request ...........................................15 Cancel Request .....................................................18 Cancel/Replace Request .............................................18 New Order – Multi-Leg ..............................................19

Order Mass Status Request ..........................................20 Post Trade Messages ....................................................20 Collateral Request (Balance Request) ..............................21 Request for Positions .............................................21SERVER/OUTBOUND APPLICATION MESSAGES.......................................................................22

Pre-Trade Messages ....................................................22 Trading Session Status ............................................22 News Message ......................................................22 Trading Messages ......................................................23 Business Message Reject ...........................................23 Order Cancel Reject ...............................................23 Execution Report ..................................................24 Post Trade Messages ...................................................27 Collateral Report .................................................27 Collateral Inquiry Acknowledgment .................................27 Position Report ...................................................28 Request for Position Acknowledgment ...............................29APPENDIX A – ORDER FORMATTING GRID................................................................................30

APPENDIX B – EXAMPLE FIX MESSAGES....................................................................................32 Logon Request .....................................................32 Logon Response ....................................................32 Trading Session Status ............................................32 Collateral Request ................................................32 Position Request ..................................................32 New Order-Single and Responses ....................................33 New Order – Cancel Request ........................................33

APPENDIX C – MBT FIX GATEWAY SYMBOLOGY....................................................................34APPENDIX D – PROPRIETARY DEFINED FIELDS.......................................................................36APPENDIX E – XML DATA .................................................................................................................37APPENDIX F – TESTING IN DEMO ..................................................................................................37

GENERAL

MBT FIX Gateway Introduction

This document details the expected and supported fields used when connecting to the MBT FIX Server. MBT FIX follows the standards defined in the FIX 4.4 protocol. FIX supports: Trading messages for order placement, management, and post trading messages for account balance and position information. Post trading messages can query for a snapshot or snapshot & subscribe, to receive real time updates. Client requests accepted are:

Trading – New Order – Single, Cancel Request, Cancel/Replace Request Post Trading – Collateral Request (for Balance Information), Position RequestPre Trade – Trading Session Status Request

This document assumes the reader understands the FIX 4.4 (and earlier) protocol available at http://www.fixprotocol.org/. This document is intended to ensure that a firm’s FIX client, constructed according to the FIX 4.4 protocol, will be compatible with the FIX Host on the ambiguous details of the FIX Specification.

This document is broken down into specific sections; General information for the FIX client, specific advanced trading information and FIX messages by FIX category: General session level messaging, Client inbound request and server outbound request by pre-trade, post-trade and trade messaging.

MB Trading refers collectively to Manhattan Beach Trading Financial Services, Inc. (“MBTFS”) and MB Trading Futures, Inc. (“MBTF”). Securities products are offered though MBTFS, a member of FINRA and the Securities Investor Protection Corporation (“SIPC”). MBTF, a CFTC registered FCM and member of the NFA, offers execution and settlement services for futures based products, as well as off-exchange foreign currency (Forex) products.

Connection

MBT FIX Gateway accepts TCP/IP SSL connections. Data will be accepted and transmitted, as per the FIX protocol, along this connection. You may request via e-mail a demo FIX connection to mbtfix@mbtrading.com for your development and testing. A production IP/Port pair, along with a SenderCompID and TargetCompID, will be assigned to the connecting firm after testing and certification has been completed. It is required that all connections established through us over the internet are SSL. If you have a direct line established with us we can setup a plain text port. There is a free production tunnel which can easily be used to do the SSL encryption.

MBT FIX Gateway Special Offering – DROP COPY

MB Trading FIX users can request connections to receive duplicate execution reports, through MB Trading's special 'DROP COPY' via an alternative server connection. The Drop Copy service is available by subscribing through our FIX connection for a copy of all executions done in your account(s). These orders may also be placed through other MB Trading systems, such as: MBT Desktop, MBT Desktop Pro, MBT Mobile. FIX users interested in setting up 'DROP COPY' connections, are to e-mail mbtfix@mbtrading.com providing their request.

Hours of Operation

Equities (orders not restricted to these hours):Options (trading during core session only):

Session 1 (pre-market) - 7:30AM EST through 9:30AM ESTSession 2 (core session) - 9:30AM EST through 4:00PM ESTSession 3 (post-market) - 4:00PM EST through 8:00PM EST

FOREX :

Sunday 5:00PM EST through Friday 5:00PM EST. There will be a pause daily for rollover/server maintenance between 5:00PM and 5:05PM EST.

NOTE: FIX users may elect to have their MBT FIX server maintenance at either 5:00PM EST or 12:00 AM EST. Please communicate with your FIX Support Representative to submit your preferred server maintenance time.

Futures :

CBOT: 11:55PM EST to 12:30AM EST CME: 11:55PM EST to 12:30AM EST (Please check out website for the most current updated times)

FIX Support Hours:Monday through Friday – 7:30AM to 4:00PM EST

Contact Information:Phone: (866) 628-3001Email: mbtfix@mbtrading.com

Destinations

The MBT FIX Gateway Server will use a proprietary routing algorithm to direct order messages. Direct ECN connections are also available upon request.

Client Trading Platform

Execution Reports are returned on all orders received through the MBT FIX Gateway, as well as any order placed through the client trading platform on any specific SenderCompId’s linked accounts. It is highly suggested that FIX clients use the client trading platform during their demo testing as it can be used to validate all orders being sent to the account through the MBT FIX Gateway.

Additional Documentation

Additional FIX documentation would include our Third Party Software Provider Implementation Guide and Sample FIX Messages. Please contact your MBT FIX Support Representative to receive copies of the above documentation.

Alerts

Alerts that clients may receive in their client trading platform are also available through the MBT FIX connection. These are sent via the NEWS message. These news alerts will inform the client to specific system critical issues. As of this version, alerts have been added as a required support tool for our MBT FIX certification.

Certification

All MBT FIX clients must complete certification before obtaining a live production connection. If the client has tested the demo environment efficiently and all information is supported properly, then this should take no longer than one hour. Certification will be done over the phone with a MBT FIX Support Representative. It will confirm that your connection successfully handles Session Level situations; including multiple resend instances, effectively receives news alerts and ensures that all order types have been formatted correctly. If the client does not plan to support certain order types that are offered, it may be noted at this time. Pre-trade and post-trade messages are not requirements of the certification.

Trading Information

This section provides more detail regarding specific MB Trading features that are important for all MBT FIX users to understand.

- Order Types

MBT FIX Gateway supports all of the MB Trading’s order types: Market, Limit, Stops, Trailing Stop, Orders on Time, Cancel and Close, Conditional Trigger Orders (CTO), Threshold Triggered Orders (TTO) and Plus orders. Also included, when supported by product type, are Reserve, Pegged, and Pegged plus offset orders. The Trading Messaging section define all FIX tags required for New Order and New Order Multi-leg Requests. Appendix A provides a chart specifying which FIX tags are necessary for each order type.

- GTC Orders

All GTC orders require that the ClOrdID remain the same throughout the life of the order. MB Trading GTC orders are currently good for 60 days (90 for Forex) from the initial order placement. The expiration time of that order is provided in the new order acknowledgment. GTC orders are restated to the client daily via FIX Execution Reports; included with the pending acknowledgment, ExecType will be sent to clients upon their initial daily log on for all prior day’s GTC orders. Also, if there had been any partial fills on an order, an Execution Report restating the partial fills will be sent each day after the initial pending acknowledgment. The ExecType of this rollover partial fill is specified as D (Restated). Once each GTC hits its applicable market start time for the day, another Execution Report (New) will be sent on the order to confirm it is Live for that day.

- Suspended/Pending Order Status

Suspended/Pending Order Status is used with every GTC order. It is possible, though rare, that they may be provided on a Day order as well. An order status of Suspended means that your order is currently held by our system, however, not Live at the market. An order status of Resume means your order has been sent to the market, and is typically followed by an order status of Live. It is up to the MBT FIX user’s discretion as to whether they would like to display these states to their client.

- Stop Orders

There are two different triggers for stop orders we support: Default and Trade Through (applicable to Options and Forex only). An MBT FIX user can specify this type via the ExecInst tag 18. The default setting in the client trading platform is the Default stop method. In order to specify a Trade Through, set the ExecInst tag 18 to w.

- Forex Trading

Forex orders require the currency pairs be specified in the symbol and defined by base-currency / cross-currency formatting, i.e. EUR/USD, USD/JPY, EUR/CHF. Forex orders support a Time In Force (TIF) of GTC and IOC. See Appendix C for more details on symbology.

- Plus Orders

The MBT FIX Plus Order types allow you, when entering an order, to specify an order to close the position. This order will trigger and be automatically placed by the system when any part of the opening order executes.

- TTO Order

This is our proprietary Threshold Triggered Order. The user may enter a price above the market and a price below the market as part of one single order. Once one of those prices has hit, a market order is sent for execution. This is similar to what is known as an One Cancels the Other (OCO) order.

- Multi-Leg Option Orders

The New Order – Multi-Leg Request is supported for certain advanced options strategies. The MBT FIX Gateway does not support any change requests on multi-leg orders. The options root symbol, required in the leg symbol tag, is the same as the ticker symbol. , i.e. Option symbol: +SPY-100930C113.00 (Call SPY September 10 30), the options root is: SPY. Multi-leg orders are posted to the market where they are eligible for execution; if the multi-leg order is not a valid strategy in the market it will be rejected. Multi-leg orders may be canceled using the standard Cancel Request. Executions on multi-leg orders will be reported back to the client with individual Execution Reports per each leg, identifying the leg by LegRefID tag 654.

- Options Orders

Closing Options orders, FIX new order message to MBT FIX Gateway; Sell should only be used when that new order is closing a position of the same option's symbol. Options order for writing, covered calls and CSEP Cash Secured equity puts, etc., is to be sent to MBT FIX Gateway as a sell short.

- Order Group Tag

Clients may use this tag to facilitate the grouping of orders together on their end. This tag will be returned with all execution reports per each order that it was specified on.

- Trade Breaks

Trade breaks seen in the client trading platform are also returned to the FIX client. The ExecType of trade breaks is H (Trade Cancel).

- Orders via Client Trading Platform

MBT FIX clients will receive execution reports on all orders of the accounts that are linked to their SenderCompID. For example, if an order is entered via the client trading platform, an execution report is returned through the MBT FIX Gateway. Pending acknowledgments are the first messages returned to clients on orders not received through the MBT FIX Gateway, i.e. client trading platform orders, and plus orders that have triggered. The ClOrdID on these orders will be set by the system. All subsequent execution reports on these orders will contain this ClOrdID. Your MBT FIX connection can then send a cancel or cancel/replace on that order.

FIX Session Messaging

Basic Session Information

An MBT FIX Gateway session is created once a FIX logon message is received and validated. A logon is required each day to activate the session for each customer. The sequence number used in the daily logon must be equal to 1; if any other number is received the session will not be opened. It assumes a 30 second heartbeat interval; as per the FIX Specification, a heartbeat will only be sent if a message has not been received or sent within a 30 second period.

The FIX ResetSeqNumFlag (Tag 141) is supported. A FIX client may set this tag to =Y on a new logon and FIX sequence numbers will be reset for both sides. According to FIX Specs we recommend only using this in cases of emergency.

The server will only accept requests from a client after it has sent the Trading Session Status message. Any application level requests received by the server before the Trading Session Status message has been sent will be rejected.

MBT FIX Gateway will reset inbound and outbound numbers to 1 at a designated time daily. Standard reset is 12AM EST. Upon request, a 5PM EST sequence number reset time is available and recommended for a Forex FIX client. Although FIX 4.4 supports 24-hour connections, we do not implement the FIX 4.4 24-hour connections. The client will be disconnected from the server at the designated reset time. The client may also set the ResetSeqNumFlag field to =Y in order to force the sequence number reset on this initial log on.

All messages are validated before the message is handled. Validations include: the sequence number (must be the next expected number), the body length (the message length must equal the body length specified in the message), and fields sent (each message must include all fields detailed below). If a message does not pass these validations, the server will reject the message using an Administrative Reject message containing a text field with the reason it was rejected. This message will not increment the incoming sequence number. Thus, if the next message received is out of sequence, the MBT FIX Gateway will send a resend request to recover the lost messages.

All messages must contain the Standard Header defined below. Header fields are not detailed in each specific message definition; it is assumed the standard header is included.

Standard Header

Tag FIXFieldName Required Description8 BeginString Y FIX.4.4 - Identifies beginning of new message and protocol version.9 BodyLength Y Message length, forward to the checksum field35 MsgType Y Defined in each message description49 SenderCompID Y Assigned value used to identify the firm sending the message56 TargetCompID Y Provided to the customer by MB Trading 34 MsgSeqNum Y Integer message sequence number - should not be repeated52 SendingTime Y Time of message transmission (expressed in UTC)

43 PossDupFlag N

Indicates possible retransmission of message with this sequence number. Valid values: Y = Possible duplicate; N = Original transmission

116 OnBehalfOfSubID N

May be used to send a Sub-Account. Assigned value used to identify specific message originator (i.e. trader) if the message was delivered by a third party.

129 DeliverToSubID N May be used to specify broker MPID142 SenderLocationID N Used on certain collateral request to specify IP of end user.

10 CheckSum Y

Three byte, simple checksum. Always last field in message; i.e. serves with the trailing, as the end-of-message delimiter. Always defined as three characters. (Always unencrypted)

Log On

The log on message must be the first message you send after establishing a TCP connection with the MBT FIX Gateway. Your firm must wait for a log on acknowledgment from the MBT FIX Gateway before sending any other messages. If a FIX session is disconnected and reconnects again, the log on you will receive may have a higher sequence number than expected. It is critical that your client detects this condition and issues a resend request to retrieve any missed executions. If the initial log on response is out of sequence the server will reply with a resend request to the client. This must be responded to before the client sends any resend requests. This is done in order to avoid an endless loop situation.

If a log on message is sent to MBT FIX with an invalid password, then MBT FIX will return a log off message (35=5) providing the text tag 58 reason: Bad Logon Password. Other bad log on attempts, will result in MBT FIX disconnecting the user.

Tag FIXFieldName Required Description35 MsgType Y Type: A98 EncryptMethod Y Value = 0. No encryption108 HeartBtInt Y Number of seconds between heartbeats - should be 30

141 ResetSeqNumFlag NOptional; client may use if they cannot recover old seqno - they start the seqno with one, set this flag to =Y and server will reset seqno to 1

347 MessageEncoding Y Value = 554_H1 (required with hashed password)554 Password Y A password is required in your log on message for additional

security. This field should be hashed according to SHA-256. (ASCII string of 64 hex digits)

Resend Request

All resend requests sent by the client will be processed appropriately, re-transmitting any missed application level messages. Gap Fill sequence messages will be sent in place of missed Administrative messages. The client must check for dupes of any resent executions in their system. As detailed in the session information, upon log on the client must respond (with tag 35=4) to an the MBT FIX Gateway resend request first before issuing their own resend request.

Tag FIXFieldName Required Description35 MsgType Y Type: 27 BeginSeqNo Y The beginning sequence number to be resent16 EndSeqNo Y The last sequence number to be resent

Administrative Reject Message

All administrative reject messages will include the sequence number of the message that is rejected, and whenever possible a text field indicating the reason for the rejection. It is strongly recommended that your firm keep a record of all reject messages and NOT resend them. Additional reject examples can be obtained from your MBT FIX Support Representative. In compliance with the FIX specifications, any messages your firm rejects will not be resent.

Tag FIXFieldName Required Description35 MsgType Y Type: 345 RefSeqNum Y Reference message sequence number of rejected message.

58 Text Y

Possible values: "duped ClOrderID" = a duplicate ClOrderID was sent - ClOrderID's must be unique. "Msg length incorrect" = the message did not have the proper length as specified in the header. "Req field Num Missing" = the required field is missing.

373 SessionRejectReason YCode which identifies reason for rejection. Valid values 0 - 11 based on FIX.4.4 Specs

Log Out

Your firm must log out at the end of each day before the midnight Eastern Standard Time (or depending when your FIX server maintenance is scheduled). You must verify, prior to log out, that there are no pending orders, otherwise your firm may miss trade reports. No pending order will be canceled automatically upon log out or abnormal disconnect.

The party initiating the log out must be the party that breaks the TCP connection to the MBT FIX Gateway. This requirement allows for both sides to issue a Resend Request should the log out or its reply arrive with a sequence gap. If you receive a log out with a sequence gap, as per the protocol specification, issue a Resend Request and then your own log out.

Tag FIXFieldName Required Description35 MsgType Y Type: 558 Text N Reason for logout message

Heartbeat

Tag FIXFieldName Required Description35 MsgType Y Type: 0108 HeartBtInt N Heartbeat interval (30 seconds)

Test Request

Tag FIXFieldName Required Description35 MsgType Y Type: 1

112 TestReqID NIdentifier included in Test Request message to be returned in resulting Heartbeat

Client/Inbound Application Messages

Pre-Trade Messages

Trading Session Status Request

Tag FIXFieldName Required Description35 MsgType Y Type: g263 SubscriptionRequestType Y Values: 0=Snapshot, 1=SnapShot +Updates, 2=Disable335 TradSesReqID Y Unique ID making the Trading Session Status request

336 TradingSessionID Y

Values: TSSTATE (back end trading connection status), GTC - updates on current GTC status (i.e. Spun (Live) or Suspended)

Trading Messages

New Order Single Request

Tag FieldName Required Description35 MsgType Y Type: D1 Account Y The account which the order is placed in.11 ClOrdId Y A unique identifier for an order within the trading day.18 ExecInst N String field, can contain multiple values delimited by a

space. Trade through stop setting: Value = w. Required on plus orders. Values: p=plus Trail , s=plus Stop , t= plus TTO, 6=Post No Preference (PNP Orders for Forex Only)

21 HandInst Y Instructions on how to handle this order; the only valid value is 1 (automated execution).

38 OrderQty Y The total number of shares to be traded. (Forex set to true size., 1 standard lot is equal to 38=100000)

40 OrdType Y The type of order which is placed; valid values are: 1=Market, 2=Limit, 3=Stop,4=StopLimit, P=TrailingStop, T=TTO

44 Price N Required for all orders which are limit, stop limit, and stop orders.

47 Rule80A (No Longer Used)

Y No longer used as of FIX.4.4. Included here for reference to prior versions.

52 SendingTime Y The time this order was sent54 Side Y The action to take on the order. Valid entries are: 1=Buy,

2=Sell, 5=Sell Short, and 6=Sell Short Exempt.55 Stock Y Stock, Options. Futures Symbol or Currency Pair59 TimeInForce Y Orders are assumed to be Day orders unless specified

otherwise. Valid values are: 0 = Day , 1 = GTC (required for all Forex orders), 2 = At the open, 3 = Immediate or Cancel (IOC), 4 = Fill or Kill (FOK), 6 = Good Till Date (GTD), 9 = Day + (only available for ARCA route touching pre-market, intraday regular market hours and after hours trading.

60 TransactTime Y Time of order initiation (expressed in UTC).99 StopPrice N Required on Stop and Stop Limit orders.100 ExecDestination Y MBTX or ECN when alternate destinations are permitted111 MaxFloor N Max volume of order to be shown to the market; if exists,

the order is assumed to be a reserve order (and the OrdType must be limit).

114 LocateReqd C Required on sell short orders, not required on FOREX, when 167=FOR

126 ExpireTime C Required when TIF = GTD167 SecurityType N Value FOR for FOREX trades168 EffectiveTime N Indicates time for order to go live, on a time triggered

order.200 MaturityMonthYear N Month and year of the maturity, required when trading

options. Format: YYYYMM201 PutorCall N Indicates if option is put or call, required when trading

options. Values: 0=Put , 1 = Call202 StrikePrice N Strike Price of an option, required when trading options.211 PegDifference N Required on TrailingStop orders (40=P) . This is the trail

offset.376 ComplainceID N Required on all new orders. Enter OATS id for order.

(Required on Equities)388 DiscretionInst N Required on a Discretionary Order. Should be set to 0:

Related to displayed price.389 DiscretionOffset N Required on a Discretionary Order. 526 SecondaryClOrdID N Optional and applicable to plus orders only. When set this

will be used as a ClOrdID of the plus portion when triggered

529 OrderRestrictions N Required on a plus order - (Value = 1)553 Username Y end user who entered the trade should have their username

specified here.566 LegPrice N Required on plus TTO orders. It is the stop price of the

TTO583 ClOrdLinkID N Permits order originators to tie together groups of orders in

which trades resulting from orders are associated for a specific purpose, for example, One Cancels All request.

640 Price2 N Required on plus TTO orders. It is the target price of the TTO

768 NoTrdRegTimestamps N Optional, only 1 supported, must be specified if Timestamps specified below

769 TrdRegTimestamp N Optionally required, for OATS reporting, when 60 is not time received from client

770 TrdRegTimeStampType N Required when above specified supported: 4 Broker Receipt

771 TrdRegTimestampOrigin N Required when above specified supported: OrderRecd839 PeggedPrice N The price the order is currently pegged at, included when

sending Initial Trail Stop order type. 847 TargetStrategy N Required on Conditional Trigger Order (CTO), must have

values of 1001 or 1002.10022 MBTX Aggressive N Value from 1 - 10 which instructs MBTX to work towards

getting you a better price or faster fill. Default is 0, for best price. *Not applicable on Forex orders

10055 OrderGroupId1 N May be set on NewOrder requests, when set will be returned on all execution reports related to that order. Can be used to group trades for managed accounts.

10065 MultiSymbol N Required on Conditional Trigger Order (CTO), must have value.

10066 MultiPrice N Required on Conditional Trigger Order (CTO), must have value.

10068 MBTMultifunction N Required when sending a Cancel and Close order, side would be the proper side as if sending a closing order, cancel is handled first, value supported =1.

10073 TriggerFromOrderID N Required when sending One Triggers Other order type, references OrderID of order to trigger other.

Cancel Request

Tag FIXFieldName Required Description35 MsgType Y Type: F1 Account Y Account number11 ClOrdID Y A unique identifier for an order within the trading day41 OrigClOrdID Y The ClOrdId of the order which is attempted to be canceled.54 Side Y This must match the side on the original order.55 Symbol Y This must match the symbol on the original order.60 TransactTime Y This is the time the cancel is sent553 Username Y End user who entered the trade should have their username

specified here.

Cancel/Replace Request

Tag FIXFieldName Required Description35 MsgType Y Type: G1 Account Y Account number11 ClOrdID Y A unique identifier for an order within the trading day.21 HandlInst Y Instructions on how to handle this order; the only valid value

is 1 (automated execution)38 OrderQty Y The new volume for the order.40 OrdType Y The type of order which is placed; valid values are:

1=Market, 2=Limit, 3=Stop,4=StopLimit, P=TrailingStop41 OrigClOrdID Y The ClOrdId of the order which is attempted to be canceled.44 Price C The new price for the order54 Side Y This must match the side on the original order.55 Symbol Y This must match the symbol on the original order.59 TimeInForce Y Must match TIF on initial order, TIF is not changeable60 TransactTime Y This is the time the cancel is sent553 Username Y End user who entered the trade should have their username

specified here.

New Order – Multi-Leg

Tag FIXFieldName Required Description35 MsgType Y Type: AB1 Account Y The account which the order is placed in.11 ClOrdID Y A unique identifier for an order within the trading day.18 ExecInst N G=All or None, is the only value supported21 HandInst Y 1=Automated Execution, the only valid value38 OrderQty Y Number of times the spread is available40 OrderType Y 1=Market, 2=Limit, etc.44 Price N The Net price of the spread - Debit (positive) is willing to

pay - Credit (negative) wants cash back.54 Side Y 1= As defined, the only valid value59 TimeInForce Y 0=Day60 TransactTime Y Time this order was sent by the trader77 PositionEffect N Stated whether this order or fill results in opening a

position or closing a position. Supported values: O (Open),C (Closed).

100 ExecDestination Y MBTX or MBTR (based on commission plan) or ECN when alternate destinations are permitted

167 SecurityType Y MLEG = multi-leg order, the only valid value553 Username Y End user who entered the trade should have their

username specified here555 NoLegs Y Number of legs, valid value is: 2768 NoTrdRegTimestamps N Optional, only 1 supported, must be specified if

timestamps specified below769 TrdRegTimestamp N Optionally required, for OATS reporting, when 60 is not

time received from client 770 TrdRegTimestampType N Required when above specified supported: 4 Broker

Receipt771 TrdRegTimestampOrigin N Required when above specified supported: OrderRecd

Instrument Leg – Repeating Group

564 LegPositionEffect Y Options Only: Valid Values: O=Open, C=Close600 LegSymbol Y For Options Legs: option root symbol must be first tag in

each repeating group.608 LegCFICode Y Multi-leg instruments individual CFI code, Valid Values:

OC=Option Call, OP=Option Put610 LegMaturityMoYear Y Options Only: Expiration month and year in the format:

YYYYMM612 LegStrikePrice Y Options Only: Strike price for the option623 LegRatioQty Y The ratio of quantity for this leg, relative to the entire multi-

leg order624 LegSide Y Valid Values: 1=Buy, 2=Sell654 LegRefID Y Unique ClOrdID value for each leg. Must be last tag in each

repeating group.

Order Mass Status Request

Tag FIXFieldName Required Description35 MsgType Y Type: AF1 Account C Required, if no username and password provided. 17 ExecID Y First ExecID to send from - client can cache Execution

Reports on his side, and request only from last msg received.

347 MessageEncoding C Value = 554_H1 (required with hashed password)553 Username C Required with password if account not provided. Will

provide all execution reports for this username.554 Password C Required with username if account not provided. A

password is required in your logon message for additional security. This field should be hashed according to SHA-256. (ASCII string of 64 hex digits)

584 MassStatusReqID Y ID of status request.585 MassStatusReqType Y 7 - Status All Orders

Post Trade Messages

Collateral Request (Balance Request)

Tag FIXFieldName Required Description35 MsgType Y Type: BB1 Account C Required, if no username and password provided.

142 SenderLocationID N Used on certain collateral request to specific IP of end user.

263 SubscriptionReqType N 0=Snapshot, 1=Snapshot+Updates, 2=Disable 347 MessageEncoding C Value = 554_H1 (required with hashed password)553 Username C Required with password if account not provided, will

provide all execution reports for this username.554 Password C Required with username if account not provided. A

password is required in your logon message for additional security. This field should be hashed according to the SHA-256 format. (ASCII string of 64 hex digits)

909 CollInquiryID N Identifier of inquiry, will be provided back to the client on snapshot request.

Request for Positions

Tag FIXFieldName Required Description35 MsgType Y Type: AN1 Account C Required, if no username and password provided.

263 SubscriptionReqType N 0=Snapshot, 1=Snapshot+Updates, 2=Disable (default =0)347 MessageEncoding C Value = 554_H1 (required with hashed password)553 Username C Required with password if account not provided. Will

provide all execution reports for this username.554 Password C Required with username if account not provided. A

password is required in your log on message for additional security. This field should be hashed according to SHA-256. (ASCII string of 64 hex digits)

710 PosReqID Y Unique identifier for this request724 PosReqType Y 0=Positions (current), 9=Positions (BOD only applicable

to snapshot)

Server/Outbound Application Messages

Pre Trade Messages

Trading Session Status

This message is sent once the client has logged in and the server is ready to accept client requests.Tag FixFieldName Required Description35 MsgType Y Type: h335 TradeSesReqID N Unique ID of a trading session status message

336 TradingSessionID N

Values: STANDARD (on auto response, when your log on is ready for requests), GTC updates on current GTC status (i.e. spun (live) or suspended, TSSTATE

340 TradingSessionStatus Y 2 (Open), 3 (Closed), 0 (Unknown)

625 TradingSessionSubID NProvided when Trading SessionID is: GTC, will list exchange GTC status is applicable to

News Message

These messages will be sent to alert clients to any urgent ECN/trading issues.Tag FixFieldName Required Description35 MsgType Y Type: B33 LinesOfText Y Will normally be set to 142 OrigTime N The time the alert originated.58 Text Y Contains the actual news alert message

61 Urgency NCode indicating the severity of the message, possible values: 0 (Normal), 1 (Flash - most urgent)

148 Headline YDescribes message as a news alert, will contain the text: "MBT NEWS ALERT"

Trading Messages

Business Message Reject

Tag FixFieldName Required Description35 MsgType Y Type: j45 RefSeqNum Y MsgSeqNum of rejected message58 Text Y Reason for Rejection372 RefMsgType Y The MsgType of the FIX message being referenced379 BusinessRejectRefID N Supplies the ClOrdID of the message this is rejecting, if the

ClOrdID was provided in the original message.380 BusinessRejectReason Y Code which identifies reason for rejection: 3= Unsupported

Message Type710 PosReqID Y References ID in original Request for Position (35=AN)909 CollInquiryID Y References ID in original Collateral Inquiry (35=AF)

Order Cancel Reject

Tag FixFieldName Required Description35 MsgType Y Type: 91 Account Y Account specified for this order

11 ClOrdID Y The client assigned ID to which this reject refers.37 OrderID Y Order id of order to cancel, if unknown then "NONE"

39 OrdStatus YStatus of Cancel or Replace request to which this reject applies.

41 OrigClOrdID YThe client assigned ID to original order to which could not be canceled or replaced.

58 Text N Description of reason for rejection65 SymbolSfx N Symbol suffix102 Treasonable Y Code which identifies reason for rejection 434 CxlRejResponseTo Y 1 = Order Cancel request, 2 = Order Cancel/Replace Request

Execution Report

These messages will be sent in response to every orders state change, i.e., when an order is Accepted, when an order is Filled, or when an order is Canceled.

Tag FixFieldName Required Description35 MsgType Y Type: 81 Account Y Account specified for this order6 AvgPx Y Average price of executed shares to this point11 ClOrdID Y The client assigned ID to which this Execution report

refers12 Commission N On trades - the amount of commission that is charged14 CumQty Y Total number of shares filled to this point17 ExecID Y Unique String value 18 ExecInst N Exec instructions entered on order31 LastPX N Price for the shares executed32 LastShares N Number of shares completed in this Partial Fill and/or Fill37 OrderID Y Unique OrderId given to the execution38 OrderQty N Quantity entered on order39 OrdStatus Y Status of the Order:

Possible Default Values: 0, 1, 2, 3, 4, 5 (Replaced), 6, 8, 9, A, E Custom Values: H (Break), I (Status), R (Resumed)

40 OrdType N Type of the order41 OrigClOrdId C Returned when applicable i.e. Pending change/cancel

request44 Price N Price entered on order54 Side Y Side of trade, as defined above55 Symbol Y Stock Symbol, or Currency Pair58 Text N String description59 TIF N TimeInForce of the order60 TransactTime N Time of the Execution, expressed in UTC77 PositionEffect N Stated whether this order or fill results in opening a

position or closing a position. Supported values: O (Open ), C (Closed)

99 StopPrice N Stop Price100 ExDestination N MBTX, Execution destination as defined by institution

when order is entered.103 OrdRejReason N Code to identify reason for order rejection where

0=BrokerOpt and reasons for rejections can be determined through tag 58 in the text message.

109 ClientID Y Represents the username who has made the initial request, i.e. new order, cancel or change request, etc.

111 MaxFloor N Maximum quantity (e.g. number of shares) within an order to be shown on the exchange floor at any given time.

126 ExpireTime N Provided on a GTC order 150 ExecType Y Describes the specific ExecutionRpt

Possible Default Values: 0, 1 (Partial fill), 2 (Fill), 3, 4, 5, 6, 8, 9, A, D, E, FCustom Values: H (Break), I (Status), R (Resumed)

151 LeavesQty Y Amount of shares still live in the Order167 SecurityType N Indicates type of security168 EffectiveTime N Time the details within the message should take effect

(always expressed in UTC, Universal Time Coordinated, also known as 'GMT')

198 SecondaryOrderId N May be returned with OrderID from the secondary destination on acceptance of order.

311 UnderlyingSymbol N Underlying securities symbol, see symbol (tag 55) field for description.

376 ComplianceID N Required on all new orders. Enter OATS ID for order. (Required with Equities).

388 DiscretionInst N Code to identify the price a DiscretionOffsetValue (tag 389) is related to and should be mathematically added to.

389 DiscretionOffsetValue N Amount (signed) added to the 'related to' price specified via DiscretionInst (tag 388), in the context of DiscretionOffsetType (tag 842).

442 MultiLegReportingType N Applicable to multi-leg orders only, values: 1=Single Security, 2=Individual Leg, 3=Multileg Security.

460 Product N Returned on pending acknowledgment of the order. Supported values are: 2=Commodity(Futures), 4=Currency(Forex), 5=Equity, 12=Other(Options)

529 OrdRestrictions N Order restriction value entered on order.555 NoLegs N Number of legs, valid value is: 2566 LegPrice N Required on plus TTO orders, it is the stop price of the

TTO order.583 FN_CLORD_LINK_ID Y Permits order originators to tie together groups of orders

in which trades resulting from orders are associated for a

specific purpose, for example, One Cancels All request.584 MassStatusReqID C Value assigned by issuer of Mass Status Request to

uniquely identify the request (GTS)600 LegSymbol N For options legs: Option Root Symbol, must be the first

tag in each repeating group.607 LegProduct N Multi-leg instruments individual securities products. See

Product (tag 460) field for description612 LegStrikePrice N Options only: Strike price for the option623 LegRatioQty N The ratio of quantity for this leg, relative to the entire

multi-leg order.624 LegSide N Valid values: 1=Buy, 2=Sell640 Price2 N Required on plus TTO orders, it is the limit price of the

TTO order.654 LegRefID N Applicable to multi-leg orders only, contains legrefid from

multi-leg order to which this execution report applies.839 Pegged Price N The price the order is currently pegged at, included when

sending Initial Trail Stop order type. 912 LastRptRequest N In response to mass order status – last report returned9730 LiquidityTag N When provided indicates whether order was adding or

removing liquidity, A=Add, R, X or anything else =Remove

10004 PosRealizedPNL N On closing trades – the amount of profit/loss incurred by the trade.

10017 MBTInternalOrderId N MBT internal ordered: varchar value10055 OrderGroupId1 N If provided on the new order request it will be returned on

all execution reports for that order.10073 Trigger From Order ID N Required when sending One Triggers Other order type,

references OrderID of order to trigger other.

Post Trade Messages

Collateral Report

Tag FixFieldName Required Description35 MsgType Y Type: BA1 Account Y Account sent in original message request12 Commission N Total Commission charged to the account15 Currency N Currency account funds are held in898 MarginRatio N Margin rate of Forex account

899 MarginExcess YTotal current Excess Equity in account (Excess Equity field in the MBT Desktop – Account Balances).

900 TotalNetValue Y Total current value of Account (total equity)908 CollRptID Y Unique Identifier for collateral report909 CollInquiryID N Identifier of collateral inquiry to which this is a reply910 CollStatus Y N/A in our usage, defaulted to 0

10002 MorningBuyingPower Y BOD buying power of the account

10005 MBTAccountType YMBT Account Type values: 1=cash, 2=US Margin, 6=DVP, 20=Forex.

10006 OvernightBuyingPower N BOD, May be different than intraday in case of equities10008 RealizedPnL N Total realized Profit/loss in the account10009 MorningAccountValue N Account value at start of the trading day10010 MorningExcessEquity N BOD excess equity of the account10018 AccountCredit N Amount by which account value has been adjusted (+/-)

10024 AcctBasedPerms Bit Map NProvided when validated username/password on Collateral Inquiry request.

10040 MorningExcessEquity NMorning Excess Equity value at the start of day (Morning Excess field in the MBT Desktop)

10401 FLID N FLID = MBT four letter ID code provided to each account.10402 USER_SESSION_ID N MBT Internal Tag – Related to Session Token

10048 OvernightExcess NOvernight Excess Equity for account (Overnight Excess field in the MBT Desktop – Account Balances)

10050 BODOvernightExcessEq N Overnight Excess Equity value at the start of the day.

Collateral Inquiry Acknowledgment

Tag FixFieldName Required Description35 MsgType Y Type: BG909 CollInquiryID N Identifier of collateral inquiry to which this is a reply.911 TotNumReports Y Total number of collateral reports that will be returned to this

inquiry (snapshot only)945 CollInquiryStatus Y 0 (Accepted), 4 (Rejected) – status returned when collateral

request cannot be processed.10402 USER_SESSION_ID N MBT Internal Tag – Related to Session Token10059 Quote Perm Bitmap

ValueN Provided when validated username/password on collateral

inquiry request.10071 User Route Perm Y Equities Only. Provides customer order route permissions.

MBTX = 65536MBTR = 536870912

Position Report

Tag FixFieldName Required Description35 MsgType Y Type: AP1 Account Y Account12 Commission N Total commissions charged on all trades on this symbol.54 Side N 1 = Long, 5 = Short 55 Symbol N Position symbol, only not provided if PosReqResult is 2.75 TradeDate N Last date of purchase of this position (YYYYMMDD) by

EST. 200 MaturityMonthYear N Required for Options only.201 PutorCall N Required for Options only. Valid Values: 0=Put, 1=Call202 StrikePrice N Required for Options only.263 SubscriptionReqType N 0=Snapshot, 1=Snapshot+Updates, 2=Disable (default =0)325 UnsolictedIndicator N Set to Y is result of subscription request640 Price2 N Secondary average price calculation used on this position, for

equities is running cost basis price.704 LongQty N Quantity of a long position.705 ShortQty N Quantity of a short position.710 PosReqID N Provided on snapshot reports, is PosReqID from initial

request.715 ClearingBusinessDate Y System trading date of this position data (YYYYMMDD) by

EST.721 PosMaintRptID Y Unique identifier for this position report 727 TotalNumPosReports N Total number of position reports returned on snapshot request.728 PosReqResult Y 0 = Valid Request, 2 = No Position Found

730 SettlPrice Y Cost basis of this position.10000 PosPendBuy N The pending quantity on current buy orders.10001 PosPendSell N The pending quantity of current sell orders.10003 PosBuyPowerUsed N The amount of buying power needed for this position.10004 PosRealizedPNL N Today's closed profit or loss on this symbol10015 PosEquityUsed N The amount of equity required for this position.10047 OptionStrategyCode N Applicable to Options Only. 0=None, 1=CoveredCall,

2=CoveredPut, 3=ProtectiveCall, 4=ProtectivePut, 5=LongStraddle, 6=Collar, 7=CSEPID, 8=DebitCallSpread, 9=DebitPutSpread, 10=CreditCallSpread, 11=CreditPutSpread, 12=LongCallButterfly, 13=LongPutButterfly, 14=LongCallCondor, 15=LongPutCondor, 16=LongIronButterfly, 17=LongIronCondor, 18=ShortIronButterfly, 19=ShortIronCondor, 20=LongBoxSpread, 21=ShortBoxSpread, 22=ShortStraddle, 23=ShortCallButterfly, 24=ShortPutButterly, 25=ShortCallCondor, 26=ShortPutCondor, 27=Freestyle, 28=ForwardConversion, 29=ReverseConversion, 30=ShortStraddleLev3

10069 Today_Realized_PNL2 N Today's Basis Closed Profit/Loss.

Request for Position Acknowledgment

This message is sent in response to a request for positions from the client, only when the request was for a snapshot only. This indicates the end of the position snapshot.

Tag FixFieldName Required Description35 MsgType Y Type: AO1 Account Y Account52 SendingTime Y Time of message transmission (expressed in UTC)58 Text Y End of snapshot - for this account710 PosReqID Y Provided from PosReqID in client request721 PosMaintRptID Y Unique identifier for this position report727 TotalNumPosReport Y 0 - end of snapshot reached no more position snapshot data728 PosReqResult Y 9 - End Of Positions

Appendix A – Order Formatting Grid

Tag DescOrderType

OrderRest

ExcInst

Px StopPx

TrlAmt

Leg Px

Px2 Eff Tim

e

MaxFlr

Disc.Instr

Disc. Offst

TIFPeggedPric

e

TargetStrateg

y

Target Symbol

Target Price

MBTMulti- Func Tag

Sec. Type

ClOrdLinkId

TriggeredFromId(chged from

groupId)

GroupId

User

Tag No. 40 529 18 44 99 211 566 640 168 111 388 389 59 839 847 10065 10066 10068 583 10073 10055

Market 1 EOCFLimit 2 Y EOCFStop 3 Y EOCF CStop Limit 4 Y Y EOCF CTrailing Stop P Y EOCF C CTTO T Y Y EOCF C CTTO w/Trail T Y Y Y E CF C COn Open 1,2 2 E C COn Close 1,2 7 E C COrder on Time

1,2,3,4,P

C C Y EOCF C

Post no Pref 2 F CReserve 2 Y Y E F CDiscretionary 2 Y Y Y E F CDisc. Reserve 2 Y Y Y Y E F CPegged P R E F CPLUS ORDERS

Market + Trail

1 1 p Y E CF C

Market + TTO

1 1 t Y Y E CF C

Limit + Stop 2 1 s Y Y E CF CLimit + Trail 2 1 p Y Y E CF CLimit + TTO 2 1 t Y Y Y E CF CStop + Trail 3 1 p Y Y E CF CStop + TTO 3 1 t Y Y Y E CF Y

(groupID

OCA)

Stop Limit + Trail

4 1 p Y Y Y E CF Y (orderID

of Triggered

Order)

Stop Limit + TTO

4 1 t Y Y Y Y E CF

Market + Stop

1 1 s Y

Stop + Limit 3 1 q Y Y CReserve + TTO

E C C

Pegged Rsv. P R Y E CInitial Trail Stop

P Y(initial stop)

C Y(end

stop)

Key Blank Not applicable to this order.

Y RequiredC Conditionally required

Value Specific value – required for that order type.

Security Type KeyE = EquitiesO = OptionsC = FuturesF = Forex

Appendix B – Example FIX Messages

Logon Request

8=FIX.4.4 9=64 35=A 49=DEMOXZVQ 56=MBT 34=596 52=20100315-23:58:15 98=0 108=30 10=015

Logon Response

8=FIX.4.4 9=63 35=A 49=MBT 56=DEMOXZVQ 34=71 52=2010315-23:58:17 108=30 98=0 10=212

Trading Session Status

8=FIX.4.4 9=75 35=h 49=MBT 56=DEMOXZVQ 34=72 52=20100315-23:58:17 43=N 336=STANDARD 340=2 10=011

Collateral Request

35=BB 49=TEST 56=MBT 34=456 52=20101222-21:26:44 263=0 1=12345678 909=2

Position Request

35=AN 49=TEST 56=MBT 34=31 52=20101222-21:40:39 263=0 1=12345678 710=2 724=0

New Order – Single and Responses

Buy 100 MSFT @ Market (Executed)

8=FIX.4.4 9=153 35=D 49=DEMOXZVQ 56=MBT 34=609 52=20100316-00:03:58 1=21=33001448 21=1 100=MBTX 55=MSFT 54=1 114=N 60=20100316-00:03:58 38=100 40=1 44=27.34 59=0 47=A 10=042

8=FIX.4.4 9=206 35=8 49=MBT 56=DEMOXZVQ 34=84 52=20100316-00:03:58 43=N 17=114 55=MSFT 54=1 60=20100316-00:03:58.228 40=1 44=27.34 38=100 1=33001448 11=2 37=0c7002s:09gr 10017=0c7002s:09gr 59=0 150=A 39=A 151=100 6=0 14=0 10=077

8=FIX.4.4 9=201 35=8 49=MBT 56=DEMOXZVQ 34=85 52=20100316-00:03:58 43=N 17=115 55=MSFT 54=1 60=20100316-00:03:58.510 40=1 38=100 1=33001448 11=2 37=0c7002s:09gr 10017=0c7002s:09gr 150=0 39=0 151=100 44=27.34 6=0 14=0 10=070

8=FIX.4.4 9=226 35=8 49=MBT 56=DEMOXZVQ 34=86 52=20100316-00:03:59 43=N 17=116 55=MSFT 54=1 32=100 31=26.47 60=20100316-00:03:59.041 38=100 10004=0 1=33001448 11=2 37=0c7002s:09gr 10017=0c7002s:09gr 150=F 39=2 151=0.0 44=27.34 6=26.47 14=100 10=254

Buy 100 MSFT @26.35 - Then cancel request and order canceled

8=FIX.4.4 9=153 35=D 49=DEMOXZVQ 56=MBT 34=613 52=20100316-00:05:12 11=7 1=33001448 21=1 100=MBTX 55=MSFT 54=1 114=N 60=20100316-00:05:12 38=100 40=2 44=26.35 59=0 47=A 10=027

8=FIX.4.4 9=206 35=8 49=MBT 56=DEMOXZVQ 34=92 52=20100316-00:05:12 43=N 17=120 55=MSFT 54=1 60=20100316-00:05:12.713 40=2 44=26.35 38=100 1=33001448 11=7 37=0c7002s:09hn 10017=0c7002s:09hn 59=0 150=A 39=A 151=100 6=0 14=0 10=056

8=FIX.4.4 9=201 35=8 49=MBT 56=DEMOXZVQ 34=93 52=20100316-00:05:13 43=N 17=121 55=MSFT 54=1 60=20100316-00:05:13.026 40=2 44=26.35 38=100 1=33001448 11=7 37=0c7002s:09hn 10017=0c7002s:09hn 150=0 39=0 151=100 6=0 14=0 10=054

8=FIX.4.4 9=109 35=F 49=DEMOXZVQ 56=MBT 34=614 52=20100316-00:05:17 41=7 11=-7- 1=33001448 55=MSFT 54=1 60=20100316-00:05:17 10=231

8=FIX.4.4 9=203 35=8 49=MBT 56=DEMOXZVQ 34=94 52=20100316-00:05:17 43=N 17=122 55=MSFT 54=1 60=20100316-00:05:17.416 38=100 1=33001448 11=-7- 41=7 37=0c7002s:09hn 10017=0c7002s:09hn 150=6 39=6 151=100 44=26.35 6=0 14=0 10=177

8=FIX.4.4 9=201 35=8 49=MBT 56=DEMOXZVQ 34=95 52=20100316-00:05:17 43=N 17=123 55=MSFT 54=1 60=20100316-00:05:17.776 38=100 1=33001448 11=-7- 41=7 37=0c7002s:09hn10017=0c7002s:09hn 150=4 39=4 151=0 44=26.35 6=0 14=0 10=085

Appendix C – MBT FIX Gateway Symbology

** All symbology are case sensitive and is in uppercase unless otherwise noted **

Forex

55=CP1/CP2Where CP1 is the base currency and CP2 is the cross currency formatting. The volume of the orders is of the base currency.

Example: EUR/USD, USD/JPY, EUR/GBP

Futures

55=/PrefixContractExpiration

Where prefix is the contract designation and contract expiration is the two character code for the contract expiration.

Example: /YMM0, /ESU0, /6EH0

Note : To view Futures Expiration Codes, please see the Link below.

http://www.mbtrading.com/data/symbolData.aspx?type=futures

Options

55=+Root symbol + Expiration Year(yy)+ Expiration Month(mm)+ Expiration Day(dd) + Call/Put Indicator (C or P) + Strike price

A root symbol is same as the ticker symbol. And Strike is the one character code for the options strike price.

Examples: +CSCO-101016C22.00 = CSCO Oct ’10 Call, strike 22.00+IBM-101016P130.00 = IBM Oct ’10 Put, strike 130.00+RIMM-101120C45.00 = RIMM Nov ’10 Call, strike 45.00

Canadian Exchange

55=CAExchSymbol 207=Exch

Where CAExchSymbol is the symbol for this equity on the Canadian exchange and exch is the code designating which exchange: TO for Toronto Stock Exchange and V Canadian Venture Exchange.

Note: The client trading platform will display the symbol with a prefix of CAT. Or CAV. For the above exchanges respectively.

Equities

55=Equity Symbol 75=Symbol fx

Where Equity Symbol is symbol and Symbol fx is an option field which can be used to designate Class only. Preferred securities require a – appended to the symbol, see below. Warrants follow the symbology: 4 letter symbol plus W at the end, in cases of multiple warrants, Z may also be used (.W in case of listed warrants). Rights follow similar symbology: 4 letter symbol plus R at the end. When Issued: NASDAQ symbol plus V or listed symbol plus .V.

Examples:

Standard Equity: 55=DELL Dell Inc, Common StockClass Security 55=VIA 75=B Viacom Inc. Class BPreferred Securities 55=AHL Aspen Insurance Preferred Inc.

55=GDV-D Gabelli Pref DWarrants 55= FREEW FreeSeas Inc. – Freesees Warrant W

55=FREEZ FreeSeas Inc. – Freeseas Warrant Z55=AKH.W AIR FRN Warrants55=AKH.Z AIR FRN Warrants WI

Rights 55=ELUXR AB Electrolux – ADS RightsWhen Issued 55=CREOV Creo Inc. – Common Stock When Issued

55=GGG.V Graco Inc. When Issued

Appendix D – Proprietary Defined fields

Tag FixFieldName Required Description

9730 LiquidityTag N

When provided, indicates whether order was adding or removing liquidity. A= Add; R, X, or anything else= Remove

10000 PosPendBuy N The pending quantity on current buy orders10001 PosPendSell N The pending quantity of current sell orders10002 MorningBuyingPower Y BOD buying power of an account10003 PosBuyPowerUsed N The amount of buying power needed for this position10004 PosRealizedPNL N Today's closed profit & loss on this symbol

10005 MBTAccountType YMB Trading Account Type values: 1= Cash, 2= US Margin, 6= DVP

10006 OvernightBuyingPower NBOD, May be different than intraday in case of equities

10008 RealizedPnL N Total realized Profit/Loss in the account10009 MorningAccountValue N Account value at the start of the trading day10010 MorningExcessEquity N BOD excess equity of an account10015 PosEquityUsed N The amount of equity required for this position10017 MBTInternalOrderId N MB Trading internal ordered: varchar value

10018 AccountCredit NAmount by which account value has been adjusted (+/-)

10047 OptionStrategyCode NInteger code which defines what strategy this grouping message represents

10048 OvernightExcessEquity N Overnight excess equity for account10050 BODOvernightExcessEquity N Overnight excess equity for value at start of day

10055 OrderGroupid1 NIf provided on the new order request it will be returned on all execution reports for that order

10059 UserQuote NProvided when validated username/password on collateral inquiry request

10060 PosRunAvgPrice NIf provided this is the current average of the open position on this symbol

Appendix E – XML Data

http://www.mbtrading.com/data/symbolData.aspx?type=futures

http://www.mbtrading.com/data/symbolData.aspx?type=exchRate

http://www.mbtrading.com/data/symbolData.aspx?type=forex

Appendix F - Testing in Demo

To do:

- part fills- fills in demo environment-version changes Notes