Error – Insufficient room for integer part of numeric value

[Jeff Manley]

I get a lot of these error messages.  Does anyone have any idea where they come from?  These numbers are not in the messages.

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 00:29:30] Insufficient room for integer part of numeric value ‘70309010901818’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 00:32:49] Insufficient room for integer part of numeric value ‘80143214321717’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 00:32:55] Insufficient room for integer part of numeric value ‘72282128212222’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 07:17:05] Insufficient room for integer part of numeric value ‘76155415541515’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 07:54:00] Insufficient room for integer part of numeric value ‘82497319731414’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 08:00:20] Insufficient room for integer part of numeric value ‘78128712871717’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 08:08:16] Insufficient room for integer part of numeric value ‘70309040904242’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 08:08:16] Insufficient room for integer part of numeric value ‘70309010901818’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 08:49:24] Insufficient room for integer part of numeric value ‘67329252925050’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 08:49:50] Insufficient room for integer part of numeric value ‘67329252925050’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 08:50:05] Insufficient room for integer part of numeric value ‘67329252925050’

[msg :RecF:ERR /0:qdxbrad22_xlate:12/03/2009 08:57:57] Insufficient room for integer part of numeric value ‘80586518651414’

Topic

[Max Drown (Infor)]

Do you see the errors in the xlt tester? If so, try reducing (deactivate or delete) the lines of the xlate until you find the exact line that is causing the error.

-- Max Drown (Infor)

[Jeff Manley]

I can test the xlt, but the error does not happen for every message.  It is just once in a blue moon.

[Max Drown (Infor)]

Use one of the bad messages for testing.

-- Max Drown (Infor)

[Levy Lazarre]

As Max pointed out, you need one of the offending messages to test. Use the time in the log and SMAT to retrieve one “bad” message and test it against the appropriate HL7 variant.

I had similar errors a while ago and it was related to one field in the IN1 segment. The field length in the HL7 variant was too short for the data that was coming in. Once I increased the number of characters for the field in the variant, the errors stopped.

[Jeff Manley]

Ok, I found an offending message.

There was a xlt, and in the Z1N segment, it was looking at Z1N-6(insurance holder number).  99% of the time it was the MRUN number which is ##-##-##.  A few messages now and then have a 8 digit number ########.

Someone had written a tcl proc and placed it in the copy action.  It looks like this:

lassign $xlateInVals mrun

if [llength $xlateInVals] {

  set first [csubstr $mrun 0 end]

  set new_first [split $first -]

  set second [csubstr $mrun 3 end]

  set new_second [split $second -]

  set new_third [csubstr $mrun 6 end]

  # set new_third [split $third -]

  lassign $new_first first

  lassign $new_second second

  lassign $new_third third

  set xlateOutVals

}

Seems like what they are trying to do is to take the dashes out of the MRUN.

Can I do something simple like the following?

lassign $xlateInVals mrun

if [llength $xlateInVals] {

set xlateOutVals [string map {- “”} $xlateInVals]

}

Testing of my code allows the dashes to be removed and the number without dashes no longer causes error messages.

[Max Drown (Infor)]

Your code appears to be much better. 🙂

But, you do need to treat xlateInVals and xlateOutVals as list variables (lassign, list, lappend, lindex, etc.)

-- Max Drown (Infor)

[Levy Lazarre]

Yes. In fact you can eliminate the “lassign” statement since you don’t use the mrun variable at all.

[Jeff Manley]

I went from:

if [llength $xlateInVals] {

set xlateOutVals [string map {- “”} $xlateInVals]

}

no dashes in the output

to this:

if [llength $xlateInVals] {

lassign xlateOutVals [string map {- “”} $xlateInVals]

}

dashes show back up in the output

[Max Drown (Infor)]

Try it like this …

if [llength $xlateInVals] {
[code]if [llength $xlateInVals] {

-- Max Drown (Infor)

[Jeff Manley]

Works perfect.  No dashes and no errors.

Thanks everyone!

[Jeff Manley]

Again, thanks to everyone.

I checked this morning and the only thing in the log is “Engine idle”.

Very nice!

[Jo Ellen Laansma]

I’m also seeing that message in the tester.  HL7v2.6 FT1-29 is defined as 250 CWE.  When the input string is more than 4 bytes, it yields the error.  I tried changing from CWE to ST, but to no avail.

[Jo Ellen Laansma]

forget the above question.

[Jim Kosloskey]

I am just curious – what release of Cloverleaf?

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Author]

Replies