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

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Rob,

Save files are a very special animal.  They have to be opened as 
record-based files with a particular byte-length record, and they have 
to have special checksums at particular points in the record, or the 
system will not accept them.

That means that for an FTP software to load them, it must have special 
code inside it that understands that it's a save file, and understands 
how to manipulate it properly.  Generic FTP software is unlikely to do 
that, as no other platform on earth has the equivalent of a save file 
that I'm aware of.

What you CAN do, however, is upload your SAVF to the IFS as a stream 
file instead of a save file.  Then copy it across to a QSYS.LIB object 
using CPYFRMSTMF.




On 2/1/2013 1:45 PM, 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 /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