Internal XPM Tcl failure (301)

i just got the exact same error that mary has posted above.  i pulled the message out of the error database and ran it through the route testing tool.  here is the error.  not quite sure i understand it…

Command output:

Output going to stdout

INBOUND TPS PROCS

PROC=RawHl7Ack ARGS=

RUNNING INBOUND TPS IN START MODE

DONE STARTING INBOUND TPS

06/05/2008 18:53:15

[xpm :xlt :ERR /0:  UNNAMED_TID] QDX_Tcl_SplitList({}V) failed: list element in braces followed by “V” instead of space

06/05/2008 18:53:15

[xlt :xlat:ERR /0:  UNNAMED_TID] [0.0.2] Xlate ‘X_AncADT_to_Lab.xlt’ failed: Internal XPM Tcl error

erroCode: NONE

errorInfo:

invalid command name “tix”

   while executing

“tix option get fixed_font”

[xpm :xlt :ERR /0:  UNNAMED_TID] QDX_Tcl_SplitList({}V) failed: list element in braces followed by “V” instead of space

This is bad … possibly one of your configuration files is corrupted, or you have a translation action that is doing something the engine doesn’t like.  

I suggest following up with Support to get this tracked down.

Folks,

What version of the engine are we talking about here?  My concern is our plan to migrate from CIS5.3 Rev3 to CIS 5.6 Rev1 next month.  We run our engine on AIX5.2 build 6.

Thanks.

i am on version 5.3 rev 3 on AIX5.2

the reason for my error is that i am passing a blank field into xlateInVals and the translation craps out.  i haven’t figured out how to get tcl to handle it yet.  putting an IF in the translation to skip it if it equals @null is my current way around it, but i dont like that as my final solution.

the {}V is me trying to add a V to the end of a field.  the {} is representing that the field is empty.  if i do a comparison where if the field == “” , it doesnt like “” and empty.

Mary,

  Look at any inline tcl code in your translation for that message.  I have received similar errors when ever there has been a tcl error in a translation.  If you run the message through the xlate testing tool you should be able to narrow down what tcl code is the problem.

Darren,

  From what you are describing it sounds like you are using the xlateInVals variable directly.  You have to remember that this is a list and even if you only expect one value you need to use lassign or lindex to parse the value before using it.  If you do this then the resulting value will be an empty string instead of {} when you do your comparisons.

Internal XPM Tcl failure (301)

MESSAGE 1

[0:TEST] QDX_Tcl_SplitList(90 {) failed: unmatched open brace in list

Internal XPM Tcl error

erroCode: NONE

errorInfo:

can’t unset “Hl7FieldsLoaded(2)”: no such element in array

   while executing

“unset Hl7FieldsLoaded($iokey) “

I had similar error.

It was happening in OBR segment. I just deleted the segment and redid it and it worked.