|
4.4 Changes
< Previous Next >
Re: Parties component problem
John Cameron / Cameron Edge <>
24 May 2012 8:34AM ET See also the notes on the FIXwiki page for the NumInGroup data type -
http://fixwiki.org/fixwiki/NumInGroupDataType - which covers the use of all NoXXX type fields.
The Parties component is described at http://fixwiki.org/fixwiki/Parties
> This may be a gap in the documentation you looked at (where did you look?). If you look at the Parties component at http://www.fixprotocol.org/FIXimate3.0/ then you should see all three fields of the block having "Required if PartyIDSource is specified. Required if NoPartyIDs > 0." which effectively makes them mandatory. Volume 1 of the FIX Spec defines in the tag=value syntax rules that "The first field listed after the NoXXX, then becomes conditionally required if the NoXXX field is greater than zero." and "Senders should never send NoXXX=0.". You should be more pessimistic as a receiver, i.e. "Sending NoXXX=0 (e.g. NoPartyIDs=0) for optional repeating group is valid but not recommended." and "Recipients should be able to accept NoXXX=0, but Recipients should not require this.". Last not least, "For repeating groups that are marked as required, sending NoXXX=0 is not FIX compliant.".
> To answer your question, an optional repeating group that you do not need is simply omitted. A mandatory repeating group that you do not need should be provided with NoXXX=1 together with the first field as well as other fields defined as required when NoXXX>0. This use case should however not occur as a repeating group is defined by FIX as mandatory if it is deemed essential for the message. Providing dummy values to overcome the syntax check of the FIX engine on the other side only solves a technical problem. FIX does change a field or component from mandatory to optional if a use case is provided where the mandatory element has no semantic purpose. The usage description of the lement in the message will then explain under which conditions the element is still required.
> Regards,
> Hanno.
>
> > HI,
> >
> > The Parties component contains only a repeatgroup(NoPartyIDs),and all the fields included in Parties component are optional.And Parties component is also optional in New order-single(msgtype=D FIX4.4), If we change the status optional to required in New order-single message. What should we do about the Parties component under the condition that we won't need repeatgroup information? Should we set NoPartyIDs(the first field of Parties component)=0?
> >
> > Thanks in advance
> > Lswallow
Re: Parties component problem
John Cameron / Cameron Edge 24 May 2012 8:34AM ET
|
@FIXProtocol
