IFS, not quite Integrated Was: Unix??? was: ftp: mget specifying path names -- MIDRANGE-L

Subject: IFS, not quite Integrated Was: Unix??? was: ftp: mget specifying path names
From: rob@xxxxxxxxx
Date: Fri, 1 Feb 2013 14:45:00 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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 /mypcdirectory/downloaded.savf /someIfsDirectory.dir/downloaded.savf
but I can't
put /mypcdirectory/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.

Rob Berendt

Follow-Ups:

Re: IFS, not quite Integrated Was: Unix??? was: ftp: mget specifying path names , Scott Klement

This mailing list archive is Copyright 1997-2026 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.