Extra CR between messages

[Mark Brown]

On some threads an extra CR appears between messages.  Most ancillary systems don’t seem to care, but one vendor’s system has decided to start throwing a snit about it.  I know that some of the TCL procs we use put an extra CR at the end of the message and I’ve added code to remove double CR’s, but there still seems to be a CR sometimes.

I looked at two threads, one with Xlates and one without and the the one without didn’t generate the extra CR.  Now, I can’t just remove the xlate, so is there any way to eliminate any CR’s between messages?

We’re running Cloverleaf 5.7R3 on a Windows 2003 server.

Topic

[Jim Kosloskey]

Mark,

Check the Xlate closely for Tcl procs and inspect those.

Also validate any use of the CONTINUE or SEND Action.

Of course check all UPoC usage for an offending Tcl proc.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[Robert Milfajt]

Wow, I just had this happen to me, or at least some version of this.  To preface, I am CL 5.5Rev1.

Using TCL, when you split a message on r, you get a list that has all of the segments indluding a null element at the end, i.e., {MSH…} {PID…} … {OBX…} {}.

I have no idea why this element was there and got caught up in it.  I was looping through the segments, building them back in the message after some manipulation.  However my code also appended segments at the end, and right smack in the middle of the message I had a null segment!  This caused problems later down the pike in the down stream system.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Author]

Replies