105 lines
6.8 KiB
HTML
105 lines
6.8 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="Transfer *SAVF files" />
|
||
|
|
<meta name="abstract" content="Because *SAVF files must be sent as images, you must issue FTP BINARY subcommand before transferring these types of files." />
|
||
|
|
<meta name="description" content="Because *SAVF files must be sent as images, you must issue FTP BINARY subcommand before transferring these types of files." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqfrmt.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaiqreferencedt2" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Transfer *SAVF files</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiqreferencedt2"><a name="rzaiqreferencedt2"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Transfer *SAVF files</h1>
|
||
|
|
<div><p>Because *SAVF files must be sent as images, you must issue FTP
|
||
|
|
BINARY subcommand before transferring these types of files.</p>
|
||
|
|
<div class="section"><p>When transferring a *SAVF file using name format 0, the save file
|
||
|
|
on the receiving system must be pre-created. It is recommended that files
|
||
|
|
are pre-created in other situations as well for reasons of performance and
|
||
|
|
integrity.</p>
|
||
|
|
<p>The transfer of a save file--because it is a file format
|
||
|
|
peculiar to iSeries--can only be made usable if the sending and receiving
|
||
|
|
servers are both iSeries™ servers.
|
||
|
|
However, a save file can be sent to a non-iSeries server and stored there
|
||
|
|
for backup purposes. The save file can be transferred later to the iSeries with
|
||
|
|
FTP.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Example: Transferring a *SAVF file from VM to an iSeries</h4><p>The
|
||
|
|
following example shows how to transfer a *SAVF file from VM to an iSeries for
|
||
|
|
both NAMEFMT 0 and 1. The FTP session has already been initiated, the BINARY
|
||
|
|
subcommand has been issued, and NAMEFMT 0 has been specified.</p>
|
||
|
|
<p>First,
|
||
|
|
transfer the file P162484 SAVF310L from the VM A disk to the iSeries. VM
|
||
|
|
FTP requires that you insert a period between its file name and file type.
|
||
|
|
Give it the file name P162484 in library P162484 on the iSeries, and
|
||
|
|
specify REPLACE as it has been pre-created even if it has not been used before.
|
||
|
|
You will recall that pre-creation is mandatory with NAMEFMT 0.</p>
|
||
|
|
<div class="p">Change
|
||
|
|
the NAMEFMT to 1, and repeat the file transfer using the new name format.
|
||
|
|
Once again, specify REPLACE, because the file exists from the previous step.<div class="note"><span class="notetitle">Notes:</span> <ul><li>If you had not pre-created the file on the iSeries before performing the transfer
|
||
|
|
with NAMEFMT 0, the transfer would have appeared to have completed satisfactorily.
|
||
|
|
However, on inspection of the file on the iSeries, it would be seen that a physical
|
||
|
|
file (*PF) has been created and not a save file (*SAVF).</li>
|
||
|
|
<li>Some preprocessing might be necessary on the VM system depending on how
|
||
|
|
the *SAVF file was sent to VM: <ul><li>If FTP was used to send the *SAVF file to VM, you can just issue a GET
|
||
|
|
subcommand to transfer it back to the iSeries.</li>
|
||
|
|
<li>If the Send Network File (SNDNETF) command was used to send the *SAVF
|
||
|
|
file to VM, it is first necessary to convert the file on the VM system from
|
||
|
|
a record format (RECFM) of variable to a RECFM of fixed before using FTP to
|
||
|
|
transfer it back to the iSeries server. To do this, use the COPYFILE command
|
||
|
|
on VM. For example: <pre> COPYFILE P162484 SAVF310L A = = = (RECFM F REPLACE </pre>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="fignone" id="rzaiqreferencedt2__FIGSAVFVM"><a name="rzaiqreferencedt2__FIGSAVFVM"><!-- --></a><span class="figcap">Figure 1. Transferring a *SAVF from VM to iSeries using
|
||
|
|
NAMEFMT 0 and NAMEFMT 1</span><pre> ___________________________________________________________________________________
|
||
|
|
| |
|
||
|
|
| > GET P162484.SAVF310L P162484/P162484 (REPLACE |
|
||
|
|
| 200 Port request OK. |
|
||
|
|
| 150 Sending file 'P162484.SAVF310L' |
|
||
|
|
| 250 Transfer completed successfully. |
|
||
|
|
| 384912 bytes transferred in 3.625 seconds. Transfer rate106.183 KB/sec |
|
||
|
|
| |
|
||
|
|
| > namefmt 1 |
|
||
|
|
| 202 SITE not necessary; you may proceed |
|
||
|
|
| Client NAMEFMT is 1. |
|
||
|
|
| > GET P162484.SAVF310L/QSYS.LIB/P162484.LIB/P162484.savf(REPLACE |
|
||
|
|
| 200 Port request OK. |
|
||
|
|
| 150 Sending file 'P162484.SAVF310L' |
|
||
|
|
| 250 Transfer completed successfully. |
|
||
|
|
| 384912 bytes transferred in 3.569 seconds. Transfer rate107.839 KB/sec |
|
||
|
|
| Enter an FTP subcommand. |
|
||
|
|
| ===> |
|
||
|
|
| |
|
||
|
|
|__________________________________________________________________________________|
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiqfrmt.htm" title="Before you begin to transfer files, you must choose the appropriate file transfer type.">Data transfer methods</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|