Processing Different File Types › USS Files › Handling BINARY USS Files as TEXT

Handling BINARY USS Files as TEXT

It may be necessary to cause CA XCOM Data Transport to allocate a USS file in BINARY, but process the file as TEXT. If the USS file does not contain new line characters (x'15') at the end of each logical line, it still may be possible to process the data as TEXT. To do this, specify FILEDATA=BINARY, CODE=EBCDIC, and LRECL=nn.

When FILEDATA/LFILEDATA=BINARY is specified, CA XCOM Data Transport allocates the USS file as if FILEDATA=BINARY had been specified on the JCL statement. However, the number of characters read from the file and considered to be a logical record depends on the value of LRECL.

Note: On ISPF panels and CICS screens there is a separate field, USSLRECL, to specify the logical record length. The SYSIN01 parameter is LRECL.

Example

If you specify LRECL=10, then CA XCOM Data Transport treats each sequential 10 bytes as a separate record. If you specify LRECL=133, then CA XCOM Data Transport treats the data as 133-byte records. Because there are no new line characters in the data, you must tell CA XCOM Data Transport how long each record is.