|
PureBytes Links
Trading Reference Links
|
this is old news, many months old. and welcome to the wacky world of
y2k weirdness :)))
this list's very own jim m.,ie, tagteam, NOT omega support, first
suggested the fix outlined below and verified by others (including
myself, thank you very much). omega support dropped the ball badly on
this one.
TJ
the omega-list, best tech advice on ts that money can buy; oops,
scratch that, this list is FREE <g>
---Joseph Biran <j.biran@xxxxxxxxxxxxx> wrote:
>
> This is very interesting. The mysterious contracts are all
> related to
> *Jan 99* expired commodity contracts! A year before 1/2000.
>
> Are you going to be providing me with replacement data for
> the whole 1999 year for expired contract then??
>
>
> Joseph Biran
> ________________________________________________
>
>
> -----Original Message-----
> From: TechSupp [mailto:TechSupp@xxxxxxxxxxxxxxxxx]
> Sent: Monday, March 15, 1999 10:42 AM
> To: 'j.biran@xxxxxxxxxxxxx'
> Subject: Mysterious Expired symbols in the portfolio (0315mj/)
>
>
>
> Dear Mr. Biran,
>
> You are experiencing a Y2K issue. You can collect and save data
> for year
> 2000 futures contracts. To do this you will need to disable the
> morning
> update. Below are the list of things that you will need to do
> manually with
> the morning update disabled until the Y2k patch is released.
>
> Workaround for Year 2000 Contract Expiration Issue
>
> This applies to real-time and delayed Futures and Options Traders
> only.
>
> The information below explains the procedures accomplished by the
> Morning
> Update. You will not encounter any problems if you decide not to
> run a
> Morning Update.
>
> We apologize if the Server manual gives the impression that it is
> unsafe to
> disable this feature. Although the Morning Update provides a less
> time
> consuming way to perform routine maintenance automatically, these
> procedures
> can be done manually. Performing these procedures manually can be
> helpful if
> the Morning Update interferes with the collection of data. The
> procedures
> are as follows:
>
> - Deleting Log File Information
>
> The log files record information displayed in the System Status,
> Morning
> Update and Daily Data Collection windows. These files are
> "cleaned" by
> deleting any information older than 5 days. (5 is the default
> number of days
> specified. This may be changed by the user.)
>
> These files may be deleted manually or by adding a line to your
> AUTOEXEC.BAT. They will be rebuilt upon opening the server.
>
> These log files are located in:
>
> OMEGA\SERVER\BTC for BMI
>
> OMEGA\SERVER\SIG for DBC SIGNAL
>
> OMEGA\SERVER\CSK for S&P COMSTOCK
>
> The files are:
>
> OSERVER.LOG for the System Status Log window
>
> MORNING.LOG for the Morning Update Log window
>
> DAILY.LOG for the Daily Data Log window
>
> To delete the files manually:
>
> 1. Use the Start - Find - Files or Folders menu sequence to
> access the Find:
> All Files dialog.
>
> 2. Enter the name of the file, OSERVER.LOG, MORNING.LOG or
> DAILY.LOG into
> the Named edit box.
>
> 3. Click OK. The file will be listed and highlighted.
>
> 4. Use the File - Delete menu sequence to delete the file.
>
> If you would like to have these files deleted automatically when
> you reboot
> your computer you can add the following line to your AUTOEXEC.BAT
> file.
> Please note that the lines are written specifically for the data
> provider
> you use. The 1st line is for BMI users, the 2nd for DBC SIGNAL
> and the 3rd
> for S&P COMSTOCK.
>
> DEL C:\OMEGA\SERVER\BTC\OSERVER.LOG MORNING.LOG DAILY.LOG
>
> DEL C:\OMEGA\SERVER\SIG\OSERVER.LOG MORNING.LOG DAILY.LOG
>
> DEL C:\OMEGA\SERVER\CSK\OSERVER.LOG MORNING.LOG DAILY.LOG
>
> - Deleting Old Data
>
> Another maintenance procedure handled during the Morning Update
> is the
> removal of data older than the number of days you specified to
> save. To
> delete data use the File - Delete menu sequence from the Omega
> Server to
> specify the date range for the symbols you want to delete. We
> recommend you
> do this periodically.
>
> - Data File and Symbol Portfolio Backup
>
> Backing up the Symbol Portfolio and the tick data file is another
> procedure
> performed during the Morning Update. Whatever method you use for
> your
> regular backups, such as tape backup, zip drive or removable hard
> drive,
> will also backup your tick data file and portfolio list.
>
> - Symbol Portfolio Maintenance
>
> The Morning Update adds new future symbols, renames expired
> future and
> option symbols with an archive name and deletes expired future
> and option
> symbols. To do this manually, use the steps listed below.
>
> 1. To delete a symbol from the Symbol Portfolio, highlight the
> symbol and
> hit the Delete button. Please note that when you delete a symbol
> from the
> portfolio you also delete the data for that symbol.
>
> 2. To add the next contract month for a future symbol, highlight
> the current
> contract and click the Next Month button.
>
> 3. To rename a symbol, highlight the symbol and click Rename.
>
> I hope this provides the necessary information to make an
> informed decision
> in this matter and allows you to feel more comfortable in
> disabling the
> Morning Update.
>
>
> If you need further assistance, please feel free to contact us.
> Thank you for your continued support.
>
> Mark J
> Technical Support
> Omega Research Inc.
>
> -----Original Message-----
> From: Joseph Biran [mailto:j.biran@xxxxxxxxxxxxx]
> <mailto:[mailto:j.biran@xxxxxxxxxxxxx]>
> Sent: Sunday, March 14, 1999 3:51 PM
> To: OmegaResearch Tech Support-all
> Cc: List - Code List (E-mail); List - RealTrders
> (e-mail); List - omega-list@xxxxxx <mailto:omega-list@xxxxxx> .
> com (e-mail)
> Subject: Mysterious Expired symbols in the portfolio
>
> I apologize if you receive 3 copies of the same message.
> Would you know why there are suddenly so many Expired
> Symbols in my portfolio whose names are XYZ90 and have no data in
> them?
> For instance I have SPH90 (Expired but empty) but no SPH99.
> Also, I have SP0H (Expired) with some sprinkles of data between
> 01/12/99 and
> 02/25/99 (1 tick per random date).
> Is this part of the wonderful Y2K problem?
> Joseph Biran
> ________________________________________________
>
>
|