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)




"I noticed that ******* quotes locked up shortly after the interest rate announcement yesterday while yours stayed stable." - Comment from Ron in Utah
"This is an excellent value, the system is generous (allowing for 500 stocks) and stable (and really is tick-by-tick), and the support is fantastic." - Comment from Shirin via Email
"I ran your IQFeed DDE vs. my broker vs. a level II window for some slow-moving options. I would see the level II quote change, then your feed update instantaneously. My broker's DDE, however, would take as much as 30 seconds to update. I am not chasing milliseconds, but half a minute is unacceptable." - Comment from Rob
"IQFeed version 4 is a real screamer compared to anything else I have seen." - Comment from Tom
"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
"Version 4.0.0.2 has been working well for me and I appreciate that it is now a much tighter client to work with. I feel I can go to press with my own application and rely on a stable platform" - Comment from David in IA.
"I have been using IQFeed now for a few years in MultiCharts and I have zero complaints. Very, very rare to have any data hiccups or anything at all go wrong." - Comment from Public Forum
"I will tell others who want to go into trading that DTN ProphetX is an invaluable tool, I don't think anyone can trade without it..." - Comment from Luther
"If you want customer service that answers the phone, your best bet is IQFeed. I cannot stop praising them or their technical support. They are always there for you, and they are quick. I have used ****** too but the best value is IQFeed." - Comment from Public Forum
"I was with ******* for 4 years at $230 a month, this is a huge savings for me, GOD BLESS YOU PEOPLE," - Comment from T.S. via Email
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
Viewing User Profile for: arth_trader
About Contact
Joined: Apr 16, 2014 09:03 PM
Last Post: Jul 25, 2016 06:52 AM
Last Visit: Jul 25, 2016 08:16 AM
Website:  
Location:
Occupation:
Interests:
Avatar:
AIM:
ICQ:
MSN IM:
Yahoo IM:
Post Statistics
arth_trader has contributed to 5 posts out of 21191 total posts (0.02%) in 3,676 days (0.00 posts per day).

20 Most recent posts:
IQFeed Developer Support » Settle trades not chronological Jul 25, 2016 06:52 AM (Total replies: 1)

I was trying to get historical tick data for GC (Gold future). I noticed that a settle trade (basis for last='S') with an older time stamp came after a trade with basis for last='C'. I was getting historical tick data with oldest to newest order. Is this natural or an error? It was messing up my historical tick database.
The time stamp in question was 2016-02-08 14:14:59.

Thanks.


What is the definition of trading hours for historical tick data availability ( 8 days vs 180 days) for futures? For example for LE (Live Cattle) is the time window for getting 180 days tick data outside of the LE trading hours (8:30am CT - 1:05pm CT) or the standard NYSE trading hours?


I was trying to write a function to retrieve the earliest date tick data is available for a symbol. I am sending a HTT request with begin date as a very old date ( 20000101 000000), end date as blank, data direction as oldest to newest and maxdatapoints as 1. Its only returning the latest tick.

But if I supply only the end date with trial and error it does return the oldest date. Is there any other simple way?

Thanks.


Thanks Tim.


I am trying to get historical tick data using the Java API (IQFeed version 5.2.1). Here is the code snippet:

String command = "HTX,IBM,5,,testid,\r\n\n";
// String line;
C_LookupIQFeed_Socket.brBufferedWriter.write(command);
C_LookupIQFeed_Socket.brBufferedWriter.flush();

while ((line = C_LookupIQFeed_Socket.brBufferedReader.readLine()) != null) {
logger.debug("HistoryRecord={}", line);
}

It prints the output till the last record ("!ENDMSG!,"), but hangs at the readLine() thereafter i.e. the readLine() is never returning null after the last record. I have tested this on the samples provided, same thing happens. Any idea? Is it possible that the server is not sending a new line after the last message. Is there any other way to handle this?

Thanks.


Time: Wed May 8, 2024 9:16 AM CFBB v1.2.0 8 ms.
© AderSoftware 2002-2003