{{Quickfixn}} Invalid Type TENOR

[Grant Birchmeier]

Sagar, next time please give a little more info in your issue report.
(e.g. *When* are you getting that error?  What field are you decoding?)

But I think Lanfranco is correct.  You are probably getting a tag 63 value
that is not defined in your DD.

(Not sure if this is about tag 63, but the advice should be similar for
other tags.)

The default tag 63 def is:  (this is FIX50SP2, it might differ in other
versions)
  <field number='63' name='SettlType' type='STRING'>
   <value enum='0' description='REGULAR' />
   <value enum='1' description='CASH' />
   <value enum='2' description='NEXT_DAY' />
   <value enum='3' description='T_PLUS_2' />
   <value enum='4' description='T_PLUS_3' />
   <value enum='5' description='T_PLUS_4' />
   <value enum='6' description='FUTURE' />
   <value enum='7' description='WHEN_AND_IF_ISSUED' />
   <value enum='8' description='SELLERS_OPTION' />
   <value enum='9' description='T_PLUS_5' />
   <value enum='C' description='FX_SPOT_NEXT_SETTLEMENT' />
   <value enum='B' description='BROKEN_DATE' />
  </field>

If you receive a 63 that doesn't match 0-9 or B or C, your engine will
reject it.  Two ways to fix:

1) Add the "new" 63 value as another <value enum=""> entry
2) Delete all the <value enum=""> entries, turning 63 into a plain string
(this is what Lanfranco advised).

-Grant

On Tue, Oct 6, 2020 at 6:31 AM Lanfranco Morini <Lanfranco.Morini at cegeka.it>
wrote:

> Hi Sagar,
>
> TENOR type in FIX Protocol is not defined as a “standard” DataType such as
> String, Int, etc., but as a Pattern - that is “a string that can contain
> also a well-defined data structure” - as you can see on fiximate
> documentation for tag 63
> https://fiximate.fixtrading.org/legacy/en/FIX.5.0/tag63.html: there you
> ca see that the field 63 DataType is String, but it has also a Union
> DataType (Tenor) that allows the field to contain in addition to elder
> enums, also some particular value (Dx, Mx, etc.)
>
> In fact tag 63 is defined as String in the “original” (FIX50.xml for
> example) DataDictionary …
>
> To apply a workaround to this problem you could change, in your
> DataDictionary, type “TENOR” to “STRING”, and also, delete all the enum
> values: in this way you will be able to accept every received values –
> TENRO included - , but at the same time you should parse each “Tenor” field…
>
>
>
> Hope this can help…
>
>
>
> Best,
>
> Lan
>
>
>
> *From:* Quickfixn <quickfixn-bounces at lists.quickfixn.com> *On Behalf Of *sagar
> kohli
> *Sent:* martedì 6 ottobre 2020 12:50
> *To:* Mailing list for QuickFIX/n <quickfixn at lists.quickfixn.com>
> *Subject:* {{Quickfixn}} Invalid Type TENOR
>
>
>
> Hi,
>
>
>
> I am getting error invalid type: error.
>
>
>
> I have tried using fix version 1.10.0. So does this mean these data type
> are currently not supported.
>
> Or is there something I am missing?
>
>
>
> Regards
>
> Sagar Kohli
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>


-- 
Grant Birchmeier
*Connamara Systems, LLC*
*Made-To-Measure Trading Solutions.*
Exactly what you need. No more. No less.
http://connamara.com

-- 
This email, along with any attachments, is confidential. If you believe you 
received this message in error, please contact the sender immediately and 
delete all copies of the message. Thank you from Connamara Systems, LLC.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20201006/d8af861d/attachment.htm>