[This message was posted by Robert Mitchell of NYU <[email protected]> to the "4.4
Changes" discussion forum at http://fixprotocol.org/discuss/17. You can reply
to it on-line at http://fixprotocol.org/discuss/read/a31ac79d - PLEASE DO NOT
REPLY BY MAIL.]
Deprecated in favor of what?
Cheers!
> > There appears to be an inconsistency in the definitions of fields
> > RepoCollateralSecurityType(239),
> > UnderlyingRepoCollateralSecurityType(243) and
> > LegRepoCollateralSecurityType(250). These are defined to be of type
> > "int". However, these fields all contain security types which are
> > strings ("FUT", "OPT", etc.).
> >
> > I assume that this is just a typo and the field type should be
> > "String".
> >
> > Note that this typo is in both the Data Dictionary (vol. 6) and in the
> > DTD released on June 18.
> >
>
> Thanks for the posting, these fields are all deprecated but take thier
> values and datatype from Tag 167 which they are based on. This is
> reflected in the spec in the wording but not in the datatype column and
> the DTD is based on the spec so shares the error.
>
> The datatype column should say string.
>
> Cheers Kevin Houstoun
[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.
