I have been using this for a while and it is much easier than creating a file transfer or anything of that sort.
Basically, the client PC must be set up with IIS and then slightly tweaked. Right-click on the Default FTP site and click on Properties. Under the Home Directory tab, make sure that "Write" is checked. Under Security Accounts, make sure "Allow Anonymous Connections" is checked.
On the 400 side, I created two files called FTPCMDS and FTPLOG. An example of my FTPCMDS is listed below.
A CL Program will need to be created that uses the FTPCMDS file for input and the FTPLOG file for a detailed log of each thing that happens.
I called my CL program BATCH_FTP and it is attached as well. Make sure that the host name you are FTPing to is in the 400's host table (CFGTCPHTE).
The file will automatically be placed on the PC that you intend for it to go to. The default place is C:Inetpubftproot.
FTPCMDS: ANONYMOUS HUNT@GDXAUTOMOTIVE.COM LCD QOS PUT INVENTORY INVENTORY.TXT QUIT BATCH_FTP (CL Program): PGM OVRDBF FILE(INPUT) TOFILE(QOS/QCLSRC) MBR(FTPCMDS) OVRDBF FILE(OUTPUT) TOFILE(QOS/QCLSRC) MBR(FTPLOG) FTP RMTSYS(QOSTEMP) ENDPGM
This was first published in March 2002