× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yes, if you use NAMEFMT 0 (library naming). As someone else said, if you use the .savf extension, it will create an actual SAVF for you.

In James' case, he's probably using name format 0, so this statement

    put jimsave/source.savf

puts the file into the present working directory (PWD) on the 400, which seems to have been QGPL. And it will use the name after the slash as the default name. Now in namefmt 0, the text after the period means a member. His physical file QGPL/QOURCE probably had member SAVF.

To have the FTP server create the SAVF for you, one must use name format 1, which makes the above statement into

   put   jimsave/source   /qsys.lib/jimsave.lib/source.savf

This assumes that library JIMSAVE exists on the remote machine. It also is using name format 0 on the client. To force name format 1 on the remote machine (the server), execute this subcommand on the client:

   quote site nam 1

BTW, (replace is not valid for a PUT from an iSeries client, only for GET. PUT always replaces a file at the destination of the same type.

All this is documented in the help for PUT in the 400 client. Execute

    ? put

on the FTP command line, then look for the "Default names" link.

Another thing - strtcpsvr *ftp is not needed on the client, because you are using the client, not the server. It does need to be run on the destination machine (the 9406).

So a script that should work might be

ftp
username
password
bin
quote site nam 1
put jimsave/source /qsys.lib/jimsave.lib/source.savf
quit

HTH
Vern

At 01:08 PM 8/21/2004, you wrote:
You must create the target save file first, or, from within ftp, you can do:

    quote rcmd crtsavf tgtlib/tgtsavf

and then (in binary mode)

    put srclib/srcsavf.srcsavf tgtlib/tgtsavf.tgtsavf (replace

Hope that helps!

----- Original Message -----
From: "James R. Newman, CDP" <newman400@xxxxxxxxxxx>
To: "Midrange L" <MIDRANGE-L@xxxxxxxxxxxx>
Sent: Friday, August 20, 2004 8:57 PM
Subject: RSTLIB and *SAVF


I'm using FTP for the first time to move libraries from a 9402 to a 9406. I saved a library to a savfile called SOURCE in library JIMSAVE. Here's what I do on the 9402 to send the file:

strtcpsvr *ftp
ftp
username
password
bin
put jimsave/source.savf

I've also tried this:

put jimsave/source.source


The file goes over into QGPL and the attribute gets changed to PF-DTA. Then when I try to do a RSTLIB I get a message saying "File SOURCE in QGPL not a save file". This is probably something really simple that I'm omitting. TIA.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.