Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)




"Boy, probably spent a thousand hours trying to get ******* API to work right. And now two hours to have something running with IQFeed. Hmmm, guess I was pretty stupid to fight rather than switch all this time. And have gotten more customer service from you guys already than total from them… in five years." - Comment from Jim
"I just wanted to say how happy I am with your service. I was able to download the API docs last week and I was able to replicate Interactive Brokers historical bar queries and realtime bar queries over the weekend. That was about one of the fastest integrations that I've ever done and it works perfectly!!!!" - Comment from Jason via Email
"I started a trial a few weeks back before the market went wild. DTN.IQ didn’t miss anything and beat my other provider. I decided to stay with you because of the great service through all the volatility." - Comment from Mike
"With HUGE volume on AAPL and RIMM for 2 days, everyone in a trading room was whining about freezes, crashes and lag with *******, RealTick, TS and Cyber. InvestorRT with IQFeed was rock solid. I mean SOLID!" - Comment from Public IRC Chat
"DTN feed was the only feed that consistently matched Bloomberg feed for BID/ASK data verification work these past years......DTN feed is a must for my supply & demand based trading using Cumulative Delta" - Comment from Public Forum Post
"Just a thank you for the very helpful and prompt assistance and services. You provided me with noticeably superior service in my setup compared to a couple of other options I had looked at." - Comment from John
"I am a hedge fund manager here. It’s funny, I have a Bloomberg terminal and a Bridge feed, but I still like having my DTN feed!" - Comment from Feras
"I used to have *******, but they are way more money for the same thing. I have had no probs with data from DTN since switching over." - Comment from Public Forum Post
"It’s so nice to be working with real professionals!" - Comment from Len
"Interactive Brokers tick data was inconsistent, so I have switched to using DTN exclusively. It is great to no longer have to worry about my datafeed all day long." - Comment from Philippe
Home  Search  Register  Login  Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »Archive (2017 and earlier) »IQFeed Developer Support »SELECT UPDATE FIELDS
Author Topic: SELECT UPDATE FIELDS (7 messages, Page 1 of 1)

ericm
-DTN Evangelist-
Posts: 145
Joined: Mar 31, 2008


Posted: Apr 4, 2013 09:53 AM          Msg. 1 of 7
I am testing some new software on 5.0.0.9 and am having some problems with selecting the fields for P and Q records. I send the following command:

"S,SELECT UPDATE FIELDS,Symbol,Change,Total Volume,High,Low,Bid,Ask,Bid Size,Ask Size,Open Interest,Open,Delay,Last Trade Date,Market Open,TickID,Most Recent Trade,Most Recent Trade Size,Most Recent Trade TimeMS,Most Recent Trade Conditions,Message Contents,\r\n"

and get the following response:

"S,CURRENT UPDATE FIELDNAMES,Symbol,Most Recent Trade,Most Recent Trade Size,Most Recent Trade TimeMS,Most Recent Trade Market Center,Total Volume,Bid,Bid Size,Ask,Ask Size,Open,High,Low,Close,Message Contents,Most Recent Trade Conditions"

1. Note that the following fields requested are not received:
Change, Open Interest, Delay, Last Trade Date, Market Open, and TickID.

2. The following fields were received but not requested:
Most Recent Trade Market Center, Close.

3. The fieldnames are in a different order from that requested.

My old software (running concurrently) uses 4.9 and is working correctly. Any ideas about where I might start looking for problems?

Eric

DTN_Steve_S
-DTN Guru-
Posts: 2093
Joined: Nov 21, 2005


Posted: Apr 4, 2013 10:18 AM          Msg. 2 of 7
Eric, when switching to protocol 5.0, the default fieldset you are using automatically changes and you get a S,CURRENT UPDATE FIELDNAMES message indicating the new default fieldset (which is the one you are saying you are getting as a response to your request).

So, if you are sending the following:

S,SET PROTOCOL,5.0\r\n
S,SELECT UPDATE FIELDS,Symbol,Change,Total Volume,High,Low,Bid,Ask,Bid Size,Ask Size,Open Interest,Open,Delay,Last Trade Date,Market Open,TickID,Most Recent Trade,Most Recent Trade Size,Most Recent Trade TimeMS,Most Recent Trade Conditions,Message Contents,\r\n

you can expect the following responses:

S,CURRENT PROTOCOL,5.0\n
S,CURRENT UPDATE FIELDNAMES,Symbol,Most Recent Trade,Most Recent Trade Size,Most Recent Trade TimeMS,Most Recent Trade Market Center,Total Volume,Bid,Bid Size,Ask,Ask Size,Open,High,Low,Close,Message Contents,Most Recent Trade Conditions\n
S,CURRENT UPDATE FIELDNAMES,Symbol,Change,Total Volume,High,Low,Bid,Ask,Bid Size,Ask Size,Open Interest,Open,Delay,Last Trade Date,Market Open,TickID,Most Recent Trade,Most Recent Trade Size,Most Recent Trade TimeMS,Most Recent Trade Conditions,Message Contents,\n

My guess is that you are processing the first one and ignoring the second one (which is the one that will be using.

ericm
-DTN Evangelist-
Posts: 145
Joined: Mar 31, 2008


Posted: Apr 4, 2013 10:24 AM          Msg. 3 of 7
You are correct. Thanks, Eric

Eric

XoCe
-Interested User-
Posts: 9
Joined: Sep 19, 2013


Posted: Nov 19, 2013 12:59 PM          Msg. 4 of 7
Do I understand right, that one "S,CURRENT UPDATE FIELDNAMES" message is sent always, regardless of anything?
And if I want to send "S,SELECT UPDATE FIELDS" command I need to skip the first response and to process the second one only?

There is nothing about the first "S,CURRENT UPDATE FIELDNAMES" message in the documentation...

DTN_Tim Walter
-DTN Guru-
Posts: 1238
Joined: Apr 25, 2006


Posted: Nov 19, 2013 01:17 PM          Msg. 5 of 7
There are a couple of pages that help define the update messages. You may have an older copy of the documentation causing their omission, but they are also found at;

http://www.iqfeed.net/dev/api/docs/Level1viaTCPIP.cfm
http://www.iqfeed.net/dev/api/docs/DynamicFieldsets.cfm

S,CURRENT UPDATE FIELDNAMES,.... is sent when a protocol is changed and when a update fields command is issued. So the first will be from setting the protocol, where it goes to the 5.x default set, the second return is from your requested set of fields.

Tim

XoCe
-Interested User-
Posts: 9
Joined: Sep 19, 2013


Posted: Nov 19, 2013 02:43 PM          Msg. 6 of 7
Tim,
Thank you for your answer, now it's clear.

But if to be honest, I can't find no word about the case you have specified, that "S,CURRENT UPDATE FIELDNAMES,.... is sent when a protocol is changed". I have checked both of the links you have mentioned.

DTN_Tim Walter
-DTN Guru-
Posts: 1238
Joined: Apr 25, 2006


Posted: Nov 19, 2013 02:48 PM          Msg. 7 of 7
I'll get an update made to the SET PROTOCOL documentation, thanks for letting us know.

Tim
 

 

Time: Sat May 18, 2024 10:42 PM CFBB v1.2.0 10 ms.
© AderSoftware 2002-2003