80 lines
5.6 KiB
HTML
80 lines
5.6 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="Get data to report a failure" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.subject" content="getting data to report a failure, data, failure, failure data" />
|
||
|
|
<meta name="keywords" content="getting data to report a failure, data, failure, failure data" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1problem.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1pjl.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1findjl.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1pel.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1jobt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1commt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1papptrace.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="rbal1gdrf" />
|
||
|
|
<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>Get data to report a failure</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1gdrf"><a name="rbal1gdrf"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Get data to report a failure</h1>
|
||
|
|
<div><p>This topic collection describes the kinds of data that you can
|
||
|
|
print to help you diagnose a problem in a distributed relational database
|
||
|
|
on <span class="keyword">iSeries™ server</span>s.</p>
|
||
|
|
<p>This data is produced by the <span class="keyword">i5/OS™</span> licensed
|
||
|
|
program. You can also use system operator messages and the application
|
||
|
|
program (along with its data) to diagnose problems.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1pjl.htm">Print a job log</a></strong><br />
|
||
|
|
Every job on the <span class="keyword">iSeries server</span> has
|
||
|
|
a job log that contains information related to requests entered for that job.
|
||
|
|
When a user is having a problem at an application requester (AR),
|
||
|
|
the information in the job log might be helpful in diagnosing the problem.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1findjl.htm">Find job logs from TCP/IP server prestart jobs</a></strong><br />
|
||
|
|
When the connection ends that is serviced by one of the QRWTSRVR prestart jobs associated with the distributed data management (DDM) TCP/IP server, the prestart job is recycled for use by another connection. When this happens, the job log associated with the ended connection is cleared.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1pel.htm">Print the product activity log</a></strong><br />
|
||
|
|
The Product Activity Log on the <span class="keyword">iSeries server</span> is
|
||
|
|
a record of machine checks, device errors, and tape statistics.
|
||
|
|
It also contains FFDC information including the first 1000 bytes of each FFDC
|
||
|
|
dump. By reviewing these errors you might be able to determine the nature
|
||
|
|
of a problem.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1jobt.htm">Job tracing</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1commt.htm">Communications trace</a></strong><br />
|
||
|
|
If you get a message in the CPF3Exx range or the CPF91xx range
|
||
|
|
when using Distributed
|
||
|
|
Relational Database Architecture™ (DRDA<sup>®</sup>) to access a distributed relational
|
||
|
|
database, you should run a communications trace.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1papptrace.htm">TCP/IP communications trace</a></strong><br />
|
||
|
|
One of the uses of the trace tool is to show the clear text of a transmission in an environment where the data is encrypted.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1problem.htm" title="When a problem occurs accessing a distributed relational database, it is the job of the administrator to determine the nature of the problem and whether it is a problem with the application or a problem with the local or remote system.">Troubleshooting</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|