Re: How to write a saved file to IFS
- From: Tom Liotta <thomas@xxxxxxxxxxx>
- Date: Sat, 31 Mar 2007 01:08:36 -0700
Holger Scherer wrote:
When using FTP to transfer objects from one system to an other,
one always should state the name of the object twice so the target
system will create the object correctly. I found, sometimes the
file name is transferred in upper case if omitted and the target
system will be confused.
Thus, use this method:
FTP (target system)
cd /some/where (on the target system)
namefmt 1 (if using AS400-FTP, or QUOTE SITE NAMEFMT 1)
lcd /my/source (on the target system)
bin (binary transfer)
put mylib.savf mylib.savf (twice stated, save file does not need to
exist on target system)
I see Karl Hanson has already mentioned this, but I'll send anyway with a little more description.
FTP under OS/400 or i5/OS recognizes the .SAVF extension when using NAMEFMT 1 and will create a savefile. The reason to have it "twice stated" would be to have a different name on the receiving system. A savefile must be transferred as BINARY because it's not text data and should not be translated due to different character encodings -- a savefile is a binary file.
Those FTP subcommands are sufficient to transfer savefile MYLIB to the remote system. It will be created as a savefile in the current directory.
To work, it must be transferred BINARY, it must be done under NAMEFMT 1 _and_ the extension must be .SAVF. The .SAVF extension works by default when transferring to or from an AS/400. If the sending or receiving system is a PC for example, then the file must actually have .SAVF as the extension.
- Prev by Date: AS400 170 replace drives
- Next by Date: Re: How to write a saved file to IFS
- Previous by thread: Re: How to write a saved file to IFS
- Next by thread: Re: How to write a saved file to IFS