Technical attributes

Technical attributes

Persistent and non-persistent orders

Orders can be entered as persistent or as non-persistent orders. Orders are considered persistent if as a backup they are written to disk and for this reason remain in the order book until their validity expires. Persistent orders stay in the order book after a trading interruption or a technical problem with the trading system. Non-persistent orders are automatically deleted as soon as a trading interruption occurs in the corresponding instrument. From a participant’s point of view non-persistent orders always offer clarity as regards their status in the event of trading interruptions or technical problems.

Lean orders

For orders flag as “lean”, the receipt of status information messages is restricted to the session, through which the order had been entered. Furthermore, only such information messages may be recovered via a retransmission request that is about executions and about events, which were not solicited by the owner of the order. For an order that is not flagged as a lean order, the receipt of status information messages is not restricted to the session, through which the order had been entered, and information messages about all events regarding the order may be recovered via a retransmission request.

T7 does not accept orders that are both lean and persistent. Orders that are entered through a high-frequency session must always be lean and non-persistent.

Market Status

XETR

-

-

Parts of the trading system are currently experiencing technical issues

The trading system is currently experiencing technical issues

Xetra newsboard

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 Xetra webpage under Technology --> T7 trading architecture --> Emergency procedures. 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.


Emergency procedures


An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.