111 lines
8.9 KiB
HTML
111 lines
8.9 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="Operating considerations for DDM" />
|
||
|
|
<meta name="abstract" content="This topic provides task-oriented information and examples that describe various aspects of DDM operation considerations." />
|
||
|
|
<meta name="description" content="This topic provides task-oriented information and examples that describe various aspects of DDM operation considerations." />
|
||
|
|
<meta name="DC.subject" content="DDM operating considerations" />
|
||
|
|
<meta name="keywords" content="DDM operating considerations" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5kickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5fac.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5mbraccess.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5amc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5otherremote.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5mtserv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5end.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5perfcon.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5probana.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5source36.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5pcsource.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5clcon.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5advcncp.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="rbae5ddmop" />
|
||
|
|
<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>Operating considerations for DDM</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5ddmop"><a name="rbae5ddmop"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Operating considerations for DDM</h1>
|
||
|
|
<div><p>This topic provides task-oriented information and examples that
|
||
|
|
describe various aspects of DDM operation considerations.</p>
|
||
|
|
<p>This topic tells how the <span class="keyword">iSeries™ server</span> functions,
|
||
|
|
both as a source or target server, when it communicates with another <span class="keyword">iSeries server</span> to perform remote file processing.
|
||
|
|
It also describes the significant differences when an <span class="keyword">iSeries server</span> is
|
||
|
|
communicating with another server that is not an <span class="keyword">iSeries server</span>.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Although this topic contains information about servers other than the <span class="keyword">iSeries server</span>, it does not contain all the
|
||
|
|
information that the other server types using DDM might need
|
||
|
|
to communicate with an <span class="keyword">iSeries server</span>.
|
||
|
|
For complete information about how DDM is used with a particular remote server,
|
||
|
|
refer to that server's documentation.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5fac.htm">Access files with DDM</a></strong><br />
|
||
|
|
These topics describe the types of files supported by an <span class="keyword">iSeries server</span>, when the DDM file and remote
|
||
|
|
file must exist, and how to specify the names of remote files. Also included
|
||
|
|
are examples and considerations for <span class="keyword">iSeries</span>-to-<span class="keyword">iSeries</span> and <span class="keyword">iSeries</span>-to-<span class="keyword">System/36™</span> file accessing.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5mbraccess.htm">Access members with DDM</a></strong><br />
|
||
|
|
Members are supported for database I/O operations only if the target
|
||
|
|
server is an <span class="keyword">iSeries server</span> or a <span class="keyword">System/38™</span>. Members are not supported
|
||
|
|
if the target server is neither an <span class="keyword">iSeries server</span> nor
|
||
|
|
a <span class="keyword">System/38™</span>.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5amc.htm">Work with access methods for DDM</a></strong><br />
|
||
|
|
Access methods control what subsets of functions can be performed
|
||
|
|
after a particular remote file is opened. This might mean that an <span class="keyword">iSeries</span> program, or a group
|
||
|
|
of programs sharing a non-<span class="keyword">iSeries</span> file,
|
||
|
|
cannot do all the same operations that are possible using a file that is on
|
||
|
|
the local <span class="keyword">iSeries server</span>.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5otherremote.htm">Other DDM-related functions involving remote files</a></strong><br />
|
||
|
|
Besides accessing remote files for data record I/O operations, other operations related to remote files can be performed. These are briefly described in these topics.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5mtserv.htm">Manage the TCP/IP server</a></strong><br />
|
||
|
|
These topics describe how to manage the DRDA<sup>®</sup> and DDM server jobs that communicate
|
||
|
|
using sockets over TCP. It describes the subsystem in which the server runs,
|
||
|
|
the objects that affect the server, and how to manage those resources.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5end.htm">Cancel distributed data management work</a></strong><br />
|
||
|
|
Whether you are testing an application, handling a user problem, or monitoring a particular device, there are times when you may want to end work that is being done on a server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5perfcon.htm">Performance considerations for DDM</a></strong><br />
|
||
|
|
These topics provide information to help you improve performance when using DDM and also provide some information about when to use something other than DDM to accomplish some functions.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5probana.htm">DDM problem analysis on the remote server</a></strong><br />
|
||
|
|
Some functions that involve a target server may take a relatively long period of time to complete. In these situations, the target server may not appear to be functioning when it is actually waiting for a reply.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5source36.htm">System/36 source and target considerations for DDM</a></strong><br />
|
||
|
|
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>.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5pcsource.htm">Personal computer source to iSeries target considerations for DDM</a></strong><br />
|
||
|
|
<span class="keyword">iSeries Access Family</span> uses DDM
|
||
|
|
to allow a personal computer to communicate as a source server to access objects
|
||
|
|
on an <span class="keyword">iSeries</span> target. <span class="keyword">iSeries Access Family</span> uses Level 3.0 of the DDM
|
||
|
|
architecture stream file access support to access folder management services
|
||
|
|
(FMS) folders and documents.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5kickoff.htm" title="This topic contains i5/OS distributed data management (DDM) concepts, information about preparing for DDM communications, and DDM-related programming information.">Distributed data management</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbae5advcncp.htm" title="Most users of DDM will not need the information in the remainder of these topics; it is intended primarily for experienced programmers who need to know more about DDM.">Additional DDM concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbae5clcon.htm" title="Both compiled control language (CL) programs and interactively entered CL commands can refer to DDM files.">CL command considerations for DDM</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|