AHA
-Interested User-
Posts: 37
Joined: Jan 31, 2012
|
Posted: Jan 30, 2013 10:49 AM
Msg. 1 of 10
Q,XGH13,7805.50,1,7805.50,7806.50,16,25,11:31:41.114,11:31:42.044,11:31:42.044,C Q,XGH13,7805.50,1,7805.50,7806.00,16,5,11:31:42.154,11:31:42.154,11:31:42.044,ba Q,XGH13,7806.00,4,7805.50,7806.00,16,5,11:31:42.154,11:31:42.154,11:31:42.018,C
Fieldset: Last,Last Size,Bid,Ask,Bid Size,Ask Size,Ask TimeMS,Bid TimeMS,Extended Trade TimeMS,Message Contents (I'm using Level 1 via TCP/IP)
Question 1: Why is the timestamp in row 1 (11:31:42.044) older than in row 3 (11:31:42.018) although trade in row 3 occured after trade in row 1?
Question 2: I would like to use field Last TimeMS, but it's always empty. Which field is the replacement for Last Trade Time?
The wrong timestamp applies also to bid and ask quote.
|
AHA
-Interested User-
Posts: 37
Joined: Jan 31, 2012
|
Posted: Jan 30, 2013 03:45 PM
Msg. 7 of 10
Steve, that issue is not occasionally.
As I checked with my other feeds, this problem does apply only to EUREX feed.
Every timestamp (Last, Bid and Ask) is limited from HH:MM:SS.000 to HH:MM:SS.254
I recorded 48000 bid quotes, 16050 quotes are wrong I recorded 49000 ask quotes, 16800 quotes are wrong I recorded 32500 last trades, 3600 trades are wrong
Please do check that issue on your site and with your 3rd party providers, as it seems to be a data type bug (using the "byte" data type) .
|