| ID | MsgType | Abbr | Flow |
|---|---|---|---|
| 151 | DO | MDStatsReq |
| Added | EP | Updated | EP | Deprecated | EP |
|---|---|---|---|---|---|
| FIX.5.0SP2 | 191 |
| ID | Name | Abbr | Presence | Description |
|---|---|---|---|---|
| 1024 | StandardHeader | BaseHeader | required | SYNOPSIS:
The standard FIX message header
ELABORATION: |
| 2452 | MDStatisticReqID | ReqID | required | SYNOPSIS:
Message identifier for a statistics request.
|
| 263 | SubscriptionRequestType | SubReqTyp | required | SYNOPSIS:
Subscription Request Type
|
| 1012 | Parties | Pty | optional | SYNOPSIS:
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: |
| 75 | TradeDate | TrdDt | optional | SYNOPSIS:
Indicates date of trading day. Absence of this field indicates current day (expressed in local time at place of trade).
|
| 1301 | MarketID | MktID | optional | SYNOPSIS:
Identifies the market
|
| 1300 | MarketSegmentID | MktSegID | optional | SYNOPSIS:
Identifies the market segment
|
| 1396 | MarketSegmentDesc | MarketSegmentDesc | optional | SYNOPSIS:
Description or name of Market Segment
|
| 1397 | EncodedMktSegmDescLen | EncodedMktSegmDescLen | optional | SYNOPSIS:
Byte length of encoded (non-ASCII characters) EncodedMktSegmDesc(1324) field.
|
| 1398 | EncodedMktSegmDesc | EncodedMktSegmDesc | optional | SYNOPSIS:
Encoded (non-ASCII characters) representation of the MarketSegmDesc(1396) field in the encoded format specified via the MessageEncoding(347) field. If used, the ASCII (English) representation should also be specified in the MarketSegmDesc field.
|
| 1465 | SecurityListID | ListID | optional | SYNOPSIS:
Specifies an identifier for a Security List
|
| 1003 | Instrument | Instrmt | optional | SYNOPSIS:
The Instrument component block contains all the fields commonly used to describe a security or instrument. Typically the data elements in this component block are considered the static data of a security, data that may be commonly found in a security master database. The Instrument component block can be used to describe any asset type supported by FIX.
ELABORATION: |
| 1004 | InstrumentExtension | InstrmtExt | optional | SYNOPSIS:
The InstrumentExtension component block identifies additional security attributes that are more commonly found for Fixed Income securities.
ELABORATION: |
| 1002 | FinancingDetails | FinDetls | optional | SYNOPSIS:
Component block is optionally used for financial transaction where legal contracts, master agreements or master confirmations is to be referenced. This component identifies the legal agreement under which the deal was made and other unique characteristics of the transaction. For example, the AgreementDesc(913) field refers to base standard documents such as MRA 1996 Repurchase Agreement, GMRA 2000 Bills Transaction (U.K.), MSLA 1993 Securities Loan – Amended 1998, for example.
ELABORATION: |
| 2066 | UndInstrmtGrp | Undly | optional | SYNOPSIS: ELABORATION: |
| 2019 | InstrmtLegGrp | Leg | optional | SYNOPSIS: ELABORATION: |
| 1066 | RelatedInstrumentGrp | ReltdInstrmt | optional | SYNOPSIS:
The RelatedInstrumentGrp is a repeating component at the same hierarchical level as the Instrument component, describing relationships and linkages between the Instrument, UnderlyingInstrument and InstrumentLeg entries. If all instances of the UnderlyingInstrument in the message are true underliers of the Instrument then the RelatedInstrumentGrp component is not needed. If any instance of the UnderlyingInstrument has a different relationship, e.g. underlier of an InstrumentLeg, stream, equity equivalent or nearest exchange-traded contract or there are multiple instances of InstrumentLeg, then an entry for every relationship should be included in this component. When the RelatedInstrumentGrp appears within a repeating group, each entry only apply to the Instrument component at the same hierarchical level.
In messages, such as Email(35=C) and News(35=B), where Instrument and the InstrumentLeg are within their repeating groups, the RelatedInstrumentGrp component may be used to link legs and underliers to their appropriate base Instrument.
ELABORATION: For simple relationships such as identifying a "hedges for" security the entry simply defines the symbol or identifier of an externally known security. For relationships within strategies and swaps the entry refers up through one of the "related to" fields to the Instrument, InstrumentLeg, UnderlyingInstrument, stream or dividend period with which the related security has correlation. It then points down through RelatedSecurityID(1650) or RelatedSymbol(1649) to an UnderlyingInstrument instance in the current message defining the related security. The nature of the relationship is given in RelatedInstrumentType(1648). |
| 2248 | MDStatisticReqGrp | StatsReq | optional | SYNOPSIS:
This component block is used within the MarketDataStatisticsRequest(35=DO) message to define a set of parameters describing the desired statistics.
ELABORATION: |
| 60 | TransactTime | TxnTm | optional | SYNOPSIS:
Timestamp when the business transaction represented by the message occurred.
|
| 58 | Text | Txt | optional | SYNOPSIS:
Free format text string
(Note: this field does not have a specified maximum length)
|
| 354 | EncodedTextLen | EncTxtLen | optional | SYNOPSIS:
Byte length of encoded (non-ASCII characters) EncodedText (355) field.
|
| 355 | EncodedText | EncTxt | 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.
|
| 1025 | StandardTrailer | Trlr | optional | SYNOPSIS:
The standard FIX message trailer
ELABORATION: |