NoMDEntries = 7, but the repeating group size is only 1

24 views
Skip to first unread message

Arman

unread,
Apr 5, 2018, 9:45:25 PM4/5/18
to fix8 developer
Good Day!

I have this issue when I tried to print the FIX log to my application using the Message print().
I received the FIX log with the correct 7 repeating groups. However, when I parsed and print() to my application, the repeating group is only 1.

NOTE: Those with "***" were replaced from their original value for security purpose.

This is the FIX log:
8=FIXT.1.1 9=000315 35=W 49=*** 56=*** 34=3816 52=20180406-01:28:34.889 264=5 75=20180406 262=1 48=**** 22=99 762=NM 451=-0.07 268=7 269=P 270=0.48 272=20180405 274=2 326=17 811=-0.07 332=0.48 333=0.195 64=20180411 31=0.41 269=u 270=0.48 269=4 270=0.4 271=200 269=7 270=0.41 269=8 270=0.38 269=9 270=0.397 269=B 270=238 271=3 1020=600 10=137

And this is the Message::print()
 MarketDataSnapshotFullRefresh Print: header ("header")
   BeginString (8): FIXT.1.1
   BodyLength (9): 315
   MsgType (35): W
   SenderCompID (49): ***
   TargetCompID (56): ***
   MsgSeqNum (34): 3816
   SendingTime (52): 20180406-01:28:34.889
MarketDataSnapshotFullRefresh ("W")
   MarketDepth (264): 5
   TradeDate (75): 20180406
   MDReqID (262): 1
   SecurityID [Instrument] (48): ****
   SecurityIDSource [Instrument] (22): BLOOMBERG_SYMBOL (99)
   SecuritySubType [Instrument] (762): NM
   NetChgPrevDay (451): -0.07
   NoMDEntries [MDFullGrp] (268): 7
   NoMDEntries (Repeating group 1/1)
      MDEntryType (269): EARLY_PRICES (P)
      MDEntryPx (270): 0.48
      MDEntryDate (272): 20180405
      TickDirection (274): MINUS_TICK (2)
      SecurityTradingStatus (326): READY_TO_TRADE (17)
      PriceDelta (811): -0.07
      HighPx (332): 0.48
      LowPx (333): 0.195
      SettlDate (64): 20180411
trailer ("trailer")
   CheckSum (10): 137

By the way, I am using the FIX8 Community version. 
Anything I missed that I should be aware of? What should I do to fix this issue?

Thanks in Advance

Mazz Barker

unread,
Apr 8, 2018, 3:09:11 AM4/8/18
to fix8 developer
Probably an unrecognised field in the message. Check the schema.
/mazz

Arman

unread,
Apr 19, 2018, 1:02:14 AM4/19/18
to fix8 developer
You're right the prob is my schema, there is no LastPx. 
I fixed this issue. Thanks Mazz!
Reply all
Reply to author
Forward
0 new messages