Robert Mitchell
21 April 2017 4:00pm
Trying to determine how to identify a MiFID2 instrument via the SecurityList. Certain fields being required on NewOrderSingle messages for MiFID2 instruments, how is one to know when an instrument is subject to MiFID2 rules?
Hanno Klein
24 April 2017 9:18am
Suggest to use SecurityListType(1470) and SecurityListTypeSource(1471). Both allow user-defined values above 100. Probably also makes sense to add standard values for MiFID, e.g. liquid/illiquid instruments. Has not been raised as an issue by the MiFID working groups in FIX.
Robert Mitchell
24 April 2017 4:16pm
Not sure SecurityListType would work for a SecurityList containing a large number of instruments, only some of which are subject to MiFID2 regulation. Really seems like something that belongs in the NoRelatedSym group.
Hanno Klein
25 April 2017 7:28am
My idea was to create a list that only contains instruments subject to MiFID 2 regulation. SecurityListType is on the root level and hence applies to the entire content of the repeating group SecListGrp. You can send multiple SecurityList messages, one for each group you need to distinguish.