MaturityMonthYearIncrement (FIX tag 1229)
MaturityMonthYearIncrement (tag 1229) is an int field defined in FIX 5.0 SP2. It appears in 6 message types, always optionally.
At a glance
- Tag
- 1229
- Name
- MaturityMonthYearIncrement
- Datatype
- int
- Dialects
- FIX 5.0 SP2
- Messages
- 6
What the specification says
Increment between successive maturities for an option class
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1229
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 147 | |
| 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 | NoStrikeRules1 entry | 1 | repeating group |
| 1223 | StrikeRuleID | EXAMPLE | |
| 1236 | NoMaturityRules2 entries | 2 | repeating group |
| 1222 | MaturityRuleID | EXAMPLE | |
| 1229 | MaturityMonthYearIncrement | 1 | |
| 1222 | MaturityRuleID | EXAMPLE | |
| 1229 | MaturityMonthYearIncrement | 1 | |
| 10 | CheckSum | 241 |
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 1229 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 › MaturityRules |
| DerivativeSecurityListUpdateReport | BR | Optional | inside DerivativeSecurityDefinition › MarketSegmentGrp › StrikeRules › MaturityRules |
| SecurityDefinition | d | Optional | inside MarketSegmentGrp › StrikeRules › MaturityRules |
| SecurityDefinitionUpdateReport | BP | Optional | inside MarketSegmentGrp › StrikeRules › MaturityRules |
| SecurityList | y | Optional | inside SecListGrp › StrikeRules › MaturityRules |
| SecurityListUpdateReport | BK | Optional | inside SecLstUpdRelSymGrp › StrikeRules › MaturityRules |
Wire format
A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.
Read tag 1229 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[1229];field?.name; // "MaturityMonthYearIncrement"field?.raw; // the verbatim wire stringfield?.value; // coerced to a numberOther int fields
- 1246DerivativeProduct
- 1210NestedInstrAttribType
- 1209TickRuleType
- 1198ListMethod
- 1194ExerciseStyle
- 1273DerivativePositionLimit
- 1274DerivativeNTPositionLimit
- 1178MDSecSizeType
- 1176StatsType
- 1174SecurityTradingEvent
- 1173MDSubBookType
- 1172RespondentType
- 1287DerivativeEventType
- 1170TotNoRejQuotes
- 1169TotNoAccQuotes
- 1168TotNoCxldQuotes
- 1167QuoteEntryStatus
- 1295DerivativeInstrumentPartyRole
- 1298DerivativeInstrumentPartySubIDType
- 1159SettlObligMode
- 1156ApplExtID
- 1302MaturityMonthYearIncrementUnits
- 1303MaturityMonthYearFormat
- 1304StrikeExerciseStyle
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