The process by which, in the event of missed messages, the client system requests and Drop Copy resends the missed messages using the FIX Resend – Standard FIX resend process using the iLink 2 Resend Request message.Please Note: Company information has been directly obtained from the service provider and is subject to change without notice. For Drop Copy, this message alerts the client system to initiate the Application Resend. Notification of missing messages sent to client system with the Sequence Reset (tag 35-MsgType=4, tag 123GapFillFlag=Y) message.

A single Drop Copy Group may have multiple Target sessions based on the configuration characteristics of the Source sessions which feed the Drop Copy Group. A given iLink session can be a source session for more than one Drop Copy Group.Įxchange defined FIX session over which drop copy data is delivered. Message types sent over a session to perform business functions, e.g., New Order.Ĭustomer-defined grouping of iLink Source sessions for which drop copy data will be delivered (e.g., all the iLink sessions for a given business unit, trading customer or clearing firm).Ĭlient iLink session from which the Drop Copy Application messages originate. Message types used to establish and maintain a FIX session, e.g. The following table highlights the terms and definitions used in the service. Mandatory certification for Drop Copy is comprised of three tests to validate client system ability to receive and process Drop Copy messages, perform a FIX resend, and perform an Application resend.įor more information contact Certification Support for Electronic Trading (CSET). Drop Copy uses the same packet size as an outbound iLink message, i.e., thirty Source sessions will use the equivalent bandwidth of thirty iLink Source session Execution Report and reject messages.

Since Drop Copy Target sessions transmit Acknowledgment and Execution messages only (no market data), bandwidth impact should be minimal, but is dependent upon the number of Source sessions bundled to the Drop Copy Group. Customers must be able to accommodate this contingency. This fee is assessed on a per Drop Copy Group basis with the fee waived for the customer's first Drop Copy Group.ĭue to load balancing and optimization of the iLink order entry infrastructure, the aggregation of Source session data under a single Drop Copy group is subject to constraints that may require a customer to maintain multiple Drop Copy Target sessions. These messages can be used to determine the trading customer's open order position.Ī monthly fee for the Drop Copy service is charged as a separate line item on regular monthly CME Globex connection billing. Acknowledgments – These messages include all confirmation and elimination messages generated by the Source session(s).These messages can be used to determine the trading customer's filled position. Execution Reports – These messages include all fills and any trade cancel messages generated by the Source session(s).The configuration request should include which iLink Source sessions should be configured to feed the Drop Copy Group as well as the message types the customer wishes to receive for the Drop Copy Group. The available messages types are categorized as:Ĭustomers can also choose to implement Drop Copy Automation based on their Execution Firm ID or if they are a Clearing Firm (CME Class A Clearing Firm ID). See Schedule 12, Section II B for details or contact your Global Account Manager. Once the completed Schedule 12 is submitted all configuration requests for Drop Copy must be submitted by an authorized contact for the Drop Copy Group. Drop Copy FeesĬonfiguration of the Drop Copy service should be requested through your Global Account Manager. If you do not send the correct SenderCompID, the message will be ignored.įor questions regarding iLink or CME Direct as related to Drop Copy, please contact Global Account Management (GAM). The SenderCompID should not be changed by client systems using Drop Copy functionality (i.e.

Dropcopy android