Imported from previous forum
[ original email was from Jim Northey - jnorthey@lasalletech.com ]
The Security Definition Request Message permits a request to return a list of Security Types. The Security Definition supports returning a list of securities. The problem is that if you are returning a list of Security Types which do not have symbols. In the repeating group denoted by NoRelatedSym(146) - the required field is UnderlyingSymbol(311) - which is required if NoRelatedSym(146) is greater than zero. If we move UnderlyingSecurityType(310) to be the first field in the repeating group it has two advantages: 1) Makes a better hierarchy or tree - when mapping to XML 2) Makes it possible to support of all the valid requests (security type, securities). The one downside is that UnderlyingSecurityType(310) will be required.
Any thoughts
[ original email was from Ryan Pierce - rpierce@taltrade.com ]
> The Security Definition Request Message permits a request to return a list of Security Types. The Security Definition supports returning a list of securities. The problem is that if you are returning a list of Security Types which do not have symbols. In the repeating group denoted by NoRelatedSym(146) - the required field is UnderlyingSymbol(311) - which is required if NoRelatedSym(146) is greater than zero. If we move UnderlyingSecurityType(310) to be the first field in the repeating group it has two advantages: 1) Makes a better hierarchy or tree - when mapping to XML 2) Makes it possible to support of all the valid requests (security type, securities). The one downside is that UnderlyingSecurityType(310) will be required.
I haven’t looked too closely at the message itself, so I’m not sure what the best solution here would be. Requiring UnderlyingSecurityType seems problematic if it would make the Security Definition message derivatives-specific and wouldn’t support equities or bonds, which don’t have underlying securities.