70 lines
5.4 KiB
HTML
70 lines
5.4 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="Access files with DDM" />
|
|
<meta name="abstract" content="These topics describe the types of files supported by an iSeries server, 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 iSeries-to-iSeries and iSeries-to-System/36 file accessing." />
|
|
<meta name="description" content="These topics describe the types of files supported by an iSeries server, 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 iSeries-to-iSeries and iSeries-to-System/36 file accessing." />
|
|
<meta name="DC.subject" content="system, server, iSeries, files, access considerations, DDM file, accessing, file access considerations" />
|
|
<meta name="keywords" content="system, server, iSeries, files, access considerations, DDM file, accessing, file access considerations" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ddmop.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5typeoffile.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5existence.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5namecon.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5exiseries.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ex36.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="rbae5fac" />
|
|
<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>Access files with DDM</title>
|
|
</head>
|
|
<body id="rbae5fac"><a name="rbae5fac"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Access files with DDM</h1>
|
|
<div><p>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.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbae5typeoffile.htm">Types of files supported by i5/OS DDM</a></strong><br />
|
|
<span class="keyword">i5/OS™</span> DDM supports
|
|
all <span class="keyword">iSeries</span> file types when
|
|
the target server is another <span class="keyword">iSeries server</span>.</li>
|
|
<li class="ulchildlink"><strong><a href="rbae5existence.htm">Existence of DDM file and remote file</a></strong><br />
|
|
A file on a target server cannot be accessed for any type of operation (such as open, read, write, or display) unless a DDM file associated with the remote file already exists on the source server.</li>
|
|
<li class="ulchildlink"><strong><a href="rbae5namecon.htm">Rules for specifying target server file names for DDM</a></strong><br />
|
|
The rules for specifying the name of a DDM file (on the local <span class="keyword">iSeries server</span>) are the same as for any other
|
|
file type on an <span class="keyword">iSeries server</span>. The
|
|
rules, however, for specifying the name of a remote file depend on the type
|
|
of target server.</li>
|
|
<li class="ulchildlink"><strong><a href="rbae5exiseries.htm">Examples: Access iSeries DDM remote files (iSeries-to-iSeries)</a></strong><br />
|
|
The examples show how access to a DDM file becomes an indirect
|
|
reference (by using DDM) to the actual file on some other server. These examples
|
|
are <span class="keyword">iSeries</span>-to-<span class="keyword">iSeries</span> examples.</li>
|
|
<li class="ulchildlink"><strong><a href="rbae5ex36.htm">Example: Access System/36 DDM remote files (iSeries-to-System/36)</a></strong><br />
|
|
Of the command examples given in the previous topic (showing <span class="keyword">iSeries</span>-to-<span class="keyword">iSeries</span> examples),
|
|
all except the first example can be coded the same way for accessing a file
|
|
on a <span class="keyword">System/36</span>.</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> |