107 lines
7.8 KiB
HTML
107 lines
7.8 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="task" />
|
||
|
|
<meta name="DC.Title" content="Find first-failure data capture data" />
|
||
|
|
<meta name="abstract" content="This topic describes tips on how to locate first-failure data capture (FFDC) data on an iSeries server. The information is most useful if the failure causing the FFDC data output occurred on the application server (AS). The FFDC data for an application requester (AR) can usually be found in one of the spooled files associated with the job running the application program." />
|
||
|
|
<meta name="description" content="This topic describes tips on how to locate first-failure data capture (FFDC) data on an iSeries server. The information is most useful if the failure causing the FFDC data output occurred on the application server (AS). The FFDC data for an application requester (AR) can usually be found in one of the spooled files associated with the job running the application program." />
|
||
|
|
<meta name="DC.subject" content="finding first-failure data capture data, first-failure data capture (FFDC), data capture, FFDC, (FFDC) first-failure data capture, interpreting, FFDC data from the error log, FFDC data, error log" />
|
||
|
|
<meta name="keywords" content="finding first-failure data capture data, first-failure data capture (FFDC), data capture, FFDC, (FFDC) first-failure data capture, interpreting, FFDC data from the error log, FFDC data, error log" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1problem.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1fdodes.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/dspmsg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/wrkprb.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/strsst.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="rbal1firstfail" />
|
||
|
|
<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>Find first-failure data capture data</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1firstfail"><a name="rbal1firstfail"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Find first-failure data capture data</h1>
|
||
|
|
<div><p>This topic describes tips on how to locate first-failure data capture
|
||
|
|
(FFDC) data on an <span class="keyword">iSeries™ server</span>.
|
||
|
|
The information is most useful if the failure causing the FFDC data output
|
||
|
|
occurred on the application server (AS). The FFDC data for an application
|
||
|
|
requester (AR) can usually be found in one of the spooled files associated
|
||
|
|
with the job running the application program.</p>
|
||
|
|
<div class="section"><div class="note"><span class="notetitle">Note:</span> No FFDC data is produced unless the QSFWERRLOG system value
|
||
|
|
is set to *LOG.</div>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span>Execute a <span class="cmdname">Display Messages (DSPMSG)</span> QSYSOPR
|
||
|
|
command and look for a <samp class="codeph">Software problem detected in Qccxyyyy</samp> message
|
||
|
|
in the QSYSOPR message log. (<samp class="codeph">cc</samp> in the program name is usually
|
||
|
|
RW, but could be CN or SQ.) The presence of this message indicates that FFDC
|
||
|
|
data was produced. You can use the help key to get details on the message.
|
||
|
|
The message help gives you the problem ID, which you can use to identify the
|
||
|
|
problem in the list presented by the <span class="cmdname">Work with Problems (WRKPRB)</span> command.
|
||
|
|
You might be able to skip this step because the problem record, if it exists,
|
||
|
|
might be at or near the top of the list.</span></li>
|
||
|
|
<li class="stepexpand"><span>Enter the <span class="cmdname">Work with Problems (WRKPRB)</span> command
|
||
|
|
and specify the program name (Qccxyyyy) from the <samp class="codeph">Software problem
|
||
|
|
detected in Qccxyyyy</samp> message. Use the program name to filter out
|
||
|
|
unwanted list items. When a list of problems is presented, specify option
|
||
|
|
5 on the line containing the problem ID to get more problem details, such
|
||
|
|
as symptom string and error log ID.</span></li>
|
||
|
|
<li class="stepexpand"><span>When you have the error log ID, enter the <span class="cmdname">Start System
|
||
|
|
Service Tools (STRSST)</span> command.</span> On the first screen,
|
||
|
|
select <samp class="codeph">Start a service tool</samp>. On the next screen, enter 1
|
||
|
|
to select <samp class="codeph">Error log utility</samp>. On the next screen, enter 2
|
||
|
|
to select <samp class="codeph">Display or print by error log ID</samp>. In the next screen,
|
||
|
|
you can:<ul><li>Enter the error log ID.</li>
|
||
|
|
<li>Enter Y to get the hexadecimal display.</li>
|
||
|
|
<li>Select the Print or Display option.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"> <p>The Display option gives 16 bytes per line instead of 32. This
|
||
|
|
can be useful for online viewing and printing screens on an 80-character workstation
|
||
|
|
printer. If you choose the Display option, use F6 to see the hexadecimal data
|
||
|
|
after you press Enter.</p>
|
||
|
|
<p>The hexadecimal data contains the first one KB
|
||
|
|
of the FFDC dump data, preceded by some other data. The start of the FFDC
|
||
|
|
data is identified by the FFDC data index. The name of the target job (if
|
||
|
|
this is on the application server) is before the data index. If the FFDC dump
|
||
|
|
spool file has not been deleted, use this fully qualified job name to find
|
||
|
|
the spool file. If the spool file is missing, either:</p>
|
||
|
|
<ul><li>Use the first one KB of the dump stored in the error log.</li>
|
||
|
|
<li>Re-create the problem if the one KB of FFDC data is insufficient.</li>
|
||
|
|
</ul>
|
||
|
|
<p>When interpreting FFDC data from the error log, the FFDC data in the
|
||
|
|
error log is not formatted for reading as well as the data in the spooled
|
||
|
|
files. Each section of the FFDC dump in the error log is prefixed by a four-byte
|
||
|
|
header. The first two bytes of the header are the length of the following
|
||
|
|
section (not counting the prefix). The second two bytes, which are the section
|
||
|
|
number, correspond to the section number in the index.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<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 class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbal1fdodes.htm" title="This information describes the data areas and types of information available in a first-failure data capture (FFDC) dump output.">FFDC dump output description</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../cl/dspmsg.htm">Display Messages (DSPMSG) command</a></div>
|
||
|
|
<div><a href="../cl/wrkprb.htm">Work with Problem (WRKPRB) command</a></div>
|
||
|
|
<div><a href="../cl/strsst.htm">Start System Service Tools (STRSST) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|