Parameter: fixTag and Multiple Char/String value

, , ,
1

Imported from previous forum

2

[ original email was from Dev Ashish - dashish@lab49.com ]
Perhaps I’m missing something but why isn’t fixTag a required attribute for a Parameter_t?

Also, shouldn’t enumPairs underneath MultipleCharValue_t and MultipleStringValue_t be required? If not, then what is the expected usage of these parameter types?

Thanks

3

[ original email was from Zoltan Feledy - zoltan_feledy@ssga.com ]
Hello,

I’ve been away from FIXatdl for a long time now but one of the original ideas was to encourage the use of the algorithmic extension repeating groups whereby all parameters are in the repeating group as opposed to their own tag.

Hope this helps and I am not giving out wrong information.

Cheers,
Zoltan

Perhaps I’m missing something but why isn’t fixTag a required attribute
for a Parameter_t?

Also, shouldn’t enumPairs underneath MultipleCharValue_t and
MultipleStringValue_t be required? If not, then what is the expected
usage of these parameter types?

Thanks

4

[ original email was from Dev Ashish - dashish@lab49.com ]
> Hello,

I’ve been away from FIXatdl for a long time now but one of the original
ideas was to encourage the use of the algorithmic extension repeating
groups whereby all parameters are in the repeating group as opposed to
their own tag.

Thanks for the update, Zoltan. I’m not using repeatingGroups at the moment, so will treat fixTag as a required field.

Another thing to clarify on MultipleStringValue_t: it seems that an EnumPair having wireValue with spaces in them are treated as valid. Won’t this cause an issue when the values are concatenated with a space into the FIX message? Is this a case where “best practices” would inform the developer that spaces aren’t valid?

Thanks