In my experience this is when the message encapsulation charcters don’t match those defined in the protocol driver you are using. For instance the mlp_tcp.pdl driver expects your hl7 message here . This is how the protocol driver determines that a complete message has been received. If you turn up eoalias debugging, you can view what characters in HEX are actually being received by the protocol driver in your process log file. I use an eoalias for pdl that allows me to see the message. You may need to have the sending system do the fixing to correct this issue once it has been identified.
The eoalias will look something like ENABLE pdl * * * in the engine output configurator. Or possibly ENABLE pdl * DBUG *.
Keith is right. I would talk to the foreign system that is sending you the message and ask them if they changed something (if this problem just cropped up).
Also, you could perform an octal dump of the offending message and see what characters are being sent.
Author
Replies
Viewing 1 reply thread
The forum ‘Cloverleaf’ is closed to new topics and replies.