Problem with incomplete fields

, ,
1

Imported from previous forum

2

[ original email was from John Prewett - jprewett@lavatrading.com ]
In FIX.5.0SP2 Fields.xml, here is the specification for Tag 261: 261 Reserved/Allocated to the Fixed Income proposal Reserved/Allocated to the Fixed Income proposal 1 I personally think we should not have a Tag reservation system at all, but that is off-topic. If we really, absolutely must have field Tag reservation, can all the attributes still have valid values? It presumably won't matter if they are even wrong as I imagine they aren't used at present. I am specifically referring to the which has a null value. Please give it the correct data type for what was intended or "String" if that cannot be determined. Thanks JohnP

3

We no longer permit reserving tags. The Extension Pack mechanism has eliminated the need. This is one of the fields initially reported as being a problem. If the Repository WG agrees - we will remove all unused fields such as this one during the Repository Maintenance release.

In FIX.5.0SP2 Fields.xml, here is the specification for Tag 261:

261 Reserved/Allocated to the Fixed
Income proposal
Reserved/Allocated to the Fixed Income proposal
1

I personally think we should not have a Tag reservation system at all,
but that is off-topic.

If we really, absolutely must have field Tag reservation, can all the
attributes still have valid values? It presumably won’t matter if they
are even wrong as I imagine they aren’t used at present.

I am specifically referring to the which has a null value. Please
give it the correct data type for what was intended or “String” if that
cannot be determined.

Thanks

JohnP