quickfix-users

[Quickfix-users] Tag specified out of required order

[Tom F. <tom...@ki...>]

Hi,

I'm wondering why QuickFix rejects the following drop with "Tag specified
out of required order":

8=3D
FIX.4.2=019=3D224=0135=3D8=0134=3D17=0149=3DFIMAT_PREF=0156=3DMCOMPASS_DROP=
=0152=3D20060426-20:27:32=01115=3Dara=016=3D27.09=0114=3D1=0117=3D2=0120=3D=
0=0131=3D27.09=0132=3D1=0137=3D939349=0138=3D1=0139=3D2=01150=3D2=0140=3D2=
=011=3D1MA=0154=3D1=0155=3DMSFT=0130=3Dara=0160=3D20060426-20:27:32=01198=
=3D12=01483=3D20060426-20:27:32=0150=3Dp2126=0110=3D128=01
8=3D
FIX.4.2=019=3D132=0135=3D3=0134=3D9=0149=3DMCOMPASS_DROP=0152=3D20060426-20=
:27:32.703=0156=3DFIMAT_PREF=01128=3Dara=0145=3D17=0158=3DTagspecified
out of required order=01371=3D50=01372=3D8=0110=3D038=01

As far as I know only the first 3 and last tag have to have a specific
order?

Thanks,

Tom

[Quickfix-users] Tag specified out of required order

[spencer <sru...@db...>]

Hello,

I have quick fix working against a broker successfully. To make testing a
new version of my app easier, I am trying to get the example app -
executer_csharp.exe working to execute my orders. I can log in successfull
and heartbeats are fine. However, when I send this message (which works fin=
e
with my broker):

8=3DFIX.4.2=019=3D166=0135=3DD=0134=3D27=0149=3DRBCFG=0152=3D20060720-08:17=
:32.180=0156=3DROYBTEST=0111=3D18771=0121=3D3=0122=3D3=0138=3D500=0140=3D1=
=0144=3D0=0148=3D2337=0154=3D2=0155=3D2337=0158=3DCD=0159=3D0=0160=3D200607=
20-08:17:32=01100=3DOJ=01128=3DBNPPTEST=0110=3D253=01


I get this response:

8=3DFIX.4.2=019=3D123=0135=3D3=0134=3D47=0149=3DROYB=0152=3D20060802-15:52:=
55.982=0156=3Dmerrin2=01115=3DBNPP=0145=3D45=0158=3DTag
specified out of required order=01371=3D128=01372=3DD=0110=3D168=01

Any help is greatfully received.

Thanks.

--=20
View this message in context: http://www.nabble.com/Tag-specified-out-of-re=
quired-order-tf2040806.html#a5617135
Sent from the QuickFIX - User forum at Nabble.com.

Re: [Quickfix-users] Tag specified out of required order

[Oren M. <or...@qu...>]

You put field 128, DeliverToCompID, in the body of the message.  It =20
should be in the header.

--oren

On Aug 2, 2006, at 11:15 AM, spencer wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/=20
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> Hello,
>
> I have quick fix working against a broker successfully. To make =20
> testing a
> new version of my app easier, I am trying to get the example app -
> executer_csharp.exe working to execute my orders. I can log in =20
> successfull
> and heartbeats are fine. However, when I send this message (which =20
> works fine
> with my broker):
>
> 8=3DFIX.=20
> 4.2=019=3D166=0135=3DD=0134=3D27=0149=3DRBCFG=0152=3D20060720-08:17:32.1=
80=0156=3DROYBTEST=0111=3D=20
> 18771=0121=3D3=0122=3D3=0138=3D500=0140=3D1=0144=3D0=0148=3D2337=0154=3D=
2=0155=3D2337=0158=3DCD=0159=3D0=0160=3D20=20
> 060720-08:17:32=01100=3DOJ=01128=3DBNPPTEST=0110=3D253=01
>
>
> I get this response:
>
> 8=3DFIX.=20
> 4.2=019=3D123=0135=3D3=0134=3D47=0149=3DROYB=0152=3D20060802-15:52:55.98=
2=0156=3Dmerrin2=01115=3DB=20
> NPP=0145=3D45=0158=3DTag
> specified out of required order=01371=3D128=01372=3DD=0110=3D168=01
>
> Any help is greatfully received.
>
> Thanks.
>
> --=20
> View this message in context: http://www.nabble.com/Tag-specified-=20
> out-of-required-order-tf2040806.html#a5617135
> Sent from the QuickFIX - User forum at Nabble.com.
>
>
> ----------------------------------------------------------------------=20=

> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =20
> share your
> opinions on IT & business topics through brief surveys -- and earn =20
> cash
> http://www.techsay.com/default.php?=20
> page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users
>

Re: [Quickfix-users] Tag specified out of required order

[Oren M. <or...@qu...>]

You also need to make sure that all header fields precede any body 
fields, and all body field precede and trailer fields.  The reject 
message is complaining about tag 50 (371=50).  This is the header field 
SenderSubID, which is appearing in the body of the message.  You are 
probably doing a setField( SenderSubID ), instead of a 
getHeader().setField( SenderSubID ).

--oren

Tom Frey wrote:

> Hi,
>
> I'm wondering why QuickFix rejects the following drop with "Tag 
> specified out of required order":
>
> 8=FIX.4.2
9=224
35=8
34=17
49=FIMAT_PREF
56=MCOMPASS_DROP
52=20060426-20:27:32
115=ara
6=27.09
14=1
17=2
20=0
31=27.09
32=1
37=939349
38=1
39=2
150=2
40=2
1=1MA
54=1
55=MSFT
30=ara
60=20060426-20:27:32
198=12
483=20060426-20:27:32
50=p2126
10=128
 
>
> 8=FIX.4.2
9=132
35=3
34=9
49=MCOMPASS_DROP
52=20060426-20:27:32.703
56=FIMAT_PREF
128=ara
45=17
58=Tag 
> specified out of required order
371=50
372=8
10=038

>
> As far as I know only the first 3 and last tag have to have a specific 
> order?
>
> Thanks,
>
> Tom

[Quickfix-users] Tag specified out of required order

[chris1985 <chr...@ho...>]

I am having a problem with the FIX message below which is saying the "Tag
specified out of required order". Have I got the correct tags in the header
and body? If anyone can tell me which tag is wrong I would be grateful

toApp:
8=FIX.4.2☺9=130☺35=V☺34=2☺49=USERNAME☺52=20080716-19:47:27.874☺56=BROKER☺
1=1567222☺50=1854K16030☺55=EUR/USD☺146=1☺262=101☺263=0☺264=1☺267=1☺269=0☺10=035☺

fromAdmin:
8=FIX.4.2☺9=114☺35=3☺34=2☺49=BROKER☺52=20080716-19:47:25.915☺56=USERNAME☺45=2☺58=Tag
specified out of required order☺371=50☺372=V☺10=026☺



Thanks in advance,
Chris


-- 
View this message in context: http://www.nabble.com/Tag-specified-out-of-required-order-tp18495510p18495510.html
Sent from the QuickFIX - User mailing list archive at Nabble.com.