Messages by MsgType |  Messages by Name |  Fields by Tag |  Fields by Name |  FIX 4.3 | Home

FIX 4.3 : Security Definition Request <c> message

Structure | Related Messages

Description

The Security Definition Request <c> 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 <d>, Security Status <f>, and Trading Session Message Scenarios"

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

15 Currency N
58 Text N

Comment, instructions, or other identifying information.

354 EncodedTextLen N

Must be set if EncodedText <355> field is specified and must immediately precede it.

355 EncodedText N

Encoded (non-ASCII characters) representation of the Text <58> field in the encoded format specified via the MessageEncoding <347> 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
555 NoLegs N

Number of legs that make up the Security

=> Component Block - <InstrumentLeg> N

Insert here the set of "<InstrumentLeg>" (leg-specific symbology) fields defined in "COMMON COMPONENTS OF APPLICATION MESSAGES"

Required if NoLegs <555> > 0.

=> 556 LegCurrency N
263 SubscriptionRequestType N

Subscribe or unsubscribe for security status to security specified in request.

<MessageTrailer> Y  

Related Messages

Onix Solutions