This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Now I understand. When I thought that I was adding a destination by using the second parameter, /rob/*, what in fact I was doing was adding more files to send, in addition to the first parameter /rob/spool2*.txt. Thank you for clearing this up. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Scott Klement <firstname.lastname@example.org> Sent by: email@example.com 05/22/2002 04:11 PM Please respond to midrange-l To: firstname.lastname@example.org cc: Fax to: Subject: Re: Problems with MPUT, ignores NAMEFMT and wildcards perform strange. I don't know if things are different in V5R1, but on V4R5, MPUT treats each file listed as one of the files to transfer. So, mput /rob/spool2*.txt /rob/* would first put everything matching spool2*.txt and then put anything matching /rob/* to the remote server. MPUT does not have an argument for the remote filename. This behavior is consistent with Win98, Linux and FreeBSD's FTP clients as well. On Wed, 22 May 2002 email@example.com wrote: > > I am doing FTP between two iSeries. They are both running V5R1, cum > TL02071. When I execute the following: > Enter login ID > xxx > Enter password: > yyy > namefmt 1 > 250 Now using naming format "1". > Server NAMEFMT is 1. > Client NAMEFMT is 1. > put /rob/spool2.txt /rob/spool2.txt > 150 Sending file to /rob/spool2.txt > > but mput continues to use the library system > mput /rob/spool2*.txt /rob/* > 150 Sending file to member TXT in file SPOOL2 in library QGPL. > > This is lousy. The workaround is to do a > cd /rob > prior to the mput > > What is even worse is that: > mput /rob/spool2*.txt /rob/* > actually copied every file in my /rob directory into QGPL: > mput /rob/spool2*.txt /rob/* > 250 Now using naming format "1". > 257 "/QSYS.LIB/QGPL.LIB" is current library. > 150 Sending file to member TXT in file SPOOL2 in library QGPL. > 150 Sending file to member TXT in file SPOOL2 in library QGPL. > 150 Sending file to member TXT in file SPOOL3 in library QGPL. > 150 Sending file to member JPG in file DECOY1 in library QGPL. > 150 Sending file to member CSV in file LL855T01 in library QGPL. > 150 Sending file to member TEST in file TEST in library QGPL. > 150 Sending file to member INI in file NOTES in library QGPL. _______________________________________________ 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-Lfirstname.lastname@example.org Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact