Try FIX parser and click on the "sample data" button. It will generate a set of valid fix messages (including execution reports). Obviously you can also use it as a FIX parser to help you make sense of your data. Note that this text is separated by the actual FIX delimiter (SOH character). This means that visually all the text will look like a jumble of characters.
The problem with FIX is it'a a real catch-all protocol. It allows a lot of flexibility.
If you look, for example, at the spec for the Execution Report message in FIX 4.4 (BTW: always better to specify a version number with FIX), you'll notice that most of the tags you mentioned are not required by the protocol. Of the three you mentioned, only tag 55 is required on that message type. That means that whether tag 1 or 207 are there or not is up to the implementation in question.
So, unfortunately, there are no canonical samples. You should ask for sample messages from the party with whom you're trying to communicate.
There are some examples of the TradeCaptureReport message you're talking about on my Online FIX Decoder page (shameless plug) which will not only show you the contents of the encoded message, but will decode it neatly into a table for you, assigning labels to the otherwise cryptic integers.
These particular examples were made publicly available by the LSE.
If you're doing trade reporting, the exact format you have to send will depend upon the vendor you're using. It's best to contact them directly and ask for samples as what is valid for one vendor is likely different from another.
There are some on the FIX protocol website if you have access (I don't know if they are available without logging on) or you can generate them yourself using the examples provided by quickfix.
Go to the CME-DataMine website where you can find Market Depth FIX files with all market data messages required to recreate the order book. ( CME DataMine )
I had the same need and ended up having to build something to automatically reformat FIX messages from one session to another. It turned out to be quite useful in our own testing, so I ended up hosting a server for it. Shameless plug here, but FIXSIM.com might be of use.
发布评论
评论（7）
尝试 FIX 解析器 并单击“示例数据”按钮。它将生成一组有效的修复消息（包括执行报告）。显然，您也可以将它用作 FIX 解析器来帮助您理解数据。请注意，此文本由实际的 FIX 分隔符（SOH 字符）分隔。这意味着所有文本在视觉上看起来都像一堆字符。
Try FIX parser and click on the "sample data" button. It will generate a set of valid fix messages (including execution reports). Obviously you can also use it as a FIX parser to help you make sense of your data. Note that this text is separated by the actual FIX delimiter (SOH character). This means that visually all the text will look like a jumble of characters.
FIX 的问题在于它是一个真正的包罗万象的协议。它允许很大的灵活性。
例如，如果您查看 FIX 4.4 中执行报告消息的规范（顺便说一句：使用 FIX 指定版本号总是更好），您会注意到协议不需要您提到的大多数标签。在您提到的三个中，该消息类型仅需要标记 55。这意味着标签 1 或 207 是否存在取决于所讨论的实现。
因此，不幸的是，没有规范的样本。您应该向您尝试通信的一方索取示例消息。
The problem with FIX is it'a a real catch-all protocol. It allows a lot of flexibility.
If you look, for example, at the spec for the Execution Report message in FIX 4.4 (BTW: always better to specify a version number with FIX), you'll notice that most of the tags you mentioned are not required by the protocol. Of the three you mentioned, only tag 55 is required on that message type. That means that whether tag 1 or 207 are there or not is up to the implementation in question.
So, unfortunately, there are no canonical samples. You should ask for sample messages from the party with whom you're trying to communicate.
您可以从 validfix 获取一些示例数据。
fix-analyzer.html 有许多不同修复消息的示例
fix-log-analyzer.html 只是来自某种修复引擎的真实日志的一个重要示例。
（修复了损坏的链接）
You can get some sample data from validfix.
fix-analyzer.html has many examples of different fix messages
fix-log-analyzer.html has just one big example of a real log from some sort of fix engine.
(fixed broken link)
您在我的在线 FIX 解码器<上讨论了一些
TradeCaptureReport消息的示例/a> 页面（无耻的插件），它不仅会向您显示编码消息的内容，还会为您将其整齐地解码为表格，为原本神秘的整数分配标签。这些具体例子由伦敦证券交易所公开发布。
如果您正在进行贸易报告，则必须发送的确切格式将取决于您使用的供应商。最好直接联系他们并索取样品，因为对一个供应商有效的样品可能与另一个供应商不同。
There are some examples of the
TradeCaptureReportmessage you're talking about on my Online FIX Decoder page (shameless plug) which will not only show you the contents of the encoded message, but will decode it neatly into a table for you, assigning labels to the otherwise cryptic integers.These particular examples were made publicly available by the LSE.
If you're doing trade reporting, the exact format you have to send will depend upon the vendor you're using. It's best to contact them directly and ask for samples as what is valid for one vendor is likely different from another.
如果您有权访问，FIX 协议网站上有一些（我不知道它们是否可以在不登录的情况下使用），或者您可以使用 QuickFix 提供的示例自行生成它们。
There are some on the FIX protocol website if you have access (I don't know if they are available without logging on) or you can generate them yourself using the examples provided by quickfix.
访问 CME-DataMine 网站，您可以在其中找到市场深度 FIX 文件，其中包含重新创建订单簿所需的所有市场数据消息。 （CME DataMine）
Go to the CME-DataMine website where you can find Market Depth FIX files with all market data messages required to recreate the order book. ( CME DataMine )
我有同样的需求，最终不得不构建一些东西来自动将 FIX 消息从一个会话重新格式化为另一个会话。事实证明它在我们自己的测试中非常有用，所以我最终为其托管了一个服务器。无耻的插件在这里，但 FIXSIM.com 可能有用。
I had the same need and ended up having to build something to automatically reformat FIX messages from one session to another. It turned out to be quite useful in our own testing, so I ended up hosting a server for it. Shameless plug here, but FIXSIM.com might be of use.