Filter:
Submit Search

HULFT Transfer function

There are two types of HULFT file transfer functions provided by HULFT Square, HULFT Transfer services and HULFT Transfer Application.

HULFT Transfer services allow you to transfer files with the minimum settings while HULFT Transfer Application offers file transfers with settings closer to on-premises HULFT.

= Remarks =

For details on how to transfer files using HULFT Transfer services, refer to the following:

For details on how to transfer files using HULFT Transfer Application, refer to the following:

Select HULFT Transfer Application or HULFT Transfer services according to your needs.

A comparison of the transfer function that uses HULFT Transfer services, the transfer function that uses HULFT Transfer Application, and the transfer function of HULFT8 is as follows.

 

Function

HULFT Transfer service

HULFT Transfer Application

HULFT for Linux Ver.8.5.2 (on-premises)

Sending side function

 

Overall

The only transfer types supported are binary and text

(format and multi format are not supported)

The only transfer types supported are binary and text

(format and multi format are not supported)

 

Send File and Resend File

None

Send File

To send from HULFT Square, you need to put the operation that executes the Send File in the script and create the Send File processing.

Resend File

It can't be executed.

None

Send File

To send from HULFT Square, you need to put the operation that executes the Send File in the script and create the Send File processing.

Resend File

It can't be executed.

check

Checkpoint Resend File

None

 

check

Auto Resend

Limited

  • When a network error occurs

*

:

If the send processing fails due to reasons other than communication errors, auto resend is not executed.

check

  • When a network error occurs

  • When a failover occurs in the HULFT system on the receiving host and the host is forcibly stopped

check

  • When a network error occurs

  • When a failover occurs in the HULFT system on the receiving host and the host is forcibly stopped

Synchronous Transfer and Asynchronous Transfer

Limited

  • Synchronous Transfer requests are set in the Send File that you create in the HULFT connector script.

  • Synchronous is the default.

None

  • Asynchronous Transfer is applied to all transfers.

  • Synchronous Transfer can't be specified.

check

  • Synchronous Transfer Request is set using the command.

  • Asynchronous is the default.

Multicasting

None

Limited

  • For VPN connections, multicasting is available.

  • For PrivateLink connections, the port allocation settings of the VPC Endpoint Service (on the connection destination side) need to be configured.

check

Intermittent transfer

Limited

  • Specify the interval per transfer unit (transfer block length x transfer block count).

  • The transfer unit (transfer block length and transfer block count) is optimized automatically.

Limited

  • Specify the interval per transfer unit (transfer block length x transfer block count).

  • The transfer unit (transfer block length and transfer block count) is optimized automatically.

check

  • Interval

  • Transfer Block Length

  • Transfer Block Count

Compressed transfer

Limited

  • DEFLATE compression

check

  • Horizontal compression

  • Vertical compression

  • DEFLATE compression

check

  • Horizontal compression

  • Vertical compression

  • DEFLATE compression

Send multiplicity

Limited

The multiplicity is fixed at 10.

The number possible to send at the same time (send multiplicity) is up to 10 for one HULFT Transfer service.

check

  • MUX (set in the HULFT Transfer App service) for setting the Send multiplicity for the entire Send system

  • MUX (set in the Host configuration) for setting the Send multiplicity on a per-host basis

check

  • Send Process Multiplex Level for setting the Send Multiplex Level for the entire Send system

  • Send Process Multiplex Level by Host (set in Host Information) for setting the Send Multiplex Level on a per-host basis

Setting changes for the priority and Send Queue processing

None

Transfer Priority (TRANSPRTY) is fixed at 50.

check

check

Receiving side function

 

Send Request and Resend Request

None

Send Request

There are no send requests. Alternatively, by sending an empty file and then specifying a send operation in a subsequent job, functionality equivalent to Send Request is achievable.

Resend Request

It can't be executed.

None

Send Request

There are no send requests. Alternatively, by sending an empty file and then specifying a send operation in a subsequent job, functionality equivalent to Send Request is achievable.

Resend Request

It can't be executed.

check

Checkpoint Resend Request

None

None

check

Single Receive and Multiple Receive

Limited

  • Single Receive

Limited

  • Single Receive

check

Generational management

None

Generational Management isn't available.

By using the on-premises HULFT message function with the following procedure, you can receive files that are sent consecutively with the same file ID as separate files.

  1. Setting the message transmission parameter with the on-premises Send File command

  2. Setting the parameter to File to receive in the Receive configuration of HULFT Square

The file to receive will be replaced based on the above settings 1 and 2.

None

Generational Management isn't available.

By using the on-premises HULFT message function with the following procedure, you can receive files that are sent consecutively with the same file ID as separate files.

  1. Setting the message transmission parameter with the on-premises Send File command

  2. Setting the parameter to File to receive in the Receive configuration of HULFT Square

The file to receive will be replaced based on the above settings 1 and 2.

check

Receive multiplicity

Limited

The receive multiplicity is fixed at 10.

The number possible to receive at the same time (receive multiplicity) is up to 10 for one HULFT Transfer service.

check

check

Notification

Limited

  • Receive Completion

check

  • Transfer

  • Job

(*1)

check

  • Receive Completion

  • Successful Job Completion

Receive Ready Notification

None

None

check

Functions used by Send and Receive

 

Sending and receiving of networked files

None

None

check

Code Conversion

Limited

  • EBCDIC set (CODESET) is configured to "0" (Autoconfiguration).

  • There is no user table or custom character table.

  • Because there are no format transfers or multi format transfers, there are also no numeric data conversions.

Limited

  • There is no user table or custom character table.

  • Because there are no format transfers or multi format transfers, there are also no numeric data conversions.

check

Selection of a data transfer method (Framed Message Transfer Type)

Limited

The data transfer method is configured by setting Transferring direction in > SERVICES > HULFT Transfer.

 

When Inbound (Receive) is selected for Transferring direction

  • Error Detection Priority

  • Best Speed (default)

When Outbound (Send) is selected for Transferring direction

  • Error Detection Priority

  • Best Speed (default)

check

check

  • Error Detection Priority mode

  • Send Speed Priority mode

  • Receive Speed Priority mode

  • Send and Receive Speed Priority mode (default)

Cancel

Limited

  • Cancellation of file processing during a transfer

None

check

  • Cancellation of file processing during a transfer

  • Cancellation of file processing in the Send Queue

Dynamic specification

Limited

When sending

  • Synchronous Transfer (synchronous mode and asynchronous mode)

  • Timeout (sec.)

  • File to send

  • Messages 0 to 5 and long messages 0 to 1

When receiving

  • File to receive

  • Path name (when the sending-side host and receiving-side host are the same host type) (*1)

*1

:

Because only local storage (S3) of HULFT SQUARE is supported, you must take this into consideration when setting the path (file name).

None

check

When sending

  • Send File Name

  • Transfer Group ID

  • Name of a host on the receiving side

When receiving

  • Receive File Name

  • Path name (when the sending-side host and receiving-side host are the same host type)

Instant transfer

None

None

check

Observe function

 

Handling connection requests from HULFT Manager

None

None

check

System management function

 

Management information

Limited

  • Receive configuration

  • Send configuration

  • Host configuration

Limited

  • Receive configuration

  • Send configuration

  • Host configuration

  • Host group information

check

List output of management information

None

None

check

System Environment Settings

None

None

check

Management of logs

None

Rather than being the same format as HULFT, logs are provided as an event log of HULFT Square.

None

Rather than being the same format as HULFT, logs are provided as an event log of HULFT Square.

check

Support functions for the system operation

 

Operation language and date format selection

None

Switching the language between Japanese and English is supported. You can't select the date format.

Limited

hullang is fixed to ENG and datefmt is fixed to 2.

check

Message transmission

None

Limited

During sending, the message can't be set dynamically.

During receiving, only msg0 and msg1 are available.

check

Mail Interface

None

There is no management information called Mail Interface Information. Equivalent functions are available when you execute the email send operations of HULFT Square.

None

There is no management information called Mail Interface Information. Equivalent functions are available when you execute the email send operations of HULFT Square.

None

Job Start-up

None

If you combine jobs and scripts, an equivalent function is available. However, external commands can't be used.

None

If you combine jobs and scripts, an equivalent function is available. However, external commands can't be used.

check

Scheduler function

check

check

None

Job Execution Result Notification

None

If you combine jobs and scripts with the notification function, an equivalent function is available.

None

If you combine jobs and scripts with the notification function, an equivalent function is available. (*1)

check

Post-receive Job Result Inquiry Request

None

None

check

Remote job execution

None

By using REST API jobs, an equivalent function is available.

None

If a job is registered in HULFT Square, it can be called from a REST API job, but a file transfer of HULFT Transfer Application can't be called.

check

File trigger

None

By using file jobs, an equivalent function is available.

check

check

File Record Edit function

None

None

check

Multiple File Join function

None

None

check

Display of the status of a transfer

None

None

check

Provision of HULFT API

None

None

check

Remote heartbeat monitoring

None

None

check

Transfer Test

None

None

check

Automatic optimization of transfer settings

check

check

check

Security

 

Data Verification function

check

check

check

Verification of the Host group information

None

check

check

Operation Log Output

None

Although there is a function to output the audit and event logs, it isn't exactly the same as the HULFT function.

None

Although there is a function to output the audit and event logs, it isn't exactly the same as the HULFT function.

check

Encryption

None

There is no Forced Strong Key mode

There is no C4S.

You can't explicitly specify HULFT Encryption Scheme.

None

There is no C4S.

You can't explicitly specify HULFT Encryption Scheme.

check

Observe setting functions for requests from unregistered hosts

None

None

check

Observe setting functions for requests from registered hosts

None

None

check

Other functions

 

Inquiry function for the System Environment Settings

None

None

check

Restoration function for the System Environment Settings

None

None

check

HULFT8 Script

None

An equivalent function is provided by the Data Integration function.

None

An equivalent function is provided by the Data Integration function.

check

check

:

Supported.

Limited

:

Some of the functions are supported.

None

:

Not supported. If there is an alternate function, it is listed.

*1

:

About the behavior when Notification is set to Successful Job Completion

Even if the execution of the script set in All > Triggering conditions on the HULFT Transfer Application page fails, a HULFT transfer is completed successfully.

For the success or failure of a script execution after receiving, a notification is sent to the sending side HULFT using Job Execution Notification (hulsndrc).

For information on how to check job execution notifications, refer to "Job Execution Result Notification service settings."

The job execution notifications that are sent from HULFT Transfer Application are as follows:

  • HOSTNAME

    Host name of the HULFT Transfer Application service (8 bytes)

  • JOBNAME

    Application name (Truncated to fit into 60 bytes.)

  • DATE

    Job end date (hulsdnrc execution date)

  • TIME

    Job end time

  • RC

    Numbers that indicate script success and failure (0: successful completion, -1: unsuccessful completion)

  • MESSAGE

    When a script finishes successfully, it is blank. For unsuccessful completions, text such as the following is entered. Truncated to fit into 128 bytes.

    {Script name where the error occurred}|{Component name where the error occurred}

    (Example) Script|csv_read

  • DN

    Domain name

 

About the Code Conversion function

For details on the functional specifications and points to note for the code conversion function of HULFT Transfer App, refer to the HULFT8 manual.

 

About the cipher options

For details on the functional specifications and points to note for the cipher options of HULFT Transfer Application, refer to the HULFT8 manual.

Policies     (c) Saison Technology Co.,Ltd. 2021

TOP