114 lines
8.3 KiB
HTML
114 lines
8.3 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="CRTDTAQ (Create Data Queue) command" />
|
||
|
<meta name="abstract" content="The Create Data Queue (CRTDTAQ) 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." />
|
||
|
<meta name="description" content="The Create Data Queue (CRTDTAQ) 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." />
|
||
|
<meta name="DC.subject" content="command, DDM-related, CL command considerations, CRTDTAQ (Create Data Queue), command, Create Data Queue (CRTDTAQ), command, CL, Create Data Queue (CRTDTAQ), data queue, creating, command, CL, CRTDTAQ (Create Data Queue), TYPE parameter, RMTDTAQ parameter, RMTLOCNAME parameter, DEV parameter, LCLLOCNAME parameter, MODE parameter, RMTNETID parameter" />
|
||
|
<meta name="keywords" content="command, DDM-related, CL command considerations, CRTDTAQ (Create Data Queue), command, Create Data Queue (CRTDTAQ), command, CL, Create Data Queue (CRTDTAQ), data queue, creating, command, CL, CRTDTAQ (Create Data Queue), TYPE parameter, RMTDTAQ parameter, RMTLOCNAME parameter, DEV parameter, LCLLOCNAME parameter, MODE parameter, RMTNETID parameter" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbae5cmdcnsd.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../rbam6/rbam6clmain.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../apiref/api.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="rbae5crtdq" />
|
||
|
<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>CRTDTAQ (Create Data Queue) command</title>
|
||
|
</head>
|
||
|
<body id="rbae5crtdq"><a name="rbae5crtdq"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1"><span class="cmdname">CRTDTAQ (Create Data Queue)</span> command</h1>
|
||
|
<div><p>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.</p>
|
||
|
<div class="section"><p>The <span class="cmdname">CRTDTAQ</span> command can optionally create a
|
||
|
distributed data management (DDM) data queue. This is done by specifying *DDM
|
||
|
on the TYPE parameter. The DDM data queue is used as a reference data queue
|
||
|
by programs to access data queues located on a remote (target) server in the
|
||
|
DDM network. Programs on the local (source) server reference a remote data
|
||
|
queue by the DDM data queue's name, not by the remote data queue's name. (The
|
||
|
DDM data queue name, however, can be the same as the remote data queue name.)</p>
|
||
|
</div>
|
||
|
<div class="section"><p>The DDM data queue (on the source server) contains the name of
|
||
|
the remote data queue and the name of the remote (target) server on which
|
||
|
the remote data queue is located.</p>
|
||
|
</div>
|
||
|
<div class="section"><p>Consider the following items when using this command with DDM:</p>
|
||
|
<ul><li>The TYPE parameter specifies the type of data queue to be created. A standard
|
||
|
data queue or a DDM data queue can be created.</li>
|
||
|
<li>The RMTDTAQ parameter is the name of the remote data queue on the target
|
||
|
system. The data queue does not need to exist when the DDM data queue is created.</li>
|
||
|
<li>The RMTLOCNAME parameter is the name of the remote location that is used
|
||
|
with this object. Multiple DDM data areas can use the same remote location
|
||
|
for the target system. RMTLOCNAME must point to a target server that is an <span class="keyword">iSeries™</span> running at a release of <span class="keyword">i5/OS™</span> that supports remote data
|
||
|
areas. The possible values for RMTLOCNAME include: <ul><li><samp class="codeph">remote-location-name</samp>: Specifies the name of the remote
|
||
|
location that is associated with the target system. The remote location, which
|
||
|
is used in accessing the target system, does not need to exist when the DDM
|
||
|
data area is created, but it must exist when the DDM data area is accessed.</li>
|
||
|
<li>*RDB: The remote location information for the relational database entry
|
||
|
specified in the relational database (RDB) parameter is used to determine
|
||
|
the remote system.</li>
|
||
|
</ul>
|
||
|
</li>
|
||
|
<li>The DEV parameter is the name of the APPC device description on the source
|
||
|
system that is used with this DDM data queue. The device description does
|
||
|
not need to exist when the DDM data queue is created.</li>
|
||
|
<li>The LCLLOCNAME parameter is the local location name.</li>
|
||
|
<li>The MODE parameter is the mode name that is used with the remote location
|
||
|
name to communicate with the target system.</li>
|
||
|
<li>The RMTNETID parameter is the remote network ID in which the remote location
|
||
|
resides that is used to communicate with the target system.</li>
|
||
|
</ul>
|
||
|
</div>
|
||
|
<div class="section"><p>Consider the following restrictions when using this command with
|
||
|
DDM:</p>
|
||
|
<ul><li>Only the API interface for data queues is supported when using DDM data
|
||
|
queues. The following APIs are supported: <ul><li><span class="apiname">Send to Data Queue (QSNDDTAQ)</span></li>
|
||
|
<li><span class="apiname">Receive from Data Queue (QRCVDTAQ)</span></li>
|
||
|
<li><span class="apiname">Clear Data Queue (QCLRDTAQ)</span></li>
|
||
|
</ul>
|
||
|
The <span class="apiname">Retrieve Data Queue Description (QMHQRDQD)</span> and <span class="apiname">Retrieve
|
||
|
Data Queue Messages (QMHRDQM)</span> APIs are not supported for DDM data
|
||
|
queues. <p>When using the *ASYNC parameter on the <span class="apiname">Send Data Queue</span> API,
|
||
|
messages resulting from errors encountered when accessing the remote data
|
||
|
queue are placed in the target server's job log, and a DDM protocol error
|
||
|
(CPF9173 - <samp class="codeph">Error detected in DDM data stream by target server</samp>)
|
||
|
is posted in the source system's job log. Look in the target server's job
|
||
|
log for the cause of the error and correct the problem before using the remote
|
||
|
data queue. Attempts to access the remote data queue after you receive this
|
||
|
error message without first correcting the problem will produce unpredictable
|
||
|
results.</p>
|
||
|
</li>
|
||
|
<li>You cannot create a data queue remotely. This function can be done remotely
|
||
|
by using the <span class="cmdname">Submit Remote Command (SBMRMTCMD)</span> command.</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 class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
<div><a href="../rbam6/rbam6clmain.htm">Control language</a></div>
|
||
|
</div>
|
||
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
<div><a href="../apiref/api.htm">Application Programming Interfaces</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|