DTN IQFeed, DTN.IQ, DTN ProphetX Support Forums

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 had always used ******* but for the past 2 weeks have been trying DTN IQFeed. Customer support has been extraordinary. They call just to make sure your problem hasn't recurred." - Comment from Public Forum

"Everything is working great ! Very impressive client. The news refreshes better and is more pertinent than the ******* feed I paid $ 100/month for. I Also like the charts a lot." - Comment from Leon

"I just wanted to let you know how fast and easy I found it to integrate IQFeed into our existing Java code using your JNI client. In my experience, such things almost never go so smoothly - great job!" - Comment from Nate

"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

"Can I get another account from you? I am tired of ******* going down so often" - Comment from George

"Excellent datafeed !!!" - Comment from Arely

"The service is great, I see a noticeable improvement in my volume profiles over [broker]'s data feed" - Comment from Larry

"I am very pleased with the DTNIQ system for quotes and news." - Comment from Larry

"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

"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.

Home

Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather

DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter

»Forums Index »Archive (2017 and earlier) »IQFeed Developer Support »chained RBOB futures data begins 1995, but cannot access individual daily contracts before QRB

Author	Topic: chained RBOB futures data begins 1995, but cannot access individual daily contracts before QRB (3 messages, Page 1 of 1)
shkim -Interested User- Posts: 4 Joined: Jan 27, 2017	Posted: Jan 19, 2019 04:31 AM Msg. 1 of 3 Hi, I have the following problem: requesting the maximal amount of daily data points for the NYMEX RBOB future "QRB#" I receive the earliest daily trade as of 1995-07-21. However, I always get "no data error" if I try to access the individual contracts before 2002-K (i.e., "QRBK01"), which means the oldest data point I get is 2001-05-02. Requesting futures before (for example, "QRBJ01", which would be the one before) results in "no data". This behavior is confirmed with the IQFEED Times & Sales application, i.e., I get the exact same results. Anyone any idea what is going on? Would really appreciate any hint... Cheers, Seong-Han
DTN_Stephen -DTN Guru- Posts: 453 Joined: Aug 22, 2014	Posted: Jan 22, 2019 01:42 PM Msg. 2 of 3 Sorry about the delay in our response. We have resolved the daily data for the individual contracts for example QRBJ01. You will now be able to request history from historical contracts you were concerned about on RBOB futures on the NYMEX exchange. Please let us know if there is anything else we can help you with. Stephen Shockey \| DTN \| Trading Customer Service Technical Support Phone: 800.779.7299 \| International 402.255.3918 stephen.shockey@dtn.com www.dtn.com
shkim -Interested User- Posts: 4 Joined: Jan 27, 2017	Posted: Jan 23, 2019 05:47 AM Msg. 3 of 3 Hi & thanks for the update/correction! I agree with so many other that the customer support response times are great... One more related thing: Requesting the 1min bars for the chained RBOB contract (symbol "QRB#") the earliest data is from April 2007. However, the individual contracts for 1 min data only start April 2008, i.e., 12 contracts are missing with regard to direct access. Would you mind correcting this as well, please?