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: 2096
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: 2096
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.
|