Eurex Gateway

7.18.25.16

Released: Dec 01, 2017 File Size: 0
Package Contents:
No notes available.

Important Notes

Eurex Gateway 7.18.25 is released to support the T7 6.0 upgrade on December 4, 2017.

Customers must upgrade all Eurex Gateways after the close on Friday, December 1, and prior to the market open on Monday, December 4.

Why Should I Upgrade?

Eurex Gateway 7.18.25 is released to support the T7 6.0 upgrade on December 4, 2017.

Customers must upgrade all Eurex Gateways after the close on Friday, December 1, and prior to the market open on Monday, December 4.

In addition, Eurex Gateway 7.18.25 supports MiFID II Compliance. For details on Customer Defaults, Algo Defaults and MiFID related updates, please refer to X_TRADER® Support for MiFID II.

System Requirements

Eurex Gateway 7.18.25 is released to support the T7 6.0 upgrade on December 4, 2017.

Customers must upgrade all Eurex Gateways after the close on Friday, December 1, and prior to the market open on Monday, December 4.

In addition, Eurex Gateway 7.18.25 supports MiFID II Compliance. For details on Customer Defaults, Algo Defaults and MiFID related updates, please refer to X_TRADER® Support for MiFID II.

Installation Notes

Values required when submitting orders to Eurex as of the T7 6.0 upgrade, as well as for MiFID II compliance, may now be set in Customer Defaults using X_TRADER® 7.17.80 and TT User Setup 7.17.84. For details on configuring the appropriate values in Customer Defaults, please refer to X_TRADER® Support for MiFID II.

Full details on required fields by exchange may be found here.

IMPORTANT NOTE: Because many customers will not yet have client applications upgraded to support configuration of the MiFID II fields, we have implemented a parameter which will send default values for these required tags. To turn this feature on, the following section and parameter should be added to the Eurexhostinfo.cfg:

[ORDER_SERVER]
UseDefaultMiFID=true


When the UseDefaultMIFID parameter is set to true, if values for the MIFID fields are set by the client, the submitted values will be used instead of the defaults. When defaults are used, the following values will be submitted on orders:
  • Client ID = 2
  • Liquidity Provision = FALSE
  • Trading Capacity = Set based on Account Type

    IMPORTANT NOTE: Customers who are required to populate the Compliance ID for Algo orders are required by Eurex, as of December 4th, to properly set both the Execution Decision ID and the Execution Decision Qualifiers correctly in accordance with German HFT regulations.

    When the UseDefaultMIFID parameter is used, these values will be set as follows:
    While the UseDefaultMIFID parameter is enabled:
  • Execution Decision ID will be populated with the data from the Compliance ID that customers have configured in previous versions.
  • Execution Decision Qualifier will be set to indicate that the order is or is not coming from an algo based on whether an order is sent via an automated tool. The logic used here is the same logic that has been in place for years on the Eurex gateway to support the German HFT Act, so no additional configuration should be necessary.
    When the UseDefaultMIFID parameter is disabled and TT Client applications are upgraded to minimum versions required for MiFID compatibility:
  • Execution Decision ID will be populated based on the Algo Defaults configured for the trader.
  • Execution Decision Qualifier will be set based on the Algo Defaults configured for the trader.
  • Enhancements

      1. Added support for the T7 6.0 API upgrade, including new tags introduced for MiFID II (Ref 234142)

    1. Orders / Fills
      1. Support New FIX Tags for Self Match Prevention ID and SMP ID Type when sending via FIX Adapter (Ref 234213)

    Fixes

    Known Issues