FIX execution message and NYSE Rule 123

, ,
1

Imported from previous forum

2

[ original email was from George Wolf - georgew@trinitech.com ]
Hello all,

I am currently reviewing the NYSE requirements for sending a drop copy of all incoming order flow to the NYSE MFDC (Member Firm Drop Copy DataBase).

(See NYSE document "Member Firm Front End Systemic Capture Drop Copy Interface Specification" on the NYSE website)

One of the two supported methods for sending a drop copy is via a FIX message. However, it is not a fix order they want, but rather, a fix execution (drop copy of "pending new", "pending cancel" OrdStatus messages)

So now, my question:

  • New FIX fields. The document states that they will support FIX 3.0, 4.0, and 4.1, however it expects the following new fix fields to be used:
  • WriteInTime
  • AsOfIndicator
  • DropCopyFlag

These fields as listed as having FIX tag # ("TBD by FIX"). I do not see them, even in the draft of FIX 4.2.

Are we to assume then, that these are going to be user defined fields? If so, when are standard values going to be assigned?

3

Yes, the assumption is that they will be user-defined fields. NYSE/SIAC has registered them as 9404-9406. You can view these via "Tech Resources", "Custom Fields" on the FIX website.

> Hello all,
>
> I am currently reviewing the NYSE requirements for sending a drop copy of all incoming order flow to the NYSE MFDC (Member Firm Drop Copy DataBase).
>
> (See NYSE document "Member Firm Front End Systemic Capture Drop Copy Interface Specification" on the NYSE website)
>
> One of the two supported methods for sending a drop copy is via a FIX message. However, it is not a fix order they want, but rather, a fix execution (drop copy of "pending new", "pending cancel" OrdStatus messages)
>
> So now, my question:
> - New FIX fields. The document states that they will support FIX 3.0, 4.0, and 4.1, however it expects the following new fix fields to be used:
> - WriteInTime
> - AsOfIndicator
> - DropCopyFlag
>
> These fields as listed as having FIX tag # ("TBD by FIX"). I do not see them, even in the draft of FIX 4.2.
>
> Are we to assume then, that these are going to be user defined fields? If so, when are standard values going to be assigned?
>
>
>