{{Quickfixn}} Create Quickfix message from String

[Grant Birchmeier]

1) I recommend that you have a DataDictionary.  If the message has a
repeating group, then you MUST have one.  It is impossible to parse
repeating groups without a DataDictionary.

2) 10 is required to be the last field in the message.  It sounds like you
might not know FIX.

3) It sounds like what you are doing is not well-considered.  You can't
send a verbatim message and expect it to work.  The sending-time and
sequence number need to be updated, and hence the checksum also needs to be
updated.  *You can't "replay" a FIX log and expect it to work.*

On Wed, Sep 11, 2019 at 9:53 AM Jie Zhu <Jie.Zhu at icbkfs.com> wrote:

> I removed the tag/value 10=153 from the string, now it has the same error “could
> not parse message: Error at postion(347) while parsing msg(…)”. Position
> 347 is where the last the last equal sign seated.
>
>
>
> *From:* Quickfixn [mailto:quickfixn-bounces at lists.quickfixn.com] *On
> Behalf Of *Jie Zhu
> *Sent:* Wednesday, September 11, 2019 10:37 AM
> *To:* quickfixn at lists.quickfixn.com
> *Subject:* {{Quickfixn}} Create Quickfix message from String
>
>
>
> Hi,
>
>
>
>      I am creating a fix message from a string.  As I don’t have data
> dictionary and our client only want me to send the fix message he created
> in txt file.    In my configurations, I set:
>
>
>
> UseDataDictionary=N
>
> ValidateLengthAndChecksum=N
>
> ValidateFieldsOutOfOrder=N
>
> ValidateFieldsHaveValues=N
>
> ValidateUserDefinedFields=N
>
>
>
>        I read the string (tradeStr) message, and use var msg=new
> Message(tradeStr) to create the fix message object.   There comes out an
> exception, “could not parse message: Error at postion(359) while parsing
> msg(…)”. I looked at the position 359 in his string is the position after
> tag 10 in the trailer.
>
>
>
>         So how can I fix this issues.
>
>
>
> Thanks for the help.
>
>
>
>
>
> Jie
>
> This email and any attached files are confidential and may be legally
> privileged. If you are not the intended recipient, any disclosure,
> reproduction, copying, distribution, or other dissemination or use of this
> communication is strictly prohibited. If you have received this
> transmission in error please notify the sender immediately and then delete
> this email. Email transmission cannot be guaranteed to be secure or error
> free as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. The sender therefore is in
> no way liable for any errors or omissions in the contents of this message
> which may arise as a result of email transmission. If verification is
> required please request a hard copy.
>
> This email and any attached files are confidential and may be legally
> privileged. If you are not the intended recipient, any disclosure,
> reproduction, copying, distribution, or other dissemination or use of this
> communication is strictly prohibited. If you have received this
> transmission in error please notify the sender immediately and then delete
> this email. Email transmission cannot be guaranteed to be secure or error
> free as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. The sender therefore is in
> no way liable for any errors or omissions in the contents of this message
> which may arise as a result of email transmission. If verification is
> required please request a hard copy.
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>


-- 
Grant Birchmeier
*Connamara Systems, LLC*
*Made-To-Measure Trading Solutions.*
Exactly what you need. No more. No less.
http://connamara.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20190911/5bab14f5/attachment.htm>