[This message was posted by anand pandey of Deutsche Bank <[email protected]> to the "4.4 Changes" discussion forum at http://fixprotocol.org/discuss/17. You can reply to it on-line at http://fixprotocol.org/discuss/read/275eecfe - PLEASE DO NOT REPLY BY MAIL.]
> Hi, > > 35=3 is a session level reject, this is not application level reject but > engein level, for example if a FIX tag that is required for a spesific > msg type is missing, the order will be rejected by the engine. > > 39=8 is application level reject, orders that are rejected by the > trading application. > > 35=j is also application level reject, not session level. > > I hope this helps. > > Hi, We have lot of theoritical info for this on different pages in one good liner i would say if something which FIX engine cannot understand( config file of your engine doesn't know abt it) send 35=3( e.g 35=&) then if it is a functional mistake and tehir is a code in your system and have a proper error to send a rejection back( e.g. Limit price required for a limit 40=2 order) send 35=8,39=8,150=8,58=text and if their is no code in your application system for something which just somes new and not supported at app level but true at FIX send Business Reject ( 35=j). The best way to implement this is to have seperate error files in your application and reject pick from that. > > > Instead I would think both should send 35=8 , as per my understand of > > page 146, Business Message Reject, section. > > > > I believe 35=3 should be used between fix engines level communication > > instead. > > > > > Hi, > > > > > > Could someone please clarify, when do we use > > > (35=3)/(35=8)/(35=j) to reject an order.Please see examples > > > below. > > > > > > 1.Place an order(35=D) with orderType 40=200,which is not a valid > > > value as per FIX standards, So in this case I would expect 35=3 > > > ,with 373 = 5(Value is incorrect for this tag).I beleive this is > > > correct in rejecting at session level. > > > > > > 2.Place an order(35=D) with OrderType 40=4(Stop Limit), which is a > > > valid value as per FIX standard, but what if FIX client does not > > > support this,do we expect 35=3(with 373=5) or 35=8(with 39=8,150=8, > > > 103=0,58=Order Type not recognized) or 35=j(with 380=0,58=OrderType > > > not recognized).In this case, I wouldn't expect 35=3 since it passes > > > session level, but fails at application level.So once at application > > > level, which one would you prefer to use (35=j) or (35=8). > > > > > > FIX protocol says use 35=j when no other message can be used to > > > report reject at application level. > > > > > > Any help on this would be appreciated. > > > > > > Thanks, Jayaram [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
