86 lines
6.6 KiB
HTML
86 lines
6.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="concept" />
|
||
|
|
<meta name="DC.Title" content="Parts of DDM: DDM file" />
|
||
|
|
<meta name="abstract" content="A system object with type *FILE exists on the source server to identify a remote file. It combines the characteristics of a device file and a database file. As a device file, the DDM file refers to a remote location name, local location name, device name, mode, and a remote network ID to identify a remote server as the target server. The DDM file appears to the application program as a database file and serves as the access device between a source server program and a remote file." />
|
||
|
|
<meta name="description" content="A system object with type *FILE exists on the source server to identify a remote file. It combines the characteristics of a device file and a database file. As a device file, the DDM file refers to a remote location name, local location name, device name, mode, and a remote network ID to identify a remote server as the target server. The DDM file appears to the application program as a database file and serves as the access device between a source server program and a remote file." />
|
||
|
|
<meta name="DC.subject" content="parts of DDM, DDM file, DDM, parts of, DDM file, introduction" />
|
||
|
|
<meta name="keywords" content="parts of DDM, DDM file, DDM, parts of, DDM file, introduction" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5partsofddm.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5crtsna.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5crttcpip.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5crtrdb.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5dirrel1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5xappn1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5sbmcmd.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="rbae5partfile" />
|
||
|
|
<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: DDM file</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5partfile"><a name="rbae5partfile"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Parts of DDM: DDM file</h1>
|
||
|
|
<div><p>A system object with type *FILE exists on the source server to
|
||
|
|
identify a remote file. It combines the characteristics of a device file and
|
||
|
|
a database file. As a device file, the DDM file refers to a remote location
|
||
|
|
name, local location name, device name, mode, and a remote network ID to identify
|
||
|
|
a remote server as the target server. The DDM file appears to the application
|
||
|
|
program as a database file and serves as the access device between a source
|
||
|
|
server program and a remote file.</p>
|
||
|
|
<p>A DDM file is a file on the source server that contains the information
|
||
|
|
needed to access a data file on a target server. It is <em>not</em> a data file
|
||
|
|
that can be accessed by a program for database operations. Instead, when a
|
||
|
|
source server program specifies the name of a DDM file, the file information
|
||
|
|
is used by DDM to locate the remote file whose data <em>is</em> to be accessed.</p>
|
||
|
|
<p>DDM file information is based on <em>locations</em>. The remote location
|
||
|
|
where the remote file is located is specified using the remote location name
|
||
|
|
(RMTLOCNAME) parameter on the <span class="cmdname">Create DDM File (CRTDDMF)</span> or <span class="cmdname">Change
|
||
|
|
DDM File (CHGDDMF)</span> commands.</p>
|
||
|
|
<p>The remote file name specified on the <span class="cmdname">CRTDDMF</span> or <span class="cmdname">CHGDDMF</span> commands
|
||
|
|
must be in the format used by the remote system.</p>
|
||
|
|
<p>Another use of the DDM file is to submit control language (CL) commands
|
||
|
|
to the target system to run on that system. In this case, the remote file
|
||
|
|
normally associated with the DDM file is ignored. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5crtsna.htm">Create a DDM file using SNA</a></strong><br />
|
||
|
|
You can create a DDM file that uses SNA as the communication protocol for connecting with the remote system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5crttcpip.htm">Create a DDM file using TCP/IP</a></strong><br />
|
||
|
|
You can create a DDM file that uses TCP/IP as the communication protocol for connecting with the remote server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5crtrdb.htm">Create a DDM file using RDB directory entry information</a></strong><br />
|
||
|
|
You can create a DDM file that uses the remote location information from a relational database (RDB) directory entry.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5dirrel1.htm">Example: Use the basic concepts of DDM in an APPC network</a></strong><br />
|
||
|
|
This topic presents a sample application that uses DDM to access a remote file.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5xappn1.htm">Example: Use the basic concepts of DDM in an APPN network</a></strong><br />
|
||
|
|
The Advanced
|
||
|
|
Peer-to-Peer Networking<sup>®</sup> (APPN) support of an <span class="keyword">iSeries™ server</span> can
|
||
|
|
be used to allow DDM access to systems not directly connected to the local
|
||
|
|
server.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<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="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbae5sbmcmd.htm" title="The Submit Remote Command (SBMRMTCMD) command submits a command using DDM to run on the target server.">SBMRMTCMD (Submit Remote Command) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|