Previous Topic: Handling USS Files as BINARY

Next Topic: Handling BINARY USS Files as TEXT


Handling USS Files as TEXT

Unless CODE=BINARY is specified, CA XCOM Data Transport normally allocates a USS file as FILEDATA=TEXT (the JCL equivalent). There is no concept of LRECL and BLKSIZE for USS files. Input records are terminated by a new line character (x'15'). When CA XCOM Data Transport writes a USS TEXT file, it inserts new line characters at the end of each record.

Handling USS Files as RECORD

When CODE=UTF8 or CODE=UTF16 is specified, CA XCOM Data Transport allocates the USS file as FILEDATA=RECORD. CA XCOM Data Transport also processes the data as TEXT data. Instead of records being terminated with a new line character (x’15’), a prefix is appended which contains the length of the record. When CA XCOM Data Transport writes a USS RECORD file, new line characters are not inserted at the end of each record.