Limitations common to send processing and receive processing

(1) Successful Job Completion

If the host on the receiving side is HULFT for K, you cannot set "Successful Job Completion" for the Notification.

If the host on the sending side is HULFT for K, the Notification is enabled on the host on the receiving side.

(2) Cancellation of receiving

HULFT for K does not have cancellation program for receiving.

(A command to cancel sending has been available in HULFT for K Ver.2.1.0 or higher.)

(3) Code Conversion

If the host on the sending side is HULFT for K, you cannot set "No Conversion" for the Code Conversion.

Further, when code conversion is executed in HULFT for K, it is performed always assuming EBCDIC Set is set to EBCDIC Katakana.

If you want to let HULFT carry out conversion to a code set other than EBCDIC Katakana in the conversion between ASCII-type host and EBCDIC-type host, specify the EBCDIC Set on the remote host in order to allow conversion on the remote host.

(4) Subsequent character in fixed-length file

There is no Subsequent Character function in the sending function for HULFT for K. Padding is not available for the receiving function.

(5) Conversion between EBCDIC Codes

HULFT for K does not support conversion between EBCDIC codes.

(6) Support for NEC Kanji

HULFT for K does not support NEC Kanji conversion.

(7) Support for UTF-8

HULFT for K does not support UTF-8 conversion.

(8) C4S and AES

There is no C4S Cipher Option or AES Cipher Option in HULFT for K.

(9) Transfer Data Encryption

Transfer of encrypted data to or from HULFT for K is not available. There are no HULFT Cipher Options.

(10) Verification of consistency in transfer data

Verification of consistency in transfer data is not available for transfer between HULFT for K and HULFT8.

(11) Message Transmission

If the host on the sending side or the host that issued the Send Request (receiving) is HULFT for K, you cannot specify the Message Transmission.

When the host on the sending side is HULFT Ver.6 or higher, HULFT replaces the variables with messages that are transmitted by a sending host, but the application does not transmit messages to a receiving host.

Meanwhile, when the host that issued the Send Request (receiving) is HULFT Ver.6 or higher and the host that acknowledges the request (sending) is HULFT for K, HULFT replaces variables with messages upon issuing the Send Request, but the application does not transmit the messages to the host that acknowledges the request or receives a file.

(12) Conversion of Field Attributes and Signs in Format Transfer

If a remote host of transfer is HULFT Ver.6 or higher and the remote host carries out code conversion, the conversion of field attributes and sign parts is available for HULFT for K.

(13) Improvement in Transfer Speed by Selecting Data Transfer Method

Transfer Speed Priority Mode is not supported for transfer with HULFT in HULFT for K.

(14) XML interface

XML interface is not available, except for transfers between the hosts of HULFT Ver.6 or HULFT Ver.7.