Addressing in case of circuits

, ,
1

Imported from previous forum

2

Release FIX 4.0

When 2 circuits are connected, which is the correct way of addressing?
I mean, let’s check an example like this:

              ORDER

CUST1–CIRCUIT1----------->CIRCUIT2–CUST2

How are populated the following tags?

49 SenderCompID
50 SenderSubID
56 TargetCompID
57 TargetSubID
115 OnBeHalfOfCompID
116 OnBeHalfOfSubID
128 DeliverToCompID
129 DeliverToSubID

And what about this other case?

               EXEC

CUST1–CIRCUIT1----------->CIRCUIT2–CUST2

3

Can you clarify what "circuit" means in your example? Is this a physical data circuit, in which case then I am not sure it is relevant.

Think of the FIX Session as a TCP socket. One FIX engine opens the socket with another FIX engine which is listening and they send messages to each other over that socket.

Are there more than 2 FIX engines in your example?

Please review “Message Routing Details” in FIX 4.3’s Volume 2. It has examples of both “One Firm-to-One Firm (point-to-point)” and of “Third Party Message Routing”. Those examples and rules apply to FIX 4.0 (with the exception of the optional HopCompID and HopSendingTime).

> Release FIX 4.0
>
> When 2 circuits are connected, which is the correct way of addressing?
> I mean, let’s check an example like this:
>
> ORDER
> CUST1–CIRCUIT1----------->CIRCUIT2–CUST2
>
> How are populated the following tags?
>
> 49 SenderCompID
> 50 SenderSubID
> 56 TargetCompID
> 57 TargetSubID
> 115 OnBeHalfOfCompID
> 116 OnBeHalfOfSubID
> 128 DeliverToCompID
> 129 DeliverToSubID
>
>
>
> And what about this other case?
>
> EXEC
> CUST1–CIRCUIT1----------->CIRCUIT2–CUST2
>
>

4

I mean, there are only 2 FIX engines in my example.
The FIX sessions are just TCP sockets, but is necessary the admittment of the indication of the customers operating under these FIX engine directly connected.
I hope to be clear.

> Can you clarify what “circuit” means in your example? Is this a physical data circuit, in which case then I am not sure it is relevant.
>
> Think of the FIX Session as a TCP socket. One FIX engine opens the socket with another FIX engine which is listening and they send messages to each other over that socket.
>
> Are there more than 2 FIX engines in your example?
>
> Please review “Message Routing Details” in FIX 4.3’s Volume 2. It has examples of both “One Firm-to-One Firm (point-to-point)” and of “Third Party Message Routing”. Those examples and rules apply to FIX 4.0 (with the exception of the optional HopCompID and HopSendingTime).
>
>
> > Release FIX 4.0
> >
> > When 2 circuits are connected, which is the correct way of addressing?
> > I mean, let’s check an example like this:
> >
> > ORDER
> > CUST1–CIRCUIT1----------->CIRCUIT2–CUST2
> >
> > How are populated the following tags?
> >
> > 49 SenderCompID
> > 50 SenderSubID
> > 56 TargetCompID
> > 57 TargetSubID
> > 115 OnBeHalfOfCompID
> > 116 OnBeHalfOfSubID
> > 128 DeliverToCompID
> > 129 DeliverToSubID
> >
> >
> >
> > And what about this other case?
> >
> > EXEC
> > CUST1–CIRCUIT1----------->CIRCUIT2–CUST2
> >
> >
>