Re: FTP to fast -- MIDRANGE-L

That could work nicely - another idea is use Scott's FTPAPI service program - you then control the pace in your CL even more easily, perhaps.

Cheers
Vern

On 2/1/2022 9:14 PM, Roger Harman wrote:

I don't have access to a system to try this but the syscmd (or !) subcommand might work. You could call a CL with a DLYJOB in it.

https://www.ibm.com/docs/en/i/7.4?topic=ssw_ibm_i_74/rzaiq/rzaiqsyscmd.htm

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Laura Ubelhor
Sent: Tuesday, February 1, 2022 6:01 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: FTP to fast

Hello:
This is a first. We are working with a customer on an application that we create files on IBM i and transfer to a mircrosoft server using FTP. We've already asked and repeatedly been told FTP is the only way we can send the files.
The job stopped working in December and it wasn't noticed until sometime later the application was not completing. After researching and testing and troubleshooting on the IBM i and checking out the script............to no avail. Oddly the script ran fine when we ran it manually but we could not get it to work through a submitted job scheduled to run late at night. Everything was exactly the same for the script used to FTP when we did it manually and when the job ran as a scheduled job.
We finally were able to get some help on the microsoft server side and the following was determined. Working with the networking and server team to validate the following conclusions were reached.
They believe the reason the manual run works is because it was run slow.
The failure is that the server is placed into passive mode by IBM i. And not enough is granted to get it out of PASV mode. They were able to get the logs from a recent run from the FTP Server. It was competing with a very large amount of other FTP traffic. They said they cannot stress this enough we need to slow it down. Based on the traffic from the FTP Logs and the Network capture. The IBM i is jamming the data through. They asked the script be changed to slow it down to fix the problem.
Following is the script used for the job
xx-de-ffm-FTPSXXXX xxxxxxxx
namefmt 1

lcd ..

lcd /Bxxxxxxx

cd /DataxxxxImport/PURCH_DlvTerm

put DlvTerm_031.txt

cd ..

cd /DataxxxxImport/PURCH_GoodsReceipt

mput GoodsReceipt_031*

cd ..

cd /DataxxxxImport/PURCH_Invoices

mput Invoices_031*

cd ..

cd /DataxxxxImport/PURCH_Item

put item_031.txt

cd ..

cd /DataxxxxImport/PURCH_PaymentTerm

put PaymentTerm_031.txt

cd ..

cd /DataxxxxImport/PURCH_PricesMaster

put PricesMaster_031.txt

cd ..

cd /DataxxxxImport/PURCH_SettlementDisc

put SettlementDisc_031.txt

cd ..

cd \DataxxxxImport\PURCH_Supplier

put Supplier_031.txt

quit

Here is the last log from when it ran in batch successfully

This is in the last GOOD FTP Log:

             look at next rcd~ > put DlvTerm_031.txt

         --now check for response

             look at next rcd~ 227 Entering Passive Mode (10,101,1,10,0,100).

             look at next rcd~ 150 File status okay; about to open data connection.

             look at next rcd~ 226 Closing data connection. Transferred 252 bytes in 1 seconds. 0KB/second.

This is a first but does anyone have ideas how to so to speak slow the job down. We've been told FTP is the only option.
Regards,Laura

Laura Ubelhor

President

Consultech Services, Inc.

Office: (248) 628-6800

ubelhor@xxxxxxxxxxxxx | https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.consultechservicesinc.com%2F&data=04%7C01%7C%7C4d8d8f707c364657b3d608d9e5efe6c4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637793640811160213%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=k%2BcXBuG2m%2Bn62wvdjtnEhjsL4NFK6rETf0akKc875Ak%3D&reserved=0