74 lines
4.9 KiB
HTML
74 lines
4.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="Parts of DDM: Source DDM" />
|
||
|
|
<meta name="abstract" content="The support on the source (or local) iSeries server is started, as needed, within a source job to do DDM functions." />
|
||
|
|
<meta name="description" content="The support on the source (or local) iSeries server is started, as needed, within a source job to do DDM functions." />
|
||
|
|
<meta name="DC.subject" content="parts of DDM, source DDM (SDDM), DDM, parts of" />
|
||
|
|
<meta name="keywords" content="parts of DDM, source DDM (SDDM), DDM, parts of" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5partsofddm.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5xs3xsrc.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="rbae5partsddm" />
|
||
|
|
<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>Parts of DDM: Source DDM</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5partsddm"><a name="rbae5partsddm"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Parts of DDM: Source DDM</h1>
|
||
|
|
<div><p>The support on the source (or local) <span class="keyword">iSeries™ server</span> is
|
||
|
|
started, as needed, within a source job to do DDM functions.</p>
|
||
|
|
<p>The source DDM (SDDM) translates requests for remote file
|
||
|
|
access from source server application programs into DDM requests that are
|
||
|
|
routed to the target server for processing. The SDDM support establishes and
|
||
|
|
manages a DDM conversation with the target server that has the desired remote
|
||
|
|
file.</p>
|
||
|
|
<p>When an application program first attempts to access a remote file, a search
|
||
|
|
for the requested DDM file is done on the source server. As with local file
|
||
|
|
processing, if the file name is not qualified with a library name, the current
|
||
|
|
library list for the job in which the program is running is searched for the
|
||
|
|
specified file. When the file is found, the server accesses the file, determines
|
||
|
|
that it is a DDM file and starts the SDDM.</p>
|
||
|
|
<p>When the SDDM is started, it checks to see if a DDM conversation is already
|
||
|
|
active between the source job starting the SDDM and the target server identified
|
||
|
|
by the remote location and mode values in the DDM file. If a conversation
|
||
|
|
that can be used exists, it is used. If not, a program start request is issued
|
||
|
|
to the appropriate target server to start a TDDM (a target job) on the target
|
||
|
|
server to establish a DDM conversation between the SDDM and TDDM. Parameters
|
||
|
|
that are automatically created from information in the DDM file about the
|
||
|
|
remote file are passed when the remote server sends a program start request.</p>
|
||
|
|
<p>After the TDDM is started, the SDDM can forward each program request to
|
||
|
|
the target job for processing. If, for example, input/output (I/O) operations
|
||
|
|
are to be done on a remote file, the program opens the file and then issues
|
||
|
|
the desired operation requests. The SDDM forwards the open request and the
|
||
|
|
TDDM opens the remote file. Then the SDDM forwards each file operation request
|
||
|
|
to the TDDM, and both of them handle the interchange of data between the application
|
||
|
|
program and the remote file. When a DDM function is being processed, the requesting
|
||
|
|
program waits for the function to be completed and the results to be received,
|
||
|
|
just as it does for local file operations.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5partsofddm.htm" title="DDM consists of several parts to handle remote file processing among the systems using DDM.">Parts of DDM</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbae5xs3xsrc.htm" title="When an application program or user in a source server job first refers to a DDM file, several actions occur as part of processing the request on the source server.">iSeries server as the source server for DDM</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|