Imported from previous forum
[ original email was from Gerard Putter - Gerard.Putter@fincomplus.com ]
The FIX 4.3 specifications are not very clear on what to react to an invalid Trade Capture Report Request. For example, suppose someone sends such a message with SubscriptionRequestType = “2” (Unsubscribe), but specifies an unknown TradeRequestID. According to the table on page 39 of volume 1 (FIX 4.3) this should be reported by replying with the same message type, Trade Capture Report Request. This seems unlikely, because there appears to be no tag in the message that indicates an error condition. I suppose the table is in error, and a Trade Capture Report must be used to report the error, but even then I don’t see an appropriate tag to report the error condition. Anyone has a solution for this? Should I use the Business Message Reject instead?
[ original email was from Dean Kauffman - dean.kauffman@tradeweb.com ]
Gerard,
I think you’ve found a new error in the 4.3 spec. To be consistent with other dialogs the appropriate reject response to a TradeCaptureReportRequest would be TradeCaptureReport with ExecType=“8” Rejected. However the OrdRejReason field has been omitted, so for now you’ll need to spell out the reason in Text. I’ll forward this to the 4.3 errata team.
Dean Kauffman
> The FIX 4.3 specifications are not very clear on what to react to an invalid Trade Capture Report Request. For example, suppose someone sends such a message with SubscriptionRequestType = “2” (Unsubscribe), but specifies an unknown TradeRequestID. According to the table on page 39 of volume 1 (FIX 4.3) this should be reported by replying with the same message type, Trade Capture Report Request. This seems unlikely, because there appears to be no tag in the message that indicates an error condition. I suppose the table is in error, and a Trade Capture Report must be used to report the error, but even then I don’t see an appropriate tag to report the error condition. Anyone has a solution for this? Should I use the Business Message Reject instead?
>