|
PureBytes Links
Trading Reference Links
|
Thanks to Scott who found an earlier Thread that identifies the problem and
solves it. Original thread is listed below from 'DB' at Dynastore.
Following the logic of DB's comments here's exactly what I did:
1) Dynastore for Bloomberg: Go into Portfolio / Edit symbol area. Select the
US T bond future symbol you have created. Double click. Check "Ignore Trade
volume" field at the middle right area of the edit window. Save and close.
2) Esignal: rather than fool eSignal from providing volume for the ZF Z2 or
ZB #F symbols by recreating them under a Stock category, I did with under a
"Index" Category. You will need to set up the electronic and regular CBOT
session times/ breaks in the TS edit symbol area and make other adjustments
consistent with the Bond futures characteristics. What's great is that the
new Dynaloader for eSignal took this new symbol and was able to download
about 60 days of tick data quickly. So I was able to start charting a
continous 24 hour T Bond futures symbol right away.
Here's DB' original thread on this issue forwarded by Scott....
> -----Original Message-----
> From: Scott Davis > Sent: Thursday, September 12, 2002 12:09 PM
> From: "DB"
> To: <omega-list@xxxxxxxxxx>
> Sent: Friday, August 17, 2001 11:56 AM
> Subject: Re: TS2000i bogged down
>
>
> > There is nothing to do with Windows 2000 - it's the same at Win 95, 98,
> Me,NT and 2000.
> >
> > The bug is in "DBC Subserver" and "DBC Online Subserver" of Global
>>Server and it's very simple: if the trade quote for the Futures symbol has
> > TradeVolume different from zero, it causes Global Server to get all
> > available CPU resources for some amount of time and this causes chart
> > flicks, hour glass mouse cursor etc.
> > Ex-Omega just hard-coded the old behavior of DBC Signal data feed - no
> trade volume for the Futures.
> >
> > This is not the issue for any other kind of symbols, so you may add your
> "ES U1" to Global Server as STOCK (with the same settings - CME as the
> exchange, price scale, exchange settings etc) - and it will work
correctly.
> >
> > DB
----- Original Message -----
From: "Michael Holder" <mholder@xxxxxxxxxxxx>
To: "Omega-list@xxxxxxxxxx" <omega-list@xxxxxxxxxx>
Sent: Tuesday, September 10, 2002 10:01 PM
Subject: US Tbond all session tick charts suddenly corrupt TS2000i 's
> Yes.Really. Suddenly 24 hour US T bond tick data is causing TS2000i
charts
> to freeze both TS and Windows (2000). Its not just my machines, I am now
> sure. Symptoms began June this year. It is only the 24 hour version of the
T
> Bond contract that is causing problems. Symptoms are 100% processor speed
on
> powerfull and clean W2000 machines - dedicated for Trade Station
operation.
> Tick charts won't stay in mid horizontal scroll position, for instance-
they
> spring back to last tick position. Computer resources become fully maxed
out
> upon launch of a T bond tick chart, preventing even the insert of
> indicators.
> Here's how I know: I got the same symptoms on completely separate Trade
> Stations/ W2000 machines at different times with completely separate data
> sources, symbols and workspaces. First it happened through Bloomberg data
> via Dynastore on a duo processor PIII machine with loads of ECC RAM, and
> then later with eSignal data with the ZB U2 electronic symbol and/or the
ZB
> #F Continuous electronic symbol on a equally powerfull but separate W2000
> machine.
> I have the logs for errors with dlls effected. Shutdown of TS32.exe is
> usual result. These machines have / and still do run flawlessly before and
> in the absence of any 24 hour version of the T Bond contract. There were
no
> prior problems for 3 years with 24 hour T Bond contracts until June of
this
> year. I have tired numerous re naming of symbols/ overwriting of tick data
> and replacing of potentially corrupted workspaces - all with no effect.
>
> Anybody else having this experience ? I am now sure its something about
the
> data. I can't be the only 24 hour contract user for the US T bond out
there.
> Try it. Must be an all session tick data set in a raw ohlc price chart.
> Suggestions welcome.
>
> Mike Holder
> Toronto
>
|