- This topic has 7 replies, 5 voices, and was last updated 6 years, 1 month ago by
.
-
Topic
-
-
Replies
-
-
Hi Simon,
I knew I had seen this error somewhere before, but couldn’t remember. Until I just now tested an Xlate:
Code:hcixlttest: short read from /cloverleaf/cis6.0/integrator/test/testberichten/pi_siu_in_06 — read 1 characters but expected 0
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?
Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
-
-
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).
Peter Heggie
-
Thanks guys.
Nothing in SMAT, nothing in the error database. Using fileset-local.
There is a translation involved so, being fairly new to Cloverleaf, I’ll have to find out how to check if it failed on that. Good chance it did as I cut down a large live file to one patient record to do this testing and maybe left something out.
I’ll let you know how I get on.
-
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.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
Fixed. There’s a header for each record which contains simply the number of characters to come for the next patient, eg: 000000831
I didn’t know what this was and when I anonymized the data the number of characters changed. The testing tool showed that a different number of characters was present than what was expected (from the header).
Learning every day! Thanks again.
-
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.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
