The Security Status Request message provides for the ability to request the status of a security. One or more Security Status messages are returned as a result of a Security Status Request message.
Added in protocol FIX.4.2
See in: FIX.4.2, FIX.4.3, FIX.4.4, FIX.5.0SP1, FIX.5.0SP2, FIX.5.0SP2 EP240.
Field or Component | Name | Description | Is Required | Added | Is Deprecated |
---|---|---|---|---|---|
Block | StandardHeader | MsgType = e (lowercase) | Y | FIX.4.2 | |
324 | SecurityStatusReqID | Must be unique, or the ID of previous Security Status Request to disable if SubscriptionRequestType = Disable previous Snapshot + Updates Request (2). | Y | FIX.4.2 | |
Block | Instrument | Insert here the set of "Instrument" (symbology) fields defined in "Common Components of Application Messages" | Y | FIX.4.3 | |
Block | InstrumentExtension | Insert here the set of "InstrumentExtension" fields defined in "Common Components of Application Messages" | FIX.4.4 | ||
OptimisedImplicitBlockRepeating | UndInstrmtGrp | Number of underlyings | FIX.4.4 | ||
OptimisedImplicitBlockRepeating | InstrmtLegGrp | Number of legs that make up the Security | FIX.4.4 | ||
15 | Currency | FIX.4.2 | |||
263 | SubscriptionRequestType | SubcriptionRequestType indicates to the other party what type of response is expected. A snapshot request only asks for current information. A subscribe request asks for updates as the status changes. Unsubscribe will cancel any future update messages from the counter party.) | Y | FIX.4.2 | |
336 | TradingSessionID | FIX.4.2 | |||
625 | TradingSessionSubID | FIX.4.3 | |||
Block | StandardTrailer | Y | FIX.4.2 |