Technical

Tips

I Want to Notify the Sending Host When the Receiving Host is Able to Receive Files

Introduction

In this tip, I would like to explain a function that can help simplify the resending of files.
If you execute send processing from the sending host when the receive process on the receiving host is not running, the file is queued for resending on the sending host, as shown in diagram (1).
After the file is queued for resending, you need to manually resend the file after the receive process on the receiving host is started in order to complete the file transfer.

However, if you set up Receive Ready Notification, which I will introduce in this tip, the receiving host automatically notifies the sending host when the receive process starts, as shown in diagram (2). When you use this function, the file is resent automatically, even if you don't manually resend it.

In this example, I will use HULFT8 for WINDOWS to explain the procedure for setting up this function and performing an operation check.


Procedure for Setting Up the Function

This function must be set up on the receiving host.
You can specify the settings in the HULFT management screen or in the System Environment Settings.

Specifying Settings in the HULFT Management Screen

1. Under System Environment Settings, open Send and Receive, and set Receive Ready Notification to Yes.

2. Restart the HULFT service and the HULFT Management screen.


Entering Settings in the System Environment Settings File

1. In the System Environment Settings file (hulenv.cnf), add the following tag:

2. Restart the HULFT service and the HULFT management screen.

When you specify the above settings, every time the receive process is started, a Resend Request is issued to all hosts that are registered in the Host Information.
If an error occurs on even one of those hosts, or if a Resend Request is issued to a host on which no resend queue files exist, the Resend Request for that host results in an error because no file could be resent. However, resend queue files are still resent from the hosts that are able to correctly acknowledge the request.
In this example, an error is output on the receiving host because no resend queue files exist on Sending Host 1.

In HULFT for UNIX/Linux, if you want to automatically execute the Receive Ready Notification command when you start the computer, the procedure for enabling this automatic execution differs depending on the OS. (For example, in some cases you can enable automatic execution by adding utlrecv -a to the system startup script file.)
For details, see the Administration Manual for the OS you are using.


Operation Check
  • Check the following operations in an environment like the one shown in the diagram below.

1. Send a file when the receive process on the receiving host is running.
=> Confirm that the sending of the file finishes successfully.
2. Send a file when the receive process on the receiving host is stopped.
=> Confirm that an error occurs and that the file is added to the Resend Queue Status List.
3. Restart the receive process on the receiving host.
=> Confirm the following:
- That a Receive Ready Notification is sent to Sending Host 1 and Sending Host 2
- That a resend error is output for Sending Host 1 (because there are no resend queue files)
- That Sending Host 2 resends the queued file automatically, and that the list of files that are queued to be resent is now empty


1. Send a file when the receive process on the receiving host is running.

Receiving Host

Sending Host 1

2. Send a file when the receive process on the receiving host is stopped.

Receiving Host

Sending Host 2


3. Restart the receive process on the receiving host.

Receiving Host

Sending Host 1

Sending Host 2

As you can see, when Receive Ready Notification in the System Environment Settings is set to On, even when a transfer fails because the other host is stopped, you can detect when the host starts and automatically resend files at that time.


Conclusion

So, what do you think? By setting up Receive Ready Notification, you can cut operational losses.

However, you should be aware that if a large number of hosts are registered in the Host Information, the command may take a long time before it ends.

  • Well, that concludes my introduction of the Receive Ready Notification function.
  • I hope you will find this function useful in your day-to-day operations.