Xetra Auction Only

, ,
1

Imported from previous forum

2

I’m trying to find the best way to implement the Auction Only parameter in Xetra, and the only thing I could find that would do this is TradingSessionID(336).

Is this what everyone is using for Xetra’s Auction Only flag?

Is there an industry standard in how to represent this?

Thanks

Quadir

3

[ original email was from Kathryn Hanff - Kathryn.Hanff@deutsche-boerse.com ]
Hi Quadir,
I have spoken to my technical guys and they have come back with the following reply…

does Quadir Hussain mean the Xetra order attribute ‘trdResTypCod’ = Auction only?
If so - in our FIX Gateway we implemented this order attribute as a custom tag for our New order - single/Execution report messages.
Our FIX Gateway does not extend existing FIX tags with Xetra special order attributes.

hopefully this helps, if not drop me a mail back
best regards
Kathryn

I’m trying to find the best way to implement the Auction Only parameter
in Xetra, and the only thing I could find that would do this is
TradingSessionID(336).

Is this what everyone is using for Xetra’s Auction Only flag?

Is there an industry standard in how to represent this?

Thanks

Quadir

4

Hi Qadir,

in year 2000 we choose to solve this problem in a non “industry standard” way: Our FIX4.1 - Xetra Gateway uses TimInForce=7 to fill Xetra field trdResTypCod = “AU”. But this is in a bank-internal use only where mutual agreement is easier to accomplish.

Best Regards

Uli Hofmann

I’m trying to find the best way to implement the Auction Only parameter
in Xetra, and the only thing I could find that would do this is
TradingSessionID(336).

Is this what everyone is using for Xetra’s Auction Only flag?

Is there an industry standard in how to represent this?

Thanks

Quadir

5

Hi Uli,

in year 2000 we choose to solve this problem in a non “industry
standard” way: Our FIX4.1 - Xetra Gateway uses TimInForce=7 to fill
Xetra field trdResTypCod = “AU”. But this is in a bank-internal use only
where mutual agreement is easier to accomplish.

Hmmm, TimeInForce=7 is at “At the closing” since FIX 4.3. Does this match your usage?

Cheers, Jörg

6

Hi Jörg,

definitely not any more. But that was before FIX 4.3 saw light.

cheers

Uli

Hi Uli,

in year 2000 we choose to solve this problem in a non “industry
standard” way: Our FIX4.1 - Xetra Gateway uses TimInForce=7 to fill
Xetra field trdResTypCod = “AU”. But this is in a bank-internal use
only where mutual agreement is easier to accomplish.

Hmmm, TimeInForce=7 is at “At the closing” since FIX 4.3. Does this
match your usage?

Cheers, Jörg