[This message was posted by Ryan Pierce (FPL Technical Director) of FIX Protocol Ltd. <[email protected]> to the "5.0 SP2 Feedback" discussion forum at http://fixprotocol.org/discuss/121. You can reply to it on-line at http://fixprotocol.org/discuss/read/3cef1c9a - PLEASE DO NOT REPLY BY MAIL.]
> Tag 1618 (RelationshipRiskEncodedSecurityDescLen) refers to itself > instead of tag 1619 (RelationshipRiskEncodedSecurityDesc). The tag > description says > > "Byte length of encoded (non-ASCII characters) > RelationshipRiskEncodedSecurityDesc (1618) field." > > It should be "Byte length of encoded (non-ASCII characters) > RelationshipRiskEncodedSecurityDesc (1619) field." > > Similarly, Tag 1620(RiskEncodedSecurityDescLen) refers to itself instead > of Tag 1621(RiskEncodedSecurityDesc). Thanks for letting us know. I'm wondering how you found this. Were you considering implementing the Parties Reference Data messaging in FIX 5.0 SP2, or was it by chance that you found this? If the former, I need to inform you that the Parties Reference Data messaging introduced in FIX 5.0 SP2 has been substantially overhauled by the Extension Pack 105. I strongly suggest against implementing Parties Reference Data as implemented in SP2, and suggest that instead you implement the EP105 version. This issue has already been fixed by EP105, "Parties Reference Data Extensions" which was ratified at the end of last month. We are still working on coding this as an Extension Pack to the Repository. However, I can say that this EP deletes 1618 and 1619. 1620 is renamed, and it properly refers to 1621. [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 -~----------~----~----~----~------~----~------~--~---
