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

222 lines
6.7 KiB
HTML
Raw 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>Log Transaction (QYPELOGT, qypeLogTransaction) 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. -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<!-- Change History: -->
<!-- YYMMDD USERID Change description -->
<!-- Created for V5R2 -->
<!-- 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 type="text/javascript" language="Javascript" src="../rzahg/synch.js">
</script>
<h2>Log Transaction (QYPELOGT, qypeLogTransaction) API</h2>
<div class="box" style="width: 80%;">
<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="45%">Application identifier</td>
<td align="left" valign="top" width="15%">Input</td>
<td align="left" valign="top" width="30%">Char(20)</td>
</tr>
<tr>
<td align="center" valign="top">2</td>
<td align="left" valign="top">Transaction identifier</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Binary(4) Unsigned</td>
</tr>
<tr>
<td align="center" valign="top">3</td>
<td align="left" valign="top">Application trace data</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(*)</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="left" valign="top">Length of application trace data</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Binary(4) Unsigned</td>
</tr>
<tr>
<td align="center" valign="top">5</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;Service Program Name: QYPESVPG<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Default Public Authority: *USE<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Threadsafe: Yes<br>
<!-- iddvc RMBR -->
<br>
</div>
<p>The Log Transaction (OPM, QYPELOGT; ILE, qypeLogTransaction) API is used
together with the <a href="qypestrt.htm">Start Transaction</a> (QYPESTRT,
qypeStartTransaction) API and the <a href="qypeendt.htm">End Transaction</a>
(QYPEENDT, qypeEndTransaction) API to collect performance data for user-defined
transactions. The Log Transaction API is called by an application any time
between the calls to the Start Transaction API and the End Transaction API to
trace the progress of a user-defined transaction.</p>
<p>This API can be used to provide trace type of performance data - collected
by Performance Explorer (PEX). Collection Services ignores this API.</p>
<p>If the Performance Explorer (PEX) is running, this API generates a log
transaction trace record. In addition to the data supplied by the application
in the application trace data parameter, PEX will capture the current values of
performance counters associated with the current thread such as CPU time used,
I/O activity and seize/lock activity. After the End Performance Explorer
(ENDPEX) command is run, the application-supplied data
for this record is written to the QMUDTA field in the QAYPEMIUSR file. The performance counters are written to individual fields in the QAYPEMIUSR and QAYPETIDX files.</p>
<p>See <a href="qypestrt.htm#USAGENOTES">Usage Notes</a> for the Start
Transaction (QYPESTRT, qypeStartTransaction) API for more information.</p>
<br>
<h3>Authorities and Locks</h3>
<dl>
<dt><em>API Public Authority</em></dt>
<dd>*USE</dd>
</dl>
<br>
<h3>Required Parameter Group</h3>
<dl>
<dt><strong>Application identifier</strong></dt>
<dd>INPUT; CHAR(20)
<p>The name of the application. Given that many applications could use this
API, the name should be chosen so that it is unique. Application identifiers
starting with "QIBM_Qccc_", where ccc is a component identifier, are reserved
for IBM use.</p>
</dd>
<dt><strong>Transaction identifier</strong></dt>
<dd>INPUT; BINARY(4) UNSIGNED
<p>Any sort of unique transaction identifier, such as a sequential number. In
order to collect meaningful data, the identifier passed to the Log Transaction
API should be the same as the identifier used in the call to the Start
Transaction API for the same transaction.</p>
</dd>
<dt><strong>Application trace data</strong></dt>
<dd>INPUT; CHAR(*)
<p>Application-defined trace data to be saved by PEX. This can be any data that
the user wants to associate with this transaction - for example, the user ID of
the client performing the transaction, the name of the file being updated by
the transaction, or the account ID being accessed by the transaction. The data
can be up to 3032 bytes long. This data is reported by PEX in the QAYPEMIUSR
file.</p>
</dd>
<dt><strong>Length of application trace data</strong></dt>
<dd>INPUT; BINARY(4) UNSIGNED
<p>The length (in bytes) of application-defined trace data to be saved by PEX.
The value must be between 0 and 3032.</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>Usage Notes</h3>
<p>For the description of how Performance Explorer (PEX) saves and reports
performance data for this API, see <a href="qypestrt.htm#USAGENOTES">Usage
Notes</a> for the Start Transaction API.</p>
<br>
<h3>Error Messages</h3>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<th align="left" valign="top" nowrap>Message ID</th>
<th align="left" valign="top">Error Message Text</th>
</tr>
<tr>
<td align="left" valign="top">CPF3C36 E</td>
<td align="left" valign="top">Number of parameters, &amp;1, entered
for this API was not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C3C E</td>
<td align="left" valign="top">Value for parameter &amp;1 is not valid.</td>
</tr>
</table>
<br>
<hr>
API introduced: V5R2
<hr>
<center>
<table cellpadding="2" cellspacing="2">
<tr align="center">
<td valign="middle" align="center"><a href="qypscsca.htm">Top</a> | <a href=
"perfmgmt.htm">Performance Management APIs</a> | <a href="aplist.htm">APIs by
category</a></td>
</tr>
</table>
</center>
</body>
</html>