Re: FTP scritp.. PUT vs GET for SAVF

We are confusing an object type with an object attribute.  
.savf does not exist.  .file does.  
A SAVF is a file object first, it has an attribute of savf.  
So, therefore, the object name would be /qsys.lib/locallib.lib/savefile.file
You must create the remote save file first.




melrothman@home.com on 09/03/99 06:12:14 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re: FTP scritp.. PUT vs GET for SAVF

After setting NAMEFMT to 1, change BOTH the local and remote directories
using IFS syntax.  For example (comments in parentheses):

bin (binary mode)           
cd /qsys.lib/remotelib.lib (change remote current directory)
lcd /qsys.lib/locallib.lib (change local current directory)
get remote.savf local.savf 
  (get savefile named remote; create & save into savefile named local)

Mel Rothman

Tony Haines wrote:
> 
> I'm attempting to GET a *savf from another as/400.  While I understand by
> setting the NAMEFMT = 1, I can have the savf created for me upon transfer.
> This obviously only works for the PUT.   Using a GET .../file.savf still
> creates a PF on the local system and not a SAVF.
> 
> Is there a workaround that I can use so that I don't have to CRTSAVF on my
> local system before I GET the savf?
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---