|
I have tried both methods as far as entering in the user and password. I have many .bat files that do ftp and many ftp input files that contain script to do it with db2 files. My problem seems to be becuase of the port#. I can do it all manually from a DOS command now, I have the correct syntax for the port#. However when I put it in script i get invalid user. I am not sure on the examples on FAQ and even from other users on the list you put the word 'user' before the user and password. This did nothing put cause more errors as it thought i was trying to logon as 'user' and was then sending 2 parms. Running manually from a DOS command: C:\>ftp ftp> open 192.168.0.245 20 Connected to 192.168.0.245. 220 ntsvr03-nt Microsoft FTP Service (Version 4.0). User (192.168.0.245:(none)): angie 331 Password required for angie. Password: 230 User angie logged in. ftp> dir 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls. 01-11-02 12:51PM 182496 db.txt 01-10-02 02:26PM 74 netfinity.txt 226 Transfer complete. ftp: 101 bytes received in 0.00Seconds 101000.00Kbytes/sec. ftp> put \\qausteel\home\dunnbrad\dab.txt db.txt 200 PORT command successful. 150 Opening ASCII mode data connection for db.txt. 226 Transfer complete. ftp: 182496 bytes sent in 0.21Seconds 864.91Kbytes/sec. ftp> .BAT file RMTCMD STRTCPSVR SERVER(*FTP) ftp -s:\\qausteel\HOME\dunnbrad\dunnbrad.txt START /W RMTCMD ENDTCPSVR SERVER(*FTP) .txt file open 192.168.0.245 20 angie password1 put \\qausteel\home\dunnbrad\dab.txt db.txt quit >From AS/400 files: FTPINDB ANGIE PASSWORD1 PUT \\QAUSTEEL\HOME\DUNNBRAD\DAB.TXT DB.TXT QUIT FTPoutdb: Output redirected to a file. Input read from specified override file. Connecting to remote host 192.168.0.245 using port 20. 220 ntsvr03-nt Microsoft FTP Service (Version 4.0). Enter login ID (wawrzaszek): 331 Password required for ANGIE. 530 User ANGIE cannot log in. Enter an FTP subcommand. > PUT \\QAUSTEEL\HOME\DUNNBRAD\DAB.TXT DB.TXT You must first issue the USER subcommand. Enter an FTP subcommand. > QUIT More... To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.