85 lines
6.3 KiB
HTML
85 lines
6.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="concept" />
|
||
|
|
<meta name="DC.Title" content="Deleted records" />
|
||
|
|
<meta name="abstract" content="The DLTPCT parameter specifies the percentage of deleted records a file can contain before you want the system to send a message to the system history log (CRTPF, CHGPF, CRTSRCPF, and CHGSRCPF commands)." />
|
||
|
|
<meta name="description" content="The DLTPCT parameter specifies the percentage of deleted records a file can contain before you want the system to send a message to the system history log (CRTPF, CHGPF, CRTSRCPF, and CHGSRCPF commands)." />
|
||
|
|
<meta name="DC.subject" content="deleting, database record, record, DLTPCT (Deleted Percentage) parameter, Deleted Percentage (DLTPCT) parameter, parameter, DLTPCT (Deleted Percentage)" />
|
||
|
|
<meta name="keywords" content="deleting, database record, record, DLTPCT (Deleted Percentage) parameter, Deleted Percentage (DLTPCT) parameter, parameter, DLTPCT (Deleted Percentage)" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafophyfm.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafomngprgz.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbaforsdlt.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="rbafoadr" />
|
||
|
|
<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>Deleted records</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafoadr"><a name="rbafoadr"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Deleted records</h1>
|
||
|
|
<div><p>The DLTPCT parameter specifies the percentage of deleted records
|
||
|
|
a file can contain before you want the system to send a message to the system
|
||
|
|
history log (CRTPF, CHGPF, CRTSRCPF, and CHGSRCPF commands). </p>
|
||
|
|
<p>When a file is closed, the system checks the member to determine the percentage
|
||
|
|
of deleted records. If the percentage exceeds the value specified in the DLTPCT
|
||
|
|
parameter, a message is sent to the history log. (For information about processing
|
||
|
|
the history log, see the <a href="../rbam6/rbam6clmain.htm">Control language (CL) </a> topic. One reason
|
||
|
|
you might want to know when a file reaches a certain percentage of deleted
|
||
|
|
records is to reclaim the space used by the deleted records. After you receive
|
||
|
|
the message about deleted records, you can run the Reorganize Physical File
|
||
|
|
Member (RGZPFM) command to reclaim the space. You can also specify to bypass
|
||
|
|
the deleted records check by using the *NONE value for the DLTPCT parameter.
|
||
|
|
*NONE is the default for the DLTPCT parameter.</p>
|
||
|
|
<div class="p">REUSEDLT parameter specifies
|
||
|
|
whether deleted record space should be reused on subsequent write operations
|
||
|
|
(CRTPF and CHGPF commands). When you specify *YES for the REUSEDLT parameter,
|
||
|
|
all insert requests on that file try to reuse deleted record space. Reusing
|
||
|
|
deleted record space allows you to reclaim space used by deleted records without
|
||
|
|
having to issue a RGZPFM command. When the CHGPF command is used to change
|
||
|
|
a file to reuse deleted records, it might take a long time to run, especially
|
||
|
|
if the file is large and there are already a lot of deleted records in it.
|
||
|
|
It is important to note the following items: <ul><li>The term <em>arrival order</em> loses its meaning for a file that reuses
|
||
|
|
deleted record space. Records are no longer always inserted at the end of
|
||
|
|
the file when deleted record space is reused.</li>
|
||
|
|
<li>If a
|
||
|
|
new physical file is created with the reuse deleted record space attribute
|
||
|
|
and the file is keyed, the FIFO or LIFO access path attribute cannot be specified
|
||
|
|
for the physical file, nor can any keyed logical file with the FIFO or LIFO
|
||
|
|
access path attribute be built over the physical file. </li>
|
||
|
|
<li>You cannot change an existing physical file to reuse deleted record space
|
||
|
|
if there are any logical files over the physical file that specify FIFO or
|
||
|
|
LIFO ordering for duplicate keys, or if the physical file has a FIFO or LIFO
|
||
|
|
duplicate key ordering.</li>
|
||
|
|
<li>Reusing deleted record space should not be specified for a file that is
|
||
|
|
processed as a direct file or if the file is processed using relative record
|
||
|
|
numbers. </li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p></p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafophyfm.htm" title="This topic describes some of the attributes you can specify for physical files and members on the Create Physical File (CRTPF), Create Source Physical File (CRTSRCPF), Change Physical File (CHGPF), Change Source Physical File (CHGSRCPF), Add Physical File Member (ADDPFM), and Change Physical File Member (CHGPFM) commands.">Specify physical file and member attributes when creating a physical file</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><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><a href="rbaforsdlt.htm" title="Sometimes you might want to reuse deleted records for your database files. In this case, you can use the REUSEDLT parameter.">Reuse deleted records</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|