With the text processing mode, when data is read, record boundaries are marked with the end-of-line terminators such as lf or crlf. These terminator characters have the same data representation as the data that is read (the CCSID of the data read in is the same as the CCSID of the appended end-of-line terminators). The data representation of the record formatted data is then changed to the client representation (client CCSID). If the client data representation is the same as the data representation of the data that is read, then there is no data translation.

When the record formatted data is received from the client for writing to the data set, its data representation is changed to the data representation of the data stored in that data set, with the converted end-of-line terminators used to recognize the record boundaries.

In text processing mode, the representation of data along with end-of-line terminators is changed between client representation (client CCSID) and data set representation. All data and end-of-line terminators are converted according to the active translation table. Therefore, if the data set contains a mixture of characters and binary data, binary data is converted as well. In text mode, be careful not to mix your text data (characters) with binary data. Also pay attention that end-of-line terminator conversion depends on the Unicode Conversion Technique - convserv() attribute.

NFS version 4 protocol (NFSv4) differs from NFSv2 and NFSv3 protocol in handling single to multiple byte conversion. Therefore, the technique-search-order specified in the convserv() attribute should consider the effects of the NFS protocol being used. SeeCreating the conversion environment for Unicode Services for further details.