Imported from previous forum
[ original email was from Jeremy Sutton - jezza.sutton@patsystems.com ]
Patsystems intends to use the SenderSubId field in our FIX Trading Gateway as a mechanism to identify users who should have UUIDs set for the new CBOT Connect based trading platform eCBOT. The tag value will be data that can identify to our servers these specific users and therefore set their UUID on the trade.
We are interested in comments from the community on this matter.
[ original email was from Jim Northey - jnorthey@lasalletech.com ]
CBOE has implemented a similar usage of the SenderSubID field for userid in their FIX 4.2 interface. This is only required at logon.
Is your usage more on a per message basis, as opposed to a one time session initiation thing?
Are you planning on returning the UUID value in TargetSubID on subsequent responses? This can be a bit problematic - depending upon implementation and downstream system.
Also, you may want to talk with Tom McCabe and Marshall Rowe over at CBOT to see if they are forming any FIX gateway recommendations.
> Patsystems intends to use the SenderSubId field in our FIX Trading Gateway as a mechanism to identify users who should have UUIDs set for the new CBOT Connect based trading platform eCBOT. The tag value will be data that can identify to our servers these specific users and therefore set their UUID on the trade.
>
> We are interested in comments from the community on this matter.
>
[ original email was from Jeremy Sutton - jezza.sutton@patsystems.com ]
This would be (optional) per trade information, received by our sell-side application. To clarify a bit more, the contents would not actually be the UUID, rather it would be logon on our servers that is later mapped to the UUID.
Use of TargetSubId has not been considered in depth, but as a good starting point I’d set the TargetSubId on the returned execution reports or rejections for these orders to the SenderSubId received on the New Order Single.
I’ll also see if the CBOT has any thoughts on the matter.
[ original email was from Jeremy Sutton - jezza.sutton@patsystems.com ]
This would be a per message value to map to our current ability to submit a trade under a different username from the single gateway logon (for example, our handheld technology uses this to audit trades from the handheld logons, since the handheld server logs on once but manages many H-trade users).
This "per message" use is a limitation of our existing system interface - in the new Trademark version of the system we would support multiple session and consider this a session level field.
>
> CBOE has implemented a similar usage of the SenderSubID field for userid in their FIX 4.2 interface. This is only required at logon.
>
> Is your usage more on a per message basis, as opposed to a one time session initiation thing?
>
> Are you planning on returning the UUID value in TargetSubID on subsequent responses? This can be a bit problematic - depending upon implementation and downstream system.
>
> Also, you may want to talk with Tom McCabe and Marshall Rowe over at CBOT to see if they are forming any FIX gateway recommendations.
>
>
> > Patsystems intends to use the SenderSubId field in our FIX Trading Gateway as a mechanism to identify users who should have UUIDs set for the new CBOT Connect based trading platform eCBOT. The tag value will be data that can identify to our servers these specific users and therefore set their UUID on the trade.
> >
> > We are interested in comments from the community on this matter.
> >
>