Final few FIX 4.2 questions ?

, ,
1

Imported from previous forum

2

[ original email was from John Hardman - yiq12@dial.pipex.com ]
Question #1

Fields 22 (IDSource) and 305 (UnderlyingIDSource) are both of type String. Are there any plans to change these to type Int (which would appear to be their more natural type) ?

Question #2

The comments for field 65 (SymbolSfx) say “As defined in the NYSE Stock and bond Symbol Directory and in the AMEX Fitch Directory”. Does anyone know where I can find these in electronic form ?

Question #3

In many places the specification uses the word “unique”. Can it be clarified in the 4.2 errata the scope of the uniqueness – I assume in most cases the uniqueness is for the trading day/session.

Question #4

Is it true to say that field 310 (UnderlyingSecurityType) can not contain “?” ? At present the Field Definitions say that UnderlyingSecurityType can contain the same values as SecurityType.

Question #5

The comments for field 167 (SecurityType) in the Security Definition message say

‘Set to “?” if Security Definition Request is looking for the Security Types’

For validation of individual messages it would allow more thorough checking if this was rephrased to say

‘Set to “?” if SecurityResponseType = 3 (List of security types returned per request)’

Any chances of making this change in the 4.2 errata or would this change make too much existing code non-compliant ?

Also, does “Set to” mean that the field is required in this situation ?

Question #6

In the Field Definitions a number of fields have the comment “Represented as a percentage”. Are these percentages restricted to the range 0 <= x <= 100 or can they fall outside that range ?