RE: [Quickfix-developers] Tag missing messages

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Shankar,
=20
It looks like ill-formed message but the reject reflects a side-effect
rather than the direct cause of problem. Your message appears to be
missing tag 453 (NoPartyIDs) which is a group indicator for the group
within the "Parties" component in the NoSides group. Because this tag is
missing, the parsing of the NoSides group ends before the order ID is
parsed. The order ID is in the message fields but not within the group
where it is expected and required. My guess is your error is related to
how your are setting the data for the NoPartyIDs group. Are you setting
the PartyID field directly on the NoSides group or the top level
message? If so, this will break the parsing and subsequent validation of
the message.
=20
Look at tag 453 in the FIX 4.4 specification and at the
TradeCaptureReport/NoSides/NoPartyIDs group class. I'm a Java guy so the
names may be a little different in C# but they should be close.
=20
Steve Bate
Smart Trade Technologies
Phone: +33 4 42 90 03 97
http://www.smart-trade.net/

________________________________

	From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Shankar Krishnan
	Sent: Tuesday, February 07, 2006 11:22 PM
	To: Shankar Krishnan; qui...@li...
	Subject: [Quickfix-developers] Tag missing messages
=09
=09

	=20

	Hi,

	=20

	Has anyone implemented TradeCaptureReports in FIX 4.4 using
QuickFIX. I have run into a problem as mentioned below.

	I do have onMessage handlers for all tradecapture related
messages, yet a business reject message is being sent back

	I presume due to a message I am not handling, I donot see a
problem, any ideas appreciated.

	=20

	Tks

	=20

	=20

=09
________________________________

	From: Shankar Krishnan=20
	Sent: Tuesday, February 07, 2006 11:12 AM
	To: qui...@li...
	Subject: RE: [Quickfix-developers] ToApp : 58=3DUnsupported
Message Type mes sages

	=20

	=20

	Hi,

	=20

	Below is the logfile, I see tag 37 in the logfile, however my
app is sending out the error message:

	=20

	To
Admin:::::8=3DFIX.4.4_=3D122_5=3D3_4=3D167_9=3Dxxx-TCR-TEST_2=3D20060207-=
15:47:58.75
3_6=3DFOX-FIX-ENGINE_5=3D203_8=3DRequired tag missing371=3D37 372=3DAE =
373=3D1
10=3D033

	=20

	Is there any reason for this issue.

	=20

	---logfile--------------------------------------

	14:25:19,703 INFO  - <80 TradeCaptureReportRequest
(8=3DFIX.4.4^A9=3D101^A35=3DAD^A34=3D80^A49=3Dxxx-tcr-xx^A52=3D20060207-1=
4:25:13.128
^A56=3Dyyy-yy-yy^A58=3DTCR^A263=3D1^A568=3Dabc101^A569=3D0^A10=3D036^A)

	=20

	14:25:20,262 INFO  - >89 TradeCaptureReportRequestAck
(8=3DFIX.4.4^A9=3D96^A35=3DAQ^A34=3D89^A49=3Dyyy-yy-yy^A56=3Dxxx-tcr-xx^A=
52=3D20060207
-

	14:25:20^A568=3Dabc101^A569=3D0^A749=3D0^A750=3D0^A10=3D202^A)

	=20

	=20

	14:25:20,370 INFO  - >92 TradeCaptureReport
(8=3DFIX.4.4^A9=3D395^A35=3DAE^A34=3D92^A49=3Dyyy-yy-yy^A56=3Dxxx-tcr-xx^=
A52=3D2006020
7-

=09
14:25:20^A571=3DCYCCDQWC10528854294967292^A568=3Dabc101^A150=3D2^A39=3D2^=
A17=3D007
RR0000L^A570=3DY^A55=3DUSD/JPY^A40=3DD^A167=3DFOR^A38=3D450000.000000^A60=
54=3D3817.6
00000^A44=3D117.875000^A32=3D450000.000000^A31=3D117.8750

=09
00^A194=3D117.875000^A195=3D0.0000^A75=3D20060207^A6215=3DSP^A60=3D200602=
07-14:02:
48^A552=3D1^A54=3D1^A448=3DJpuy-TEST^A447=3DmtyreYK^A452=3DTRADER^A37=3D0=
07RR0000L^A
64=3D20060208^A15=3DJPY^A487=3DN^A10=3D202^A)

	=20

	=20

	=20

	=20

=09
________________________________

	From: Shankar Krishnan=20
	Sent: Tuesday, February 07, 2006 10:55 AM
	To: 'Shepheard, Toby (London)';
qui...@li...
	Subject: RE: [Quickfix-developers] ToApp : 58=3DUnsupported
Message Type mes sages

	=20

	=20

	Thanks,=20

	=20

	Done, apologies.  Fixed most of my issues by following what you
mentioned. The only issue I have is with the an Admin level message

	That my app is sending out -  Required Tag missing for tag 37
which is order Id, I can see tag 37 in the trade capture report,  I do
have

	My own  onMessage for TradeCaptureReport msgType =3D AD, why
should this happen.

	=20

	Thanks

	=20

	=20

=09
________________________________

	From: Shepheard, Toby (London) [mailto:Tob...@ml...]=20
	Sent: Tuesday, February 07, 2006 9:59 AM
	To: Shankar Krishnan; qui...@li...
	Subject: RE: [Quickfix-developers] ToApp : 58=3DUnsupported
Message Type messages

	=20

	1) If you haven't already, make sure you read this:
http://www.quickfixengine.org/quickfix/doc/html/receiving_messages.html
<http://www.quickfixengine.org/quickfix/doc/html/receiving_messages.html
%20>=20

	2) Follow the instructions under "Most Type Safe... DO THIS!"

	3) Implement your version of onMessage which takes the
TradeCaptureReportRequestAck message and acts on it in whatever manner
you want to.

	4) Implement your version of onMessage which takes the
TradeCaptureReport message and acts on that appropriately.

	=20

	The following is from
http://www.quickfixengine.org/quickfix/doc/html/application.html

	fromApp is one of the core entry points for your FIX
application. Every application level request will come through here. If,
for example, your application is a sell-side OMS, this is where you will
get your new order requests. If you were a buy side, you would get your
execution reports here. If a FieldNotFound exception is thrown, the
counterparty will receive a reject indicating a conditionally required
field is missing. The Message class will throw this exception when
trying to retrieve a missing field, so you will rarely need the throw
this explicitly. You can also throw an UnsupportedMessageType exception.
This will result in the counterparty getting a reject informing them
your application cannot process those types of messages. An
IncorrectTagValue can also be thrown if a field contains a value that is
out of range or you do not support.

	=20

	The default implementation will always result in the behaviour
I've highlighted in bold. This is what is happening in your case. You
need to override this default behaviour by implementing the onMessage
calls for the application message types you are expecting (note that
admin messages are handled for you)

	=20

		-----Original Message-----
		From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Shankar Krishnan
		Sent: 07 February 2006 14:51
		To: Shankar Krishnan;
qui...@li...
		Subject: RE: [Quickfix-developers] ToApp :
58=3DUnsupported Message Type messages

		=20

		Hi,

		=20

		=20

		My counterparty has sent me his logs, he does receive my
TradeCaptureReportRequest ,

		Followed by  TradeCaptureReportRequestAck =3D AQ. This is
followed by 3 TradeCaptureReports

		At this point my App is sending out a
BusinessMessageReject,

		=20

		Why would the app send out a Business Message Reject on
the AQ ?

		=20

		Any help appreciated.

		=20

		Thanks

		=20

	=09
________________________________

		From: Shankar Krishnan=20
		Sent: Tuesday, February 07, 2006 9:12 AM
		To: qui...@li...
		Subject: [Quickfix-developers] ToApp : 58=3DUnsupported
Message Type messages

		=20

		=20

		Hi,

		=20

		ToApp is sending out the following message: The message
type is Business Message Reject,=20

		=20

		58=3DUnsupported Message Type

		372=3DAQ

		380=3D3

		10=3D075

		=20

		35 =3D j, Where j =3D Business Message Reject

		=20

		I donot see a reason why this reject should happen .

		Tks

		=20

		=20

		=20

=09
________________________________

	If you are not an intended recipient of this e-mail, please
notify the sender, delete it and do not read, act upon, print, disclose,
copy, retain or redistribute it. Click here
<http://www.ml.com/email_terms/> for important additional terms relating
to this e-mail.     http://www.ml.com/email_terms/

=09
________________________________