Size limitation to String types

, ,
1

Imported from previous forum

2

[ original email was from Jochen de Lima - jdelima@siac.com ]
Specifically, I would like to apply this to the QuoteID (#117) tag, but the discussion could be generalized to some other defined string-type tags.

If an application receives a message that passes session validation, but the tag value is a string that is too long for the application to handle, what would the rejection message be?

Thanks.

3

> Specifically, I would like to apply this to the QuoteID (#117) tag, but the discussion could be generalized to some other defined string-type tags.
>
> If an application receives a message that passes session validation, but the tag value is a string that is too long for the application to handle, what would the rejection message be?
>
> Thanks.

Well, it rather depends on the message you receieved and the workflow you were in. eg, if I was in the Indicative Quoting Model and I recieved a QuoteRequest ® with a QuoteReqID (131) that was too long my first choice would be to send a QuoteRequestReject(AG).

If for some reason the String length problem prevented my application from forming a proper QuoteRequestReject, I’d probably send a BusinessMessageReject(j) as a fallback solution. You can learn about this message in Volume 1 of the FIX specification. (Exactly when you are technically allowed to send BusinessMessageReject varies depending on the FIX protocol version you are using, but it does serve as a useful “catch-all” error, if your counterparty can handle it.)

If you can be more specific about your workflow and message types, people here can probably offer more targetted advice.