[Francesca Mei]

At the end it was decided to implement this interface as a point to point (direct connection not through Cloverleaf). Thank you everybody for all your help. I really appreciated it

[Francesca Mei]

Thank you very much for the explanation. Ok, then I think I will definitely need your proc. Where do you place it? In the each route in the Route Replies tab or in the TPS Outbound Data field of the Outbound tab? In the latter case I am guessing I would have to move the routes from the Route Replies tab to the Route Messages tab

[Francesca Mei]

Since I specified the destination thread as thread C in the Route Replies tab of thread B, I would think it should send all replies to thread C. Why wouldn’t that be the case? Not sure if this matters, but thread B does not send an ACK back after it receives they query message from thread A. The acknowledgement is sent as part of the response to thread C.

Unfortunately, I can’t test yet; otherwise, I would have a better idea of how the Route Reply option works

As a side note, thank you Jim for offering to discuss/share your code   🙂

[Francesca Mei]

Thank you so much for your help! I do see the dotted paths now.

As far as configuring the process, I do not see the “Route Replies to original source only” check box. Maybe it’s the version of Cloverleaf I am on? It’s 6.0.2.0

[Francesca Mei]

The communication protocol is pdl-tcpip

The RSP message is generated by the application as a response to the query message and sent outbound.

The query message is generated by an application connected to thread A and sent to thread B (another system). Then the other system connected to thread B sends back a reply into Cloverleaf on the same port. It then actually send this reply to a different thread (let’s call it thread C), so the reply is not generated by cloverleaf. It is created by the same system that got the query and sent outbound on the same port.

[Author]

Replies