Imported from previous forum
[ original email was from Donald Mendelson - dmendelson@capital-mkts.com ]
Is there an official or unofficial standard usage for how the Sender and Target fields are used with futures and options exchanges? For example, SenderCompID for firm number (usually 3 digits in U.S. to identify firm to clearinghouse), SenderSubID for trader acronym (usually 3 or 4 characters), etc. For messages going to an exchange, I presume the TargetCompID would identify the exchange. How are TargetSubID and TargetLocationID typically used?
[ original email was from Jim Northey - jnorthey@lasalletech.com ]
There is not an official standard at this time for the use of these fields.
With that said, the following is being used at CBOE:
SenderCompID - is the firm acronym in our 4.1 system - which will be replaced by the numeric firm number (assigned by OCC). It would probably make sense to come up with a standard guideline for US based exchanges - certainly this would be good for options - as positions are reported centrally to the OCC.
SenderSubID - is used in our 4.2 service for login & password - would not expect that this would be something to standardize.
The TargetCompID - contains "CBOE" - but also has connection number information.
The TargetLocationID - is not used but is reserved for planned enhancements
The TargetSubID - is not used.
> Is there an official or unofficial standard usage for how the Sender and Target fields are used with futures and options exchanges? For example, SenderCompID for firm number (usually 3 digits in U.S. to identify firm to clearinghouse), SenderSubID for trader acronym (usually 3 or 4 characters), etc. For messages going to an exchange, I presume the TargetCompID would identify the exchange. How are TargetSubID and TargetLocationID typically used?
>
[ original email was from Francesc Prats - fprats@meff.com ]
Another possibility could be to use TargetSubID to identify different divisions in one exchange.
> There is not an official standard at this time for the use of these fields.
>
> With that said, the following is being used at CBOE:
>
> SenderCompID - is the firm acronym in our 4.1 system - which will be replaced by the numeric firm number (assigned by OCC). It would probably make sense to come up with a standard guideline for US based exchanges - certainly this would be good for options - as positions are reported centrally to the OCC.
>
> SenderSubID - is used in our 4.2 service for login & password - would not expect that this would be something to standardize.
>
> The TargetCompID - contains "CBOE" - but also has connection number information.
>
> The TargetLocationID - is not used but is reserved for planned enhancements
>
> The TargetSubID - is not used.
>
> > Is there an official or unofficial standard usage for how the Sender and Target fields are used with futures and options exchanges? For example, SenderCompID for firm number (usually 3 digits in U.S. to identify firm to clearinghouse), SenderSubID for trader acronym (usually 3 or 4 characters), etc. For messages going to an exchange, I presume the TargetCompID would identify the exchange. How are TargetSubID and TargetLocationID typically used?
> >
>