Also, have you set on the cut off date yet? I haven't tested my application against the new server yet. My application is an option trading system, it needs to have a valid option chain.

Option Chains are not currently working. I will get our server team checking into this.

it seems SSO still isn't working. Have you heard anything from your server team?

SSO is working for me. Option Chains have also been enabled. Are you still having problems?

I tried VIX last night. The option chain I got has May 07 series and no July 07 series. I couldn't confirm it (I am at work) at this moment. Could you double check if the option chain has latest series issued by exchange?

Right now, I am gettin the same data from an Option chain lookup on Pre as I do on our production servers.

However, SSO would be a symbol lookup (not an option chain lookup).

I can confirm that there is a difference between the results returned here but I will need to do some more digging before I can find the cause.

Hi Steve, I am aware of the difference. I use SSO because it is based on simple string matching, my program will filter out the correct series. Where as with OEA, I found out sometimes it could miss option chains, especially, if an underlying has multiple roots. I've been using SSO as option chain lookup for 4 years, it is simple and has less dependencies on server logic.

Could you double check OEA command on new pre-production server? It seems new pre-production server returns only near money option series.

I am still not noticing any differences between the production and pre-production servers for the OEA command.

There are a few differences when using the OFO as well as the SSO commands but as far as I can tell this is due to the Pre-Production servers still having some expired contracts returned (the Pre servers are returning more data than the production servers).

Can you give me an example of the output where you are seeing discrepancies?

OEA,SPY,1,4; pre-production server returns much shorter list :-)

Yes, you right, SSO returns July 07 series. It wasn't the case last week, though.

BTW, do you know why new server returns expired series?

Hi Steve, I tried to download option chains from new server, but IQFeed client crashed before it can finish. With few underlyings that finished, I found CUB is missing strike 30. BCO doesn't have LK/XK. Could you check, thx.

Our server team is looking into this.

Hi Steve, have you heard anything? the switch over date is approaching, I need to get the option chain before I can test my application

This is not yet fixed. I believe the server team has identified what is causing the problem but have not yet gotten a fix implemented.

This should be resolved. Let me know if you still see any problems.

It seems SSO still returns expired contracts.

The expired contracts is an issue that should be isolated to running in the pre-production environment and should not be an issue once this is rolled out onto the production servers.

We will do some more testing with this to verify this is the case.

Hi Steve,

I am still seeing this? do you know if I need to wait till Aug to not receive July series?

Thanks,