81 lines
5.4 KiB
HTML
81 lines
5.4 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="task" />
|
||
|
<meta name="DC.Title" content="Manage the storage used by a data queue" />
|
||
|
<meta name="abstract" content="Because smaller data queues have better performance than large ones, it's important to manage the size of the storage allocated to a data queue." />
|
||
|
<meta name="description" content="Because smaller data queues have better performance than large ones, it's important to manage the size of the storage allocated to a data queue." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="qcomm.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="compq.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../cl/crtdtaq.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../cl/dltdtaq.htm" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="mangq" />
|
||
|
<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>Manage the storage used by a data queue</title>
|
||
|
</head>
|
||
|
<body id="mangq"><a name="mangq"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Manage the storage used by a data queue</h1>
|
||
|
<div><p>Because smaller data queues have better performance than large
|
||
|
ones, it's important to manage the size of the storage allocated to a data
|
||
|
queue.</p>
|
||
|
<div class="section"> <p>Each entry receives a storage allocation when sent to a data
|
||
|
queue. The storage allocated will be the value that is specified for the maximum
|
||
|
entry length of the data queue that was specified on the <span class="cmdname">Create Data
|
||
|
Queue (CRTDTAQ)</span> command. When receiving an entry from a data queue,
|
||
|
the data queue removes the entry, but it does not free the auxiliary storage.
|
||
|
The system uses the auxiliary storage again when sending a new entry to the
|
||
|
data queue. The queue grows larger when not receiving entries that are sent
|
||
|
to the queue. Smaller queues that have not been extended past the initial
|
||
|
number of entries have better performance. If a data queue has grown too large,
|
||
|
delete the data queue by using the <span class="cmdname">Delete Data Queue (DLTDTAQ)</span> command.
|
||
|
On completion of the data queue deletion, recreate the queue by using the <span class="cmdname">Create
|
||
|
Data Queue (CRTDTAQ)</span> command.</p>
|
||
|
<p>There is another way to manage
|
||
|
the size of a data queue on Release V4R5M0 and beyond. This consists of using
|
||
|
the SIZE and AUTORCL keywords on the <span class="cmdname">Create Data Queue (CRTDTAQ)</span> command.
|
||
|
You can use the SIZE keyword to specify the maximum number of entries and
|
||
|
the initial number of entries for the data queue. You can use
|
||
|
the AUTORCL keyword for a queue that has been extended to indicate if the
|
||
|
data queue should have storage automatically reclaimed when the queue is empty.
|
||
|
The amount of storage that remains allocated to the queue equals the initial
|
||
|
number of entries specified for the queue when it was created. If AUTORCL
|
||
|
contains a value of *NO, which is the default, the system does not automatically
|
||
|
reclaim storage from unused space. To reclaim the storage the data queue uses,
|
||
|
you would need to delete and recreate it as described in the preceding paragraph.
|
||
|
Auto reclaim may be expensive depending on the size of the queue, so the initial
|
||
|
number of entries specified on the <span class="cmdname">Create Data Queue (CRTDTAQ)</span> command
|
||
|
should be set to the largest typical number of entries that are expected to
|
||
|
be on the data queue. If the initial number of entries is set too small, the
|
||
|
system will execute the reclaim function more frequently.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="qcomm.htm" title="Data queues are a type of system object that you can create, to which one HLL procedure or program can send data, and from which another HLL procedure or program can receive data.">Use data queues</a></div>
|
||
|
</div>
|
||
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
<div><a href="compq.htm" title="This describes the differences between using data queues and using database files.">Comparisons with using database files as queues</a></div>
|
||
|
</div>
|
||
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
<div><a href="../cl/crtdtaq.htm">Create Data Queue (CRTDTAQ) command</a></div>
|
||
|
<div><a href="../cl/dltdtaq.htm">Delete Data Queue (DLTDTAQ) command</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|