ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddm_5.4.0.1/rbae5otherremote.htm

81 lines
5.9 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="Other DDM-related functions involving remote files" />
<meta name="abstract" content="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." />
<meta name="description" content="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." />
<meta name="DC.Relation" scheme="URI" content="rbae5ddmop.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5filmgmt.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5lckfile.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5ctlcnv.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5dsprfi.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5brwrcds.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5ccsid.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5objdist.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5nonsnad.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="rbae5otherremote" />
<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>Other DDM-related functions involving remote files</title>
</head>
<body id="rbae5otherremote"><a name="rbae5otherremote"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Other DDM-related functions involving remote files</h1>
<div><p>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.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbae5filmgmt.htm">Perform file management functions on remote servers</a></strong><br />
<span class="keyword">i5/OS™</span> DDM supports
creating, deleting, or renaming of files on a remote server. </li>
<li class="ulchildlink"><strong><a href="rbae5lckfile.htm">Lock files and members for DDM</a></strong><br />
Putting object locks on DDM files and their associated remote files requires special consideration.</li>
<li class="ulchildlink"><strong><a href="rbae5ctlcnv.htm">Control DDM conversations</a></strong><br />
Normally, the DDM conversations associated with a source server job are kept active until one of the conditions described in this topic is met.</li>
<li class="ulchildlink"><strong><a href="rbae5dsprfi.htm">Display DDM remote file information</a></strong><br />
The CL commands <span class="cmdname">Display File Description (DSPFD)</span> and <span class="cmdname">Display
File Field Description (DSPFFD)</span> can be used by an <span class="keyword">iSeries™</span> source
server user to display the attributes of one or more DDM files on the source
server, or to display the attributes of one or more remote files on a target
server.</li>
<li class="ulchildlink"><strong><a href="rbae5brwrcds.htm">Display DDM remote file records</a></strong><br />
The <span class="cmdname">Display Physical File Member (DSPPFM)</span> command
can be used to display a remote file on a target server.</li>
<li class="ulchildlink"><strong><a href="rbae5ccsid.htm">Coded character set identifier with DDM</a></strong><br />
Support for the national language of any country requires the proper handling of a set of characters.</li>
<li class="ulchildlink"><strong><a href="rbae5objdist.htm">Use of object distribution</a></strong><br />
Although DDM file names can be specified on the <span class="cmdname">Send Network
File (SNDNETF)</span> and <span class="cmdname">Receive Network File (RCVNETF)</span> commands,
these commands should be run, whenever possible, on the server where the data
actually exists. Therefore, if both servers are <span class="keyword">iSeries™ server</span>s
and both are part of a SNADS network, <dfn class="term">object distribution</dfn> can
be used instead of DDM to transfer the data between them. </li>
<li class="ulchildlink"><strong><a href="rbae5nonsnad.htm">Use of object distribution with DDM</a></strong><br />
You can also use <em>both</em> SNADS (on <span class="keyword">iSeries™ server</span>s)
and DDM (on <span class="keyword">iSeries™ server</span>s and non-<span class="keyword">iSeries™ server</span>s) to transfer files between <span class="keyword">iSeries™ server</span>s and servers that are not part
of a SNADS network but have DDM installed. </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>