Flow of sending started on the receiving side

The sending operation can also be started with a request from the receiving side. This request is called as 'Send Request' in HULFT.

This processing is based on the assumption that both the Send process and the Observe process on the sending side as well as the Receive process on the receiving side have already been started.

The flow of sending that is started on the receiving side is illustrated in Figure 2.2 .

Figure 2.2 Flow of Sending That Is Started on Receiving Side

1) Creating the Send file

The target file (Send file) can be any file that you create in the course of your daily office operations.

2) Waiting for the Send Request from the receiving side

The Observe thread receives the Send Request from the receiving side. When the Send Request is received, a Send File thread is created and operations from 3) onwards are executed.

In the Send Management Information, you can define the Pre-send Job, which HULFT executes before the operation described in 3) starts.

3) Send File

The Send File thread issues the request for the Send processing to the Send Acknowledge thread.

4) Writing the request to the Observe Log file

The Send File thread writes the request from the receiving side to the Observe Log file.

5) Creating the Send thread

The Send Acknowledge thread receives the Send File command (utlsend.exe) and creates a Send thread within itself according to the criteria in each management information file. This operation is carried out at the time of each transfer.

6) Carrying out Send processing

The Send thread carries out Code Conversion and file compression based on the settings in the Send Management Information and transfers the data of the Send file to the remote host.

7) Writing the result to the Send Log file

The Send thread writes the result of the Send processing in the Send Log file after the processing is complete. In addition, if the Send processing ends unsuccessfully, the Send thread writes the information about the failed transfer into the Resend Queue file (sddreqls.dat).

8) Starting up the Post-send Job

The Send thread activates the Post-send Job that is registered in the Job Information according to the condition that is registered in the Send Management Information. HULFT activates either the job that is specified for the successful end of the sending or the one for the unsuccessful end of the sending, depending on the transfer result.

9) Writing the result to the Post-send Job Execution Log file

The Send thread writes the job execution results to the Post-send Job Execution Log file.

10) Triggering an email

The Send thread triggers to send an email according to the settings that are registered in the Mail Interface Information.

Note

  • The term 'job' represents an operation unit. A job specifies the execution of an application program, the execution of a batch file, and so on.

  • HULFT does not write the execution result of the Pre-send Job to the log file.

  • HULFT does not execute the Pre-send Job for the Resend Request.

  • For the Send Request, HULFT sends the file only to the host that issued the Send Request, even if multiple hosts are registered in the Transfer Group Information that is specified in the Send Management Information.

    An error occurs if the host that issued the Send Request is not registered in the Transfer Group Information.