Imported from previous forum
[ original email was from Himanshu Sharma - himanshu.sharma@schwab.com ]
Just wanted to confirm whether the msg below is correct representation of repeating feilds.
…35=V^A49=STE^A56=FMT^A34=000^A52=20020826-20:25:38^A262=20020826202538635^A263=1^A264=1^A267=2^A269=0^A146=1^A55=IBM^A269=1^A146=1^A55=IBM^A10=10^A
[ original email was from Dean Kauffman - dean.kauffman@tradeweb.com ]
Himanshu,
My intuition tells me you’re correct:
267=2^ NoMDEntryTypes
269=0^ MDEntryType = Bid
146=1^ NoRelatedSym
55=IBM^ Symbol
269=1^ MDEntryType = Offer
146=1^ NoRelatedSym
55=IBM^ Symbol
But the 4.3 FIX specification says otherwise - the NoRelatedSym block is not nested in the NoMDEntryTypes block but stands alone:
267=2^ NoMDEntryTypes
269=0^ MDEntryType = Bid
269=1^ MDEntryType = Offer
146=1^ NoRelatedSym
55=IBM^ Symbol
There is an anomaly in the spec though - NoTradingSessions (which you don’t provide) is required according to the the table but optional in the FIXML DTD fragment.
Dean Kauffman
> Just wanted to confirm whether the msg below is correct representation of repeating feilds.
>
> …35=V^A49=STE^A56=FMT^A34=000^A52=20020826-20:25:38^A262=20020826202538635^A263=1^A264=1^A267=2^A269=0^A146=1^A55=IBM^A269=1^A146=1^A55=IBM^A10=10^A
>
[ original email was from Keith Olivares - kolivares@javtech.com ]
Hi,
I have to disagree with the first assumption. Just as you said in your description for FIX 4.3, NoRelatedSym is not nested in the NoMDEntryTypes Block. In FIX 4.2 (FIX 4.2 w/ Errata 20010501), NoRelatedSym is not a repeating field. It stands alone. It sets up the number of times Symbol can be repeated, but the actual field does not repeat.
So, IMHO, the correct way to represent this is:
267=2^ NoMDEntryTypes
269=0^ MDEntryType = Bid
269=1^ MDEntryType = Offer
146=2^ NoRelatedSym
55=IBM^ Symbol
55=IBM^ Symbol
Regards,
Keith Olivares
> Himanshu,
>
> My intuition tells me you’re correct:
> 267=2^ NoMDEntryTypes
> 269=0^ MDEntryType = Bid
> 146=1^ NoRelatedSym
> 55=IBM^ Symbol
> 269=1^ MDEntryType = Offer
> 146=1^ NoRelatedSym
> 55=IBM^ Symbol
>
> But the 4.3 FIX specification says otherwise - the NoRelatedSym block is not nested in the NoMDEntryTypes block but stands alone:
>
> 267=2^ NoMDEntryTypes
> 269=0^ MDEntryType = Bid
> 269=1^ MDEntryType = Offer
> 146=1^ NoRelatedSym
> 55=IBM^ Symbol
>
> There is an anomaly in the spec though - NoTradingSessions (which you don’t provide) is required according to the the table but optional in the FIXML DTD fragment.
>
> Dean Kauffman
>
> > Just wanted to confirm whether the msg below is correct representation of repeating feilds.
> >
> > …35=V^A49=STE^A56=FMT^A34=000^A52=20020826-20:25:38^A262=20020826202538635^A263=1^A264=1^A267=2^A269=0^A146=1^A55=IBM^A269=1^A146=1^A55=IBM^A10=10^A
> >
>
[ original email was from Ryan Pierce - rpierce@taltrade.com ]
> I have to disagree with the first assumption. Just as you said in your description for FIX 4.3, NoRelatedSym is not nested in the NoMDEntryTypes Block. In FIX 4.2 (FIX 4.2 w/ Errata 20010501), NoRelatedSym is not a repeating field. It stands alone. It sets up the number of times Symbol can be repeated, but the actual field does not repeat.
This is correct for both FIX 4.2 with errata and FIX 4.3. In Market Data Request, NoMDEntryTypes starts a required repeating group. NoRelatedSym also starts a required repeating group. Both of these groups are top-level, so they are not nested in other groups. So the following syntax is correct:
> 267=2^ NoMDEntryTypes
> 269=0^ MDEntryType = Bid
> 269=1^ MDEntryType = Offer
> 146=2^ NoRelatedSym
> 55=IBM^ Symbol
> 55=IBM^ Symbol
I believe Dean mentioned an anomaly regarding NoTradingSessions.
In FIX 4.2, it was not a repeating group. Rather, TradingSessionID was included along with the security. So if you wanted an IBM quote in 3 sessions, you’re going to have to request IBM 3 times, which is inefficient.
In FIX 4.3, it was moved into a top-level repeating group. However, I believe there’s a mistake in that NoTradingSessions is required, but TradingSessionID is not.
Jim, if this hasn’t already been addressed in the proposed 4.3 errata, I’m thinking we should consider making NoTradingSessions optional in FIX 4.3. I had originally intended the whole repeating group to be optional. So what is the standard way of handling an optional repeating group? Is the “No…” field always required, and if no data follows, it’s set to 0? Or should someone just not include NoTradingSessions in the message?