Imported from previous forum
[ original email was from John Hardman - yiq12@dial.pipex.com ]
Many thanks in advance for any help with these or any of the earlier questions that remain unanswered.
Regards,
John Hardman.
Question #1
In the Quote Request message (MsgType = R) the comment for field 54 (Side) says “If OrdType = “Forex - Swap”, should be the side of the future portion of a F/X swap”.
(a) Does this mean that the field is required if OrdType = “Forex – Swap” ?
(b) Is the field ever used when OrdType <> “Forex – Swap” ?
Question #2
In the Field Definitions, the comment for ListSeqNo says “Sequence of individual order within list (i.e. ListSeqNo of ListNoOrds, 2 of 25, 3 of 25, . . . )”.
Is it safe to assume that the base value for this sequence number is 1 (one) and that 0 (zero) is invalid.
Further is it safe to assume that ALL sequence number fields have a base value of 1 (one) with only EndSeqNum permitting the value 0 (zero) to indicate infinity ?
Question #3
In the Field Definitions, the comments for field 72 say “Reference identifier to be used with Replace and Cancel AllocTransType messages”. However, in the Allocation message (MsgType = J) the comments for field 72 say “Required for AllocTransType = Calculated, Replace, or Cancel”. Which of these comments is correct ?
Question #4
In the Standard Message Header the comment for field 122 (OrigSendingTime) says “Required for message resends”. In this context is a message resend identified by field 43 (PossDupFlag) being “Y”, by field 97 (PossResend) being “Y”, or by either 43 or 97 being “Y”.
Question #5
Is there a single field that can reliably be used to identify that a message is being delivered by a third party ?
> Many thanks in advance for any help with these or any of the earlier questions that remain unanswered.
>
> Regards,
>
> John Hardman.
>
>
> Question #1
>
> In the Quote Request message (MsgType = R) the comment for field 54 (Side) says “If OrdType = “Forex - Swap”, should be the side of the future portion of a F/X swap”.
>
> (a) Does this mean that the field is required if OrdType = “Forex – Swap” ?
> (b) Is the field ever used when OrdType <> “Forex – Swap” ?
>
Side can be optionally specifed on the Quote Request regardless of the OrdType value. If the OrdType indicates "Forex - Swap", then the Side specified should be the future portion of the trade.
>
> Question #2
>
> In the Field Definitions, the comment for ListSeqNo says “Sequence of individual order within list (i.e. ListSeqNo of ListNoOrds, 2 of 25, 3 of 25, . . . )”.
>
> Is it safe to assume that the base value for this sequence number is 1 (one) and that 0 (zero) is invalid.
>
> Further is it safe to assume that ALL sequence number fields have a base value of 1 (one) with only EndSeqNum permitting the value 0 (zero) to indicate infinity ?
>
That is a reasonable assumption, however, the data type for ListSeqNo as defined is of type "int" w/ no explicit range restriction. It seems like it would be a good idea to define a "SeqNum" data type which extends "int" (similar to "Price" extending "float" and associate those fields with that data type.
>
> Question #3
>
> In the Field Definitions, the comments for field 72 say “Reference identifier to be used with Replace and Cancel AllocTransType messages”. However, in the Allocation message (MsgType = J) the comments for field 72 say “Required for AllocTransType = Calculated, Replace, or Cancel”. Which of these comments is correct ?
>
>
The Allocation message’s comments are the correct ones in this case. The Field Definition entry for that field should include Calculated (introduced in FIX 4.1) in that list.
> Question #4
>
> In the Standard Message Header the comment for field 122 (OrigSendingTime) says “Required for message resends”. In this context is a message resend identified by field 43 (PossDupFlag) being “Y”, by field 97 (PossResend) being “Y”, or by either 43 or 97 being “Y”.
>
>
A resent message is defined by PossDupFlag = Y. That indicates the same message contents, seq num, etc. are being resent. PossResend is used when the same business content is being resent with a new sequence number but the same business-level identification (e.g. OrderID, ExecID, etc.)
> Question #5
>
> Is there a single field that can reliably be used to identify that a message is being delivered by a third party ?
>
>
Because FIX relies upon certain levels of bi-lateral agreement, there is an assumption that you know who you’re communicating with (e.g. if a third party or a principal), and if a third party is involved, you know who (and how they will be specified) will be represented via the third party. Within FIX, a message you receive from a third party representing multiple firms should have OnBehalfCompID specified (as the principal) and SenderCompID (as the third party). See “Standard Message header” for more details on how these work.