|
PureBytes Links
Trading Reference Links
|
Dans un courrier daté du 27/06/98 23:07:55 ,Dennis Holverstott écrit :
<<
Pierre writes:
> TS5 will be Yk2 compliant after the beta.
Isn't that something one might want to beta test? More to the point,
since TS5 is "totally new" software, why wasn't it written to be Y2K
compliant from the outset? Sorry, but I just don't understand it. Can it
really be that big a problem?
>>
I dont knwo exactly, but this has to deal with the protection.
Usually, beta testers receive a temporary password for some couple of months.
The fact that the beta is not currently y2k compliant means only what it
means:
Its a beta, and the purpose of the beta is not to test the behaviour of the
software in the next century.
The main problem is to verify if it works today (this is also very important).
Y2k is a stupid problem regarding to such a software.
Who could believe that Omega will not make it compliant when released as it
was announced to beta testers.
The problem here is that these confidential information were spread on the
list and feed the prevaling paranoïa in the best case, the old revenge in the
worst case.
I also suspect that the yk2 problem is maybe related to the various data
source that TS uses (around 15, including realtime data). This may also
explain the delay for the TS4 patch and the delay for the TS5 compliance.
I guess that someone in Miami has been thinking of the problem.
<<
> The TS4 patch will be released after TS5.
<snip>
> My calendar shows 06/27/1998, so I do not worry about year 2000 for the
> moment.
> I do not care collecting contracts for the next century at this time.
Some people who actually use TS for *trading* care plenty. A number of
contracts, in particular LEAPS, which expire in 2000 are trading right
now.
>>
So, the need of the pach or them is more urgent than what I supposed.
As we have no way to avoid the server to remove the "expired" mark in the
portfolio (making the data collection impossible), maybe the patch is not a
stupid idea.
Or at least a patch that allows to unmark an expired contract in the
portfolio.
Maybe there is a fix that could be worth to be tried now:
The current problem exists to collect futures that have a symbol name not
accepted by TS because it do not follows the year symbology currently used by
TS.
An internal routine in the server should declare it expired, I suppose.
The idea could be to add a new symbol on the considered market, but not under
the category future, but as a stock for example (you must use the corect feed
name ,including symbol root, month and year code (do it in the symbole
universe setup, then add the symbol to the portfolio).
In this case, th expired contract potfolio routine will not be in use, and the
symbol could be collected even if its name is beyond year 2000.
Try this with category stocks, index or even forex (use it on the same market)
Maybe one of these category wil be accepted.
If it works, this should allow to trade the considered contract before year
2000.
If it does not, it will have allowed me to write dummy things too.
I can, you knew ?
<<
> They (Omega) are late on their planning.
On that we agree. :-)
>>
Maybe not.
I suspect that you are secretly thinking "very late".
Sincerely,
Pierre Orphelin
www.sirtrade.com
|