The Derivative Security List Update Report message is used to send updates to an option family or the strikes that comprise an option family.
| Tag | Field Name | FIXML | Req'd | Comments | |||
|---|---|---|---|---|---|---|---|
| <Standard Message Header> | Y | MsgType = BR | |||||
| <ApplicationSequenceControl> | N | ||||||
| 320 | SecurityReqID | @ReqID | N |
Unique ID of a Security Definition Request. |
|||
| 322 | SecurityResponseID | @RspID | N |
Identifier for the Derivative Security List message |
|||
| 560 | SecurityRequestResult | @ReqRslt | N |
Result of the Security Request identified by SecurityReqID |
|||
| 980 | SecurityUpdateAction | @UpdActn | N |
Updates can be applied to Underlying or option class. If Series information provided, then Series has explicitly changed |
|||
| <UnderlyingInstrument> | N | ||||||
| <DerivativeSecurityDefinition> | N | ||||||
| 779 | LastUpdateTime | @LastUpdateTm | N |
Represents the time at which a security was last updated |
|||
| 60 | TransactTime | @TxnTm | N |
Timestamp when the business transaction represented by the message occurred. |
|||
| 393 | TotNoRelatedSym | @TotNoReltdSym | N |
Used to indicate the total number of securities being returned for this request. Used in the event that message fragmentation is required. |
|||
| 893 | LastFragment | @LastFragment | N |
Indicates whether this is the last fragment in a sequence of message fragments. Only required where message has been fragmented. |
|||
| <RelSymDerivSecUpdGrp> | N |
Specifies semantically the type of the attached document from a business perspective. The default classification scheme reuses the FIX standard classification scheme of a high level section (pretrade, trade, posttrade, etc.) and a category, then a specific application or document type. The expression follows {"section/category/application type"}. The goal here is to map the attachment into the sections and categories of the FIX business messages if possible. The classification scheme can be expanded or replaced by counterparty agreement. This approach permits the introduction and reference to other business ontologies. Example: posttrade/confirmation/confirm pretrade//termsheet |
|||||
| <Standard Message Trailer> | Y | ||||||
© 2026.
EPAM Systems. All Rights Reserved.
All material contained within the website is copyright of EPAM Systems, Inc. No material contained herein can be copied or otherwise used without the express permission of the copyright holder.