Operational limitations in the features

This section explains limitations in features when HULFT and HULFT-HUB cooperate.

Limitations on Host Name

  • To use HULFT under the control of HULFT-HUB, the characters of the Host Names must be 44 bytes or less. If 45 bytes or more characters including domain name are used for the Host Name, it is necessary to re-specify the field within 44 bytes.

  • When you define the transfer via HULFT-HUB Server, by default, HULFT-HUB adds the Receive Port No. to the original Host Name for management purpose. In this case, the combined Host Name which consists of the Host Name and the Receive Port No. is displayed in various status display commands and logs.

    Example:

    Host Name

    HOST1

    Receive Port No.

    30000

    Host Name used in the transfer via HULFT-HUB

    HOST1_30000

Because HULFT-HUB uses a different host name, the existing job settings may require a change when a pre-send, post-send, or post-receive job might reference the host name on an environment variable.

Limitation on Multicasting and Accumulation

  • When you use multicasting function and accumulation function of HULFT-HUB, the Checkpoint Resend File is not performed. Whenever you specify the Checkpoint Resend File, the application sends the data from the top.

  • The specification of "Sending Side" for the Code Conversion is available only when the settings in the Kanji Code Type and the JIS Year of all HULFT located at the multicasting destinations are consistent with those of HULFT-HUB Server that executes the first multicasting processing. When the situation does not fall under above, it is necessary to select "No Conversion" or "Receiving Side" for the File ID specified in multicasting.

  • When you issue the Send Request or the Resend Request with the File ID in which multicasting is specified by HULFT-HUB, absence of the target data in the server results in an error on the sending side client.

Limitation on Management Console Security

Operational limitations placed by permission settings may not become effective when a use permission is set by using the Management Console Security on HULFT, even if the setting to log in HULFT via HULFT-HUB is specified. When you use HULFT-HUB, specify the permission settings on the side of HULFT-HUB again.

Limitation on requests acceptance

  • The types of the service requests that can be used in the transfer via HULFT-HUB are only the Send Request (SEND) and the Resend Request (RESEND).

  • Executing the Job Execution Result Notification request with post-send or post-receive jobs in the transfer via HULFT-HUB causes an error. Besides, executing the Job Monitor request of the Send Log on the Management Console of HULFT that carried out a transfer via HULFT-HUB causes an error.

Version of IP protocol

HULFT-HUB does not provide support for IPv6. Therefore, HULFT-HUB cannot communicate with HULFT of which communication method is only IPv6.