[This message was posted by anand pandey of Deutsche Bank <[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/e9b64e96 - PLEASE DO NOT REPLY BY MAIL.]
> > > Hi, > > > > > > Tag 41 is required for C/R request messages, you might want to > > > check that. > > > > > > > > > > Thanks all, Maybe it is the tag 17=0 because we have replied with > > > > tag11 as well. > > > > 04-FEB-9:22:21:628,TX,"8=FIX.4.29=21235=849=EFG56=ABCD34=346652=20090204- > > > > 16:22:65986111=101598:1233764525148:Replace17=020=0150=539=555=IB- > > > > 920010122=154=138=200040=115=USD59=047=A32=031=0151=200014=- > > > > 06=010=013" > > > > > > > > > > > > > > > Guys, > > > > > > > > > > > > > > Please help, we are the broker EFG, ABCD send an order and > > > > > > > somehow they receive a rejection. I cant find out why - > > > > > > > thought T41 but its not, and not even T37. Please help > > > > > > > > > > > > > > 2009-02-04 11:26:26,143 INFO out.ABCD - >2817 > > > > > > > OrderCancelReplaceRequest > > > > > > > (8=FIX.4.2^A9=179^A35=G^A49=ABCD^A56=EFG^A34=2817^ A52=20090204- > > > > > > > 142:e^A54=1^A55=IBM^A65=US^A48=459200101^A22=1^A60=20090204- > > > > > > > 16:26:26^ A38=2000^A40=1^A21=3^A10=075^A) > > > > > > > > > > > > > > 2009-02-04 11:26:40,775 INFO in.EFG_ABCD - <3471 > > > > > > > ExecutionReport > > > > > > > (8=FIX.4.2^A9=212^A35=8^A49=EFG^A56=ABCD^A34=3471^ A52=20090204- > > > > > > > 16:26:3^A11=101599:1233764786142:Replace^A17=0^A20=0^A150=5- > > > > > > > ^A39=5^A55=IBM^A65=US^A48=459200101^A22=1^ > > > > > > > A54=1^A38=2000^A40=1^A15=USD- > > > > > > > ^A59=0^A47=A^A32=0^A31=0^A151=2000^A14=0^A6=0^A10=020- > > > > > > > ^A) > > > > > > > > > > > > > > 2009-02-04 11:26:40,775 ERROR handler.ExecutionHandler - > > > > > > > PROCESSING RESP: 101599:1233764786142:Replace, 5, 0, null, > > > > > > > null, Repl: true, Cancel: false > > > > > > > > > > > > > > 2009-02-04 11:26:40,780 ERROR fix.MsgProcessor - Business > > > > > > > Reject Msg: Reason: 0, txt: Order with ID does not exist. > > > > > > > id: 'null' > > > > > > > > > > > > Hi, > > > > > > > > > > > > It seems Tag 41 is missing in replaced ER ( 39=5 & 150=5 ) and > > > > > > that resulted in Business reject. > > > > > > > > > > > > Regards, kumar > > > > > > > > > > > > > > > tag 41 is expected,but if tag 41 is not ur issue then tag 17 = 0 > > > > > seems unacceptable... > > > > In 35=G request from ABCD, T11 and T41 is missing which are > > mandatory tag. Without Tag41 in Replace request, you can identify > > the order that needs to be replaced in your system. That would have > > caused your system to send business rejection to ABCD, which is > > correct. Check it out. > > Apology. Correction -> Application can not identify order without 41 tag Hi All, I wonder here how this scenario reaches upto Business Reject level. WHy there is one 39=5/150=5 ER before. In such replace requests there should be a direct 39=8 reject occurs. Database error is very much expected before the message construction. Please check this out in your system. [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 -~----------~----~----~----~------~----~------~--~---
