FIX 5.0 : SecurityDefinitionRequest <c> message

Structure | Related Messages

Description

The Security Definition Request message is used for the following:

1. Request a specific Security to be traded with the second party. The request security can be defined as a multileg security made up of one or more instrument legs.

Subscription for security status can be optionally specified by including the SubscriptionRequestType <263>[263] field on the message.

See 'Security Definition, Security Status, and Trading Session Message Scenarios'

Security Definition Request

Structure

Tag Field Name Req'd Comments
<MessageHeader> Y MsgType <35> = c
320 SecurityReqID Y
321 SecurityRequestType Y
Component Block - <Instrument> N Insert here the set of "Instrument" (symbology) fields defined in "Common Components of Application Messages" of the requested Security
Component Block - <InstrumentExtension> N Insert here the set of "InstrumentExtension" fields defined in "Common Components of Application Messages"
Component Block - <UndInstrmtGrp> N Number of underlyings
15 Currency N
58 Text N Comment, instructions, or other identifying information.
354 EncodedTextLen N Must be set if EncodedText field is specified and must immediately precede it.
355 EncodedText N Encoded (non-ASCII characters) representation of the Text field in the encoded format specified via the MessageEncoding field.
336 TradingSessionID N Optional Trading Session Identifier to specify a particular trading session for which you want to obtain a list of securities that are tradeable.
625 TradingSessionSubID N
Component Block - <InstrmtLegGrp> N Number of legs that make up the Security
827 ExpirationCycle N
263 SubscriptionRequestType N Subscribe or unsubscribe for security status to security specified in request.
<MessageTrailer> Y

 

Related Messages

Onix Solutions