I have an issue with the generic ‘create_ack’ tcl.
One of our systems recently changed. They added a mid-point product between us and the sending system. Nothing on my side changed except the port I am listening on. They are complaining that the ACK I send this mid-point system doesn’t have the & in the encoding characters.
In the generic create_ack proc it has
set sepchar “^~\&”
THEN LATER
set sepchar [lindex $mshflds 1]
My question is…why isn’t the & being included in the ACK? They are sending the & in the inbound mesage.
It’s the same ACK program that has been used for all inbound systems.
Thanks,
Tim