| ID | MsgType | Abbr | Flow |
|---|---|---|---|
| 50 | q | OrdMassCxlReq |
| 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: |
| 11 | ClOrdID | ClOrdID | required | SYNOPSIS:
Unique identifier for Order as assigned by the buy-side (institution, broker, intermediary etc.) (identified by SenderCompID (49) or OnBehalfOfCompID (5) as appropriate). Uniqueness must be guaranteed within a single trading day. Firms, particularly those which electronically submit multi-day orders, trade globally or throughout market close periods, should ensure uniqueness across days, for example by embedding a date within the ClOrdID field.
|
| 526 | SecondaryClOrdID | ClOrdID2 | optional | SYNOPSIS:
Assigned by the party which originates the order. Can be used to provide the ClOrdID (11) used by an exchange or executing system.
|
| 530 | MassCancelRequestType | MassCxlReqTyp | required | SYNOPSIS:
Specifies scope of Order Mass Cancel Request
|
| 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
|
| 60 | TransactTime | TxnTm | required | SYNOPSIS:
Time of execution/order creation (expressed in UTC (Universal Time Coordinated, also known as "GMT")
|
| 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 field.
|
| 1025 | StandardTrailer | Trlr | required | SYNOPSIS:
The standard FIX message trailer
ELABORATION: |