122 lines
8.3 KiB
HTML
122 lines
8.3 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="task" />
|
||
|
|
<meta name="DC.Title" content="Move files or folders to another file system" />
|
||
|
|
<meta name="abstract" content="Each file system has its own unique characteristics. However, moving objects to a different file system might mean losing the advantages of the file system in which the objects are currently stored. You might want to move objects from one file system to another to take advantage of those characteristics." />
|
||
|
|
<meta name="description" content="Each file system has its own unique characteristics. However, moving objects to a different file system might mean losing the advantages of the file system in which the objects are currently stored. You might want to move objects from one file system to another to take advantage of those characteristics." />
|
||
|
|
<meta name="DC.subject" content="file system, migrating objects, migration across file systems, object, migrating across file systems" />
|
||
|
|
<meta name="keywords" content="file system, migrating objects, migration across file systems, object, migrating across file systems" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxworkfiles.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxfsknow.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxfscmp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/crtdir.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/mov.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/copy.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaaxmovingobjects" />
|
||
|
|
<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>Move files or folders to another file system</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaaxmovingobjects"><a name="rzaaxmovingobjects"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Move files or folders to another file system</h1>
|
||
|
|
<div><p><span>Each file system has its own unique characteristics.
|
||
|
|
However, moving objects to a different file system might mean losing the advantages
|
||
|
|
of the file system in which the objects are currently stored. You might want
|
||
|
|
to move objects from one file system to another to take advantage of those
|
||
|
|
characteristics. </span></p>
|
||
|
|
<div class="section"> <p>Before moving objects to another file system, you should be familiar
|
||
|
|
with the file systems on the integrated file system and their characteristics.</p>
|
||
|
|
<p>You should also consider the following situation: </p>
|
||
|
|
<ul><li>Are you using applications that use advantages of the file system that
|
||
|
|
the objects are currently in? <p>Some file systems support interfaces that
|
||
|
|
are not part of the integrated file system support. Applications that use
|
||
|
|
these interfaces may no longer be able to access objects that are moved to
|
||
|
|
another file system. <span>For example, the QDLS and
|
||
|
|
QOPT file systems support the hierarchical file system (HFS) APIs and commands
|
||
|
|
to work with document and folder objects.</span> You cannot use these interfaces
|
||
|
|
on objects that are in other file systems.</p>
|
||
|
|
</li>
|
||
|
|
<li>What characteristics of the objects are important to you? <p>Not all
|
||
|
|
characteristics are supported by all file systems. For example, the QSYS.LIB
|
||
|
|
or independent ASP QSYS.LIB file systems support storing and retrieving only
|
||
|
|
a few extended attributes, whereas the <span class="q">"root"</span> (/) and QOpenSys file systems
|
||
|
|
support storing and retrieving all extended attributes. Therefore QSYS.LIB
|
||
|
|
and independent ASP QSYS.LIB are not good candidates for storing objects that
|
||
|
|
have extended attributes.</p>
|
||
|
|
<p>Good candidates for moving are the PC files
|
||
|
|
that are in stored in QDLS. Most PC applications should be able to continue
|
||
|
|
working with PC files that are moved from QDLS to other file systems. The
|
||
|
|
"root" (/), QOpenSys, QNetWare, and QNTC file systems are good choices for
|
||
|
|
storing these PC files. Because they support many of the OS/2<sup>®</sup> file system
|
||
|
|
characteristics, these file systems can provide faster access to files. </p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>To move objects to another file system, perform the following steps:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span>Save a copy of all objects that you are planning to move.</span> <p>Having a backup copy allows you to restore the objects to the original
|
||
|
|
file system if you find that applications cannot access the objects in the
|
||
|
|
file system to which you have moved them.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> You cannot save objects
|
||
|
|
from one file system and restore them to another.</div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Create the directories in the file system that you want to move
|
||
|
|
the objects to using the <span class="cmdname">Create Directory (CRTDIR)</span> command. </span> <p>You should carefully examine the attributes of the directory the
|
||
|
|
objects are currently in to determine if you want to duplicate those attributes
|
||
|
|
on the directories you create. For example, the user who creates the directory
|
||
|
|
is its owner, rather than the user who owned the old directory. You may want
|
||
|
|
to transfer ownership of the directory after you have created it, if the file
|
||
|
|
system supports setting the owner of a directory.</p>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Move the files to the file system that you have chosen using the <span class="cmdname">Move
|
||
|
|
(MOV)</span> command.</span> <p><span class="cmdname">MOV</span> is recommended
|
||
|
|
because it preserves the ownership of the objects, if the file system supports
|
||
|
|
setting the ownership of objects. You can, however, use the <span class="cmdname">Copy
|
||
|
|
(CPY)</span> command to preserve the ownership of the objects by using
|
||
|
|
the OWNER(*KEEP) parameter. Keep in mind that this only works for file systems
|
||
|
|
that support setting the owner of an object. Note that when using <span class="cmdname">MOV</span> or <span class="cmdname">CPY</span>:
|
||
|
|
</p>
|
||
|
|
<ul><li>Attributes may not match and may be discarded.</li>
|
||
|
|
<li>Extended attributes may be discarded.</li>
|
||
|
|
<li>Authorities may not be equivalent and may be discarded.</li>
|
||
|
|
</ul>
|
||
|
|
<p>This means that if you decide to return the object to its original
|
||
|
|
file system, you may not want to just move or copy it back because of the
|
||
|
|
attributes and authorities that have been discarded. The safest way to return
|
||
|
|
an object is to restore a saved version of it.</p>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxworkfiles.htm" title="You can perform these tasks with files and folders.">Work with files and folders using iSeries Navigator</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaaxfsknow.htm" title="A file system provides you the support to access specific segments of storage that are organized as logical units. These logical units on your server are files, directories, libraries, and objects.">Work with file systems</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzaaxfscmp.htm" title="These tables summarize the features and limitations of each file system.">File system comparison</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../cl/crtdir.htm">Create Directory (CRTDIR) command</a></div>
|
||
|
|
<div><a href="../cl/mov.htm">Move (MOV) command</a></div>
|
||
|
|
<div><a href="../cl/copy.htm">Copy (CPY) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|