ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddm_5.4.0.1/rbae5varlength.htm

72 lines
5.1 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="Variable-length records" />
<meta name="abstract" content="If your iSeries source server is running OS/400 Version 2 Release 1 Modification 1, DDM supports variable-length record files as defined in the DDM architecture." />
<meta name="description" content="If your iSeries source server is running OS/400 Version 2 Release 1 Modification 1, DDM supports variable-length record files as defined in the DDM architecture." />
<meta name="DC.subject" content="variable-length records, record processing, system, iSeries, variable-length records" />
<meta name="keywords" content="variable-length records, record processing, system, iSeries, variable-length records" />
<meta name="DC.Relation" scheme="URI" content="rbae5amc.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5ddmcom.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="rbae5varlength" />
<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>Variable-length records</title>
</head>
<body id="rbae5varlength"><a name="rbae5varlength"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Variable-length records</h1>
<div><p>If your <span class="keyword">iSeries™</span> source
server is running OS/400<sup>®</sup> Version 2 Release 1 Modification 1, DDM supports
variable-length record files as defined in the DDM architecture.</p>
<div class="section"><p>You can use DDM on your <span class="keyword">iSeries server</span> to
open variable-length record files on target systems that are not <span class="keyword">iSeries</span> or S/38 servers. (Initially
you can open variable-length record files if you are not opening the file
for updating.) For subsequent read operations, variable-length records are
padded with blanks to the maximum record length of the file. Trailing blanks
are removed on write operations.</p>
</div>
<div class="section"><p>If your <span class="keyword">iSeries</span> source
server is running OS/400 Version 2 Release 2 in addition to the Version
2 Release 1 Modification 1 support mentioned earlier, <span class="keyword">iSeries</span> variable-length
record access is supported using DDM. Variable-length records can be used
when opening a variable-length record file on target servers that are not <span class="keyword">iSeries</span> or <span class="keyword">System/38™</span> servers.
For subsequent read operations against files opened with variable-length records,
variable-length records are padded with blanks to the maximum record length
of the file. Also, the actual record length (maximum record length of file
minus the number of padded blanks) is appended to the end of each record.
For write operations, the actual record length is used to determine the length
of the variable-length record to send to the target server. No counting of
trailing blanks is necessary to determine the actual length of record data.</p>
</div>
<div class="section"><p>The target DDM <span class="keyword">iSeries server</span>s
running at Version 2 Release 2 also support variable-length record files.
A variable-length record file can be created on the <span class="keyword">iSeries</span> target
server as a result of a create file request.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5amc.htm" title="Access methods control what subsets of functions can be performed after a particular remote file is opened. This might mean that an iSeries program, or a group of programs sharing a non-iSeries file, cannot do all the same operations that are possible using a file that is on the local iSeries server.">Work with access methods for DDM</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rbae5ddmcom.htm" title="This topic classifies DDM commands and parameters.">DDM commands and parameters</a></div>
</div>
</div>
</body>
</html>