Re: FTP to fast -- MIDRANGE-L

Le 04/02/2022 à 03:51, Laura Ubelhor a écrit :

Thaks Marc.
The batch job is sent through the job scheduler and coded within a CL.

I believe the trace was completed but will ask.
Manual and automatic are the same commands.

Hello

Could you paste the ftp log when it works in manual mode?
Please include all commands you use just after you get the logged on return from the server. Something like that:

   230 DIMARCO logged on.
    OS/400 is the remote operating system. The TCP/IP version is "V7R4M0".
   250 Now using naming format "1".
   257 "/home/DIMARCO" is current directory.
> dir
   200 PORT subcommand request successful.
   125 List started.
   drwx------   2 DIMARCO 0           8192 Dec 15 15:27 docs
   drwxr-xr-x   3 DIMARCO 0           8192 Dec 15 15:30 sources
   drwxr-xr-x   3 DIMARCO 0           8192 Dec 16 10:38 sqlstmt
   -rw-------   1 DIMARCO 0              8 Jan 25 13:06 .sh_history
   -rw-------   1 DIMARCO 0             19 Jan 25 13:22 .bash_history
   250 List completed.

namefmt1

lcd ..

lcd/XXXXXXaster

cd /DataXXXXX_TEST/partXXXXX/others

put031_AS400_PartXXXXX.csv
quit

Here is the log from the automatic
look at nextrcd~     Enter an FTP subcommand.
look at next rcd~     > lcd/XXXXX
look at next rcd~     Localworking directory is /Bravo
look at next rcd~     Enter anFTP subcommand
look at next rcd~     > cd/DataXXXXX/PURCH_DlvTerm
look at next rcd~     250Directory changed to "/DataXXXXX/XXXXX_DlvTerm/"
look at next rcd~     Enter anFTP subcommand
look at next rcd~     >noop
look at next rcd~     200Command OK.
look at next rcd~     Enter anFTP subcommand
look at next rcd~     put031_AS400_XXXXXTerm.csv
now check for response
look at next rcd~      Noresponse received from FTP server
look at next rcd~      Noresponse from remote host; all connections closed.
look at next rcd~     Unable to set up for an active data connection to
the server, reason code 2.
look at next rcd~     Enter an FTP subcommand
look at next rcd~     /cd ..
look at next rcd~     You mustfirst open a connection.
look at next rcd~     Enter anFTP subcommand

ThanksRegards,Laura

Laura Ubelhor

President

Consultech Services, Inc.

Office: (248) 628-6800

ubelhor@xxxxxxxxxxxxx | www.consultechservicesinc.com

On Thursday, February 3, 2022, 04:17:22 PM EST, Marc Rauzier <marc.rauzier@xxxxxxxxx> wrote:
Le 03/02/2022 à 18:54, Laura Ubelhor a écrit :
The weird thing is the FTP worked for several years. They had a network server crash and it stopped. Of course on the network side they are not being very helpful. They came up with slow the data transfer down response, They finally shared a log but have not been real helpful.
The weird thing is if you send the file manually it works just fine.
If you send it automatically (which worked for years) it does not.

What are the exact ftp subcommands in both cases (manual and automatic)?
How is the automatic transfer initiated and how does it run (is this an
homemade tool?)?

You may want to generate a trace in both cases with TRCTCPAPP APP(*FTP)
RMTNETADR(remote_server_ip_address) and compare the output, at least the
steps which run fine in manual case and fail in automatic case.

The ids are the same the ports the same. I really think it is on the network side.