IB, Globex and Limit / Stop Orders

Discussion in 'Interactive Brokers' started by aphexcoil, Sep 25, 2002.

  1. This is true, positive slippage can also occur when there is a delay in execution. But as a professional trader, one has to ask the question: who wants this uncertainty in their life? With a stop order native on Globex, 99 times out of a 100 you will be filled at that exact price. Your risk is firmly pre-determined.

    Even if the delay is only milliseconds, it also doesn't get around the problem of having your order ranked at the bottom of the priority list as far as Globex is concerned when filling it. Nor can it alleviate the risk that IB datafeed problems at the 'wrong' time can really mess you up ...with an unexecuted order.

    I stand by my comments that the way IB handles stop orders is a major negative for the futures trader. They should fix it ASAP!
    #11     Sep 25, 2002
  2. They are trying to get you confused. :D

    Globex orders look like this on my TWS ( build 775.7 ) :

    #12     Sep 25, 2002
  3. josbarr


    #13     Sep 25, 2002
  4. Carl,

    This isn't anywhere in the API documentation that I can see. I am using the OpenOrder method and don't see a flag or setting for OCO/OCA orders.

    I'm assuming that I have to program that distinction within my program -- so my program will cancel one order once the other side is executed.

    I'd like to bypass the entire IB Java-entry system but I don't think it is possible. It would probably save a few milliseconds.
    #14     Sep 25, 2002
  5. I'm not sure which API you are using. For example, I use the C++ sockets version. I use the placeOrder() call and one of the parameters for this call is an Order. The definition of the Order class includes a CString ocaGroup. If I modify this field before sending in my order, then the order will go in with that OCA identifier.

    If I send two orders in with the same OCA identifier, they operate as if they were manually entered with the same OCA identifier. Namely, when one gets cancelled, the other does too. When one gets filled, the other one decrements its number of shares according to the number of shares filled.

    #15     Sep 25, 2002
  6. hi all,

    stop limit orders for the s+p eminis now rest at globex (status green). "regular" stops still rest at IB servers. confirmed by helpdesk. bulletin should be on the way shortly (also confirmed by helpdesk :)).

    #16     Sep 25, 2002
  7. Doesn't Globex support resident stop orders? In a fast market, it could blow right past your stop-limit order.

    Otherwise, I feel better having my program keep track of the market and placing a market order when the stop gets reached.
    #17     Sep 25, 2002
  8. Carl,

    Thanks! I'll double check the manual. Maybe I overlooked this feature.
    #18     Sep 25, 2002
  9. Quah


    Your stop price and the limit price don't have to be the same - so just set the stop price to the price you want it to activate on, and set the limit price a few points higher or lower so you essentially end up with a market order (a regular stop) that resides on globex.
    #19     Sep 25, 2002
  10. Hey def, is automatic stop placement for every open position initiated something that could be a future option at IB?
    #20     Sep 25, 2002