63 lines
5.0 KiB
HTML
63 lines
5.0 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="concept" />
|
|
<meta name="DC.Title" content="Job tracing" />
|
|
<meta name="abstract" content="Sometimes a problem cannot be tracked to a specific program. In these cases, Start Trace (STRTRC) and Trace Job (TRCJOB) commands can be used for tracing module flow, i5/OS data acquisition and CL commands executed." />
|
|
<meta name="description" content="Sometimes a problem cannot be tracked to a specific program. In these cases, Start Trace (STRTRC) and Trace Job (TRCJOB) commands can be used for tracing module flow, i5/OS data acquisition and CL commands executed." />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1gdrf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1tracejob.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1starttrc.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1stsrvjb.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1commt.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="rbal1jobt" />
|
|
<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>Job tracing</title>
|
|
</head>
|
|
<body id="rbal1jobt"><a name="rbal1jobt"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Job tracing</h1>
|
|
<div><p>Sometimes a problem cannot be tracked to a specific program. In
|
|
these cases, <span class="cmdname">Start Trace (STRTRC)</span> and <span class="cmdname">Trace Job
|
|
(TRCJOB)</span> commands can be used for tracing module flow, <span class="keyword">i5/OS™</span> data acquisition and CL commands
|
|
executed.</p>
|
|
<p>These tools should be used when the problem analysis procedures do not
|
|
supply sufficient information about the problem. For distributed database
|
|
applications, these commands are also useful for capturing distributed database
|
|
requests and response data streams.</p>
|
|
<p>If you need to get a job trace of the application server job, you need
|
|
to start a service job at the server.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbal1tracejob.htm">Trace job</a></strong><br />
|
|
The Trace Job (TRCJOB) command is the older of the two tracing tools. As the trace records are generated, the records are stored in an internal trace storage area. When the trace is ended, the trace records can be written to a spooled printer file (QPSRVTRC) or directed to a database output file.</li>
|
|
<li class="ulchildlink"><strong><a href="rbal1starttrc.htm">Start trace</a></strong><br />
|
|
You can also use the Start Trace (STRTRC) command to perform traces. The STRTRC command is more flexible and less intrusive than the Trace Job (TRCJOB) command. It allows tracing across multiple jobs and shows more in-depth details about the module flow.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1gdrf.htm" title="This topic collection describes the kinds of data that you can print to help you diagnose a problem in a distributed relational database on iSeries servers.">Get data to report a failure</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rbal1stsrvjb.htm" title="When an application uses Distributed Relational Database Architecture (DRDA), the SQL statements are run in the application server job. Because of this, you might need to start debug or a job trace for the application server job that is running on the i5/OS operating system. The technique for doing this differs based on the use of either Advanced Program-to-Program Communication (APPC) or TCP/IP.">Start a service job to diagnose application server problems</a></div>
|
|
<div><a href="rbal1commt.htm" title="If you get a message in the CPF3Exx range or the CPF91xx range when using Distributed Relational Database Architecture (DRDA) to access a distributed relational database, you should run a communications trace.">Communications trace</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |