Imported from previous forum
Hi,
help required!!
what should be the behaviour of a FIX engine if it receives a message where tag msgSeqNum is missing or it is 34=SOH.
should the engine treat this message as a garbled message and ignore it or
should it send a reject ? in case of reject,
what should be the value of tag refSeqNum (which is a mandatory field in reject message)?
what happens to the inbound sequence number ?
thanks.
“FIX Session-level Test Cases and Expected Behaviors” under Organization, Technical Committee, Archive and in Vol 2 of FIX 4.3) document’s current definition of what constitutes a “garbled message” is:
- BeginString (tag #8) is not the first tag in a message or is not of the format 8=FIX.n.m.
- BodyLength (tag #9) is not the second tag in a message or does not contain the correct byte count.
- MsgType (tag #35) is not the third tag in a message.
- Checksum (tag #10) is not the last tag or contains an incorrect value
Assuming the message in question has the first three and last (Checksum) field in proper position and format/value (BodyLength is correct and Checksum computes correctly), then I don’t think you should consider it garbled (and thus ignore).
I also don’t think you should issue a Reject, either. I would recommend terminating with a Logout. This sounds like a serious flaw.
> Hi,
> help required!!
> what should be the behaviour of a FIX engine if it receives a message where tag msgSeqNum is missing or it is 34=SOH.
> should the engine treat this message as a garbled message and ignore it or
> should it send a reject ? in case of reject,
> what should be the value of tag refSeqNum (which is a mandatory field in reject message)?
> what happens to the inbound sequence number ?
> thanks.
>