× 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.



I've always created the save file on the target system first. I've never tried it, but I hear tell that if you use namefmt 1, the system will know it needs to create a save file for you because you'll specify the name as <savefilename>.savf. If you want to play with namefmt 1, the commands you need will be something like this:

quote site namefmt 1
cd /qsys.lib/qgpl
bin
put imsave/source.savf

At 21:57 8/20/2004, you wrote:
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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Pete Hall
http://www.pbhall.us



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.