DerivativeCountryOfIssue (FIX tag 1258)
DerivativeCountryOfIssue (tag 1258) is a Country field defined in FIX 5.0 SP2. It appears in 3 message types, always optionally.
At a glance
- Tag
- 1258
- Name
- DerivativeCountryOfIssue
- Datatype
- Country (String)
- Dialects
- FIX 5.0 SP2
- Messages
- 3
What the specification says
ISO Country code of instrument issue (e.g. the country portion typically used in ISIN).
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1258
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 89 | |
| 35 | MsgType | z | DerivativeSecurityListRequest |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 320 | SecurityReqID | EXAMPLE | |
| 559 | SecurityListRequestType | 0 | Symbol |
| 1258 | DerivativeCountryOfIssue | ES | |
| 10 | CheckSum | 228 |
Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.
Generated from the FIX 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Where tag 1258 appears
Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.
| Message | MsgType | Requiredness | Where in the message |
|---|---|---|---|
| DerivativeSecurityList | AA | Optional | inside DerivativeSecurityDefinition › DerivativeInstrument |
| DerivativeSecurityListRequest | z | Optional | inside the DerivativeInstrument component |
| DerivativeSecurityListUpdateReport | BR | Optional | inside DerivativeSecurityDefinition › DerivativeInstrument |
Wire format
A two-letter ISO 3166 country code. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.
Read tag 1258 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1258];field?.name; // "DerivativeCountryOfIssue"field?.raw; // the verbatim wire stringfield?.value; // coerced to a stringOther Country fields
Decode this in your own code
The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.
npm i @boarteam/fix @boarteam/fix-dict-fix50sp2