Discussion Forums

Re: Why is there both a TradeRequestResult(749) and TradeRequestStatus(750) on the TradeCaptureReportRequestAck
Rikard Hedberg / NASDAQ OMX
26 Mar 2008 11:20AM ET

Jim,

I'm not sure I understand the business workflow you are referring to. In FIX 5.0 we may have dminished the role of the Trade Capture Report Request message to be used for subscriptions/queries only (there is no need to use the TCR Request message to submit a trade report).

Regarding the two fields I see:
- TradeRequestResult (749) as the reject (or accept) code
- TradeRequestStatus (750=) as the status of the progress of the process (in cases the TCR Request Ack is sent multiple times similar to a "Pending" order state preceeding a "New" one). I agree that could be questioned, we are not using it ourselves. Especially the "reject" value seems redundant. But i guess we need to go back to the Gap Analysis that was the basis for the extension in the first place.

Regards

Rikard

> The TradeCaptureReportRequestAck message since FIX.4.4 has had two
> separate fields that convey the results/status of a query. How are these
> fields used together? Are they duplicate functionality? If they are
> duplicate we should deprecate one or the other. I sense they are not. If
> they have different functions we should update the specification to
> indicate appropriate use.
>
> 749 TradeRequestResult @ReqRslt Result of Trade Request
>
> 750 TradeRequestStatus @ReqStat Status of Trade Request


Re: Why is there both a TradeRequestResult(749) and TradeRequestStatus(750) on the TradeCaptureReportRequestAck
Rikard Hedberg / NASDAQ OMX   26 Mar 2008 11:20AM ET