StrikeIncrement (FIX tag 1204)
StrikeIncrement (tag 1204) is a float field defined in FIX 5.0 SP2. It appears in 6 message types, always optionally.
At a glance
- Tag
- 1204
- Name
- StrikeIncrement
- Datatype
- float
- Dialects
- FIX 5.0 SP2
- Messages
- 6
What the specification says
Value by which strike price should be incremented within the specified price range.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1204
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 131 | |
| 35 | MsgType | d | SecurityDefinition |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 1310 | NoMarketSegments1 entry | 1 | repeating group |
| 1301 | MarketID | XNAS | |
| 1201 | NoStrikeRules2 entries | 2 | repeating group |
| 1223 | StrikeRuleID | EXAMPLE | |
| 1204 | StrikeIncrement | 1.0 | |
| 1223 | StrikeRuleID | EXAMPLE | |
| 1204 | StrikeIncrement | 1.0 | |
| 10 | CheckSum | 077 |
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 1204 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 › MarketSegmentGrp › StrikeRules |
| DerivativeSecurityListUpdateReport | BR | Optional | inside DerivativeSecurityDefinition › MarketSegmentGrp › StrikeRules |
| SecurityDefinition | d | Optional | inside MarketSegmentGrp › StrikeRules |
| SecurityDefinitionUpdateReport | BP | Optional | inside MarketSegmentGrp › StrikeRules |
| SecurityList | y | Optional | inside SecListGrp › StrikeRules |
| SecurityListUpdateReport | BK | Optional | inside SecLstUpdRelSymGrp › StrikeRules |
Wire format
A decimal number. The wire form keeps its trailing zeros, which is why decoders expose the raw string alongside the parsed number. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.
Read tag 1204 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[1204];field?.name; // "StrikeIncrement"field?.raw; // the verbatim wire stringfield?.value; // coerced to a numberOther float fields
- 1190RiskFreeRate
- 1189TimeToExpiration
- 1188Volatility
- 1263DerivativeStrikeMultiplier
- 1264DerivativeStrikeValue
- 1143MaxPriceVariation
- 1266DerivativeContractMultiplier
- 1267DerivativeMinPriceIncrement
- 1329FeeMultiplier
- 1045UnderlyingFXRate
- 1379LegVolatility
- 1026MDEntrySpotRate
- 1382CurrencyRatio
- 1383LegCurrencyRatio
- 1017LegOptionRatio
- 969MinPriceIncrement
- 968StrikeValue
- 967StrikeMultiplier
- 850TargetStrategyPerformance
- 811PriceDelta
- 657SettlCurrOfferFxRate
- 656SettlCurrBidFxRate
- 623LegRatioQty
- 614LegContractMultiplier
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