|
<snip>
Pre-create the save file and replace
the ".savf" with ".file" on the name specification.
</snip>
Sounds a lot like
<snip>
Doing all that BS we used to have to do with namefmt 0, like making sure
the save file already exists and whatnot doesn't help.
</snip>
But maybe I misheard you. So I verified I used .file instead of .savf
cd /qsys.lib/rob.lib250 Directory changed to /qsys.lib/rob.lib
locsite namefmt 1Client NAMEFMT is 1.
lcd /qsys.lib/rob.libLocal working directory is /QSYS.LIB/ROB.LIB
bin200 Command TYPE okay.
put rob.file229 Entering Passive Mode (|||24356|)
150 File status okay; about to open data connection.
Unable to send data to server.
551 /qsys.lib/rob.lib/rob: Error on output file.
501 Invalid character in command
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: CRPence <CRPbottle@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx,
Date: 02/01/2013 03:15 PM
Subject: Re: IFS, not quite Integrated Was: Unix??? was: ftp: mget
specifying path names
Sent by: midrange-l-bounces@xxxxxxxxxxxx
On 01 Feb 2013 11:45, rob@xxxxxxxxx wrote:
The ftp server I am replacing the IBM i native ftp server with does
not support the /qsys.lib part of the IFS.
I can do a
put /mypcdir/downloaded.savf /someIfsDirectory.dir/downloaded.savf
but I can't
put /mypcdir/downloaded.savf /qsys.lib/mylib.lib/downloaded.savf
Doing all that BS we used to have to do with namefmt 0, like making
sure the save file already exists and whatnot doesn't help. Gives me
a invalid character error even though you can use dots and slashes
outside of the qsys.lib file system.
The ".savf" file extension for the /qsys.lib file system is an
extension of the IBM i FTP server. Pre-create the save file and replace
the ".savf" with ".file" on the name specification.
put /mypcdir/downloaded.savf /qsys.lib/mylib.lib/downloaded.file
--
Regards, Chuck
--
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.
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.