HULFT Short Stories

Vol.2: What to do when a data transfer error occurs

Hello.
My name is Okazaki and I am in charge of HULFT seminar.

The rainy season is over and hot days are continuing.
I'm from Kansai, and the heat there is very humid, while the heat in Tokyo feels very sunny.
I find the heat in Tokyo more difficult...
Everyone, please be careful not to get heatstroke by staying hydrated.

Now, let's move on to "HULFT Short Stories," a series that began last month and introduces how to use HULFT.
We will share some tips on how HULFT can solve common issues that arise when file transfer!

The second part is "What to do when file transfer error occurs"
We will introduce you to the following.

Once you have built file transfer infrastructure, you will need to design its operation. Of course, you need to ensure that processing completes normally, but you also need to consider the possibility of errors occurring.
If an error occurs during file transfer, it is necessary to not only reliably detect the error but also to execute recovery procedures appropriate to the operation.
For example, you may want corrupted files to be properly deleted and for the system to automatically retry several times.
Also, if the retry is unsuccessful, it is common to want to notify the operator by email that an error has occurred.
It would be a disaster if an error occurred during overnight processing and you didn't notice it until the morning!

If you build file transfer infrastructure using FTP, it takes a lot of time and effort to implement error detection and recovery processes.
On the client side, you can check the return value of the command to detect the error.
On the other hand, the server side cannot know whether the file has arrived properly unless it goes and checks for itself.
So, first we need to create a monitoring system. We create a resident program to monitor the system, and then we need to think about an error handling system.
Then we will create further recovery processes such as retries.
Also, since the considerations and recovery operations differ depending on the business, it is difficult even to solidify the specifications.
I can imagine that it's a lot of work...

If you build file transfer infrastructure using FTP, it takes a lot of time and effort to implement error detection and recovery processes.
On the client side, you can check the return value of the command to detect the error.
On the other hand, the server side cannot know whether the file has arrived properly unless it goes and checks for itself.
So, first we need to create a monitoring system. We create a resident program to monitor the system, and then we need to think about an error handling system.
Then we will create further recovery processes such as retries.
Also, since the considerations and recovery operations differ depending on the business, it is difficult even to solidify the specifications.
I can imagine that it's a lot of work...

In addition, if an error is detected, you can set it to automatically retry if it is a network error.
It is common for network outages to cause temporary disconnections, but even in such cases, HULFT will automatically retry and terminate normally.
If file transfer fails, the file can be left as is or automatically deleted as invalid data.
Email notifications to operators can also be easily done by using HULFT Script, an optional HULFT optional product, by drawing a flow in the GUI.

In this way, with HULFT, you can detect errors and perform recovery processes with almost no effort, just by setting it up.

Well, what do you think?

We have introduced HULFT 's error handling, but when customers who are planning to propose or will be in charge of file transfer systems come to our seminars, we often get questions about the comparison between FTP and HULFT and how to solve problems. We hope that this information has been of some help to you.

We will continue to share tips on how to use HULFT next time.
The next send is scheduled for the second week of September. Please look forward to it!!

Inquiry

We look forward to receiving your opinions, comments, and letters regarding this column.
Contact:hulseminar@hulft.com

Experience HULFT Products.

Related Content