Why does a record-oriented file copied from a non-HFS file to an HFS file using OPUT with the TEXT option contain more records?
When you use the TEXT option on the OPUT command to copy a record-oriented non-HFS file to an HFS file, an EBCDIC newline (NL=0x15) character is appended to the end of each record in the file. The addition of the newline character at the end of every record increases the size of the file and the number of records in the file when processed using JRIO. If you use the BINARY option on the OPUT command, the newline characters are not appended to the end of each record, and the size of the file and the number of records in the file remains the same. For example, if you have a non-VSAM data set with a logical record length of 80 that contains five records, and you use the BINARY option on OPUT, the HFS file is 400 bytes long, and it contains five records when you use JRIO. If you use the TEXT option, the HFS file is 405 bytes long, and it contains five 80-byte records and a short 5-byte record, padded to 80 bytes. This produces a six record file in HFS when processed using JRIO. These recor
