70 lines
4.4 KiB
HTML
70 lines
4.4 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="Usage notes: Reorganize a file" />
|
||
|
|
<meta name="abstract" content="Here is a list of considerations for reorganizing a file." />
|
||
|
|
<meta name="description" content="Here is a list of considerations for reorganizing a file." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafomngprgz.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbaforrgpfu" />
|
||
|
|
<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>Usage notes: Reorganize a file</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbaforrgpfu"><a name="rbaforrgpfu"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Usage notes: Reorganize a file</h1>
|
||
|
|
<div><p>Here is a list of considerations for reorganizing a file.</p>
|
||
|
|
<div class="section"> <ol><li>If a file with an arrival sequence access path is reorganized using a
|
||
|
|
keyed sequence access path, the arrival sequence access path is changed. That
|
||
|
|
is, the records in the file are physically placed in the order of the keyed
|
||
|
|
sequence access path used. By reorganizing the data into a physical sequence
|
||
|
|
that closely matches the keyed access path you are using, you can improve
|
||
|
|
the performance of processing the data sequentially.</li>
|
||
|
|
<li>Reorganizing a file compresses deleted records, which changes subsequent
|
||
|
|
relative record numbers.</li>
|
||
|
|
<li>Because access paths with either the first-changed-first-out (FCFO), first-in-first-out
|
||
|
|
(FIFO), or last-in-first-out (LIFO) DDS keyword specified depend on the physical
|
||
|
|
sequence of records in the physical file, the sequence of the records with
|
||
|
|
duplicate key fields might change after reorganizing a physical file using
|
||
|
|
a keyed sequence access path. The sequence of the records with duplicate key
|
||
|
|
fields are maintained only for the access path specified in the KEYFILE parameter.
|
||
|
|
If the access path specified in the KEYFILE parameter has a LIFO DDS keyword,
|
||
|
|
the duplicate key fields are maintained only if you specify that the reorganize
|
||
|
|
operation can be canceled (suspended).</li>
|
||
|
|
<li>If you specify that the reorganize operation cannot be canceled and you
|
||
|
|
end the job running the Reorganize Physical File Member (RGZPFM) command,
|
||
|
|
all the access paths over the physical file member might have to be rebuilt.
|
||
|
|
If you specify that the reorganize operation can be canceled, and you cancel
|
||
|
|
the RGZPFM command, only those access paths that are not maintained during
|
||
|
|
the reorganize operation might have to be rebuilt.</li>
|
||
|
|
<li>If you use the RGZPFM command twice in a row, you might notice that the
|
||
|
|
total size of the file after the first time differs from the total size after
|
||
|
|
the second. This is because the amount of space allocated for the reorganized
|
||
|
|
file is only an estimate that allows extra space for future insertion.
|
||
|
|
After records are reorganized the first time, the space allocated is calculated
|
||
|
|
exactly.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafomngprgz.htm" title="These topics describe how to reorganize physical files on the i5/OS operating system, how to suspend or cancel reorganize operations and what type of reorganize operations you can choose. Considerations for reorganizing physical files are also included.">Reorganize a physical file</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|