Type DATA v REPLY

Robert,

For the Outbound thread on the Inbound Tab Check the ‘Outbound Only’ checkbox.

What happens is a message is sent and if await replies is on and this is an ‘outbound only’ thread, the next inbound message is flagged as being a reply versus data.  Not absolutley sure about whether ‘await replies’ has to be on but I seem to recal that.

Anyway if you do not check ‘Outbound only’ any inbound is flagged as DATA.

Of course this makes things a little dicey if you receive more than one response before you can send the next message. The first will be traeted as REPLY the secodn as DATA. The second then will be processed as inbound on your outbound thread – probably resulting in a message to the Error DB with a TrxID error.

Some outbound threads can receive ack both a reply (like an acknowledgment of recipt of message) followed by another reply (like an appplication reply indicating success or failure of actually processing the message) – or – in a synchronous query/reply the query is sent, an acknowledgment of the receipt of the query is recived followed by the response to the actual query. In the query/reply scenario described, a new query should not be sent until both of the replies are processed. But in the normal ‘Outbound Only’ construct only the first is deemed to be a REPLY by Cloverleaf, the second is treated as DATA – which can be OK.