We have one application that runs third-party software under Posix. If I am out of my depth in phrasing the question, please excuse me. I assume/understand that Posix/Unix treats binary <LF> or hex '0A' as a record separator. Our problem is as follows: We have data coming from MPE/iX in which a five-character field is concatenated with a date in HP Calendar format. The date January 10, 1996 is converted by the tobyte command to 'C00A'. When the Posix application sees the '0A' in the data, a new record is created so that this file (all records have the same date) ends up with twice as many records as there ought to be. If we conduct a test with January 11,1996, there is no problem because the date is hex 'C00B'. I ascertained the result of the date conversion from FCOPY;HEX;CHAR. 'C00A' does not convert back to the calendar date -16374, but to 49162 so I guess some bit are truncated by tobyte. How can we have '0A' not read as a record separator -- or if I have the question wrong, how can we keep Posix from splitting our record in half. Thanks. ======================================================================= Leonard S. Berkowitz voice: (617) 423-2020 Warren, Gorham & Lamont fax: (617) 423-9057 31 St. James Avenue e-mail: [log in to unmask] Boston, Massachusetts 02116