151 lines
8.7 KiB
HTML
151 lines
8.7 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="Messages sent when the Open Query File (OPNQRYF) command is run" />
|
||
|
<meta name="abstract" content="When the Open Query File (OPNQRYF) command is run, messages are sent informing the interactive user of the status of the OPNQRYF request. For example, if a keyed access path is built by the OPNQRYF command to satisfy the request, a message is sent to the user." />
|
||
|
<meta name="description" content="When the Open Query File (OPNQRYF) command is run, messages are sent informing the interactive user of the status of the OPNQRYF request. For example, if a keyed access path is built by the OPNQRYF command to satisfy the request, a message is sent to the user." />
|
||
|
<meta name="DC.subject" content="message, sent when OPNQRYF is run, Open Query File (OPNQRYF) command, running, messages sent, OPNQRYF (Open Query File) command" />
|
||
|
<meta name="keywords" content="message, sent when OPNQRYF is run, Open Query File (OPNQRYF) command, running, messages sent, OPNQRYF (Open Query File) command" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbafoopnqf.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../rbam6/rbam6clmain.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="rbafomsgopn" />
|
||
|
<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>Messages sent when the Open Query File (OPNQRYF) command is run</title>
|
||
|
</head>
|
||
|
<body id="rbafomsgopn"><a name="rbafomsgopn"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Messages sent when the Open Query File (OPNQRYF) command is run</h1>
|
||
|
<div><p>When the Open Query File (OPNQRYF) command is run, messages are
|
||
|
sent informing the interactive user of the status of the OPNQRYF request.
|
||
|
For example, if a keyed access path is built by the OPNQRYF command to satisfy
|
||
|
the request, a message is sent to the user.</p>
|
||
|
<div class="section"><p> The following messages might be sent during a run of the OPNQRYF
|
||
|
command: </p>
|
||
|
</div>
|
||
|
|
||
|
<table cellpadding="4" cellspacing="0" border="1" class="tableborder"><tr><td>
|
||
|
<table cellpadding="4" cellspacing="0" summary="" width="100%" border="0"><thead align="left"><tr><th align="left" valign="bottom" width="50%" id="d0e37">Message identifier</th>
|
||
|
<th align="left" valign="bottom" width="50%" id="d0e39">Description</th>
|
||
|
</tr>
|
||
|
</thead>
|
||
|
<tbody><tr><td align="left" valign="top" width="50%" headers="d0e37 ">CPI4301</td>
|
||
|
<td align="left" valign="top" width="50%" headers="d0e39 "><samp class="codeph">Query running.</samp></td>
|
||
|
</tr>
|
||
|
<tr><td align="left" valign="top" width="50%" headers="d0e37 ">CPI4302</td>
|
||
|
<td align="left" valign="top" width="50%" headers="d0e39 "><samp class="codeph">Query running. Building access path...</samp></td>
|
||
|
</tr>
|
||
|
<tr><td align="left" valign="top" width="50%" headers="d0e37 ">CPI4303</td>
|
||
|
<td align="left" valign="top" width="50%" headers="d0e39 "><samp class="codeph">Query running. Creating copy of
|
||
|
file...</samp></td>
|
||
|
</tr>
|
||
|
<tr><td align="left" valign="top" width="50%" headers="d0e37 ">CPI4304</td>
|
||
|
<td align="left" valign="top" width="50%" headers="d0e39 "><samp class="codeph">Query running. Selection complete...</samp></td>
|
||
|
</tr>
|
||
|
<tr><td align="left" valign="top" width="50%" headers="d0e37 ">CPI4305</td>
|
||
|
<td align="left" valign="top" width="50%" headers="d0e39 "><samp class="codeph">Query running. Sorting copy of file...</samp></td>
|
||
|
</tr>
|
||
|
<tr><td align="left" valign="top" width="50%" headers="d0e37 ">CPI4306</td>
|
||
|
<td align="left" valign="top" width="50%" headers="d0e39 "><samp class="codeph">Query running. Building access path
|
||
|
from file...</samp></td>
|
||
|
</tr>
|
||
|
<tr><td align="left" valign="top" width="50%" headers="d0e37 ">CPI4307</td>
|
||
|
<td align="left" valign="top" width="50%" headers="d0e39 "><samp class="codeph">Query running. Building hash table
|
||
|
from file &1 in &2.</samp></td>
|
||
|
</tr>
|
||
|
<tr><td align="left" valign="top" width="50%" headers="d0e37 ">CPI4011</td>
|
||
|
<td align="left" valign="top" width="50%" headers="d0e39 "><samp class="codeph">Query running. Number of records
|
||
|
processed...</samp></td>
|
||
|
</tr>
|
||
|
</tbody>
|
||
|
</table>
|
||
|
</td></tr></table>
|
||
|
<div class="section"><p>To stop these status messages from appearing, you can see the
|
||
|
discussion about message handling in the Control language (CL) topic.</p>
|
||
|
</div>
|
||
|
<div class="section"><div class="p">When your job is running under debug (by using the Start Debug
|
||
|
(STRDBG) command), or requested with query options file option of DEBUG_MESSAGES
|
||
|
*YES, messages are sent to your job log. These messages describe the implementation
|
||
|
method that is used to process the OPNQRYF request. These messages provide
|
||
|
information about the optimization processing that occurred. You can use these
|
||
|
messages as a tool for tuning the OPNQRYF request to achieve the best performance.
|
||
|
Listed here are these messages: <dl><dt class="dlterm">CPI4321</dt>
|
||
|
<dd>Access path built for file...</dd>
|
||
|
<dt class="dlterm">CPI4322</dt>
|
||
|
<dd>Access path built from keyed file...</dd>
|
||
|
<dt class="dlterm">CPI4324</dt>
|
||
|
<dd>Temporary file built from file...</dd>
|
||
|
<dt class="dlterm">CPI4325</dt>
|
||
|
<dd>Temporary file built for query</dd>
|
||
|
<dt class="dlterm">CPI4326</dt>
|
||
|
<dd>File processed in join position...</dd>
|
||
|
<dt class="dlterm">CPI4327</dt>
|
||
|
<dd>File processed in join position 1.</dd>
|
||
|
<dt class="dlterm">CPI4328</dt>
|
||
|
<dd>Access path of file that is used...</dd>
|
||
|
<dt class="dlterm">CPI4329</dt>
|
||
|
<dd>Arrival sequence that is used for file...</dd>
|
||
|
<dt class="dlterm">CPI432A</dt>
|
||
|
<dd>Query optimizer timed out...</dd>
|
||
|
<dt class="dlterm">CPI432C</dt>
|
||
|
<dd>All access paths considered for file...</dd>
|
||
|
<dt class="dlterm">CPI432E</dt>
|
||
|
<dd>Selection fields mapped to different attributes...</dd>
|
||
|
<dt class="dlterm">CPI432F</dt>
|
||
|
<dd>Access path suggestion for file...</dd>
|
||
|
<dt class="dlterm">CPI433B</dt>
|
||
|
<dd>Unable to update query options file.</dd>
|
||
|
<dt class="dlterm">CPI4330</dt>
|
||
|
<dd>&6 tasks used for parallel &10 scan of file &1.</dd>
|
||
|
<dt class="dlterm">CPI4332</dt>
|
||
|
<dd>&6 tasks used for parallel index that is created over file...</dd>
|
||
|
<dt class="dlterm">CPI4333</dt>
|
||
|
<dd>Hashing algorithm used to process join.</dd>
|
||
|
<dt class="dlterm">CPI4338</dt>
|
||
|
<dd>&1 access paths used for bitmap processing of file...</dd>
|
||
|
<dt class="dlterm">CPI4339</dt>
|
||
|
<dd>Query options retrieved file &2 in library &1.</dd>
|
||
|
<dt class="dlterm">CPI4341</dt>
|
||
|
<dd>Performing distributed query.</dd>
|
||
|
<dt class="dlterm">CPI4342</dt>
|
||
|
<dd>Performing distributed join for query.</dd>
|
||
|
<dt class="dlterm">CPI4345</dt>
|
||
|
<dd>Temporary distributed result file &4 built...</dd>
|
||
|
<dt class="dlterm">CPI4346</dt>
|
||
|
<dd>Optimizer debug messages for query join step &1 of &2 follow:</dd>
|
||
|
<dt class="dlterm">CPI4347</dt>
|
||
|
<dd>Query is processing in multiple steps.</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="section"><p>Most of the messages provide a reason why the particular option
|
||
|
was performed. The second level text on each message gives an extended description
|
||
|
of why the option was chosen. Some messages provide suggestions to help improve
|
||
|
the performance of the OPNQRYF request.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafoopnqf.htm" title="The Open Query File (OPNQRYF) command is a control language (CL) command that allows you to perform many data processing functions on database files. These topics discuss how to create a query using the OPNQRYF command, how to specify parameters for its major functions, and how to use it with your high-level language program.">Use Open Query File (OPNQRYF) command</a></div>
|
||
|
</div>
|
||
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
<div><a href="../rbam6/rbam6clmain.htm">Control language (CL)</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|