|
What about escaping the spaces with backslash? /bncf/pdfs/7101\ 0412\ 3400\ ...\ 1455.pdf HTH, Adam midrange-l-bounces+aglauser=erbgroup.com@xxxxxxxxxxxx wrote on 18/07/2006 04:43:59 PM:
The iSeries ftp client is ignoring the quotes. In both your examples below, the client failed with same msg I read an older TCP manual for as/400 and everything described except embedded blanks in file name.put /bncf/pdfs/"7101 0412 3440 1365 1599..pdf"Number of arguments not valid for subcommand put. jim franz ----- Original Message ----- From: "Chris Payne" <CPayne@xxxxxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, July 18, 2006 4:04 PM Subject: RE: ftp from iSeries ifs to Win serverTry using quotes, either Put /bncf/pdfs/"7101 0412 3440 1365 1599..pdf" Or Put "/bncf/pdfs/7101 0412 3440 1365 1599..pdf" -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz Sent: Tuesday, July 18, 2006 4:01 PM To: MIDRANGE-L@xxxxxxxxxxxx Subject: ftp from iSeries ifs to Win server I get files from a win server that are stored in IFS, and now need to ftp to another win server. File names have imbedded blanks in name. Getting FTP error. Anything I can do (other than rename the files to ftp)? Am processing the ftp commands thru a source file, setting ovrdbf to "Input".locsite namefmt 1Client NAMEFMT is 1. Enter an FTP subcommand.put /bncf/pdfs/7101 0412 3440 1365 1599..pdfNumber of arguments not valid for subcommand put. jim franz -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
##################################################################################### Attention: The above message and/or attachment(s) is private and confidential and is intended only for the people for which it is addressed. If you are not named in the address fields, ignore the contents and delete all the material. Thank you. Have a nice day. For more information on email virus scanning, security and content management, please contact administrator@xxxxxxxxxxxx #####################################################################################
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.