NYSE Liffe Gateway

7.18.25.10

Released: Nov 24, 2017 File Size: 0
Package Contents:
No notes available.

Important Notes

NYSE Liffe Gateway 7.18.25 is released to support the Euronext CCG upgrade for MiFID II on November 27, 2017.

Why Should I Upgrade?

NYSE Liffe Gateway 7.18.25 is released to support the Euronext CCG upgrade for MiFID II on November 27, 2017. Customers must upgrade all NYSE Liffe Gateways after the close on Friday, November 24 and prior to the market open on Monday, November 27.

In addition, NYSE Liffe Gateway 7.18.25 is the supported version for MiFID II Compliance. For details on Customer Defaults, Algo Defaults and MiFID related updates, please refer to X_TRADER® Support for MiFID II.

NOTE: Per Euronext, GTC orders will persist through this upgrade, and customers need take no action related to these orders. Note that Euronext will purge all orders after the close of business on January 2.

System Requirements

NYSE Liffe Gateway 7.18.25 is released to support the Euronext CCG upgrade for MiFID II on November 27, 2017. Customers must upgrade all NYSE Liffe Gateways after the close on Friday, November 24 and prior to the market open on Monday, November 27.

In addition, NYSE Liffe Gateway 7.18.25 is the supported version for MiFID II Compliance. For details on Customer Defaults, Algo Defaults and MiFID related updates, please refer to X_TRADER® Support for MiFID II.

NOTE: Per Euronext, GTC orders will persist through this upgrade, and customers need take no action related to these orders. Note that Euronext will purge all orders after the close of business on January 2.

Installation Notes

Values required when submitting orders to Euronext as of the CCG MiFID II release, 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.

IMPORTANT NOTE: Null values, which are accepted by the exchange, will be automatically sent in the new MIFID fields when they are not populated by the client. Customers must ensure that these values are properly populated once required by the exchange.

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

Enhancements

  1. Gateway
    1. Support for new tags introduced for MiFID II (Ref 233835)

Fixes

Known Issues