164 lines
12 KiB
HTML
164 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="reference" />
|
|
<meta name="DC.Title" content="Copy commands with DDM" />
|
|
<meta name="abstract" content="This topic describes the DDM implications of these CL commands." />
|
|
<meta name="description" content="This topic describes the DDM implications of these CL commands." />
|
|
<meta name="DC.subject" content="command, DDM-related, CL command considerations, CPYF (Copy File), command, Copy File (CPYF), command, CL, CPYF (Copy File), Copy File (CPYF), file, copying, FROMFILE parameter, CL command considerations, CPYSRCF (Copy Source File), Copy Source File (CPYSRCF), Copy Source File (CPYSRCF), source file, command, CL, CPYFRMQRYF (Copy from Query File), Copy from Query File (CPYFRMQRYF), CPYFRMQRYF (Copy from Query File), query file, copying from, from query file" />
|
|
<meta name="keywords" content="command, DDM-related, CL command considerations, CPYF (Copy File), command, Copy File (CPYF), command, CL, CPYF (Copy File), Copy File (CPYF), file, copying, FROMFILE parameter, CL command considerations, CPYSRCF (Copy Source File), Copy Source File (CPYSRCF), Copy Source File (CPYSRCF), source file, command, CL, CPYFRMQRYF (Copy from Query File), Copy from Query File (CPYFRMQRYF), CPYFRMQRYF (Copy from Query File), query file, copying from, from query file" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5cmdcnsd.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="rbae5cpyfcmd" />
|
|
<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>Copy commands with DDM</title>
|
|
</head>
|
|
<body id="rbae5cpyfcmd"><a name="rbae5cpyfcmd"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Copy commands with DDM</h1>
|
|
<div><p>This topic describes the DDM implications of these CL commands.</p>
|
|
<div class="section"><ul><li><span class="cmdname">Copy File (CPYF)</span></li>
|
|
<li><span class="cmdname">Copy from Query File (CPYFRMQRYF)</span></li>
|
|
<li><span class="cmdname">Copy from Tape (CPYFRMTAP)</span></li>
|
|
<li><span class="cmdname">Copy Source File (CPYSRCF)</span></li>
|
|
<li><span class="cmdname">Copy to Tape (CPYTOTAP)</span></li>
|
|
</ul>
|
|
</div>
|
|
<div class="section"><p>These commands can be used to copy data or source between files
|
|
on local and remote servers. You specify with these commands which file to
|
|
copy from and which file to copy to. The following table shows you what database
|
|
and device files can be copied between local and remote servers.</p>
|
|
</div>
|
|
|
|
<div class="tablenoborder"><a name="rbae5cpyfcmd__cpyft"><!-- --></a><table cellpadding="4" cellspacing="0" summary="" id="rbae5cpyfcmd__cpyft" width="100%" frame="hsides" border="1" rules="rows"><caption>Table 1. Copy database and device
|
|
files</caption><thead align="left"><tr><th valign="top" width="50%" id="d0e161">From file</th>
|
|
<th valign="top" width="50%" id="d0e163">To file</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="50%" headers="d0e161 ">Local or remote database files</td>
|
|
<td valign="top" width="50%" headers="d0e163 ">Local or remote database files</td>
|
|
</tr>
|
|
<tr><td valign="top" width="50%" headers="d0e161 ">Local or remote database files</td>
|
|
<td valign="top" width="50%" headers="d0e163 ">Local device files</td>
|
|
</tr>
|
|
<tr><td valign="top" width="50%" headers="d0e161 ">Local device files</td>
|
|
<td valign="top" width="50%" headers="d0e163 ">Local or remote database files</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<div class="section"><p>A DDM file is considered a device file that refers to a remote
|
|
database file. Consider the following items when using these copy commands
|
|
with DDM:</p>
|
|
</div>
|
|
<div class="section"> <ul><li>DDM conversations are not reclaimed for a job when a copy command produces
|
|
an error. <div class="note"><span class="notetitle">Note:</span> In releases before Version 3 Release 2, copy errors caused
|
|
the <span class="cmdname">Reclaim Resources (RCLRSC)</span> command to be run, which
|
|
also ran the <span class="cmdname">Reclaim Distributed Data Management Conversations (RCLDDMCNV)</span> command.
|
|
The <span class="cmdname">RCLRSC</span> command is still run, but it no longer runs
|
|
the <span class="cmdname">RCLDDMCNV</span> command when a copy error occurs. The DDM
|
|
conversations will remain unless an explicit <span class="cmdname">RCLDDMCNV</span> is
|
|
specified following the copy command with the error.</div>
|
|
</li>
|
|
<li>If you specify a DDM file and a local file on the <span class="cmdname">CPYF</span> or <span class="cmdname">CPYSRCF</span> command,
|
|
the server does not verify that the remote and local files are not the same
|
|
file on the source server. If one DDM file is specified, a user can potentially
|
|
copy to and from the same file.</li>
|
|
<li>A DDM file can be specified on the FROMFILE and the TOFILE parameters
|
|
for the <span class="cmdname">CPYF</span> and <span class="cmdname">CPYSRCF</span> commands. <div class="note"><span class="notetitle">Note:</span> For
|
|
the <span class="cmdname">Copy from Query File (CPYFRMQRYF)</span>, and <span class="cmdname">Copy
|
|
from Tape (CPYFRMTAP)</span> commands, a DDM file name can be specified
|
|
only on the TOFILE parameter; for the <span class="cmdname">Copy to Tape (CPYTOTAP)</span> command,
|
|
a DDM file name can be specified only on the FROMFILE parameter.</div>
|
|
</li>
|
|
<li>If the target server is <em>not</em> an <span class="keyword">iSeries™ server</span> or
|
|
a <span class="keyword">System/38™</span>: <ul><li>When a file on the local <span class="keyword">iSeries server</span> is
|
|
copied to a remote file (or vice versa), FMTOPT(*NOCHK) is usually required.</li>
|
|
<li>When a <em>source</em> file on the local <span class="keyword">iSeries server</span> is
|
|
copied to a remote file (or vice versa), FMTOPT(*CVTSRC) <em>must</em> be specified.</li>
|
|
</ul>
|
|
</li>
|
|
<li>If data is copied to a target <span class="keyword">System/36™</span> file
|
|
that has alternative indexes built over it, MBROPT(*REPLACE) cannot be specified.
|
|
In this case, the copy command attempts to clear the remote file, but it fails
|
|
because of the alternative indexes.</li>
|
|
<li>When an <span class="keyword">iSeries</span> file that
|
|
can contain deleted records is copied to one that cannot contain deleted records,
|
|
you must specify COMPRESS(*YES), or an error message is sent and the job ends.</li>
|
|
<li>If the remote file name on a DDM file specifies a member name, the member
|
|
name specified for that file on the copy command must be the same as the member
|
|
name on the remote file name on the DDM file. In addition, the <span class="cmdname">Override
|
|
Database File (OVRDBF)</span> command cannot specify a member name that
|
|
is different from the member name on the remote file name on the DDM file.</li>
|
|
<li>If a DDM file does not specify a member name and if the <span class="cmdname">OVRDBF</span> command
|
|
specifies a member name for the file, the copy command uses the member name
|
|
specified on the <span class="cmdname">OVRDBF</span> command.</li>
|
|
</ul>
|
|
</div>
|
|
<div class="section"><p>If the TOFILE parameter is a DDM file that refers to a file that
|
|
does not exist, <span class="cmdname">CPYF</span> creates the file if CRTFILE(*YES)
|
|
is specified. Listed here are special considerations for remote files created
|
|
with the <span class="cmdname">CPYF</span> or <span class="cmdname">CPYFRMQRYF</span> commands:</p>
|
|
<ul><li>If the target system is an <span class="keyword">iSeries server</span> or
|
|
a <span class="keyword">System/38</span>, the user profile
|
|
for the target DDM job must be authorized to the <span class="cmdname">CRTPF</span> command
|
|
on the target server.</li>
|
|
<li>If the target server is a server other than an <span class="keyword">iSeries server</span>,
|
|
the file specified by the FROMFILE parameter cannot have any file or field
|
|
CCSIDs other than *HEX or the CCSID of the source job.</li>
|
|
<li>For the <span class="cmdname">CPYF</span> command, if the target server is a system
|
|
other than an <span class="keyword">iSeries server</span>, the
|
|
FROMFILE parameter cannot be a source file.</li>
|
|
<li>If the target server is a <span class="keyword">System/38</span>,
|
|
the TOMBR parameter must be the same as the remote file's name or *FIRST for
|
|
the copy to be successful. The copy creates a member with the same name as
|
|
the remote file's name.</li>
|
|
<li>If the target server is other than a <span class="keyword">System/38</span> or <span class="keyword">iSeries server</span>, for the copy to be successful,
|
|
the TOMBR parameter must be *FIRST or specify the DDM file name. For DDM access
|
|
to the remote file, the file appears to have a member with the same name as
|
|
the DDM file.</li>
|
|
<li>For an <span class="keyword">iSeries</span> target server,
|
|
the TOFILE parameter has all the attributes of the FROMFILE parameter.</li>
|
|
<li>For target systems that are other than <span class="keyword">iSeries server</span>s,
|
|
those attributes on the <span class="cmdname">CRTPF</span> command that are ignored
|
|
are also ignored when the copy command creates the file.</li>
|
|
<li>If the target server is a <span class="keyword">System/38</span> and
|
|
the FROMFILE parameter is a direct file that does not allow deleted records,
|
|
an attempt is made to copy the records after the last record for the file
|
|
at its maximum size. The system operator on the <span class="keyword">System/38</span> tells
|
|
the server to either add the records or cancel the copy.</li>
|
|
<li>The <span class="cmdname">CPYF</span> or <span class="cmdname">CPYFRMQRYF</span> command with
|
|
CRTFILE(*YES) creates a file on the target server with a size description
|
|
that is only as large as the target server allows.</li>
|
|
<li>For all copies, if the number of records being copied exceeds the maximum
|
|
allowed by the to-file, the copy function ends when the maximum is reached.</li>
|
|
<li>For copy commands executed on Version 2 Release 3 or earlier systems that
|
|
reference a Version 3 Release 1 remote file having a constraint relationship,
|
|
the ERRLVL parameter will not work for constraint relationship violations.
|
|
The copy ends regardless of the ERRLVL specified.</li>
|
|
<li>The copy commands allow copying from and to DDM files that reference remote
|
|
distributed files.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5cmdcnsd.htm" title="This topic collection describes DDM-related specifics about iSeries CL commands when they are used with DDM files. These topics discuss running the commands on the source server and do not discuss them being submitted to run on the target server by the Submit Remote Command (SBMRMTCMD) command.">DDM-related CL command considerations</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |