Flow of sending started on the receiving side

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

This processing is based on the assumption that both the Send daemon and the Observe daemon on the sending side as well as the Receive daemon 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 daemon waits for the Send Request from the receiving side.

3) Starting up the Observe process

When the Observe daemon acknowledges the Send Request from the receiving side, the daemon starts the Observe process. This is performed every time the request is acknowledged and the procedures from 4) onwards are executed. When a Pre-send Job is set in the Send Management Information, HULFT can execute the job before the operation described in 4) .

4) Send File

The Observe process issues the request for the Send processing to the Send daemon.

5) Writing the request to the Observe Log file

The Observe process writes the request from the receiving side into the Observe Log file (hulaccreqlog.db).

6) Starting up the Send process

The Send daemon receives the Send File and starts the Send process according to the conditions in each management information file. This operation is carried out at the time of each transfer.

7) Carrying out Send processing

The Send process 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.

8) Writing the result to the Send Log file

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

9) Starting up the Post-send Job

The Send process 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.

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

The Send process writes the job execution results to the Post-send Job Execution Log file (hulsndlog.db).

Note

  • The term 'job' represents an operation unit. A job specifies the execution of shell scripts, the execution of a command, 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.