ibm-information-center/dist/eclipse/plugins/i5OS.ic.apis_5.4.0.1/QTEMAPVP.htm

326 lines
10 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
<title>Map View Position (QteMapViewPosition) API</title>
<!-- Begin Header Records ========================================== -->
<!-- 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. -->
<!-- DEBUG1 SCRIPT A converted by B2H R4.1 (346) (CMS) by V2KEA304 -->
<!-- at RCHVMW2 on 29 Jan 1999 at 16:05:09 -->
<!-- Change History: -->
<!-- YYMMDD USERID Change description -->
<!--File Edited November 2001 -->
<!--End Header Records -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<a name="top_Of_Page"></a>
<!-- Java sync-link -->
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript">
</script>
<h2>Map View Position (QteMapViewPosition) API</h2>
<div class="box" style="width: 65%;">
<br>
&nbsp;&nbsp;Required Parameter Group:<br>
<!-- iddvc RMBR -->
<br>
<table width="100%">
<tr>
<td align="center" valign="top" width="10%">1</td>
<td align="left" valign="top" width="50%">Receiver variable</td>
<td align="left" valign="top" width="20%">Output</td>
<td align="left" valign="top" width="20%">Char(*)</td>
</tr>
<tr>
<td align="center" valign="top">2</td>
<td align="left" valign="top">Length of receiver variable</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Binary(4)</td>
</tr>
<tr>
<td align="center" valign="top">3</td>
<td align="left" valign="top">From view ID</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Binary(4)</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="left" valign="top">From line number</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Binary(4)</td>
</tr>
<tr>
<td align="center" valign="top">5</td>
<td align="left" valign="top">From column number</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Binary(4)</td>
</tr>
<tr>
<td align="center" valign="top">6</td>
<td align="left" valign="top">To view ID</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Binary(4)</td>
</tr>
<tr>
<td align="center" valign="top">7</td>
<td align="left" valign="top">Error code</td>
<td align="left" valign="top">I/O</td>
<td align="left" valign="top">Char(*)</td>
</tr>
</table>
<br>
&nbsp;&nbsp;Default Public Authority: *USE<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Service Program: QTEDBGS<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Threadsafe: No<br>
<!-- iddvc RMBR -->
<br>
</div>
<p>The Map View Position (QteMapViewPosition) API maps positions from one view to another view within the same program and module. A specified position in the view identified in the from view ID parameter is used for the mapping. The position is specified as a line number and a column number in the from view ID.</p>
<p>A position in one view can map to more than one position in another view. For example, an SQL statement in the SQL input source view may map to many positions in the C input source view.This is because a single SQL statement may distribute source throughout the output of the SQL processor.</p>
<p>One or more positions in the to view ID are returned as a line number and a column number.</p>
<br>
<!-- Please NOTE: DO NOT DELETE THIS SECTION if this API has no authorities and locks. -->
<!-- Instead, use the commented out coding below to indicate NONE. -->
<h3>Authorities and Locks</h3>
<!-- Use this if there are no authorities and locks. -->
<p>None.</p>
<br>
<h3>Required Parameter Group</h3>
<dl>
<dt><strong>Receiver variable</strong></dt>
<dd>OUTPUT; CHAR(*)
<p>The variable that is to receive the information requested. You can specify the size of this area to be smaller than the format requested if you specify the length of receiver variable parameter correctly. As a result, the API returns only the data that the area can hold. For more information on the size and format of the receiver variable, see <a href="#HDRFORCVAR">Format of Receiver Variable</a>.</p>
</dd>
<dt><strong>Length of receiver variable</strong></dt>
<dd>INPUT; BINARY(4)
<p>The length of the receiver variable. The minimum length is 8 bytes.</p>
<p>It is suggested that a receiver variable length be given that is large enough to hold one map element. Because this is normally the number of elements returned, a single call to this API is usually sufficient.</p>
</dd>
<dt><strong>From view ID</strong></dt>
<dd>INPUT; BINARY(4)
<p>The identifier of a previously registered view, which is obtained using theRegister Debug View API. This ID specifies the from view in the mapping function provided.</p>
</dd>
<dt><strong>From line number</strong></dt>
<dd>INPUT; BINARY(4)
<p>The line number in the view specified by the from view ID parameter mapped to aline number in the view specified by the to view ID parameter.</p>
<p>If the information in the from view ID parameter is a statement view, this parameter represents the line number in the statement view.</p>
<p><strong>Note:</strong> The statement view is the lowest level view. Breakpoints, steps, and unmonitored exceptions are reported as a line number within this view. Therefore, the statement view must exist and be registered to accomplish source level debugging.</p>
</dd>
<dt><strong>From column number</strong></dt>
<dd>INPUT; BINARY(4)
<p>The position in the line specified by the from line number parameter. Column numbers are 1 through 255.</p>
<p>If the from view ID parameter is a statement view, this parameter is not used and should be set to column one.</p>
</dd>
<dt><strong>To view ID</strong></dt>
<dd>INPUT; BINARY(4)
<p>The identifier of a previously registered view, which is obtained using the Register Debug View API. This specifies the to view in the mapping function provided.</p>
</dd>
<dt><strong>Error code</strong></dt>
<dd>I/O; CHAR(*)
<p>The structure in which to return error information. For the format of the structure, see <a href="../apiref/error.htm#hdrerrcod">Error Code Parameter</a>.</p>
</dd>
</dl>
<br>
<h3><a name="HDRFORCVAR">Format of Receiver Variable</a></h3>
<p>The following table shows the information supplied in the receiver
variable parameter.</p>
<table border width="80%">
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">BINARY(4)</td>
<td align="left" valign="top" width="60%">Bytes returned</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="center" valign="top">4</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Bytes available</td>
</tr>
<tr>
<td align="center" valign="top">8</td>
<td align="center" valign="top">8</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of map elements</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The following fields are repeated for each map element.</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Line number</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Column number</td>
</tr>
</table>
<br><br>
<h3><a name="Header_59">Field Descriptions</a></h3>
<p><strong>Bytes available.</strong> The number of bytes of data available to be returned to the user.</p>
<p><strong>Bytes returned.</strong> The number of bytes of data returned to the user.</p>
<p><strong>Column number.</strong> The column number within the from line number parameter that maps to the current position in the to view ID parameter. Column numbers are 1 through 255.</p>
<p>If the view is a statement view, this number is not used and is set to column one.</p>
<p><strong>Line number.</strong> The line number in the view specified by the to view ID parameter.</p>
<p><strong>Number of map elements.</strong> Theline number and column number fields are repeated this number of times, once for each map available.</p>
<br>
<h3>Error Messages</h3>
<table width="100%" cellpadding="3">
<!-- cols="15 85" -->
<tr>
<th align="left" valign="top">Message ID</th>
<th align="left" valign="top">Error Message Text</th>
</tr>
<tr>
<td align="left" valign="top">CPF3C24 E</td>
<td valign="top">Length of the receiver variable is not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3CF1 E</td>
<td valign="top">Error code parameter not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3CF2 E</td>
<td valign="top">Error(s) occurred during running of &amp;1 API.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9541 E</td>
<td valign="top">Not in debug mode.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9543 E</td>
<td valign="top">From view not found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9544 E</td>
<td valign="top">To view not found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9548 E</td>
<td valign="top">Map not available.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9567 E</td>
<td valign="top">Column number not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9568 E</td>
<td valign="top">Line number not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9549 E</td>
<td valign="top">Error addressing API parameter.</td>
</tr>
</table>
<br>
<hr>
API introduced: V2R3
<hr>
<center>
<table cellpadding="2" cellspacing="2">
<tr align="center">
<td valign="middle" align="center">
<a href="#top_Of_Page">Top</a> |
<a href="debug1.htm">Debugger APIs</a> |
<a href="aplist.htm">APIs by category</a></td>
</tr>
</table>
</center>
<br>
</body>
</html>