Skip to end of metadata
Go to start of metadata

This section provides diagram examples for the following market data event scenarios:   


New Order Add - MBO & MBP Single Book Update Shared Incremental Refresh Message

Event: New Limit Order generates a market data book update. The event is reported by a single MDP 3.0 - Market Data Incremental Refresh message.

MBO Event MBP and MBO2

 

Trade Event - MBO & MBP Single Book Update Across Multiple Incremental Refresh Messages

Event: A new Limit Order is submitted, which generates a market data book update. The event is reported in two MDP 3.0 - Market Data Incremental Refresh messages. In the example below, the last real quote message for 5799-MatchEventIndicator is sent for both MBP and MBO updates. Additionally, in this scenario, the MBP update contains the end of event update.

MBO Event Order2

New Order Add - MBO Only Single Book Update

Event: A new Limit Order is submitted, which generates a market data book update outside of the MBP book. The price update is outside of the MBP book, therefore only a MBO message is generated. In this scenario, the MBO update receives the end of event update. 

MBO Only Event Order2

New Order Implied Instrument - Real and Implied Book Updates

Event: Incoming order for implied instrument (EJM5) generates real and implied book updates.

Given the following orders are booked:

Bid 

Ask

6 @ -2.50  EJ:BF H5-M5-U5

 15 @ 9987   EJU5

 8 @ 9985   EJM5

 1   @ 9988   EJU5

When the EJM5 order is acknowledged by CME Globex, this event is reported by an Incremental Book update message, followed by an Implied book update message. In this example, there is no additional event information to be sent, therefore an empty End of Event message is generated. Included in the message are tag 60-TransactTime, tag 5799-MatchEventIndicator=10000000, and tag 268-NoMDEntries=0.

new order implied func

Book Population - Start of the Week

Event: At the beginning of each week scheduled events such as GTC and GTD order resend at the start of the week can result in one to many events represented by Market Data messages.

In GTC and GTD Book resend events book updates are grouped for each active instrument and flagged with "End of Book updates and End of Event". This allows Client systems to display the book of each instrument without waiting for the whole scheduled event to be completed.

GT Book resends

Market Data Channel Reset and Recovery Event 

Event: In the instance of a CME Globex internal component error, the GCC will trigger Market Data Channel Reset and Recovery event for each impacted channel.

The Channel Reset message is the first message sent with MatchEventIndicator=00000000. Customer systems are expected to reset all books for the instruments listed on this channel.

Remaining working Orders and Statistics are resent before the trading session resumes. For each instrument that has been active during current session the following data will be recovered: 

  • Electronic volume (for instruments that have traded or participated in the match as a leg).
  • Real book, if any orders remain on the book.
  • Highest trade, Lowest trade, Indicative Opening (if available).

Book and Statistics recovery messages are grouped by instrument and the last message for the instrument is flagged "End of Event".

Once the data for all active instruments on the channel is recovered, it will be followed by:

  • Group States - for all Security Groups listed on the channel.
  • Implied matching state messages for channels with Implied products (implied matching ON/OFF).
  • Instruments states that are different from the group will be resent.

book resend due to failure func

Group Close with Order Elimination

Event: Scheduled Group Close with order elimination.

  • Group Close triggers Day order elimination for the group. GTD and GTC orders remain on the book.

GroupCloseAndEliminate

Outright Trade - Many Price Levels

Event: Bid side aggressor order trades with multiple ask orders at the best three price levels.

outright trade multiple price levels func

Calendar Spread Trade

Event: Incoming Calendar Spread aggressor order immediately trades with resting Calendar Spread opposing-side order.

The Trade Summary message is sent for Calendar Spread instrument. Leg Trades are not included in Trade Summary, but Volume updates are sent. The book is updated and a new low trade of the day is reported.

CalendarSpreadTrade

Stop Order Elected and Immediately Trades

Event: A Bid stop order is triggered, partially traded, and the remaining quantity rests on the book as a limit order.

  • Event includes two trades - a trade at the trigger price and an elected stop order trade.

StopElected

Single Aggressor Triggers Stop Spike

Event: An aggressing order triggers a Stop Spike event as follows:

  • An aggressing bid order trades with the sell side of the book. The trades are reported. Electronic Volume, Book Updates, and Statistics are sent.
  • The Stop Spike event is triggered. Implied matching is turned off and the instrument is Reserved for the allotted period of time. The Indicative Opening Price and Quantity are generated. The new opening price is determined and Trade, Volume, Book, Statistics, and Implied Book updates are sent.
  • The instrument is re-opened and Implied Matching is turned back on. The Book is updated and the End of Event indicator is sent.

The above results in the following updates, which comprise one event because they all occur due to the aggressing bid order entry:

  • Reserve Period for the Stop Spike Event
  • New opening trade
  • Volume
  • Book
  • Statistics
  • Instrument open.
  • End of event

The diagram shows the event messaging sequence resulting from the aggressing order trading.

AggressorTriggersStopSpike

Scheduled Groups Opening to Open

Event: Market data messages are sent when the market state transitions to the 'Open' state for a given product group. 

Each instrument will open and their updates will be sent, repeating until the entire group has opened. After all Instruments in the Group have opened and the updates have been sent, the End of Event indicator will be sent.

Group Open func

  • No labels