After entering BINARY and pressing enter you would do the put command.
The format is put libraryname/savfname (on AS400 being sent from) libraryname/savfname (on remote AS400).
For example: put abclib/abcsavf rmtlib/rmtsavf then press enter. Once this has completed simply type quit then press enter. Continue on with restoring objects in the save file on the remote system.

Knowing the steps you took and the error will help.

Make sure you are pointing to the correct location on both machines – If not use change directory command.
Ensure you have sufficient authority to all objects – files, lib, etc

You can also try the DEBUG to trace the issue

Type QUOTE DBUG to begin and end the trace. The trace creates a spooled file called QTMFFTRC. The
default output queue contains the spooled file.

You probably know this, but be sure to create a blank savf on the target system if it doesn’t already exist, or you will get an unreadable PF.

Hi RPGILer,
I tried exactly as you said with the PUT command, but I get an error saying :

“Unknown extension in database file name”

ps: I created a dummy *SAVF on the remote system and the lib names on both remote and local machine is same (in case if this makes any difference)

uhm…

try
NAMEFMT 0

Another option is to use the SAVRSTOBJ Command. One step, works slick !

Hope this helps,
Bill Poulin

But not if, like me, you’re still languishing on release 5.4!

You could map a drive on your PC client for each iSeries server and drag and drop the SAVF between them.

JSellick,

Both of my systems are at V5R4 and I frequently use all of the SAVRST commands in both directions.

Hope this helps,
Bill Poulin

iSeries Navagator is a great tool to just drap and drop files from one system to another… no need to worry about having perfect syntax!

We are at a lower release level also and I just did this from one AS/400 to another and it worked properly.
ftp xxx.xx.xxx
userid
password
binary
put qgpl/filename

If your other AS/400 is at a lower release level than the sending AS/400 you will have to create the save file using a lower relase level or you will not be able to display it on the other AS/400.

If you create the savf in QGPL on your other AS/400 this shoudl work properly. If the save file does not exist on the other AS/400 it will not create it as a save file.

From your pc

ftp rmtsys
quote site namefmt 1
cd /qsys.lib/savflib.lib
Lcd C:mysavfdir
Bin
mput *.savf

Directories given are examples substitute your own using same syntax.
No need to create the save file on target in namefmt 1 .savf extension defines file type as SAVF

Great when you need to push a file or a bunch of small files out to many machines at once. Can even create a small batch program if you’re clever.

I also utilize various FTP clients Filezilla seems to work fine for me but I can get almost any client to work with little effort. You have to make sure the FTP server is configured correct to communicate properly with FTP Clients by setting the File listing format to Unix list format which can be found in OPS NAV –> Network –> TCP/IP–>servers–> Right click FTP server selecting Properties from the drop down menu then Initial Formats tab. For Small files this can be handy to move files from server to server quickly with out using a command line. Also excellent method to provide FTP to those unfamiliar with the System i.

For Large Transfers I prefer to create a CL program which I can then submit or schedule to be submitted and an appropriate time. Login and Command Data is read from and input file and results are list to an output file which I can check after job completion to ensure that their where no errors. Most commonly used when grabbing images files such as PTF’s.