Keith,
You could write enough code to do anything 😉
First, though, you probably want to make sure that the constraint is that they can’t send the next message until the reply is received to the previous message. Otherwise, the queue could contain more than one message which makes the interface vulnerable to problems.
You want to do the normal thing which is write a procedure to produce a reply. But instead of using the PROTO or OVER disposition, use CONTINUE. Then route the reply message to a thread that is connected to the Centricity reply interface.
You would have to decide whether to route replies or route data. If you route data then your ACK message type would show up in the list along with all the other routes. If you route replies then you’d define the route on the ‘Route Replies’ tab of your Centricity inbound thread (you always wondered why we had a route replies tab, didn’t you 😉
Finally to produce the reply ACK or data ACK make the message type ‘data’ or ‘reply’ when you do the msgcreate command in your reply procedure. My first choice would be to route the message as a data message, it would be more obvious to the maintenance folks.
Cheers,
.
