78 lines
6.0 KiB
HTML
78 lines
6.0 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="Initialize data in a physical file member" />
|
||
|
|
<meta name="abstract" content="To use relative record processing in a program, the database file must contain a number of record positions equal to the highest relative record number used in the program. Programs using relative-record-number processing sometimes require that these records be initialized." />
|
||
|
|
<meta name="description" content="To use relative record processing in a program, the database file must contain a number of record positions equal to the highest relative record number used in the program. Programs using relative-record-number processing sometimes require that these records be initialized." />
|
||
|
|
<meta name="DC.subject" content="initializing, data in a physical file member, data, initializing in a physical file member, Initialize Physical File Member (INZPFM) command, INZPFM (Initialize Physical File Member) command, command, CL, INZPFM (Initialize Physical File Member), Initialize Physical File Member (INZPFM), RECORDS parameter, parameter, RECORDS, physical file member, changing, initializing data" />
|
||
|
|
<meta name="keywords" content="initializing, data in a physical file member, data, initializing in a physical file member, Initialize Physical File Member (INZPFM) command, INZPFM (Initialize Physical File Member) command, command, CL, INZPFM (Initialize Physical File Member), Initialize Physical File Member (INZPFM), RECORDS parameter, parameter, RECORDS, physical file member, changing, initializing data" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafomngpfm.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/inzpfm.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafodldbr.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="rbafomngpinz" />
|
||
|
|
<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>Initialize data in a physical file member</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafomngpinz"><a name="rbafomngpinz"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Initialize data in a physical file member</h1>
|
||
|
|
<div><p>To use relative record processing in a program, the database file
|
||
|
|
must contain a number of record positions equal to the highest relative record
|
||
|
|
number used in the program. Programs using relative-record-number processing
|
||
|
|
sometimes require that these records be initialized.</p>
|
||
|
|
<div class="p">You can use the Initialize Physical File Member (INZPFM) command to initialize
|
||
|
|
members with one of two types of records: <ul><li>Default records</li>
|
||
|
|
<li>Deleted records</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>You specify which type of record you want using the RECORDS parameter on
|
||
|
|
the INZPFM command.</p>
|
||
|
|
<p>If you initialize records using default records, the fields in each new
|
||
|
|
record are initialized to the default field values defined when the file was
|
||
|
|
created. If no default field value was defined, then numeric fields are filled
|
||
|
|
with zeros and character fields are filled with blanks.</p>
|
||
|
|
<div class="p">Variable-length character fields have a zero-length default value. The
|
||
|
|
default value for null-capable fields is the null value. The default value
|
||
|
|
for dates, times, and timestamps is the current date, time, or timestamp if
|
||
|
|
no default value is defined. Program-described files have a default value
|
||
|
|
of all blanks. <div class="note"><span class="notetitle">Note:</span> You can initialize one default record if the UNIQUE keyword
|
||
|
|
is specified in DDS for the physical file member or any associated logical
|
||
|
|
file members. Otherwise, you would create a series of duplicate key records.</div>
|
||
|
|
</div>
|
||
|
|
<p>If the records are initialized to the default records, you can read a record
|
||
|
|
by relative record number and change the data.</p>
|
||
|
|
<p>If the records are initialized to deleted records, you can change the data
|
||
|
|
by adding a record using a relative record number of one of the deleted records.
|
||
|
|
(You cannot add a record using a relative record number that was not deleted.)</p>
|
||
|
|
<p>Deleted records cannot be read; they only hold a place in the member. A
|
||
|
|
deleted record can be changed by writing a new record over the deleted record. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafomngpfm.htm" title="These topics describe the member operations that are unique to physical file members. If the physical file members being operated on are associated with referential constraints, the operations might be affected.">Physical file member operations</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbafodldbr.htm" title="The delete operation allows you to delete an existing database record.">Delete database records</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/inzpfm.htm">Initialize Physical File Member (INZPFM) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|