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 like you guys better than *******...much more stable and a whole lot fewer issues." - Comment from Philip
"IQFeed version 4 is a real screamer compared to anything else I have seen." - Comment from Tom
"And by the way, have to say this. I love the IQFeed software. It's rock solid and it has a really nice API." - Comment from Thomas via RT Chat
"For anyone considering using DTN.IQ for a data feed, my experience with the quality of data and the tech support has been very positive." - Comment from Public Forum
"Excellent datafeed !!!" - Comment from Arely
"I have to tell you though that using the IQFeed API is about the easiest and cleanest I have seen for some time." - Comment from Jim
"Awesome response, as usual. It is a sincere and refreshing pleasure to do business with DTN, compared to your competition." - Comment from Ryan
"My broker in Davenport suggested I give you a try as he uses your service and says its the best." - Comment from Bill via RT Chat
"Thanks for the great product and support. During this week of high volume trading, my QuoteTracker + IQ Feed setup never missed a beat. Also, thanks for your swiftness in responding to data issues. I was on ******* for a few years before I made the switch over early this year, and wish I had done it a long time ago." - Comment from Ken
"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
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 »Option Names Have Underlying DB Key instead of Symbol
Author Topic: Option Names Have Underlying DB Key instead of Symbol (5 messages, Page 1 of 1)

EspressoE
-Interested User-
Posts: 30
Joined: Mar 8, 2006


Posted: Jul 2, 2007 11:05 PM          Msg. 1 of 5
When doing a search for option tickers, the names are coming back with some sort of DB key instead of the underlying ticker symbol.

For example, issuing a search for MSFT yields no results (because MSFT isn't in the name anymore), but searching by the option root, MQF does return:


MQF VW 59491810 OCT 2007 P 17.5


It should be:

MQF VW MSFT OCT 2007 P 17.5

EspressoE
-Interested User-
Posts: 30
Joined: Mar 8, 2006


Posted: Jul 2, 2007 11:20 PM          Msg. 2 of 5
Sorry, forgot to list the command that produced the results listed above:

SOS,MQF; 


The following command should have worked (and did on Friday):

SOS,MSFT; 

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


Posted: Jul 3, 2007 08:31 AM          Msg. 3 of 5
I am not seeing this currently. Judging by the other post on this issue it may have been something isolated to last night around the time that you posted. I will have our operations team look into why this might have happened.

EspressoE
-Interested User-
Posts: 30
Joined: Mar 8, 2006


Posted: Jul 3, 2007 08:47 AM          Msg. 4 of 5
I can tighten down the time frame a little. It did work on Sunday at 11:54 AM Eastern and did NOT work starting at 8:06 PM Eastern time through 11:46 PM Eastern time when I patched my software to work around the issue. At least the name seemed to be correct for the fundamental / update messages.

While I was having the problem, I tried disconnecting and reconnecting multiple times with the same results.

Upon looking at the data this morning, I can confirm that it is functioning correctly again.

Was this problem isolated to a single server? If it was an individual server, do you have any suggestions on how I could automatically choose a different server in case it happens again?

Thanks,

Eric

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


Posted: Jul 3, 2007 11:01 AM          Msg. 5 of 5
It turns out that this was somehting our operations department was aware of at the time it happend and the fix, I simply didn't get a notification of the issue.

No more problems are expected.
 

 

Time: Fri April 26, 2024 4:49 PM CFBB v1.2.0 8 ms.
© AderSoftware 2002-2003