Eurex Repo
Dear Participants,
The Eurex Repo F7 Production environment will be updated to F7 Release 4.2 on Saturday, 23 November 2024.
On the evening of 23 November 2024, Implementation News will announce the completion of the update. After the update, the production system will be technically available in unattended mode (no technical support).
With the start of the business day on Monday, 25 November 2024, the software version for Repo F7 production will be 004.255.000.
API clients need to update the version number to “4.2”. As of F7 Release 4.2, the only acceptable version number is 4.2.
F7 Release 4.2 includes GUI enhancements, a mandatory F7 API change and an F7 FIX Gateway upgrade with the following changes:
Core enhancements
F7 GUI-specific enhancements
F7 API-specific enhancements
F7 FIX Gateway-specific enhancements
F7 MTX-specific enhancements
F7 GUI users are strongly recommended to clear the browser cache after the Release introduction to ensure that the newly introduced GUI functionalities behave correctly.
F7 system documentation for F7 Release 4.2 is available in the Member Section of Deutsche Börse Group under the following path: Resources > Eurex Repo > System Documentation > Release 4.2
The following documents are also available under the above-mentioned path:
Best regards,
Your Client Services Team
Recipients: | All Trading Participants of Eurex Repo and Eurex Repo Vendors | |
Target groups: | Front Office/Trading, IT/System Administration | |
Contact: | repo.sales@eurex.com | |
Web: | www.eurex.com |
Market Status ⓘ
XEUR
The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.
Please find further information about incident handling in the Emergency Playbook published on the Eurex webpage under Support --> Emergencies and safeguards. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message.
We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.
An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.