[This message was posted by Hanno Klein of Deutsche Börse Systems <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/f6be5762 - PLEASE DO NOT REPLY BY MAIL.]
This sounds like a potential mis-use of the TCR message. The reason that 751 is only in the TCRAck is that only TCRAck should be used to accept or reject a TCR. You want to have 751 in the TCR and thus I assume you want to use TCR to reject a TCR, right? User-defined fields are supposed to enhance the standard message with additional attributes without changing the semantic of the entire message. Key fields such as XXXStatus, XXXReason should be used as intended and not substituted by UDFs. So, what is your business requirement that makes you want to use 751 in the TCR? Maybe one can solve the problem from that end and give you some advice that lets you remain compliant with the standard. > Hi all, > > I'm a newbie here..plz excuse if this is wrong place for my question. > > I am in the process of defining data-area(COBOL copybook) for > TradeCaptureReport(MsgType='AE'). Now I have a peculiar situation where > i need to use TAG '751'(TradeReportRejectReason), which is a valid tag > for TradeCaptureReportAck [type 'AR'] and not defined in the spec for > TradeCaptureReport [type 'AE']. So, Is it valid to define/use this '751' > TAG in my 'AE' messagetype layouot? If it is not valid, How do i > define/use TAG '751'? What is process of defining a custom(user) tag > similar to '751'? > > Appreciate you help in advance!! :) > > Thanks!! [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.
