Re: [Quickfix-developers] repeating groups

[<San...@ub...>]

I get the message in the text file. I create a fix message out of that
using the FIX::Message (string);=20

Message from text file
Orignal message is :
8=3DFIX.4.2;9=3D154;35=3DE;49=3DSSCON;56=3DUBS;34=3D991;52=3D20060825-14:=
28:44;21=3D3;50
=3DBNP;66=3DDREJECT;394=3D1;68=3D1;73=3D1;11=3D1232013_6;67=3D1;55=3DGSK;=
54=3D1;38=3D1;22=3D5;
48=3DGSK.L;40=3D2;44=3D1;10=3D047;

After construction
Fix Message to send is :
8=3DFIX.4.2=019=3D147=0135=3DE=0134=3D991=0149=3DSSCON=0150=3DBNP=0152=3D=
20060901-14:25:29=0156=3DUBS=01
11=3D1232013_6=0121=3D3=0122=3D5=0138=3D1=0140=3D2=0144=3D1=0148=3DGSK.L=01=
54=3D1=0155=3DGSK=0166=3DDREJECT=0167
=3D1=0168=3D1=0173=3D1=01394=3D1=0110=3D054=01

Thanks & Regards,
Sangram=20

-----Original Message-----
From: Oren Miller [mailto:or...@qu...]=20
Sent: Friday, September 01, 2006 11:03 AM
To: Shinde, Sangram
Cc: Qui...@li...
Subject: Re: [Quickfix-developers] repeating groups

Can you show the actual code you use to parse the incoming message?  =20
Could you also include the incoming message string and the result of
calling getString on the message you create?

--oren

On Sep 1, 2006, at 9:58 AM, San...@ub... wrote:

> I get fix message in text format. I construct a fix message using=20
> FIX::Message (string); method. Data dictionary is used for validation.
> My application then sends the fix messages to the fix engine.
>
> Problem I am facing is ordering of the tag is not correct. Tag 11=20
> comes before tag 68. Because of this fix engine is rejecting the=20
> message.
>
> How to handle this case? How to maintain the tag ordering. Any=20
> suggestions are welcome.


Visit our website at http://www.ubs.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail 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 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.