RE: [Quickfix-developers] ToApp : 58=Unsupported Message Type mes sages

[Shankar K. <skr...@jw...>]

 

Thanks, 

 

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 = AD, why should this
happen.

 

Thanks

 

 

  _____  

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

 

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>


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.

 

The following is from
http://www.quickfixengine.org/quickfix/doc/html/application.html
<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.

 

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)

 

-----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=Unsupported Message Type
messages

 

Hi,

 

 

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

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

At this point my App is sending out a BusinessMessageReject,

 

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

 

Any help appreciated.

 

Thanks

 


  _____  


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

 

 

Hi,

 

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

 

58=Unsupported Message Type

372=AQ

380=3

10=075

 

35 = j, Where j = Business Message Reject

 

I donot see a reason why this reject should happen .

Tks

 

 

 

  _____  

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/ <http://www.ml.com/email_terms/> 

  _____