[ts-gen] RE: TWS market data permissions
R P Herrold
herrold at owlriver.com
Tue Nov 14 13:34:52 EST 2006
On Tue, 14 Nov 2006, our UK debian user wrote:
> Here you go -
> VOD LSE STK
> DRX LSE STK
> Z LIFFE IND
> TSB DEC06 5.5 P LIFFE OPT
> Some that we may have feeds in common -
> EUR IDEALPRO CASH
The specification as it appears on your TWS GUI
trading screen probably looks like this:
http://www.trading-shim.org/screenshots/061114-uk-symbols.jpg
but as you can see, I do not have trading permissions on LSE,
and so no market data appears. More on that in a moment.
The non-US options trading exchanges are a harder problem than
just paying for a market data Subscription; I suspect that the
legally permissible 'tradeables' which IB is permitted to
offer and are available for a UK resident differ from those
available for a US resident. I cannot even get visibility of
the LIFFE OPT rights. I will speak to IB TAC and see if I can
get a paper account enabled with those rights for development
work.
What Trading Permissons entry do you have, similar to the list
I posted yesterday from my experience, to obtain STK trading
rights on the LSE? I think it is:
"Non-professional LSE Level I+ 10.00 GBP"
but am not sure. I listed what I was then using toward the
middle of:
http://www.trading-shim.org/pipermail/ts-general/2006-November/000028.html
> I'm looking forward to you posting a simple example, I tried
> hacking the database, putting something in Definition and
> Security, with what I thought was the right keys, but
> needless to say, it didn't work.
After posting a currency Market Data, History and Order
Management example through the Command channel, next I think I
will probably post a series of inserts to amend the database
in a consistent fashion, and one which we can carry forward,
stable as to assigned 'UID' values so that we all remain 'on
the same page' as to what is present; the alternative is to
post the series of SELECT, which run through the JOIN's to
yield the ContractID (which I also need to document [it is
just rather much more complex to explain])
As we each can see:
EUR.IDEALPRO.USD/EUR Cash
EUR.IDEALPRO.GBP/EUR Cash I think I can construct that
example with the permissions we each have, and I will turn to
that in a moment after releasing this email. In the usual
case, there are not many trading strategies which I can think
of which would call for having two base currency crosses on
the last (Cash) tuple element [none come to mind, actually, as
all such an approach does is expose one to an additional 'exit
to base' transaction fee, and possible slippage, to no benefit
to doing a paired trade on the Underlying side directly]
-- As a USD base currency user, I would simplify to this to
display both EUR and GBP:
EUR.IDEALPRO.USD/EUR Cash
GBP.IDEALPRO.USD/GBP Cash
and you using GBP would simplify to:
EUR.IDEALPRO.GBP/EUR Cash
USD.IDEALPRO.GBP/USD Cash
to obtain identical functionality.
Again, thank you for the feedback and development help; we had
anticipated that non-US users would assist us by exposing
assumptions and limitations in our understandings, data and
implementation; we are quite pleased with the help we are
receiving.
-- Russ Herrold
More information about the ts-general
mailing list