|
PureBytes Links
Trading Reference Links
|
As I attempt to simply bring Spx.omz from ts4 to ts5, when I import the
data, ts5 calls the symbol to import "sxop". If one attempts to finish the
import, it says there is no such symbol. My server has no such symbol name,
but it still wants to call spx by that name, then say it does not exist.
Real SMOOTH!!!!!! Making the process of bringing data from an older platform
to a newer one so difficult (apparently) seems to be an oversight of the nth
degree. If Bob is having difficulty with this also, you can bet 99.9999% of
other ts5 users are too.
Any ideas?
Don
----- Original Message -----
From: "Bob Fulks" <bfulks@xxxxxxxxxxxx>
To: <omega-list@xxxxxxxxxx>
Sent: Thursday, June 15, 2000 2:47 PM
Subject: RE: Importing TS4.0 OMZ data into TS2000i
> Omega Tech Support responded to my post to this list with the
> attached reply. He said it was OK to post his response here so I am
> doing so in case others have the same problem.
>
> Bob Fulks
>
> -----
>
> Mr. Fulks,
>
> Symbols expired in 4.0 will not be imported by default into the
> GlobalServer. For expired symbols, the GlobalServer Symbol Name must
> EXACTLY match the name in the omz file. For example you could rename
> the symbol in the GlobalServer (DSP M8) to the version 4.0 expired
> name (DSPM98) in order for the data to be imported. A better option
> is to rename the symbol in the 4.0 server to its unexpired name. Then
> it will be correctly matched up with the unexpired symbol in the
> GlobalServer.
>
> Transferring unexpired to unexpired is fine, but any expired 4.0
> symbol will not be automatically matched in the GlobalServer.
>
> I would not recommend expiring the symbols in the GlobalServer as the
> data will not be imported properly unless you change Unexpire and
> rename the symbol. First, you would need to edit the symbol and
> change the Last Trading Date and Expiration Data using the Edit
> button on the Future contract tab. You would have to enter a date in
> the future, unexpire the symbol using the Tools | Unexpire Symbols
> menu, and finally rename the symbol to the 4.0 archive name to be
> imported. Renaming the 4.0 symbols and importing into your unexpired
> symbols works much better.
>
> Data is not deleted when a symbol is expired. Data that falls outside
> the History to save days specified will be deleted. If you want to
> retain this data, you should increase the Num Days setting for the
> symbol's intraday data resolutions.
>
> The Unexpire Symbols command only works when the Expiration and Last
> Trading Dates are beyond the current date. The command can be used to
> restore symbols if the nightly maintenance expires symbols due to a
> bad date stamp. The date must be reset back to the correct date and
> then the command can be executed. For example, a date of 1/1/2005 is
> sent by the datafeed and the nightly maintenance expires the Sept
> 2000 S&P contract. Once the date is reset back to today's date, the
> unexpire command can be used to restore the symbol to the correct
> name.
>
> Please let us know if you have any further questions.
>
> Regards,
>
> Kevin Fortner
> Support Services Department
> Omega Research, Inc.
>
> ----
>
> Bob Fulks responded:
>
> Thank you. I will try it.
> Do you mind if I post your response to the Omega List?
> Bob Fulks
>
> ----
>
> Kevin Fortner replied:
>
> Mr. Fulks,
>
> If you believe that it would be helpful to other users, feel free to do
so.
> Please let us know if you have any further questions.
> Regards,
> Kevin Fortner
> Support Services Department
> Omega Research, Inc.
>
>
|