191 lines
14 KiB
HTML
191 lines
14 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="DDM-related CL command considerations" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.subject" content="command, CL, considerations" />
|
||
|
|
<meta name="keywords" content="command, CL, considerations" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5cldsp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5fmhandle.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5alcobj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ddm_chgjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ddm_chglf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ddm_chgpf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ddm_chgsrcpf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ddm_clrpfm.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5cpyfcmd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5crtdt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5crtdq.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5crtlf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5crtpf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5crtsrcp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5dlcobj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5dltf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5dspfd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5dspffd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5oqryf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ovrdbf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ddm_rclrsc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5rnmobj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5wrkjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5woblck.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5cmdlsts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rbam6/rbam6clmain.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="rbae5cmdcnsd" />
|
||
|
|
<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>DDM-related CL command considerations</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5cmdcnsd"><a name="rbae5cmdcnsd"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">DDM-related CL command considerations</h1>
|
||
|
|
<div><p>This topic collection describes DDM-related specifics
|
||
|
|
about <span class="keyword">iSeries™</span> 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 <span class="cmdname">Submit Remote Command (SBMRMTCMD)</span> command.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> You see message CPF9810 if the following items are true about a DDM
|
||
|
|
file:</div>
|
||
|
|
<ul><li>The file is created into library QTEMP.</li>
|
||
|
|
<li>The file is used by a CL command (such as CPYF).</li>
|
||
|
|
<li>A remote file and library was specified in the CL command and the library
|
||
|
|
does not exist on the remote server.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Message CPF9810 indicates that the QTEMP library was not found. However,
|
||
|
|
the library that was not found is the remote library that was specified in
|
||
|
|
the DDM file.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5fmhandle.htm">File management handling of DDM files</a></strong><br />
|
||
|
|
Because of the way data management handles DDM files, you must be careful when specifying a member name on commands. If a member name is specified, data management first searches for a local database file containing the member specified before looking for a DDM file.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5alcobj.htm">ALCOBJ (Allocate Object) command</a></strong><br />
|
||
|
|
When the name of a DDM file is specified on the <span class="cmdname">Allocate
|
||
|
|
Object (ALCOBJ)</span> command on the source server, the command allocates
|
||
|
|
the DDM file on the source server and its associated file or file member on
|
||
|
|
a target server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5ddm_chgjob.htm">CHGJOB (Change Job) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Change Job (CHGJOB)</span> command can be used
|
||
|
|
to change the DDMCNV parameter, which controls whether Advanced Program-to-Program
|
||
|
|
Communication (APPC) or <span class="keyword">iSeries Access Family</span> conversations
|
||
|
|
allocated for DDM use are to be kept active or automatically dropped when
|
||
|
|
they are not in use by a job. The new value goes into effect immediately for
|
||
|
|
the specified job.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5ddm_chglf.htm">CHGLF (Change Logical File) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Change Logical File (CHGLF)</span> command can
|
||
|
|
be used to change files on the source and target servers through the SYSTEM
|
||
|
|
parameter.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5ddm_chgpf.htm">CHGPF (Change Physical File) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Change Physical File (CHGPF)</span> command can
|
||
|
|
be used to change files on the source and target systems through the SYSTEM
|
||
|
|
parameter.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5ddm_chgsrcpf.htm">CHGSRCPF (Change Source Physical File) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Change Source Physical File (CHGSRCPF)</span> command
|
||
|
|
can be used to change files on the source and target servers through the SYSTEM
|
||
|
|
parameter.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5ddm_clrpfm.htm">CLRPFM (Clear Physical File Member) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Clear Physical File Member (CLRPFM)</span> command
|
||
|
|
can be used with DDM to clear all the records either from a physical file
|
||
|
|
member on a target <span class="keyword">iSeries server</span> or
|
||
|
|
from a file on a non-<span class="keyword">iSeries</span> target
|
||
|
|
server. The command works the same way as it does for local files (clearing
|
||
|
|
all data records and deleted records).</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5cpyfcmd.htm">Copy commands with DDM</a></strong><br />
|
||
|
|
This topic describes the DDM implications of these CL commands.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5crtdt.htm">CRTDTAARA (Create Data Area) command</a></strong><br />
|
||
|
|
The<span class="cmdname"> Create Data Area (CRTDTAARA)</span> command creates
|
||
|
|
a data area and stores it in a specified library. It also specifies the attributes
|
||
|
|
of the data. The data area can be optionally initialized to a specific value.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5crtdq.htm">CRTDTAQ (Create Data Queue) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Create Data Queue (CRTDTAQ)</span> command creates
|
||
|
|
a data queue and stores it in a specified library. Data queues are used to
|
||
|
|
communicate and store data used by several programs either within a job or
|
||
|
|
between jobs. Multiple jobs can send or receive data from a single queue.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5crtlf.htm">CRTLF (Create Logical File) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Create Logical File (CRTLF)</span> command can
|
||
|
|
be used to create files on the source and target servers through the SYSTEM
|
||
|
|
parameter.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5crtpf.htm">CRTPF (Create Physical File) command</a></strong><br />
|
||
|
|
The<span class="cmdname"> Create Physical File (CRTPF)</span> command can
|
||
|
|
be used to create files on the source and target servers through the SYSTEM
|
||
|
|
parameter.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5crtsrcp.htm">CRTSRCPF (Create Source Physical File) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Create Source Physical File (CRTSRCPF)</span> command
|
||
|
|
can be used to create files on the <span class="keyword">iSeries</span> source
|
||
|
|
and target servers through the SYSTEM parameter.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5dlcobj.htm">DLCOBJ (Deallocate Object) command</a></strong><br />
|
||
|
|
When the name of a DDM file is specified on the <span class="cmdname">Deallocate
|
||
|
|
Object (DLCOBJ)</span> command on the source server, the command deallocates
|
||
|
|
the DDM file on the source server and its associated file or file member on
|
||
|
|
a target server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5dltf.htm">DLTF (Delete File) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Delete File (DLTF)</span> command can be used to
|
||
|
|
delete files on the source and target servers.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5dspfd.htm">DSPFD (Display File Description) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Display File Description (DSPFD)</span> command
|
||
|
|
can be used to display (on the source server) the attributes of the DDM file
|
||
|
|
on the source server, the remote file on the target server, or both the DDM
|
||
|
|
file and the remote file. As with local files, the attributes of multiple
|
||
|
|
DDM files, multiple remote files, or both can be displayed by
|
||
|
|
the same command.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5dspffd.htm">DSPFFD (Display File Field Description) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Display File Field Description (DSPFFD)</span> command
|
||
|
|
can be used to display the file, record format, and field attributes of a
|
||
|
|
remote file. To display the remote file attributes, however, you must enter
|
||
|
|
the name of the DDM file associated with the remote file, not the name of
|
||
|
|
the remote file.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5oqryf.htm">OPNQRYF (Open Query File) command</a></strong><br />
|
||
|
|
You can query remote files using the <span class="cmdname">Open Query File (OPNQRYF)</span> command,
|
||
|
|
but only if the remote files are on a target <span class="keyword">iSeries server</span> or
|
||
|
|
a target <span class="keyword">System/38™</span>. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5ovrdbf.htm">OVRDBF (Override with Database File) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Override with Database File (OVRDBF)</span> command
|
||
|
|
can be used with DDM to override (replace) a local database file named in
|
||
|
|
the program with a DDM file; the DDM file causes the associated remote file
|
||
|
|
to be used by the program instead of the local database file.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5ddm_rclrsc.htm">RCLRSC (Reclaim Resources) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Reclaim Resources (RCLRSC)</span> command, like
|
||
|
|
the <span class="cmdname">Reclaim DDM Conversations (RCLDDMCNV)</span> command, can
|
||
|
|
be used to reclaim all DDM conversations that currently have no users in the
|
||
|
|
job.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5rnmobj.htm">RNMOBJ (Rename Object) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Rename Object (RNMOBJ)</span> command can be used
|
||
|
|
to rename a remote file.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5wrkjob.htm">WRKJOB (Work with Job) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Work with Job (WRKJOB)</span> command can be used
|
||
|
|
to display two DDM-related items.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5woblck.htm">WRKOBJLCK (Work with Object Lock) command</a></strong><br />
|
||
|
|
The <span class="cmdname">Work with Object Lock (WRKOBJLCK)</span> command
|
||
|
|
can be used to display the object lock requests (held locks and pending locks)
|
||
|
|
for DDM files. This command displays only the locks held for the local DDM
|
||
|
|
files, not locks held for the associated remote files.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5cldsp.htm" title="This topic contains DDM-related information about specific iSeries control language (CL) commands, data description specifications (DDS) considerations, DDS keywords, and DDM user profile authority.">Use CL and DDS with DDM</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rbam6/rbam6clmain.htm">Control language</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbae5cmdlsts.htm" title="The control language (CL) commands that have a specific relationship with DDM are grouped in charts in these topics to show the command functions that are available with DDM, those having common limitations when used with DDM, and those that cannot be used with DDM.">DDM-related CL command lists</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|