[This message was posted by Mahesh Kumaraguru of <[email protected]> to the "4.2 Changes" discussion forum at http://fixprotocol.org/discuss/5. You can reply to it on-line at http://fixprotocol.org/discuss/read/da100451 - PLEASE DO NOT REPLY BY MAIL.]
> > Guys, > > > > Please shed the light out for me. If I understood for an Ack we can > > have Tag20=0 and 17=X otherwise to have an ExecID= 0 we must have > > ExecTransType=3. > > > > We have sent tag17=12345 and tag20=0 but this wasnt accepted by the > > counterparty, I dont know why?. > > > > > > > > Also on another test we have sent ExecID Char 17 0 ExecTransType Char > > 20 This is wrong how can I explain and solved this. > > > > Thanks for your help > > Hi , I think you should give some more information about your issue. > 20=0 only goes in status request response. which is just impulsive thing > anywhere. Have you checked that the ER was a Status request response. > check 35=H message, if it isin response it would go like that. [Quote from http://fixprotocol.org/FIXimate3.0/en/FIX.4.2/tag17.html] 17 (ExecID) String Unique identifier of execution message as assigned by broker (will be 0 (zero) for ExecTransType=3 (Status)). Uniqueness must be guaranteed within a single trading day or the life of a multi-day order. Firms which accept multi-day orders should consider embedding a date within the ExecID field to assure uniqueness across days. [End Quote] [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 -~----------~----~----~----~------~----~------~--~---
