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

71 lines
5.4 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="System/36 source and target considerations for DDM" />
<meta name="abstract" content="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." />
<meta name="description" content="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." />
<meta name="DC.subject" content="target DDM (TDDM), System/36, considerations, TDDM (target DDM), system, AS/400, target, source DDM (SDDM), as source, SDDM (source DDM), as source, DDM source considerations, source and target considerations" />
<meta name="keywords" content="target DDM (TDDM), System/36, considerations, TDDM (target DDM), system, AS/400, target, source DDM (SDDM), as source, SDDM (source DDM), as source, DDM source considerations, source and target considerations" />
<meta name="DC.Relation" scheme="URI" content="rbae5ddmop.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5diff36.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5considerations36.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5considerations.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5ovr3836.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="rbae5source36" />
<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>System/36 source and
target considerations for DDM</title>
</head>
<body id="rbae5source36"><a name="rbae5source36"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1"><span class="keyword">System/36</span> source and
target considerations for DDM</h1>
<div><p>Before an <span class="keyword">iSeries™ server</span> can
access files on a <span class="keyword">System/36™</span>,
Level 1.0 of the DDM architecture must be installed on the <span class="keyword">System/36</span>. These topics contain information
that applies when an <span class="keyword">iSeries server</span> is
the source or target server communicating with a <span class="keyword">System/36</span>.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbae5diff36.htm">DDM-related differences between iSeries and System/36 files</a></strong><br />
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.</li>
<li class="ulchildlink"><strong><a href="rbae5considerations36.htm">System/36 source to iSeries target considerations for DDM</a></strong><br />
When <span class="keyword">System/36</span> is
using DDM to communicate as a source server to access files on an <span class="keyword">iSeries</span> target server, the information
in this topic applies and should be considered.</li>
<li class="ulchildlink"><strong><a href="rbae5considerations.htm">iSeries source to System/36 target considerations for DDM</a></strong><br />
When an <span class="keyword">iSeries server</span> is
using DDM to communicate as a source server to access files on a <span class="keyword">System/36</span> target server, the information
in this topic applies and should be considered.</li>
<li class="ulchildlink"><strong><a href="rbae5ovr3836.htm">Override considerations to System/36 for DDM</a></strong><br />
When a file override is issued on the <span class="keyword">iSeries server</span> to
get records in a logical file on a <span class="keyword">System/36</span>,
the results might be different than expected because of the difference in
how each system deals with keyed files.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5ddmop.htm" title="This topic provides task-oriented information and examples that describe various aspects of DDM operation considerations.">Operating considerations for DDM</a></div>
</div>
</div>
</body>
</html>