| ID | MsgType | Abbr | Flow |
|---|---|---|---|
| 65 | AF | OrdMassStatReq |
| Added | EP | Updated | EP | Deprecated | EP |
|---|---|---|---|---|---|
| FIX.4.3 |
| ID | Name | Abbr | Presence | Description |
|---|---|---|---|---|
| 1024 | StandardHeader | Hdr | required | SYNOPSIS:
The standard FIX message header
ELABORATION: |
| 584 | MassStatusReqID | MassStatReqID | required | SYNOPSIS:
Value assigned by issuer of Mass Status Request to uniquely identify the request
|
| 585 | MassStatusReqType | MassStatReqTyp | required | SYNOPSIS:
Mass Status 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: |
| 1 | Account | Acct | optional | SYNOPSIS:
Account mnemonic as agreed between buy and sell sides, e.g. broker and institution or investor/intermediary and fund manager.
|
| 660 | AcctIDSource | AcctIDSrc | optional | SYNOPSIS:
Used to identify the source of the Account (1) code. This is especially useful if the account is a new account that the Respondent may not have setup yet in their system.
|
| 336 | TradingSessionID | SesID | optional | SYNOPSIS:
Identifier for Trading Session
Can be used to represent a specific market trading session (e.g. "PRE-OPEN", "CROSS_2", "AFTER-HOURS", "TOSTNET", "TOSTNET2", etc).
To specify good for session where session spans more than one calendar day, use TimeInForce = Day in conjunction with TradingSessionID.
Values should be bi-laterally agreed to between counterparties.
Firms may register Trading Session values on the FIX website (presently a document maintained within "ECN and Exchanges" working group section).
|
| 625 | TradingSessionSubID | SesSub | optional | SYNOPSIS:
Optional market assigned sub identifier for a trading session. Usage is determined by market or counterparties.
Used by US based futures markets to identify exchange specific execution time bracket codes as required by US market regulations.
|
| 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: |
| 1021 | UnderlyingInstrument | Undly | optional | SYNOPSIS:
The UnderlyingInstrument component block, like the Instrument component block, contains all the fields commonly used to describe a security or instrument. In the case of the UnderlyingInstrument component block it describes an instrument which underlies the primary instrument Refer to the Instrument component block comments as this component block mirrors Instrument, except for the noted fields.
ELABORATION: |
| 54 | Side | Side | optional | SYNOPSIS:
Side of order
|
| 1025 | StandardTrailer | Trlr | required | SYNOPSIS:
The standard FIX message trailer
ELABORATION: |