131 lines
12 KiB
HTML
131 lines
12 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="iSeries server as the target server for DDM" />
|
||
|
|
<meta name="abstract" content="The iSeries target DDM (or TDDM) is actually a job that runs a DDM-related target server program. It is started when the source server sends a program start request (an SDDM)." />
|
||
|
|
<meta name="description" content="The iSeries target DDM (or TDDM) is actually a job that runs a DDM-related target server program. It is started when the source server sends a program start request (an SDDM)." />
|
||
|
|
<meta name="DC.subject" content="system, iSeries, target, considerations, target DDM (TDDM), Server, DDM target considerations, command, DDM, CHGCD (Change Current Directory), DDM command, Change Current Directory (CHGCD), CHGFAT (Change File Attribute), Change File Attribute (CHGFAT), CLSDRC (Close Directory), Close Directory (CLSDRC), CLOSE (Close Document), Close Document (CLOSE), CRTDRC (Create Directory), Create Directory (CRTDRC), CRTSTRF (Create Stream File), Create Stream File (CRTSTRF), DELDRC (Delete Directory), Delete Directory (DELDRC), DELFIL (Delete File), Delete File (DELFIL), FRCBFF (Force Buffer), Force Buffer (FRCBFF), GETSTR (Get Data Stream), Get Data Stream (GETSTR), GETDRCEN (Get Directory Entry), Get Directory Entry (GETDRCEN), LSTFAT (List File Attributes), List File Attributes (LSTFAT), LODSTRF (Load Stream File), Load Stream File (LODSTRF), LCKSTR (Lock Data Stream), Lock Data Stream (LCKSTR), OPNDRC (Open Directory), Open Directory (OPNDRC), OPEN (Open Document), Open Document (OPEN), PUTSTR (Put Data Stream), Put Data Stream (PUTSTR), QRYCD (Query Current Directory), Query Current Directory (QRYCD), QRYSPC (Query Space Available), Query Space Available (QRYSPC), RNMDRC (Rename Directory), Rename Directory (RNMDRC), RNMFIL (Rename File), Rename File (RNMFIL), ULDSTRF (Unload Stream File), Unload Stream File (ULDSTRF), UNLSTR (Unlock Data Stream), Unlock Data Stream (UNLSTR)" />
|
||
|
|
<meta name="keywords" content="system, iSeries, target, considerations, target DDM (TDDM), Server, DDM target considerations, command, DDM, CHGCD (Change Current Directory), DDM command, Change Current Directory (CHGCD), CHGFAT (Change File Attribute), Change File Attribute (CHGFAT), CLSDRC (Close Directory), Close Directory (CLSDRC), CLOSE (Close Document), Close Document (CLOSE), CRTDRC (Create Directory), Create Directory (CRTDRC), CRTSTRF (Create Stream File), Create Stream File (CRTSTRF), DELDRC (Delete Directory), Delete Directory (DELDRC), DELFIL (Delete File), Delete File (DELFIL), FRCBFF (Force Buffer), Force Buffer (FRCBFF), GETSTR (Get Data Stream), Get Data Stream (GETSTR), GETDRCEN (Get Directory Entry), Get Directory Entry (GETDRCEN), LSTFAT (List File Attributes), List File Attributes (LSTFAT), LODSTRF (Load Stream File), Load Stream File (LODSTRF), LCKSTR (Lock Data Stream), Lock Data Stream (LCKSTR), OPNDRC (Open Directory), Open Directory (OPNDRC), OPEN (Open Document), Open Document (OPEN), PUTSTR (Put Data Stream), Put Data Stream (PUTSTR), QRYCD (Query Current Directory), Query Current Directory (QRYCD), QRYSPC (Query Space Available), Query Space Available (QRYSPC), RNMDRC (Rename Directory), Rename Directory (RNMDRC), RNMFIL (Rename File), Rename File (RNMFIL), ULDSTRF (Unload Stream File), Unload Stream File (ULDSTRF), UNLSTR (Unlock Data Stream), Unlock Data Stream (UNLSTR)" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5advcncp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5parttddm.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="rbae5xs3xtgt" />
|
||
|
|
<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 as the
|
||
|
|
target server for DDM</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5xs3xtgt"><a name="rbae5xs3xtgt"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1"><span class="keyword">iSeries</span> server as the
|
||
|
|
target server for DDM</h1>
|
||
|
|
<div><p>The <span class="keyword">iSeries™</span> target
|
||
|
|
DDM (or TDDM) is actually a job that runs a DDM-related target server program.
|
||
|
|
It is started when the source server sends a program start request (an SDDM).</p>
|
||
|
|
<p> For source <span class="keyword">iSeries</span> servers,
|
||
|
|
the program start request is started on the source server using information
|
||
|
|
contained in the IBM-supplied intersystem communications function (ICF) file
|
||
|
|
for DDM. The remote location information in the DDM file being accessed is
|
||
|
|
used to send the program start request to the appropriate target server.</p>
|
||
|
|
<p>The attributes of the target job are determined by the values specified
|
||
|
|
on the <span class="cmdname">Add Communications Entry (ADDCMNE)</span> command, which
|
||
|
|
is used on the target server to add a communications entry to the subsystem
|
||
|
|
description used for the job. This command identifies the device description,
|
||
|
|
the job description (including the library list for the target job), and the
|
||
|
|
default user profile to be used by the subsystem.</p>
|
||
|
|
<p>For an <span class="keyword">iSeries Access Family</span> connection,
|
||
|
|
the routing entry in the QIWS subsystem for DDM (CMPVAL ('DDM')), along with
|
||
|
|
the device description the personal computer is connected to, is used to obtain
|
||
|
|
the attributes of the target job.</p>
|
||
|
|
<p>After it is started, the TDDM does the following things:</p>
|
||
|
|
<ul><li>For database files: <ul><li>Handles communications with the source system by using a DDM conversation
|
||
|
|
established over an APPC, over TCP/IP, or over an <span class="keyword">iSeries Access Family</span> data
|
||
|
|
link.</li>
|
||
|
|
<li>Converts the access requests from the source server into the equivalent <span class="keyword">iSeries</span> functions and runs them on the
|
||
|
|
target server. After the target object is located, the target server-created
|
||
|
|
ODP and target database management services are used to access the object
|
||
|
|
for whatever operation is requested. The TDDM can, for example, pass requests
|
||
|
|
that open the object and then do requested I/O operations to the objects.</li>
|
||
|
|
<li>Includes <span class="keyword">iSeries</span> or <span class="keyword">System/38™</span> extensions to the DDM Level
|
||
|
|
2.0 architecture for requests received from the source server (if the source
|
||
|
|
is an <span class="keyword">iSeries server</span> or a <span class="keyword">System/38</span>), which allow most <span class="keyword">iSeries</span> functions that operate on local
|
||
|
|
servers to also work on remote <span class="keyword">iSeries</span> servers.
|
||
|
|
For example, it might receive a <span class="cmdname">SBMRMTCMD</span> command from
|
||
|
|
the source server (an <span class="keyword">iSeries server</span> or
|
||
|
|
a <span class="keyword">System/38</span>) to do a nonfile-related
|
||
|
|
operation, such as using the CL command Replace Library List (RPLLIBL) to
|
||
|
|
replace the library list within the current target job.</li>
|
||
|
|
<li>Converts target <span class="keyword">iSeries</span> responses
|
||
|
|
to the equivalent DDM responses and sends them back to the source server.
|
||
|
|
When the source server is an <span class="keyword">iSeries server</span> or <span class="keyword">System/38</span>, the actual <span class="keyword">iSeries</span> or <span class="keyword">System/38</span> messages are sent back to the
|
||
|
|
source server.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>For folder management services objects: <div class="p">Converts the DDM stream and
|
||
|
|
directory access requests into the equivalent <span class="keyword">iSeries</span> folder
|
||
|
|
management services functions and then runs them on the target server. The
|
||
|
|
following commands are supported: <ul><li><span class="cmdname">Change Current Directory (CHGCD)</span></li>
|
||
|
|
<li><span class="cmdname">Change File Attributes (CHGFAT)</span></li>
|
||
|
|
<li><span class="cmdname">Close Directory (CLSDRC)</span></li>
|
||
|
|
<li><span class="cmdname">Close Document (CLOSE)</span></li>
|
||
|
|
<li><span class="cmdname">Copy File (CPYFIL)</span></li>
|
||
|
|
<li><span class="cmdname">Create Directory (CRTDRC)</span></li>
|
||
|
|
<li><span class="cmdname">Create Stream File (CRTSTRF)</span></li>
|
||
|
|
<li><span class="cmdname">Delete Directory (DELDRC)</span></li>
|
||
|
|
<li><span class="cmdname">Delete File (DELFIL)</span></li>
|
||
|
|
<li><span class="cmdname">Force Buffer (FRCBFF)</span></li>
|
||
|
|
<li><span class="cmdname">Get Data Stream (GETSTR)</span></li>
|
||
|
|
<li><span class="cmdname">Get Directory Entry (GETDRCEN)</span></li>
|
||
|
|
<li><span class="cmdname">List File Attributes (LSTFAT)</span></li>
|
||
|
|
<li><span class="cmdname">Load Stream File (LODSTRF)</span></li>
|
||
|
|
<li><span class="cmdname">Lock Data Stream (LCKSTR)</span></li>
|
||
|
|
<li><span class="cmdname">Open Directory (OPNDRC)</span></li>
|
||
|
|
<li><span class="cmdname">Open Document (OPEN)</span></li>
|
||
|
|
<li><span class="cmdname">Put Data Stream (PUTSTR)</span></li>
|
||
|
|
<li><span class="cmdname">Query Current Directory (QRYCD)</span></li>
|
||
|
|
<li><span class="cmdname">Query Space Available (QRYSPC)</span></li>
|
||
|
|
<li><span class="cmdname">Rename Directory (RNMDRC)</span></li>
|
||
|
|
<li><span class="cmdname">Rename File (RNMFIL)</span></li>
|
||
|
|
<li><span class="cmdname">Unload Stream File (ULDSTRF)</span></li>
|
||
|
|
<li><span class="cmdname">Unlock Data Stream (UNLSTR)</span></li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>The following figure shows the basic parts on the target <span class="keyword">iSeries server</span> that
|
||
|
|
are involved in processing the requested destination file.</p>
|
||
|
|
<p>The TDDM runs as a separate batch job, just as any other user APPC, TCP/IP,
|
||
|
|
or <span class="keyword">iSeries Access Family</span> target application.
|
||
|
|
A new TDDM, using additional target server resources, is started for each
|
||
|
|
distinct source server program start request received by the target server.
|
||
|
|
There is one target job for each DDM conversation. Each TDDM can handle access
|
||
|
|
requests for multiple files in the DDM conversation.</p>
|
||
|
|
<div class="fignone" id="rbae5xs3xtgt__rbae5s3xtgt"><a name="rbae5xs3xtgt__rbae5s3xtgt"><!-- --></a><span class="figcap">Figure 1. <span class="keyword">iSeries</span> server
|
||
|
|
as the DDM target system</span><br /><img src="rsll106.gif" alt="This figure is described in the text of this section." /><br /></div>
|
||
|
|
<p>The subsystem, user profiles, and server resources to be used by the TDDM
|
||
|
|
are defined the same as they are for other types of jobs.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <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="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbae5parttddm.htm" title="A target server job is started on the target (or remote) server as a result of an incoming DDM request and ends when the associated DDM conversation ends.">Parts of DDM: Target DDM</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|