nsolot
-DTN Guru-
Posts: 273
Joined: Sep 4, 2004
|
Posted: Jun 6, 2005 08:21 AM
Msg. 1 of 7
I'm seeing some messages arriving with odd data in the first field.
In some cases the "Q" is simply missing, for example:
,@NQM5,10,1548.00,-2.5,-0.001612383,6796,5,1552.50,1547.50,1548.00,1548.50,10,180,183,,5.,09:05t,319595,1550.00,1550.50,0.5,,1549.00,,,,,,,06/06/2005,,1548.00,06/17/2005,,,-2.5,0,,,0.5,0.5,-2.,1,0.003229974,,12,2,10,,,1550.00,0,0,0,920,,,,, 06,05,05,453,NQ
In other cases, the Q is prepended with the character 0x0D.
|
nsolot
-DTN Guru-
Posts: 273
Joined: Sep 4, 2004
|
Posted: Jun 6, 2005 10:23 AM
Msg. 3 of 7
My own app. Just implemented the beta API this weekend.
Watching a total of 59 tickers. I'll post a list later if you need them. As best I can tell this happened between 9 & 9:30 EST, but I'll know more when I anyalyze my log file after the mkt close today.
If you have a test app you can modify, I'd suggest putting in a trap to catch any instances where the field length is not equal to 1. I also saw this on a time message:
,20050606 09:14
Looking at my log I find the missing Q for @YMM5, DIA, @ESM5, @NQM5, CMCSA in pre mkt this morning. I don't like to disturb my app during regular trading hours.
|