89 lines
6.5 KiB
HTML
89 lines
6.5 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="DDM-related differences between iSeries and System/36 files" />
|
||
|
|
<meta name="abstract" content="Because of differences between the types of files supported by an iSeries server and a System/36, several items need to be considered when DDM is used between these two servers." />
|
||
|
|
<meta name="description" content="Because of differences between the types of files supported by an iSeries server and a System/36, several items need to be considered when DDM is used between these two servers." />
|
||
|
|
<meta name="DC.subject" content="system, iSeries, differences, to, System/36, DDM differences between systems, remote file processing, remote system, file processing differences, and, delete-capable files,, file, delete-capable, types, description, sequential file, sequential, direct, direct file (DIRFIL), on, indexed" />
|
||
|
|
<meta name="keywords" content="system, iSeries, differences, to, System/36, DDM differences between systems, remote file processing, remote system, file processing differences, and, delete-capable files,, file, delete-capable, types, description, sequential file, sequential, direct, direct file (DIRFIL), on, indexed" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5source36.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="rbae5diff36" />
|
||
|
|
<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>DDM-related differences between iSeries and System/36 files</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5diff36"><a name="rbae5diff36"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">DDM-related differences between <span class="keyword">iSeries</span> and <span class="keyword">System/36</span> files</h1>
|
||
|
|
<div><p>Because of differences between the types of files supported by
|
||
|
|
an <span class="keyword">iSeries™ server</span> and a <span class="keyword">System/36™</span>, several items need to be considered
|
||
|
|
when DDM is used between these two servers.</p>
|
||
|
|
<div class="section"><p> Generally, when a <span class="keyword">System/36</span> file
|
||
|
|
is created locally (by the BLDFILE utility, for example), the <span class="keyword">System/36</span> user
|
||
|
|
specifies such things as the type of file (S = sequential, D = direct, or
|
||
|
|
I = indexed), whether records or blocks are to be allocated, how many of them
|
||
|
|
are to be allocated, and how many additional times this amount can be added
|
||
|
|
to the file to extend it.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p> Also, you can specify whether the file is to be <em>delete-capable</em> (DFILE)
|
||
|
|
or not (NDFILE). In files specified as <em>not delete-capable</em>, records
|
||
|
|
can be added or changed in the file, but not deleted.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p> Once these attributes have been specified, <span class="keyword">System/36</span> then
|
||
|
|
creates the file and fills it with the appropriate hexadecimal characters.
|
||
|
|
If a <span class="keyword">System/36</span> user specifies
|
||
|
|
the file as:</p>
|
||
|
|
<ul><li> A <em>sequential</em> file, the entire file space is filled with hex 00
|
||
|
|
characters and the end-of-file (EOF) pointer is set to the beginning of the
|
||
|
|
initial extent. If you attempt to read an empty sequential file, an EOF condition
|
||
|
|
is received.</li>
|
||
|
|
<li>A <em>direct</em> file that is <em>delete-capable</em>, the entire file space
|
||
|
|
is filled with hex FF characters (deleted records) and the EOF pointer is
|
||
|
|
set to the end of the initial extent. If you attempt to read an empty direct
|
||
|
|
file that is delete-capable, a record-not-found condition is received.</li>
|
||
|
|
<li>A <em>direct</em> file that is <em>not delete-capable</em>, the entire file
|
||
|
|
space is filled with hex 40 characters (blank or null records) and the EOF
|
||
|
|
pointer is set to the end of the initial extent. If you attempt to read an
|
||
|
|
empty direct file that is not delete-capable, a blank record is returned for
|
||
|
|
every record in the file until the end of the file is reached.</li>
|
||
|
|
<li> An <em>indexed</em> file, it is prepared in the same manner as sequential
|
||
|
|
files.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Typically, once a delete-capable file has been in use, it contains
|
||
|
|
a relatively continuous set of active records with only a few deleted records,
|
||
|
|
possibly an end of data marker, and then a continuous set of deleted records
|
||
|
|
to the end of the file (EOF) space. This means that, unless the file is reorganized,
|
||
|
|
a user can <em>un</em>delete (recover) a deleted record.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Of the three types of <span class="keyword">System/36</span> files, <span class="keyword">System/36</span> indexed files differ little
|
||
|
|
from <span class="keyword">iSeries</span>-supported logical
|
||
|
|
files. If an <span class="keyword">iSeries</span> source
|
||
|
|
program is to use DDM to access the other types of files on a <span class="keyword">System/36</span>,
|
||
|
|
the <span class="keyword">iSeries</span> application programmer
|
||
|
|
should first consider the items remaining in this topic selection that
|
||
|
|
relate to <span class="keyword">System/36</span>.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5source36.htm" title="Before an iSeries server can access files on a System/36, Level 1.0 of the DDM architecture must be installed on the System/36. These topics contain information that applies when an iSeries server is the source or target server communicating with a System/36.">System/36 source and target considerations for DDM</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|