Why does a record-oriented file I copied from a non-HFS file to an HFS file using OPUT with the BINARY option appear as one long line when edited in HFS?
Record-oriented files do not use characters to end lines of text. For fixed-length record-format files, records end on a logical record length (LRECL) multiple, and for variable-length record-format files, the record descriptor word prefixed to each record determines the number of bytes that follows for any record. The TSO/ISPF editor shows each record on a separate line. A record’s length is the number of bytes an I/O read operation returns. For a file whose record format is fixed, this length should match the LRECL. Therefore, the editor automatically breaks each record after 80 bytes. If you use the BINARY option with OPUT (as you should to copy fixed-length record-format files), under HFS the file should normally appear as one long line when edited or viewed because the file does not contain any newline (NL=0x15) characters. If you copy a non-HFS variable-length record-format file to an HFS file using OPUT with the BINARY option, this also appears as one long line when edited. Howe
