313 lines
17 KiB
HTML
313 lines
17 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="reference" />
|
||
|
|
<meta name="DC.Title" content="FFDC dump output description" />
|
||
|
|
<meta name="abstract" content="This information describes the data areas and types of information available in a first-failure data capture (FFDC) dump output." />
|
||
|
|
<meta name="description" content="This information describes the data areas and types of information available in a first-failure data capture (FFDC) dump output." />
|
||
|
|
<meta name="DC.subject" content="first-failure data capture (FFDC), dump output description, description, FFDC dump output" />
|
||
|
|
<meta name="keywords" content="first-failure data capture (FFDC), dump output description, description, FFDC dump output" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1firstf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1firstfail.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="rbal1fdodes" />
|
||
|
|
<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>FFDC dump output description</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1fdodes"><a name="rbal1fdodes"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">FFDC dump output description</h1>
|
||
|
|
<div><p>This information describes the data areas and types of information
|
||
|
|
available in a first-failure data capture (FFDC) dump output. </p>
|
||
|
|
<div class="section"><p>Like the figure in the <a href="rbal1appxffdcdump.htm">A first-failure data capture dump</a>,
|
||
|
|
the following data areas and types of information are available in the FFDC
|
||
|
|
dump output:</p>
|
||
|
|
<div class="p"><ol><li>Each FFDC dump output will differ in content, but the format is generally
|
||
|
|
the same. An index (<strong><span>I</span></strong>) is provided to help you understand
|
||
|
|
the content and location of each section of data.</li>
|
||
|
|
<li>Each section of data is identified by SPACE and a number; for example:
|
||
|
|
SPACE- … 01. The sections of data present in your dump output are dependent
|
||
|
|
on the operation and its progress at the time of failure.</li>
|
||
|
|
<li>Each section of data is given a name; for example SQCA. SQCA is the section
|
||
|
|
name for data from the DB2<sup>®</sup> UDB Query Manager and SQL Development Kit SQL diagnostic
|
||
|
|
area. To locate the SQL diagnostic area data, find SQCA in the index (<strong><span>I</span></strong>).
|
||
|
|
In the sample dump index, SQCA is shown to be in data section 10 (10=SQCA).
|
||
|
|
To view the SQL diagnostic area data, go to the SPACE- 10 heading. </li>
|
||
|
|
<li>There are two basic classes of modules that can be dumped: <ul><li>Application requester (AR) modules</li>
|
||
|
|
<li>Application server (AS) modules</li>
|
||
|
|
</ul>
|
||
|
|
<p>The sample dump output is typical of a dump from an AR module. AR
|
||
|
|
dump outputs typically have a fixed number of data sections identified in
|
||
|
|
the index. (For example, in the sample dump output SPACE- 01 through 16 are
|
||
|
|
listed.) In addition, they have a variable number of other data sections.
|
||
|
|
These sections are not included in the index. (For example, in the sample
|
||
|
|
dump output, SPACE- 17 through 25 are not listed in the index.)</p>
|
||
|
|
<p>Application
|
||
|
|
server dump output is usually simpler because they consist only of a fixed
|
||
|
|
number of data sections, all of which are identified in the index.</p>
|
||
|
|
</li>
|
||
|
|
<li>There are index entries for all data sections whether the data section
|
||
|
|
actually exists in the current dump output or not. For example, in the sample
|
||
|
|
dump output, there is no SPACE- 08. In the index, 08 equals QDTA (query data).
|
||
|
|
The absence of SPACE- 08 means that no query data was returned, so none could
|
||
|
|
be dumped.</li>
|
||
|
|
<li id="rbal1fdodes__rbal1note6"><a name="rbal1fdodes__rbal1note6"><!-- --></a>In the sample dump output, the last entry in the index
|
||
|
|
is <span class="q">"(REST IS CCB, PCBS, SAT, PMAP, RCVB, PER CCB)"</span>. This entry means
|
||
|
|
that SPACE- 17 and upward contain one or more communications control blocks
|
||
|
|
(CCB), each containing: <ul><li>Zero, one, or more path control blocks (SPCB); there is normally just
|
||
|
|
one.</li>
|
||
|
|
<li>Exchange server attributes control block (EXCB)</li>
|
||
|
|
<li>Parser map space</li>
|
||
|
|
<li>Receive buffer for the communications control block</li>
|
||
|
|
</ul>
|
||
|
|
<div class="p">The data section number is increment by one from 17 onward
|
||
|
|
as each control block is dumped. For example, in the sample dump output, data
|
||
|
|
sections SPACE- 17 through SPACE- 21 are for the first data control block
|
||
|
|
dumped (CCB 1), while data sections SPACE- 22 through SPACE- 25 are for the
|
||
|
|
second data control block dumped (CCB 2), as shown here: <dl><dt class="dlterm">17</dt>
|
||
|
|
<dd>CCB (Eyecatcher is :'SCCB:'. For an application server module, the eyecatcher
|
||
|
|
is :'TCCB:'.)</dd>
|
||
|
|
<dt class="dlterm">18</dt>
|
||
|
|
<dd>PCB for CCB 1 (Eyecatcher is :'SPBC:'.)</dd>
|
||
|
|
<dt class="dlterm">19</dt>
|
||
|
|
<dd>SAT for CCB 1 (Eyecatcher is :'EXCB:'.)</dd>
|
||
|
|
<dt class="dlterm">20</dt>
|
||
|
|
<dd>PMAP for CCB 1 (No eyecatcher.)</dd>
|
||
|
|
<dt class="dlterm">21</dt>
|
||
|
|
<dd>RCVB for CCB 1 (No eyecatcher.)</dd>
|
||
|
|
<dt class="dlterm">22</dt>
|
||
|
|
<dd>CCB 2 (Eyecatcher is :'SCCB:'.)</dd>
|
||
|
|
<dt class="dlterm">--</dt>
|
||
|
|
<dd>(No PCB for CCB 2 because the conversation is not active.)</dd>
|
||
|
|
<dt class="dlterm">23</dt>
|
||
|
|
<dd>SAT for CCB 2 (Eyecatcher is :'EXCB:'.)</dd>
|
||
|
|
<dt class="dlterm">24</dt>
|
||
|
|
<dd>PMAP for CCB 2 (No eyecatcher.)</dd>
|
||
|
|
<dt class="dlterm">25</dt>
|
||
|
|
<dd>RCVB for CCB 2 (No eyecatcher.)</dd>
|
||
|
|
<dt class="dlterm"><strong><span>A</span></strong></dt>
|
||
|
|
<dd>Name and release information of the server on which the dump was taken.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>B</span></strong></dt>
|
||
|
|
<dd>Name of job that created the dump output.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>C</span></strong></dt>
|
||
|
|
<dd>Name of module in the operating system suspected of failure.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>D</span></strong></dt>
|
||
|
|
<dd>Name of module that detected the failure.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Symptom string-contents: </h4><dl><dt class="dlterm"><strong><span>E</span></strong></dt>
|
||
|
|
<dd>Message identifier.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>F</span></strong></dt>
|
||
|
|
<dd>Name of module suspected of causing the FFDC dump.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>G</span></strong></dt>
|
||
|
|
<dd>Return code (RC), identifying the point of failure.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The first digit after RC indicates the number of dump files associated
|
||
|
|
with this failure. There can be multiple dump files depending on the number
|
||
|
|
of conversations that were allocated. In the sample dump output, the digit
|
||
|
|
is "1", indicating that this is the first (and possible the only) dump file
|
||
|
|
associated with this failure.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><div class="p">You might have four digits (not zeros) at the rightmost end of
|
||
|
|
the return code that indicate the type of error. <ul><li>The possible codes for errors detected by the AR are: <dl><dt class="dlterm">0001</dt>
|
||
|
|
<dd>Failure occurred in connecting to the remote database</dd>
|
||
|
|
<dt class="dlterm">0002</dt>
|
||
|
|
<dd>More-to-receive indicator was on when it should not have been</dd>
|
||
|
|
<dt class="dlterm">0003</dt>
|
||
|
|
<dd>AR detected an unrecognized object in the data stream received from the
|
||
|
|
AS</dd>
|
||
|
|
<dt class="dlterm">0097</dt>
|
||
|
|
<dd>Error detected by the AR DDM communications manager</dd>
|
||
|
|
<dt class="dlterm">0098</dt>
|
||
|
|
<dd>Conversation protocol error detected by the DDM component of the AR</dd>
|
||
|
|
<dt class="dlterm">0099</dt>
|
||
|
|
<dd>Function check</dd>
|
||
|
|
</dl>
|
||
|
|
</li>
|
||
|
|
<li>The possible codes for errors detected by the AS are: <dl><dt class="dlterm">0099</dt>
|
||
|
|
<dd>Function check</dd>
|
||
|
|
<dt class="dlterm">4415</dt>
|
||
|
|
<dd>Conversational protocol error</dd>
|
||
|
|
<dt class="dlterm">4458</dt>
|
||
|
|
<dd>Agent permanent error</dd>
|
||
|
|
<dt class="dlterm">4459</dt>
|
||
|
|
<dd>Resource limit reached</dd>
|
||
|
|
<dt class="dlterm">4684</dt>
|
||
|
|
<dd>Data stream syntax not valid</dd>
|
||
|
|
<dt class="dlterm">4688</dt>
|
||
|
|
<dd>Command not supported</dd>
|
||
|
|
<dt class="dlterm">4689</dt>
|
||
|
|
<dd>Parameter not supported</dd>
|
||
|
|
<dt class="dlterm">4690</dt>
|
||
|
|
<dd>Value not supported</dd>
|
||
|
|
<dt class="dlterm">4691</dt>
|
||
|
|
<dd>Object not supported</dd>
|
||
|
|
<dt class="dlterm">4692</dt>
|
||
|
|
<dd>Command check</dd>
|
||
|
|
<dt class="dlterm">8706</dt>
|
||
|
|
<dd>Query not open</dd>
|
||
|
|
<dt class="dlterm">8708</dt>
|
||
|
|
<dd>Remote database not accessed</dd>
|
||
|
|
<dt class="dlterm">8711</dt>
|
||
|
|
<dd>Remote database previously accessed</dd>
|
||
|
|
<dt class="dlterm">8713</dt>
|
||
|
|
<dd>Package bind process active</dd>
|
||
|
|
<dt class="dlterm">8714</dt>
|
||
|
|
<dd>FDO:CA descriptor is not valid</dd>
|
||
|
|
<dt class="dlterm">8717</dt>
|
||
|
|
<dd>Abnormal end of unit of work</dd>
|
||
|
|
<dt class="dlterm">8718</dt>
|
||
|
|
<dd>Data and/or descriptor does not match</dd>
|
||
|
|
<dt class="dlterm">8719</dt>
|
||
|
|
<dd>Query previously opened</dd>
|
||
|
|
<dt class="dlterm">8722</dt>
|
||
|
|
<dd>Open query failure</dd>
|
||
|
|
<dt class="dlterm">8730</dt>
|
||
|
|
<dd>Remote database not available</dd>
|
||
|
|
</dl>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<dl><dt class="dlterm"><strong><span>H</span></strong></dt>
|
||
|
|
<dd>SPACE- number identifying a section of data. The number is related to
|
||
|
|
a data section name by the index. Data section names are defined under <strong><span>I</span></strong> below.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>I</span></strong></dt>
|
||
|
|
<dd>An index and definition of SPACE- numbers (defined in <strong><span>H</span></strong>)
|
||
|
|
to help you understand the content and location of each section of data. The
|
||
|
|
order of the different data sections might vary between dump output from different
|
||
|
|
modules. The meaning of the data section names are: <ul><li>AFT: DDM active file table, containing all conversation information.</li>
|
||
|
|
<li>ARDB: Access remote database control block, containing the AR and AS connection
|
||
|
|
information.</li>
|
||
|
|
<li>ARDP: ARD program parameters at start of user space.</li>
|
||
|
|
<li>BDTA: Buffer processing communications area (BPCA) and associated data
|
||
|
|
record from SELECT INTO statement.</li>
|
||
|
|
<li>Bind: SQL bind template</li>
|
||
|
|
<li>BPCA: BPCA structure (without data records)</li>
|
||
|
|
<li>DATA: Data records associated with the BPCA. It is possible that the records
|
||
|
|
in this section do not reflect the total BPCA buffer contents. Already-processed
|
||
|
|
records might not be included.</li>
|
||
|
|
<li>DOFF: Offset within query data stream (QRYDTA) where the error was detected.</li>
|
||
|
|
<li>EICB: Error information control block</li>
|
||
|
|
<li>EMSG: Error message associated with a function check or DDM communications
|
||
|
|
manager error.</li>
|
||
|
|
<li>FCT: DDM function code point (2 bytes)</li>
|
||
|
|
<li>FDOB: FDO:CA descriptor input to the parser in an execute operation.</li>
|
||
|
|
<li>FDTA: FDO:CA data structure consisting of: <ul><li>A four-byte field defining the length of the FDO:CA data stream (FDODTA)</li>
|
||
|
|
<li>The FDODTA</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>HDRS: Communications manager command header stack.</li>
|
||
|
|
<li>IFMT: ARD program input format.</li>
|
||
|
|
<li>INDA: Input SQLDA containing user-defined SQLDA for insert, select, delete,
|
||
|
|
update, open, and execute operations.</li>
|
||
|
|
<li>INDX: The index that maps the data section name to the data section SPACE-
|
||
|
|
code. Not all of the entries in the index have a corresponding data section.
|
||
|
|
The dump data is based on the error that occurs and the progress of the operation
|
||
|
|
at the time of the error. A maximum of 32 entries can be dumped in one spooled
|
||
|
|
file.</li>
|
||
|
|
<li>INST: SQL statement</li>
|
||
|
|
<li>ITKN: Interrupt token.</li>
|
||
|
|
<li>OFMT: ARD program output format.</li>
|
||
|
|
<li>PKGN: Input package name, consistency token and section number.</li>
|
||
|
|
<li>PMAP: Parser map in an AS dump output.</li>
|
||
|
|
<li>PRMS: DDM module input or output parameter structure.</li>
|
||
|
|
<li>PSOP: Input parser options.</li>
|
||
|
|
<li>QDTA: Query data structure consisting of: <ul><li>A four-byte field defining the length of the query data stream (QRYDTA)</li>
|
||
|
|
<li>The QRYDTA</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>RCVB: Received data stream. The contents depend on the
|
||
|
|
following conditions: <ul><li>If the dump occurs on the application server, the section contains the
|
||
|
|
DDM request data that was sent from the application requester.</li>
|
||
|
|
<li>If the dump occurs on the application requester, the section contains
|
||
|
|
the DDM reply data that was sent from the application server. If this section
|
||
|
|
is not present, it is possible the received data might be found in the receive
|
||
|
|
buffer in the variable part of the dump.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>RDBD: Relational database directory.</li>
|
||
|
|
<li>RFMT: Record format structure.</li>
|
||
|
|
<li>RMTI: Remote location information in the commitment control block.</li>
|
||
|
|
<li>RTDA: Returned SQLDA (from ARD program).</li>
|
||
|
|
<li>SMCB: DDM source master control block, containing pointers to other DDM
|
||
|
|
connection control blocks and internal DDM control blocks.</li>
|
||
|
|
<li>SNDB: Send data stream. The contents depend on the following conditions:
|
||
|
|
<ul><li>If the dump occurs on the application requester, the buffer contains the
|
||
|
|
DDM request that was sent to the application server or that was being prepared
|
||
|
|
to send. <p>Note the four bytes of zeros that are at the beginning of SPACE-
|
||
|
|
05 in the example. When zeros are present, they are not part of the data stream.
|
||
|
|
They represent space in the buffer that is used only in the case that a DDM
|
||
|
|
large object has to be sent with a DDM request. The DDM request stream is
|
||
|
|
shifted left four bytes in that case.</p>
|
||
|
|
</li>
|
||
|
|
<li>If the dump occurs on the application server, the buffer contains the
|
||
|
|
DDM reply data that was being prepared to send to the application requester.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>SQCA: Output SQL diagnostic area being returned to the user. </li>
|
||
|
|
<li>SQDA: SQLDA built by the FDO:CA parser.</li>
|
||
|
|
<li>TBNM: Input remote database table name.</li>
|
||
|
|
<li>TMCB: Target main control block.</li>
|
||
|
|
<li>TSLK: Target or source connection control block, containing pointers to
|
||
|
|
the DDM active file table and other internal DDM control blocks.</li>
|
||
|
|
<li>VARS: Local variables for the module being dumped.</li>
|
||
|
|
<li>WRCA: Warning SQLCA returned only for an open operation (OPNQRYRM).</li>
|
||
|
|
<li>XSAT: Exchange server attributes control block.</li>
|
||
|
|
<li>Remainder: Multiple conversation control blocks for all the DDM conversations
|
||
|
|
for the job at the time of the error. Each conversation control block contains
|
||
|
|
the following items: <ul><li>Path control blocks, containing information about an established conversation.
|
||
|
|
There can be multiple path control blocks for one conversation control block.</li>
|
||
|
|
<li>One exchange server information control block, containing information
|
||
|
|
about the application requester and application server.</li>
|
||
|
|
<li>One DDM parser map area, containing the locations and values for all the
|
||
|
|
DDM commands, objects, and replies.</li>
|
||
|
|
<li>One receive buffer, containing the requested data stream received by the
|
||
|
|
application server.</li>
|
||
|
|
</ul>
|
||
|
|
<p>The data section number is incremented by one as each control block
|
||
|
|
is dumped.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm"><strong><span>J</span></strong></dt>
|
||
|
|
<dd>The eyecatcher area. Information identifying the type of data in some
|
||
|
|
of the areas that were dumped.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>K</span></strong></dt>
|
||
|
|
<dd>The logical unit of work identifier (LUWID) for the conversation in progress
|
||
|
|
at the time of the failure can be found in the access RDB control block. This
|
||
|
|
data area is identified by the string 'ARDB' in the FFDC index. In this example,
|
||
|
|
it is in SPACE- 07. The LUWID begins at offset 180. The network identifier
|
||
|
|
(NETID) is APPC. A period separates it from the logical unit (LU) name, RCHAS378,
|
||
|
|
which follows. Following the LU name is the six-byte LUW instance number <span>X'A7CCA7541372'</span>.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1firstf.htm" title="The iSeries server provides a way for you to capture and report error information for the distributed relational database. This function is called first-failure data capture (FFDC).">First-failure data capture</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rbal1firstfail.htm" title="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.">Find first-failure data capture data</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|