# List Strike Price in FIX 4.4 Question **URL:** \ **Category:** General Q&A\ **Tags:** imported, 44-changes, xid\_165426\ **Created:** [June 9, 2006, 3:46pm UTC](https://forum.fixtrading.org/t/list-strike-price-in-fix-4-4-question/12880 "2006-06-09T15:46:24Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\ **Post date:** [June 9, 2006, 3:46pm UTC](https://forum.fixtrading.org/t/list-strike-price-in-fix-4-4-question/12880/1 "2006-06-09T15:46:24Z")
Imported from previous forum ---
**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\ **Post date:** [June 9, 2006, 3:46pm UTC](https://forum.fixtrading.org/t/list-strike-price-in-fix-4-4-question/12880/2 "2006-06-09T15:46:24Z")
[original email was from David Basso - [david.basso@thomson.com](mailto:david.basso@thomson.com) ] A question on the List Strike Price message in FIX 4.4. The FIX 4.4 specification currently has Component Block Underlying Instrument as a sub-heading under the repeating group NoUnderlyings. In this manner, it appears that the fields that follow (PrevClosePx, ClOrdID, etc.) are included as part of the NoUnderlyings repeating group and not the NoStrikes repeating group. However, shouldn’t the Component Block UnderlyingInstrument be a sub-heading under NoUnderlyings only. Then, the following fields such as PrevClosePx, ClOrdID, etc. would be sub-headings under the NoStrikes repeating group and not NoUnderlyings. If that is the case, it would seem that another arrow (-\>) would be necessary for the Component Block UnderlyingInstrument field. ---
**Author:** ![matthewwolfe\_x](https://avatars.discourse-cdn.com/v4/letter/m/82dd89/32.png) [@matthewwolfe\_x](https://forum.fixtrading.org/u/matthewwolfe_x)\ **Post date:** [June 12, 2006, 2:44pm UTC](https://forum.fixtrading.org/t/list-strike-price-in-fix-4-4-question/12880/3 "2006-06-12T14:44:36Z")
Kevin, Making the UnderlyingInstrument an attribute of Instrument would break OCC and our Clearing Member’s implementation of the Collateral Report and Collateral Response messages. There are cases where we show UndlyInstr without Instr. Regards, Matt Wolfe > These messages where added in FIX.4.2, then when UnderlyingInstrument > components where added in FIX.4.4, we added tags 711, NoUnderlyings and > the to almost all messages to describe more > complex instruments. Tag 711 was added at the same level of nesting, as > the block, and the block at one > level deeper to show that it could be repeated may times per > . > > We appear to have applied this incorrectly in the case of this message, > the GTC will fix this as an errata item and include in the next release > of FIX. (SP1, scheduled for this summer). We’ll also review for other > instances, the mass order messages are also curious, as they seem to > only allow on Underlying. > > The best tidy up for this may be to add the underlyingInstrument > component and NoUnderlyings tag to the Instrument component block as > it’s almost always used in conjuntion, we’ll review the exceptions and > see if this is possbile. > > In the meantime you are correct, both the UnderlyingInstrument > component block and the tag 711, NoUnderlyings needs another level of > indentation. “-\>” > > Cheers Kevin Houstoun GTC CoChair Consultant to HSBC Investment Bank > > > A question on the List Strike Price message in FIX 4.4. > > > > The FIX 4.4 specification currently has Component Block Underlying > > Instrument as a sub-heading under the repeating group NoUnderlyings. > > In this manner, it appears that the fields that follow (PrevClosePx, > > ClOrdID, etc.) are included as part of the NoUnderlyings repeating > > group and not the NoStrikes repeating group. However, shouldn’t the > > Component Block UnderlyingInstrument be a sub-heading under > > NoUnderlyings only. Then, the following fields such as PrevClosePx, > > ClOrdID, etc. would be sub-headings under the NoStrikes repeating > > group and not NoUnderlyings. If that is the case, it would seem that > > another arrow (-\>) would be necessary for the Component Block > > UnderlyingInstrument field. ---
**Author:** ![jim.northey](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/jim.northey/32/37_2.png) [@jim.northey](https://forum.fixtrading.org/u/jim.northey)\ **Post date:** [August 3, 2008, 1:46am UTC](https://forum.fixtrading.org/t/list-strike-price-in-fix-4-4-question/12880/4 "2008-08-03T01:46:12Z")
To be addressed in FIX.4.4 Errata 2 > A question on the List Strike Price message in FIX 4.4. > > The FIX 4.4 specification currently has Component Block Underlying > Instrument as a sub-heading under the repeating group NoUnderlyings. In > this manner, it appears that the fields that follow (PrevClosePx, > ClOrdID, etc.) are included as part of the NoUnderlyings repeating group > and not the NoStrikes repeating group. However, shouldn’t the Component > Block UnderlyingInstrument be a sub-heading under NoUnderlyings only. > Then, the following fields such as PrevClosePx, ClOrdID, etc. would be > sub-headings under the NoStrikes repeating group and not NoUnderlyings. > If that is the case, it would seem that another arrow (-\>) would be > necessary for the Component Block UnderlyingInstrument field.