epam / epam/java-cme-mdp3-handler
Issue parsing MaturityMonthYear
Open
- Dominant language
- Java
- Stars
- 83
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
I'm having an issue with the UDP MDP client where the MatruiryMonthYear field on
the SecurityDefinitions (MDInstrumentDefinitionFuture54) are returning
invalid month values:
MaturityMonthYear=2026/241
Is there any special handling needed before reading this field? My current code
uses:
SbeMonthYear monthYear = SbeMonthYear.instance();
mdpMessage.getMonthYear(200, monthYear);
short month = monthYear.getMonth();
I seem to either get a value of zero or 241
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.