135 lines
9.6 KiB
HTML
135 lines
9.6 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="iSeries server and System/36 DDM differences" />
|
||
|
|
<meta name="abstract" content="This topic consists of a list of differences between the iSeries server and System/36." />
|
||
|
|
<meta name="description" content="This topic consists of a list of differences between the iSeries server and System/36." />
|
||
|
|
<meta name="DC.subject" content="differences, between, server, iSeries, System/36, system, to, differences to" />
|
||
|
|
<meta name="keywords" content="differences, between, server, iSeries, System/36, system, to, differences to" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5dif.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5namecon.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzahg/rzahgupgrademigration.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="rbae5differences36" />
|
||
|
|
<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>iSeries server and System/36 DDM differences</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5differences36"><a name="rbae5differences36"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1"><span class="keyword">iSeries server</span> and <span class="keyword">System/36</span> DDM differences</h1>
|
||
|
|
<div><p>This topic consists of a list of differences between the <span class="keyword">iSeries™ server</span> and <span class="keyword">System/36™</span>.</p>
|
||
|
|
<div class="section"> <ul><li>The network resource directory (NRD) procedures are not supported on the <span class="keyword">iSeries server</span>. <ul><li>The <span class="keyword">System/36</span> NRD used one
|
||
|
|
or more libraries containing DDM files on the <span class="keyword">iSeries server</span>.
|
||
|
|
One <span class="keyword">System/36</span> NRD entry is equivalent
|
||
|
|
to one DDM file on the <span class="keyword">iSeries server</span>.
|
||
|
|
<ul><li>Use the <span class="cmdname">Work with DDM Files (WRKDDMF)</span> command in place
|
||
|
|
of the EDITNRD and DELNRD procedures.</li>
|
||
|
|
<li>Use the <span class="cmdname">Display DDM Files (DSPDDMF)</span> command in place
|
||
|
|
of the LISTNRD procedure.</li>
|
||
|
|
<li>Use the<span class="cmdname"> Restore Object (RSTOBJ)</span> command in place of
|
||
|
|
the RESTNRD procedure.</li>
|
||
|
|
<li>Use the <span class="cmdname">Save Object (SAVOBJ)</span> command in place of the
|
||
|
|
SAVNRD procedure.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>If an NRD entry on the <span class="keyword">System/36</span> refers
|
||
|
|
to a remote file, and a SAVE or RESTORE procedure is requested, the <span class="keyword">System/36</span> saves or restores the data
|
||
|
|
of the remote file. The <span class="keyword">iSeries</span> <span class="cmdname">Save
|
||
|
|
Object (SAVOBJ)</span> or <span class="cmdname">Restore Object (RSTOBJ)</span> command
|
||
|
|
saves or restores only the definition of the DDM file, not the remote data.</li>
|
||
|
|
<li>When using date-differentiated files on the <span class="keyword">System/36</span>,
|
||
|
|
the most current file is selected. When running from a <span class="keyword">System/36</span> to
|
||
|
|
an <span class="keyword">iSeries server</span>, the NRD entry
|
||
|
|
must specify a member name of *LAST to access the last member of the database
|
||
|
|
file, which is the file with the most recent date. If no member name is specified,
|
||
|
|
*FIRST is used.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>The remote label in the NRD on a <span class="keyword">System/36</span> source
|
||
|
|
must be in the syntax required by the target server. </li>
|
||
|
|
<li>The number of records allocated for a file differs between the <span class="keyword">System/36</span> and the <span class="keyword">iSeries server</span>.
|
||
|
|
File space allocation on the <span class="keyword">System/36</span> is
|
||
|
|
in block units (2560 bytes) while on the <span class="keyword">iSeries server</span>,
|
||
|
|
file space allocation is by number of records. For example, if a user asks
|
||
|
|
for a sequential file capable of storing ten 100-byte records, the <span class="keyword">System/36</span> allocates 1 block of file space
|
||
|
|
(2560 bytes), and uses as much of the file space as possible (2500 bytes),
|
||
|
|
giving the user twenty-five 100-byte records. <p>The <span class="keyword">iSeries server</span> allocates
|
||
|
|
exactly 10 records. If the user took advantage of this allocation method on
|
||
|
|
the <span class="keyword">System/36</span>, the file (nonextendable)
|
||
|
|
created using DDM on the <span class="keyword">iSeries server</span> might
|
||
|
|
be too small.</p>
|
||
|
|
</li>
|
||
|
|
<li>The DDM <span class="cmdname">Change End-of-File (CHGEOF)</span> command used on
|
||
|
|
the <span class="keyword">System/36</span> is not supported
|
||
|
|
on the <span class="keyword">iSeries server</span>.</li>
|
||
|
|
<li>The <span class="keyword">iSeries server</span> does not support
|
||
|
|
writing over data on the <span class="cmdname">Delete File (DLTF)</span> command. If
|
||
|
|
an <span class="keyword">iSeries</span> user accessing a <span class="keyword">System/36</span> wants to overwrite the data,
|
||
|
|
an application program must be written on the <span class="keyword">iSeries server</span>,
|
||
|
|
or the user must access the target <span class="keyword">System/36</span> and
|
||
|
|
perform the delete operation with the erase operation.</li>
|
||
|
|
<li>A <span class="keyword">System/36</span> source server
|
||
|
|
cannot create direct files on an <span class="keyword">iSeries</span> target
|
||
|
|
server that are nondelete-capable. The <span class="keyword">iSeries server</span> does
|
||
|
|
not support files that are nondelete-capable for all file organizations.</li>
|
||
|
|
<li>The <span class="keyword">System/36</span> does not allow
|
||
|
|
a record with hex FF in the first byte to be inserted into a delete-capable
|
||
|
|
file. The <span class="keyword">iSeries server</span> allows this.</li>
|
||
|
|
<li>When running <span class="keyword">System/36</span> applications
|
||
|
|
to another <span class="keyword">System/36</span>, the application
|
||
|
|
waits indefinitely for the resource to become available. When running <span class="keyword">System/36</span> applications to or from an <span class="keyword">iSeries server</span>, these applications might result
|
||
|
|
in time-outs while waiting for a resource to become available.</li>
|
||
|
|
<li>Direct files are extendable on the <span class="keyword">System/36</span> but
|
||
|
|
not on the <span class="keyword">iSeries server</span>. If a direct
|
||
|
|
file is created on the <span class="keyword">iSeries server</span> as
|
||
|
|
extendable, the file is allocated with three extents, but is never extended
|
||
|
|
beyond the initial size plus three extents.</li>
|
||
|
|
<li>The <span class="keyword">System/36</span> relay function
|
||
|
|
is <em>not</em> supported whenever one of the servers in the network along the
|
||
|
|
path from the source server to the target server is not a <span class="keyword">System/36</span>.
|
||
|
|
The <span class="keyword">iSeries server</span> <em>never</em> supports
|
||
|
|
the relay function; Advanced Peer-to-Peer Networking (APPN) must be used.</li>
|
||
|
|
<li>Key fields on the <span class="keyword">System/36</span> are
|
||
|
|
considered to be strictly character fields. The <span class="keyword">System/36</span> does
|
||
|
|
not recognize a key field as being packed or zoned. Unexpected results might
|
||
|
|
occur if source <span class="keyword">iSeries</span> application
|
||
|
|
programs refer to packed fields within a <span class="keyword">System/36</span> file.
|
||
|
|
Because of the way packed numbers are stored and the fact that the <span class="keyword">System/36</span> does not recognize key fields
|
||
|
|
as packed on relative keyed operations, records might be returned in a different
|
||
|
|
order than expected or no record might be found when one is expected. <p>As
|
||
|
|
an example, the ILE RPG SETLL statement might fail unexpectedly with record
|
||
|
|
not found or might select a record other than the record expected when using
|
||
|
|
packed fields to a <span class="keyword">System/36</span> file.
|
||
|
|
Only character and unsigned numeric fields should be used as key fields.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5dif.htm" title="This topic describes the DDM differences between iSeries server and System/36, and iSeries server and System/38.">Use DDM on the iSeries server versus other IBM systems</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rzahg/rzahgupgrademigration.htm">Migration</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbae5namecon.htm" title="The rules for specifying the name of a DDM file (on the local iSeries server) are the same as for any other file type on an iSeries server. The rules, however, for specifying the name of a remote file depend on the type of target server.">Rules for specifying target server file names for DDM</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|