5.8 file protocol

This topic has 6 replies, 2 voices, and was last updated 14 years, 9 months ago by James Cobane.

Creator

Topic
July 19, 2011 at 5:24 pm #52599
Jerry Magrann
Participant
We are upgrading from 5.3 to 5.8 and have a file thread that picks up a length encoded file with byte headers and processes through in 5.3 no problem, removing the byte header along the way. Now testing the files in 5.8 I’m getting an incomplete record read error message. Is anyone of aware of changes that need to be noted / made from 5.3 to 5.8?

Thanks!
Creator

Topic

Viewing 5 reply threads

Author

Replies
- July 19, 2011 at 5:56 pm #74809
  James Cobane
  Participant
  Is it an ASCII file, or does it contain binary data? You may need to play with the encoding options in the NetConfig.
  
  Jim Cobane
  
  Henry Ford Health
- July 19, 2011 at 6:01 pm #74810
  Jerry Magrann
  Participant
  It is ASCII and here is the file since it is test and has bogus patient data in there…
- July 19, 2011 at 6:16 pm #74811
  Jerry Magrann
  Participant
  in 5.8 I’m trying different encoding formats / file format and CRNL formats from the drop down and now it’s kicking out “File read failed: non-numeric length-encode string” error
- July 19, 2011 at 8:07 pm #74812
  James Cobane
  Participant
  It seems like the first record is actually only 366 bytes long, not 375 as the length-encoding specifies. Did the file get edited in some way, thus throwing the byte count off?
  
  Jim Cobane
  
  Henry Ford Health
- July 19, 2011 at 8:13 pm #74813
  Jerry Magrann
  Participant
  You know what – I did edit the last name of the first patient because it was someone’s real name here, I didn’t change the byte header to match my change.
- July 19, 2011 at 8:20 pm #74814
  James Cobane
  Participant
  Been there, done that! 😀
Author

Replies

Viewing 5 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.