[This message was posted by Ryan Pierce (FPL Technical Director) of FIX 
Protocol Ltd. <ryan.pie...@fixprotocol.org> to the "General Q/A" discussion 
forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at 
http://fixprotocol.org/discuss/read/de1b473c - PLEASE DO NOT REPLY BY MAIL.]

> Upto what number should others not use? Million / Billion / ... ?
> 
> Since TagNum is of Base type int and I could not find any minimum /
> maximum size definitions, is there a limit on the maximum tag number
> that can be used in FIX messages? For example can tag number 999999 be
> used in a FIX message ? I do not see any restriction because FIXProtocol
> is Strings exchanged on TCP so any length integer number can be
> transmitted subject to parsing capabilities of systems at both sides.

Currently, there is no upper limit on the highest tag number. It is just a 
positive integer, and as it is ASCII, not binary, the number of bits are not 
defined.

However, according to the spec itself, firms are not allowed to us any tag >= 
10,000 to communicate between firms. Those tags are supposed to be used within 
one firm only.

Under the new proposal, 10,000-19,999 is for internal use within a firm. 
20,000-39,999 is for use between firms. Any use at all above 40,000 is not 
allowed. So the question of upper limits on tags isn't really all that 
important, especially under the new proposal.

> Has using decimal tag numbers like 123.45=Value^ been considered? Has
> using alphabetic tags like SECTYP=Value^ been considered?

No. These are not allowed.


[You can unsubscribe from this discussion group by sending a message to 
mailto:unsubscribe+100932...@fixprotocol.org]

--

You received this message because you are subscribed to the Google Groups 
"Financial Information eXchange" group.
To post to this group, send email to fix-proto...@googlegroups.com.
To unsubscribe from this group, send email to 
fix-protocol+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/fix-protocol?hl=.


Reply via email to