FIX protocol violation issue

[FXCM Help]

Our specification states we do not use this tag. We indicate there are no values in this repeating group by setting it to 0 which is valid.

NoPosAmt (Tag = 753, Type: NumInGroup) Number of position amount entries.

Used in:
* Component Block - <Position Amount Data>

=> NumInGroup :
Int field (see definition of "int" below) representing the number of entries in a repeating group. Value must be positive.

int :
Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ).
The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999").
Note that int values may contain leading zeros (e.g. "00023" = "23").
Examples: 723 in field 21 would be mapped int as |21=723|, -723 in field 12 would be mapped int as |12=-723|.

[alik]

Hi everybody.

We are the FIX software vendor. One of our clients uses our applicaiton to connect to FXCM by FIX. At some point FXCM sends FIX "AP" message with tag#753 equal to 0, which violates one one ofthe basic FIX rules. According to the FIX protocol specification:

NoPosAmt - Tag = 753, Type: NumInGroup
NumInGroup - Int field representing the number of entries in a repeating group. Value must be positive.

Can anybody help me with this issue?

Best Regards, Alik.

[alik]

Thank you but 0 is not a positive value.

[alik]

Thank you but 0 is not a positive value.

http://www.google.com/search?hl=en&q=define%3Apositive+number&btnG=Google+Search

:)

[FXCM Help]

All of the FIX engine vendors that we have dealt with thus far recognize a numingroup field = 0 means no entries for that repeating group and we have not had any issues with them.

This is the way we define an empty repeating group in our specification. There is not much we can do on this at present.