Message MarketDataRequestReject Scenario base

SYNOPSIS: The Market Data Request Reject is used when the broker cannot honor the Market Data Request, due to business or technical reasons. Brokers may choose to limit various parameters, such as the size of requests, whether just the top of book or the entire book may be displayed, and whether Full or Incremental updates must be used.

ID MsgType Abbr Flow
32YMktDataReqRej

Pedigree

Added EP Updated EP Deprecated EP
FIX.4.2

Responses

None

Members

MarketDataRequestReject base members
ID Name Abbr Presence Description
1024StandardHeaderBaseHeaderrequiredSYNOPSIS: The standard FIX message header
ELABORATION:
262MDReqIDReqID required SYNOPSIS: Unique identifier for Market Data Request
1012PartiesPtyoptionalSYNOPSIS: The Parties component block is used to identify and convey information on the entities both central and peripheral to the financial transaction represented by the FIX message containing the Parties Block. The Parties block allows many different types of entites to be expressed through use of the PartyRole field and identifies the source of the PartyID through the the PartyIDSource.
ELABORATION:
281MDReqRejReasonReqRejResn optional SYNOPSIS: Reason for the rejection of a Market Data request.
2034MDRjctGrpRjctoptionalSYNOPSIS:
ELABORATION:
58TextTxt optional SYNOPSIS: Free format text string (Note: this field does not have a specified maximum length)
354EncodedTextLenEncTxtLen optional SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedText (355) field.
355EncodedTextEncTxt optional SYNOPSIS: Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text(58) field.
1025StandardTrailerTrlrrequiredSYNOPSIS: The standard FIX message trailer
ELABORATION: