Error message

Hi Simon,

I knew I had seen this error somewhere before, but couldn’t remember. Until I just now tested an Xlate:

This is a length encoded file where the length of the message is wrong. Must have edited it myself.

Are you using fileset-local as protocol? And do you see the inbound message in SMAT? Nothing in the error database?

If you see it in SMAT, then the message is received correctly and it is killed somewhere else. Are there tcl-procs somewhere along the way? If a translation is used, does the inbound message go through the Xlate correctly? Are there some outbound TPS procs on the outbound thread that shouldn’t be there?

I’m trying to recall, but if you pick length encoded (or do nothing because in 6.1 at least length encoded is the default), and the file is new line, you get the same error.

There is a formula I used to have in a sticky note on my wall..

length 10 count =

total number of bytes in the message

plus 1 for each line

minus 10 for the length 10 count

minus 1 (I think for the EOF?)

Plus when I edit it in my PSPad editor, I have to select file format of MAC (CR only).

To test the Xlate, use the single patient file as input to the Xlate Testing tool. If it fails there most likely it is failing in the engine at the Xlate.

It is quite likely it is failing on the IB. Make sure the Style you specified for the File in the NetConfig matches the actual file. If length encoded is specified in the NetConfig, make sure the file is actually length encoded.

If another system provided you with the original file, then most likely it is not length encoded and neither is your single patient file.

You can use the Xlate Testing tool to ‘verify’ the style as it has the ability to mimic the basic settings of the protocol in order to read the file for testing.

That looks like length encoded.

Whenever I have a length encoded file I want to play with I use the provided command line tool to convert len10 to nl and then work with the new line terminated file – makes life a lot easier.