TEXT specifies that each record consists of an arbitrary number of characters in the client session character set, followed by an end-of-record marker, which is one of the following:
- On UNIX platforms, the newline character (identified in Unicode as LINE FEED U+000A)
- On Windows platforms, the two-character sequence carriage return followed by line feed (identified in Unicode as CARRIAGE RETURN U+000D and LINE FEED U+000A, respectively)
For client session character sets other than UTF16, the end-of-record marker byte sequence is one of the following:
- On UNIX platforms, X'0A'
- On Windows platforms, X'0D0A'
For the UTF16 client session character set (in which each character is encoded in two bytes), the end-of-record marker byte sequence is one of the following:
- On big endian UNIX platforms, X'000A'
- On little endian UNIX platforms, X'0A00'
- On Windows platforms, X'0D000A00'
TEXT format should only be specified for character data. Do not specify TEXT format for binary data, such as, INTEGER, BYTEINT, PERIOD, and other binary data. Depending on the actual byte values of the binary data, unexpected results may occur. If any non-character or ANSI date data is specified, the warning message Warning: Text format requires all CHAR or ANSIDATE data types will be displayed.