Nasdaq CXC Limited. CHIXMMD 1.1 Multicast Feed Specification

Transcription

1 Nasdaq CXC Limited CHIXMMD 1.1 Multicast Feed Specification

2 Nasdaq CXC Limited CHIXMMD 1.1 Multicast Feed Specification Synopsis: This document describes the protocol of the Nasdaq CXC Limited (Nasdaq Canada) CHIXMMD Feed. This feed provides a recoverable stream of orders and trades to Nasdaq Canadian Equities customers and vendors through a Multicast feed. Revision Date: February 8, , Nasdaq CXC Limited. All rights reserved. Nasdaq is a registered trademark. The copyright in the whole and every part shall not be copied or reproduced in whole or any part in any manner or form or in or on any media without the prior written consent of Nasdaq CXC Limited. This information is provided for informational purposes only. It does not take into account the particular investment objectives, financial situation, or needs of any individual or entity. Under no circumstances is it to be used or considered as an offer to purchase or sell any security, or as a solicitation or recommendation of the purchase, sale, or offer to purchase or sell any security. While the information has been obtained from sources deemed reliable, neither Nasdaq CXC Limited, nor its licensors, nor any other party through whom the user obtains any such information: (i) makes any guarantees that it is accurate, complete, timely, or contains correct sequencing of information; (ii) makes any warranties with regard to the results obtained from its use; or (iii) shall have any liability for any claims, losses, or damages arising from or occasioned by any inaccuracy, error, delay, or omission, or from the use of the information or actions taken in reliance on the information. Reproduction or redistribution of this information is prohibited except with written permission from Nasdaq Canada. System response times may vary for a number of reasons including market conditions, trading volumes and system performance. CHIXMMD Feed 1. Introduction PAGE 2 OF 26

3 The CHIXMMD Feed is the Multicast data feed for Nasdaq Canada. It disseminates information about orders and executions in real time for Nasdaq Canada s three independent Trading Books: CXC, CX2 and CXD. The feed is a series of sequenced and unsequenced variable length messages. The messages themselves are encoded in printable ASCII bytes. This document describes the Multicast version. Technical aspects of this data feed including the connection protocol, message types and message structures are described in this document. 2. Revision History Name Description Date Version 1.0 Initial document Version 1.1 Added multicast address information Version 1.2 Minor format edits Version 1.3 Version 1.4 Version 1.5 Added Listing Market on Stock Status messages. Added Attribute to support Bypass ( B = Bypass) on Trade messages. Added Cross Type on Trade messages. Added CX2 connectivity details Added UAT connectivity details Updated comments and examples to incorporate CX2 Changed multicast ports for production CX2 stream 1 and stream 2 and CX2 UAT stream 1 Version 1.6 Updated heartbeat interval in Section 3.1 Updated Bandwidth Recommendation Version 1.7 Added Attribute to support Market On Close ( C = Market On Close) on Trade messages Version 1.8 Updated Network Address Summary Version 1.9 Version 2.0 Version 2.1 Added Attributes to support Settlement Terms on Cross orders ( T = Cash Today, C = Cash Tomorrow, D = Delayed Delivery). Updated Network Address Summary to Include CX2 Secondary Site. Updated Message Descriptions to Reference Nasdaq CXD where applicable. Added value X to Cross Type field on Trade messages. Added Nasdaq CXD UAT network addresses Version 2.2 Added Nasdaq CXD production multicast addresses Version 2.3 Version 2.4 Added all remaining production and UAT network addresses for Nasdaq INET platform. Added Chicago (CH4) and Markham (3500 Steeles POP) addresses PAGE 3 OF 26

4 Version 2.5 Version 2.6 Version 2.7 Updated multicast operating hours. Updated Chicago (CH4) and Markham (3500 Steeles POP) addresses. Removed legacy Nasdaq CX2 production addresses and all legacy UAT addresses. Removed legacy Nasdaq CXC production addresses. Remove value B for Bypass from Order Execution Message and Long Form Order Execution Message. Added value D to Cross Type field of Trade message and Long Form Trade message. Added value C to Listing Market field of Stock Status message for CSE listed securities Version 2.8 Housekeeping update Version 2.9 Removed note about Nasdaq CXC order attribution PAGE 4 OF 26

5 3. Overview The Multicast Market Data system consists of two data services: Real-time Multicast Market Data Feed (CHIXMMD) Multicast Message Recovery Service (MMRS) The real-time multicast market data feed delivers market data in UDP multicast packet streams over the multicast market data network. There are multiple data streams published over the network for resilience purposes. They all carry identical content. By subscribing to these data streams, market data clients receive latest market data updates from the trading system. The multicast message recovery service offers message recovery to market data clients. Clients can connect to a designated MMRS server and request for past message retransmission. The recovery process is implemented via a TCP connection established by the request client to the MMRS server. The two data services are made available in both primary and secondary site for resilience purposes. Market data clients may want to rely on primary site services and switch to secondary site services only when necessary due to matching engine location. PAGE 5 OF 26

6 3.1 Real-Time Multicast Market Data Feed Service The Nasdaq Canada CHIXMMD feed delivers real-time market data in the form of UDP packet streams. There are two streams published from the primary site and another two from the secondary site. They are published in different multicast addresses. Refer to section Network Configuration Parameters for address details. All data streams are identical in terms of market data content. They are identical at message level. However, the protocol allows packing of multiple messages into a UDP packet and different market data servers at different sites may apply packing differently. Therefore the streams may differ at UDP packet level. Market data clients need to be aware of this nature when processing the feed. Every market data message carries a unique message sequence number which starts at 1 and increments by 1 in the next message. Market data clients may use this sequence number to detect message gap and act on recovery accordingly. There are regular heartbeat messages published in each data stream to indicate line connection status. The heartbeat message itself does not increment message sequence number and does not carry market data updates. It does carry the next expected sequence number so the market data client can use it to detect if the previous data messages are missing. Normally, the heartbeat message is published every 5 seconds but may be skipped when a data stream has a high volume of messages. Market data clients need to be aware of this nature when determining their heartbeat monitoring scheme. 3.2 Multicast Message Recovery Service Market data clients may use the service provided by MMRS Server to recover missing messages of the current trading day. This is done so by establishing a TCP connection to a designated MMRS server and following the protocols described in the latter part of this specification to initiate the request. Basically, the client application needs to submit a Login Request together with the sequence number of the first missing message. After validation, the Recovery Server replays messages to the client starting from the requested message. There is a limit on message volume to replay in a single recovery session. If the limit is reached, the server will terminate the connection. The Market data client has to start a new session and continue from the last recovery point. Refer to section Network Configuration Parameter for details on server address and recovery limit setting. 3.3 Real-Time Multicast Market Data Feed Service The multicast feed will be operating from 04:00 to 19:15. During the operation hours, market data clients may expect to see market data update messages and regular heartbeat messages in the data streams. PAGE 6 OF 26

7 3.4 Network Configuration Parameters The following tables summarize network address & parameter configurations needed for accessing the multicast market data services for each of the Nasdaq Canada books: Production Nasdaq Canada INET Platform Primary TR2 (45 Parliament St, Toronto) CXC CX2 CXD Stream A Multicast Group Multicast Port RP Source / / /28 MMRS MMRS Port Stream B Multicast Group Multicast Port RP Source / / /28 MMRS MMRS Port Production Nasdaq Canada INET Platform DR CH4 (350 E. Cermak Rd, Chicago) CXC CX2 CXD Stream C Multicast Group Multicast Port RP Source / / /25 MMRS MMRS Port Stream D Multicast Group Multicast Port RP Source / / /25 MMRS MMRS Port PAGE 7 OF 26

8 Production Nasdaq Canada INET Platform MKM POP (3500 Steeles Ave E, Markham) CXC CX2 CXD Stream E Multicast Group Multicast Port RP Source / / /29 MMRS MMRS Port Stream F Multicast Group Multicast Port RP Source / / /29 MMRS MMRS Port Nasdaq Canada Test Facility (NTF) INET Platform CXC CX2 CXD Multicast Group Multicast Port RP Source / / /28 MMRS MMRS Port PAGE 8 OF 26

9 Bandwidth Recommendation Market data clients are required to order line circuits with sufficient bandwidth to cater for market data volume published in our data streams. Below table provides guidelines on sizing the bandwidth calculation. Note that all multicast data streams published in our data network carry identical content. For resilience purpose, market data clients are advised to subscribe to at least two data streams (one from primary site and one from secondary site). Market data client also need to make provision for message recovery service. Sufficient bandwidth should be arranged so that message recovery can be completed timely. Multicast Data Stream 1 Recovery Server 30Mbps 2 Mbps minimum Figure: Production Bandwidth Recommendation for CXC Multicast Data Stream 1 Recovery Server 18Mbps 2 Mbps minimum Figure: Production Bandwidth Recommendation for CX2 Multicast Data Stream 1 Recovery Server 2Mbps 2 Mbps minimum Figure: Production Bandwidth Recommendation for CXD CHIXMMD Parameters MTU setting 1500 Heartbeat message frequency At least 1 in every 5 seconds Figure: CHIXMMD Configuration Parameters 1 Bandwidth requirement of the multicast stream the figure indicates the requirement for one multicast stream. If the client intends to subscribe to both streams from a single site, the figure should be doubled. PAGE 9 OF 26

10 MMRS Parameters The MMRS Server applies limit checks in serving recovery requests. If a request exceeds the preset limit, the server will disconnect the connection automatically. Market data clients are required to start a new session and continue from the last recovery point. Message Recovery Range Limit Session Time Limit 100,000 messages TBD Figure: MMRS Configuration Parameters 4. Protocol 4.1 CHIXMMD Protocol The Real-time Multicast Market Data Feed protocol contains the definition of market data messages and the definition of the multicast packets. The market data messages describe the activities of the trading system. For example, order addition and trade execution are activities in the trading system. The format of the market data messages is described in the next section. The multicast packet definition describes how market data messages are encoded in a multicast packet Multicast Packet Layout Each multicast packet contains a packet header followed by one or more data messages as illustrated in the following diagram. PAGE 10 OF 26

11 Figure 1: CHIXMMD Multicast Packet Layout The following table describes the packet header layout. PACKET HEADER NAME OFFSET LENGTH VALUE REMARKS Sequence 0 4 Numeric Message Count Sequence number of the first message. 4 2 Numeric Number of messages in the packet The following table describes the data message layout. The following layout may repeat in the multicast packet to deliver multiple data messages in one packet. PAGE 11 OF 26

12 DATA MESSAGE NAME OFFSET LENGTH VALUE REMARKS Length Variable 2 Numeric Length of the Market Data Message Market Data Message Variable Variable Market Data Message Content of the Market Data Message Heartbeat Message The heartbeat message is used in the multicast feed to indicate health of the multicast feed. The message is delivered regularly by the Market Data Servers. The heartbeat message is delivered in a single multicast packet and indicated by the message count value of zero in the packet header described below. Figure 2: CHIXMMD Heartbeat Packet Layout The following table describes the heartbeat message layout including the packet header. HEARTBEAT MESSAGE NAME OFFSET LENGTH VALUE REMARKS Sequence 0 4 Numeric Message Count Sequence number of the next Market Data Message A zero value indicating this is a heartbeat message Session 6 10 Alphanumeric Current Session value The Session field contains the current session of the market data stream being delivered. Client applications should use this field to fill-in the Session field in the Login Request of the Recovery Service. The Session field will not change during a normal trading day. In unlikely events (e.g. the trading system is restarted in the middle of the day), it may change to a different value. When this happens, the sequence number of the market data messages will be reset to 1. PAGE 12 OF 26

13 4.2 MMRS Protocol The Multicast Message Recovery Service protocol follows the one used in the TCP version of the CHIXMD Feed. The protocol definition is described in the document CHIXMD Feed Specification. In terms of Market Data Message format, the MMRS protocol uses the same message format in the multicast feed described in section 5 of this document. The following diagram describes a typical recovery scenario: In the diagram, there are 4 steps involved Figure in the 3: message Recovery recovery Scenario process. Example Step 1: Market Data Client identified missing message(s) from the multicast stream and needs to recover the message using the recovery service. The client has to establish a TCP connection with the recovery server and format a Login Request message to request message retransmission. Step 2: After receiving the login request, the Recovery Server will validate the user authentication information in the request. The session and message sequence number in the request will also be checked to ensure relevant messages are available for retransmission. A Login Accepted message will be replied to the client to indicate the request is accepted and message retransmission will start soon. Step 3: The recovery server starts replaying the past messages one by one, starting from the one requested by the client. Step 4: When the client receives the necessary retransmissions, it should send a Logout Request to disconnect the recovery session. After the request is sent, the client may close the TCP connection immediately. PAGE 13 OF 26

14 There is a limit on message volume to replay in a single recovery session. If the limit is reached, the server will terminate the connection. Market data client has to start a new session and continue from the last recovery point. The recovery limit is described in the previous section Network Configuration Parameter. In addition, the recovery server will disconnect a client when playback of the past messages finishes. This is different from the CHIXMD feed which would continue to broadcast the real-time messages. 5. Market Data Messages The market data message format described below is the same in the multicast service and the TCP based CHIXMD recovery service. 5.1 Data Types All numeric fields are composed of a string of ASCII coded digits, right justified and space filled on the left. All alphanumeric text fields are left justified and padded on the right with spaces, and can include letters or digits. Standard prices are given in decimal format with 6 whole number places followed by 4 decimal digits. Long form prices are given in decimal format with 12 whole number places followed by 7 decimal digits. The whole number portion is padded on the left with spaces; the decimal portion is padded on the right with zeros. The decimal point is implied by position; it does not appear inside the price field. Timestamp fields are given in milliseconds past midnight Local Time. 6. Application Protocol - Market Data The CHIXMMD Feed service is composed of a series of messages that describe orders added to, removed from, and executed on CXC, CX2 and CXD. All of these messages will be contained in a Sequenced Data Message and are inbound messages to the client. The introduction of long form messages are used when either the price or size is larger than the standard messages can permit. This will be done on a per order basis. PAGE 14 OF 26

15 6.1 Add Order Message An Add Order Message indicates that CXC or CX2 has accepted a visible order into the book. It includes a day-unique Order Reference key assigned to the order. (Note: the issuing of an Add Order Message is not necessarily always for a new order. See section Modification of Existing Orders.) Not applicable to CXD. Add Order Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 A Add Order Message Order Reference 9 9 Numeric Day unique order reference number Buy/Sell Indicator 18 1 Alphanumeric B = Buy Order S = Sell Order Shares 19 6 Numeric Total number of shares being added to the book (may be less than the number of shares entered because part of the order may trade before being posted to the book). Stock Alphanumeric Stock symbol right padded with spaces. Price Price The display price of the order. Broker 45 3 Numeric The three digit numeric TSX Broker Number or 001 for anonymous. Long Form Add Order Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 a Add Order Message Order Reference 9 9 Numeric Day unique order reference number Buy/Sell Indicator 18 1 Alphanumeric B = Buy Order S = Sell Order Shares Numeric Total number of shares being added to the book (may be less than the number of shares entered because part of the order may trade before being posted to the book). Stock Alphanumeric Stock symbol right padded with spaces. Price Price The display price of the order. PAGE 15 OF 26

16 Long Form Add Order Message Broker 58 3 Numeric The three digit numeric TSX Broker Number or 001 for anonymous. 6.2 Order Execution Message An Order Execution Message is sent whenever an order on the book is executed in whole or in part. Not applicable to CXD. Order Execution Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 E Order Execution Message Order Reference 9 9 Numeric The reference key of the order that was executed. Executed Shares 18 6 Numeric The number of shares executed on this trade Trade Reference 24 9 Numeric Day unique trade reference number Contra Order Reference 33 9 Numeric The reference key of the contra-order that was executed. Trade Attribute 42 1 Alphanumeric C = Market On Close Broker 43 3 Numeric The three digit numeric TSX Broker Number or 001 for anonymous. Contra Broker 46 3 Numeric The three digit numeric TSX Broker Number of the contra order or 001 for anonymous. Long Form Order Execution Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 e Order Execution Message Order Reference 9 9 Numeric The reference key of the order that was executed. Executed Shares Numeric The number of shares executed on this trade Trade Reference 28 9 Numeric Day unique trade reference number PAGE 16 OF 26

17 Long Form Order Execution Message Contra Order Reference 37 9 Numeric The reference key of the contra-order that was executed. Trade Attribute 46 1 Alphanumeric C = Market On Close Broker 47 3 Numeric The three digit numeric TSX Broker Number or 001 for anonymous. Contra Broker 50 3 Numeric The three digit numeric TSX Broker Number of the contra order or 001 for anonymous. 6.3 Order Cancel Message An Order Cancel Message is sent whenever an order on the book is fully canceled, its quantity revised down or when a pegged order is re-priced. Not applicable to CXD. Order Cancel Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 X Order Cancel Message Order Reference 9 9 Numeric The reference number of the order being canceled. References a previously sent Add Order Message. Canceled Shares 18 6 Numeric Number of shares cancelled Long Form Order Cancel Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 x Order Cancel Message Order Reference 9 9 Numeric The reference number of the order being canceled. References a previously sent Add Order Message. Canceled Shares Numeric Number of shares cancelled 6.4 Modification of Existing Orders A price modification of an existing order is represented in CHIXMD by the issuing of a Cancel Message (for full open quantity) on the existing order followed by an Add Order Message that uses the same Order reference. Reduction of quantity order is represented in CHIXMD by the issuing of a Cancel Message on the existing order. The cancel message can reduce the number of shares currently pending in the referenced open order by the number of shares indicated. When the number of currently pending shares for an order reaches zero, the order is dead and should be removed from the book. PAGE 17 OF 26

18 6.5 Trade Message A Trade Message is sent when a trade occurs against order quantity not visible on the book (i.e. a fully or partially hidden order). They do not affect the book and can be ignored if you are building a book. Trade Messages are required to provide time-and-sales and other execution based data; they fill in the gaps left when an order that is not otherwise visible on the order book is executed. By combining the executions received separately via both Order Execution Messages and Trade Messages, it is possible to build a complete view of all executions that occur. Note that the Order Reference is always set to 0 (zero) and the Buy/Sell indicator to B. This applies to the Long Form version as well. Trade Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 P Trade Message Order Reference 9 9 Numeric The reference number of the order executed. (always 0) Buy/Sell Indicator 18 1 Alphanumeric B = buy order executed S = sell order executed (Always B ) Shares 19 6 Numeric Number of shares executed Stock Alphanumeric Symbol, right padded with spaces Price Price Match price of the order Trade Reference 45 9 Numeric Trade reference number generated for this trade. Contra Order Reference 54 9 Numeric The reference number of the contra order executed. Broker 63 3 Numeric The three digit numeric TSX Broker Number of the buyer or 001 for anonymous. Contra Broker 66 3 Numeric The three digit numeric TSX Broker Number of the seller or 001 for anonymous. Trade Attribute 69 1 Alphanumeric B = Bypass (intentional crosses only) C = Market On Close Cross Type 70 1 Alphanumeric I = Internal B = Basis C = Contingent V = VWAP X = Intentional Cross D = Derivative Related Settlement Terms 71 1 Alphanumeric T = Cash Today C = Cash Tomorrow D' = Delayed Delivery PAGE 18 OF 26

19 Long Form Trade Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 p Trade Message Order Reference 9 9 Numeric The reference number of the order executed. (always 0) Buy/Sell Indicator 18 1 Alphanumeric B = buy order executed S = sell order executed (Always B ) Shares Numeric Number of shares executed Stock Alphanumeric Symbol, right padded with spaces Price Price Match price of the order Trade Reference 58 9 Numeric Trade reference number generated for this trade. Contra Order Reference 67 9 Numeric The reference number of the contra order executed. Broker 76 3 Numeric The three digit numeric TSX Broker Number of the buyer or 001 for anonymous. Contra Broker 79 3 Numeric The three digit numeric TSX Broker Number of the seller or 001 for anonymous. Trade Attribute 82 1 Alphanumeric B = Bypass (intentional crosses only) C = Market On Close Cross Type 83 1 Alphanumeric I = Internal B = Basis C = Contingent V = VWAP X = Intentional Cross D = Derivative Related Settlement Terms 84 1 Alphanumeric T = Cash Today C = Cash Tomorrow D' = Delayed Delivery 6.6 Broken Trade Message A Broken Trade message is sent whenever an execution is broken. A Broken Trade is final; once a trade is broken it cannot be reinstated. Broken Trades happen only rarely and will only affect applications that build a time-and-sales database or maintain cumulative volumes or high/low calculations. If you are only building a book, you can ignore these messages; they have no effect on the book. PAGE 19 OF 26

20 Broken Trade Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 B Broken Trade Message Trade Reference 9 9 Numeric The trade reference number of the execution that was broken. This refers to a trade reference number from a previously transmitted Order Execution or Trade Message. 7.0 System Event Message The system event message type is used to indicate a market state event. System Event Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 S System Event Message Event Code 9 1 Alphanumeric O = First message of the day S = Start of Nasdaq Canada Trading Session Q = Start of Primary Market Trading Session M = End of Primary Market Trading Session. Indicates that Pegged orders are no longer available for execution. E = End of System Hours. Nasdaq Canada is closed and not accepting orders. It is still possible to receive Broken Trade messages and Order Cancel Messages. C = End of Messages. Last message of the day. 8.0 Stock Status Message This message indicates the current trading status of a stock. At the start of day, the feed will send out a stock status message for each of the symbols trading on CXC, CX2 and CXD. Subsequently, stock status messages will be sent when a stock is halted or is released for trading. Stock Status Message Time Stamp 0 8 Numeric Time Stamp Message Type 8 1 H Stock Trading Message Stock 9 10 Alphanumeric Stock symbol PAGE 20 OF 26

21 Stock Status Message Trading State 19 1 Alphanumeric H = Halted, T = Trading Short Exempt 20 1 Alphanumeric Y = Short Exempt, N = Not Exempt Listing Market 21 1 Alphanumeric T = TSX, V = Venture, C = CSE 9.0 Example Output 9.1 Multicast Packet Messages Single message within packet MESSAGE TYPE CHIXMMD FEED MESSAGE Trade Message f b /...; P 0B f 44 2e 4c VOD.L FIELD HEX MEANING Sequence Number f Decimal Value = 815 Message Count Decimal Value = 1 Message Length 00 3b Decimal Value = 59 Message f 44 2e 4c ASCII String P 0B 400VOD.L Multiple message within packet MESSAGE TYPE Add Order, Order Execution and Order Cancel Message in one packet CHIXMMD FEED MESSAGE c a * A 4B f 44 2e 4c VOD.L a Y.* E PAGE 21 OF 26

22 MESSAGE TYPE CHIXMMD FEED MESSAGE X FIELD HEX MEANING Sequence Number c Decimal Value = 796 Message Count Decimal Value = 3 Message Length 00 2a Decimal Value = 42 Message f 44 2e 4c ASCII String A 4B 500VOD.L Y Message Length 00 2a Decimal Value = 42 Message ASCII String E Message Length Decimal Value = 24 Message X Heartbeat message MESSAGE TYPE CHIXMMD FEED MESSAGE Heartbeat Message FIELD HEX MEANING Sequence Number Decimal Value = 790 Message Count Always zero Session ID ASCII String Market Data Messages Order added then fully trades. Not applicable to CXD. Sell of 100 RIM shares entered at Order Ref of 113 assigned A 113S 100RIM PAGE 22 OF 26

23 Matching buy order entered and trade results with Trade Ref Both sides are anonymous by default for CXC. (CX2 is not anonymous by default) E Sell of 100 RIM shares entered at Order Ref of 172 assigned. On the order Tag Anonymous (6761)=N, but add message will show 001 for CXC only (CX2 would show the appropriate broker #). Matching buy order entered and trade results with Trade Ref A 172S 100RIM E Note: There is no Add Order message for the buy order. It is not displayed on the book so no alert goes out. Note: The Execution message has no price. The consumer must infer the execution price based on the limit of the original order Order added, fully trades and residual amount of matching order is placed on the book. Not applicable to CXD. Buy of 200 RIM shares entered at Order Ref of 269 assigned. Matching sell order entered for 100 shares of RIM. Execution message sent with Trade Ref A 269B 200RIM E Pegged/Market Order added to book. Not applicable to CXD. Sell of 800 RIM shares entered with a pegged order attribute. Order Ref 296 assigned. The display price is Each time the price moves and this order is re-priced a Cancel is sent. Then an Add message is sent but note that the Order Ref is the same. The display price is now Note: Market orders will behave in the same way as above A 296B 800RIM X A 296B 800RIM Price Revision. Not applicable to CXD. PAGE 23 OF 26

24 Sell of 300 RIM shares entered. Order Ref 273 assigned. The display price is Price is revised to Cancel is sent X Then an Add message is sent but note that the Order Ref is the same. The display price is now A 273S 300RIM A 273S 300RIM Revision of Order Quantity Down. Not applicable to CXD. Sell of 1000 RIM shares entered. Order Ref 276 assigned. The display price is The order is then revised in quantity down by 500 shares; a Cancel message informs the consumer of this A 276S 1000RIM X Note: The consumer is expected to calculate the residual amount of the original order still open Revision of Order Quantity Up. Not applicable to CXD. Sell of 1000 RIM shares entered. Order Ref 278 assigned. The display price is The order is then revised in quantity up by 500 shares, a Cancel message is sent. Then an Add message is sent but note that the Order Ref is the same. The display quantity is now A 278B 1000RIM X A 278B 1500RIM Order Revision Results in Execution. Not applicable to CXD. A visible buy order for 300 RIM shares is placed on the book with a display price of Anonymous (6761)=Y or blank. A visible sell order of 300 shares is placed on the book with a display price of Anonymous=N, Broker= shows on the Add message for CXC. 123 shows on the Add message for CX2. The sell order is revised to a display price of This results in a Cancel message. Then the sell order trades and an Execution message is sent. The broker shows anonymous. The Contra broker is attributed to TSX Broker Number A 272B 300RIM A 273S 300RIM X E PAGE 24 OF 26

25 9.2.8 Execution of a Fully Hidden Order (Minimum Fill) A non-displayed minimum fill sell order of 3000 RIM shares is put on the book with a price of A visible buy order of 3000 shares is entered at 85.89, Anonymous=N, Broker 123. This results in a Trade message against the hidden order quantity. The Contra broker is attributed to TSX Broker Number 123. [ No message for non-displayed order ] P 0B 3000RIM Trades against a Partially Hidden Order (Iceberg). Not applicable to CXD. A sell order of 10,000 RIM shares is put on the book with a visible quantity of 1000 shares, price is 85.89, Anonymous=N, Broker=123. This results an Add message for the visible amount. 001 shows on the Add message for CXC or 123 for CX2. A Buy order for 500 shares is entered and crosses. 500 shares remain on the book. The Broker is attributed to TSX Broker Number 123. Then a Buy order for 4000 shares is entered and crosses against the iceberg. We first get a visible trade of 500 shares. The Broker is attributed to TSX Broker Number 123. Then a Trade is sent against the not visible quantity of 3500 shares. The Broker is attributed to TSX Broker Number 123. Finally the peak is refreshed onto the book. An Add message is sent for 1000 shares A 282S 1000RIM E E P 0B 3500RIM A 285S 1000RIM Trade Cancellation (Bust). Only Broken Trade message applicable to CXD. A sell order of 100 RIM shares is put on the book. The display price is This results an A message for the visible amount A 206S 100RIM PAGE 25 OF 26

26 An Execution message is generated by a matching order. The Trade Ref is Then the trade is cancelled by Nasdaq Canada. A Broken Trade message goes out for each side of the trade E B B Trade Correction. Only the Broken Trade message followed by a Print message is applicable to CXD. A sell order of 1000 ECA shares is put on the book. The display price is This results an A message for the visible amount. An Execution message is generated by a matching order. The Trade Ref is A 47B 1000ECA E Then the trade price is corrected B P 0B 1000ECA PAGE 26 OF 26