Transfer types

HULFT can transfer the data that consists of single byte codes, double byte codes, and numerical data as well as data in which they are mixed. The application can convert codes to match the receiving host.

You can select the transfer type that is suitable for the format of the sending data from the transfer types that HULFT provides, which are shown below.

Table 2.1 Transfer Type
Transfer Type	Transfer Data Type
Text transfer	HULFT transfers a file containing text data that is composed of only character codes, carrying out Code Conversion one record at a time. Single byte code conversion, double byte code conversion, tab code processing, newline character processing, and shift code processing are available.
Binary transfer	HULFT transfers the data that has no concept of records, without carrying out Code Conversion.
Format transfer	HULFT transfers a file that is a composite of the fixed-format records that require field-by-field conversion according to formatting definition. Single byte code conversion, double byte code conversion, Numeric Data Conversion, and shift code processing are available.
Multi format transfer	When a file contains a mixture of records that have different formats, define each format in order for HULFT to apply the appropriate format for each code and carry out conversion and transfer. Single byte code conversion, double byte code conversion, Numeric Data Conversion, and shift code processing are available.

= Remarks =

How HULFT determines what constitutes one record of data varies depending on the host type, as shown below:

Type Win-UX hosts:: By the location of a newline character (delimiter)
Mainframe:: By using the record length that is defined upon creation of the data set (for a variable-length record, the length that is contained in the RDW)
IBMi:: By using the record length that is defined for the file

For details on newline characters that HULFT handles, refer to Newline characters.