Find
Dec 04, 2012

Eurex

Common Report Engine: Update

Since 3 September 2012, trading participants and Clearing Members have been able to access the public area on the Common Report Engine where non-transactional and non-participant-specific reports and files are published.

In order to accelerate file and report availability,

·          the Common Report Engine now additionally provides the report CB001 in the public area. It will remain available in the participant-specific area during a transition period until 4 February 2013.

·          starting 17 December 2012, all uncompressed Eurex Reports listed in the Public Area are also available as ZIP-compressed files. The reference data file FILRDF01 will be provided in compressed format only. The provision of uncompressed public files will end on 4 February 2013.

·          the Common Report Engine also provides reports originating from the new Eurex OTC Clear environments (84 for Production and 85 for Simulation).

To access the Common Report Engine public area, participants must use port 2221 instead of port 2222.

For further documentation about accessing the Common Report Engine, please refer to the Common Report Engine - User Guide published on the Eurex website www.eurexchange.comunder the path:

Technology > Eurex Release 14.0 > System documentation > Manuals > Technical Manuals

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.