Just to add to what Jim was saying, it’s also possible that the sender left off an encoding character which would cause Cloverleaf to report a no-match error. I would think that the sending system would complain that Cloverleaf wasn’t sending a reply though. Other than that, if the encoding is correct then Cloverleaf put it in smat and then queued the message to state 1.
The only way to verify all the inbound data would be to turn up EO to ‘enable_all’. That would provide a hex dump of all the bytes that are evaluated by the PDL whether they were queued to the engine or not. Then you’d have to look through the logs to find what you need.
