Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
SecurityRequestType <321>
- Tag
321- Type
- int · code set
SecurityRequestTypeCodeSet - Pedigree
- Added FIX 4.2
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓
This page shows SecurityRequestType <321> as defined in FIX 4.2. For the current standard, see tag 321 SecurityRequestType in FIX Latest.
SecurityRequestType <321> in plain English
Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).
SecurityRequestType gives the type of Security Definition Request, for example to request a security's identity and specifications.
Common values
| Value | Name |
|---|---|
321=0 | RequestSecurityIdentityAndSpecifications |
321=1 | RequestSecurityIdentityForSpecifications |
A selection. The full list of values is in the table further down.
Where it is used
SecurityDefinitionRequest (35=c) .
In all, 1 message in FIX 4.2 can carry it. Full list.
Example message
8=FIX.4.2|9=92|35=c|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|320=SDR-1|321=0|55=ESZ6|167=FUT|10=128 Illustrative example, not real orders or market data. A SecurityDefinitionRequest (35=c) in FIX 4.2, shown with BeginString FIX.4.2. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.2 dictionary, but it is not a complete specification of the message.
Description (from the Orchestra file)
Type of Security Definition Request.
Values (4)
Used in
Messages (1)
| Message | MsgType | Presence |
|---|---|---|
| SecurityDefinitionRequest | c | Required |