Mismatched IR Tags – Warning in process browse

[Carol Gross]

Does anyone have an idea for trouble shooting the warnings I am seeing when viewing the Browse Process log file?  I am seeing quite a few of these in the process log, and I believe it is contributing to some of our message buffer overflow errors.

Any info is appreciated.

Topic

[Jim Kosloskey]

Generally it means your message structure definition (typically your HL/7 variant) and the actual structure of an inbound message do not match.

Run your Xlate through the Xlate Testing tool using one of the messages for which you are receiving the error to see if it related to the message definition referred to in the Xlate.

Another issue can be any Tcl procs using the grm function which might be pointing to an incorrect message definition.

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

[Bob Richardson]

Folks,

Also:  the data types may not match such as a numeric data type in the variant but a string type is passed instead in the message.  We had one of those a long time ago.  That could take some time to track down.

Happy hunting!

[Max Drown (Infor)]

Here’s a very common example of what causes that error:

1(0).1(0).0(0).OBR.00258.[0]  –>  should be 0(0).OBR.00258.[0] (for our particular variant).

I usually troubleshoot these errors by copying the xlate to a tempory .xlt file and then by removing one statement at a time (or a block of statements) and running the xlt through the testing tool.

-- Max Drown (Infor)

[Bob Richardson]

Folks,

With CIS5.6 you can disable blocks of code in an translate and test.

Then activate them again once you found the offending logic.

Pretty slick – in case you are wondering about upgrading down the road

to CIS 5.6 or 5.7.

Enjoy.

[Author]

Replies