Requirement for SecurityTradingStatus and CorporateAction fields to be of type MultiValueString

, ,
1

Imported from previous forum

2

We have found situations in which the following fields:

SecurityTradingStatus (tag=326) (defined as int)
CorporationAction (tag=292) (defines as char)

need to have multiple values. In order to allow for multivalued cases we have defined these fields as MultiValueString. Should these fields be defined as MultiValueString in the specification to take these cases into account?

3

[ original email was from Jim Northey - jnorthey@lasalletech.com ]
Euronext made a similar request during a recent presentation to the Technical Committee held on 10/4. I think the general concensus provided to us from the technical committee was changing data types of a standard tag is a very bad thing. However, since this is a new message with FIX 4.2 and we are already starting to hear back from multiple sources that there needs to support multiple values that this could be considered.

The approach that was recommended was to use a repeating group instead of a multivalued string - as it would permit the datatype of the TradingSessionStatus to remain unchanged.

Would this pose a problem? It would obviously require the introduction of a custom NoTradingSessionStatus tag.

> We have found situations in which the following fields:
>
> SecurityTradingStatus (tag=326) (defined as int)
> CorporationAction (tag=292) (defines as char)
>
> need to have multiple values. In order to allow for multivalued cases we have defined these fields as MultiValueString. Should these fields be defined as MultiValueString in the specification to take these cases into account?
>
>
>
>