70 lines
5.6 KiB
HTML
70 lines
5.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="reference" />
|
|
<meta name="DC.Title" content="Use of object distribution" />
|
|
<meta name="abstract" content="Although DDM file names can be specified on the Send Network File (SNDNETF) and Receive Network File (RCVNETF) commands, these commands should be run, whenever possible, on the server where the data actually exists. Therefore, if both servers are iSeries servers and both are part of a SNADS network, object distribution can be used instead of DDM to transfer the data between them." />
|
|
<meta name="description" content="Although DDM file names can be specified on the Send Network File (SNDNETF) and Receive Network File (RCVNETF) commands, these commands should be run, whenever possible, on the server where the data actually exists. Therefore, if both servers are iSeries servers and both are part of a SNADS network, object distribution can be used instead of DDM to transfer the data between them." />
|
|
<meta name="DC.subject" content="SNADS (SNA distribution services), object distribution, SNA distribution services (SNADS), object, distribution, alternatives to DDM, performance considerations, command, SBMNETJOB (Submit Network Job), Submit Network Job (SBMNETJOB), command, CL, Submit Network Job (SBMNETJOB), network job, submitting, SBMNETJOB (Submit Network Job)" />
|
|
<meta name="keywords" content="SNADS (SNA distribution services), object distribution, SNA distribution services (SNADS), object, distribution, alternatives to DDM, performance considerations, command, SBMNETJOB (Submit Network Job), Submit Network Job (SBMNETJOB), command, CL, Submit Network Job (SBMNETJOB), network job, submitting, SBMNETJOB (Submit Network Job)" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5otherremote.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5batchproc.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="rbae5objdist" />
|
|
<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>Use of object distribution</title>
|
|
</head>
|
|
<body id="rbae5objdist"><a name="rbae5objdist"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Use of object distribution</h1>
|
|
<div><p>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. </p>
|
|
<div class="section"><ul><li>The <span class="cmdname">SNDNETF</span> command should run directly on the server
|
|
that contains the data being sent. If necessary, the <span class="cmdname">Submit Remote
|
|
Command (SBMRMTCMD)</span> or <span class="cmdname">Submit Network Job (SBMNETJOB)</span> command
|
|
can be used to submit the <span class="cmdname">SNDNETF</span> command to the server
|
|
where the data exists. <div class="note"><span class="notetitle">Note:</span> Another way to use the <span class="cmdname">SNDNETF</span> command
|
|
without using DDM is to run it on the target server using display station
|
|
pass-through.</div>
|
|
</li>
|
|
<li>The <span class="cmdname">RCVNETF</span> command must be run on the server where
|
|
the data has been sent. If necessary, a DDM file can be referred
|
|
to on the <span class="cmdname">RCVNETF</span> command to place the data on another
|
|
server. However, if possible, you should arrange to have the data sent to
|
|
the server where the data is to be used, to avoid using a DDM file.</li>
|
|
</ul>
|
|
</div>
|
|
<div class="section"><p>For both sending and receiving operations, the file types of the
|
|
data files must match and can only be a save file or a physical database file.
|
|
If DDM is being used, however, the file being transferred cannot be a save
|
|
file.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5otherremote.htm" title="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.">Other DDM-related functions involving remote files</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rbae5batchproc.htm" title="Consider these items when using batch file processing with DDM.">Batch file processing with DDM</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |