On Mon, 8 Jun 2015 00:12:18 -0500, Shane Ginnane wrote: >On Sun, 7 Jun 2015 14:11:30 -0500, Bill Godfrey wrote: > >>That would mean there could be end-of-line characters and hex 00 characters >>in a record, which would mean "sed" would not work. > >sed won't (shouldn't) care about the nulls, but won't like newlines (yes, I >noted your careful language given the recent other thread re this) in the >midst of "records".
You are right; sed handles the nulls. >How does ocopy deal with this ? - I'm unable to test on z at present. > I haven't tried ocopy, but I inserted hex 15 into some records in a data set, used oput (as text), and the resulting file had new lines wherever I had inserted hex 15. Then an oget (as text) resulted in a data set with more records than I started with, with new records where each hex 15 had been. Bill ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
