Imported from previous forum
I am using FIX.4.2. According to definition of ‘Qty’ data type, am I correct when I say that the example below are valid values?
-good ones - ‘1.2345’ ,‘10000’ ,‘165.23’, …
but NOT the one below?
-bad qty- ‘14.000’ ,‘2222.00’,‘33.00’, …
According to definition ‘Qty’ is either a number with NO decimal places or a float with decimal places. I read that with ‘meaningful’ decimal places for a quantity i.e. a ‘fraction’.
Unfortunately I don’t have in mind an example of ‘non-share quantity asset classes’.
Regards
Why would you assume that zeroes are not considered “decimal places” if no non-zero digits follow? I do not see why you should reject whole numbers represented with decimal places. As message recipient you should be prepared to accept such numbers. As sender you can reduce message size by omitting the decimal place and leading/trailing zeroes in case of whole numbers. There is no ambiguity in the number, i.e. additional zeroes do not require different processing. In general, the data type in your application must be able to accommodate decimal places if the FIX field is defined with Qty as data type.
I am using FIX.4.2. According to definition of ‘Qty’ data type, am I correct when I say that the example below are valid values?
-good ones - ‘1.2345’ ,‘10000’ ,‘165.23’, …but NOT the one below?
-bad qty- ‘14.000’ ,‘2222.00’,‘33.00’, …According to definition ‘Qty’ is either a number with NO decimal places or a float with decimal places. I read that with ‘meaningful’ decimal places for a quantity i.e. a ‘fraction’.
Unfortunately I don’t have in mind an example of ‘non-share quantity asset classes’.
Regards