66 lines
4.5 KiB
HTML
66 lines
4.5 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="Problem handling" />
|
||
|
<meta name="abstract" content="The primary strategy for capturing and reporting error information for the distributed database function is called first failure data capture (FFDC)." />
|
||
|
<meta name="description" content="The primary strategy for capturing and reporting error information for the distributed database function is called first failure data capture (FFDC)." />
|
||
|
<meta name="DC.subject" content="distributed relational database, problem handling, first failure data capture (FFDC), error determination, in distributed relational database, first failure data capture (FFDC), FFDC (first failure data capture)" />
|
||
|
<meta name="keywords" content="distributed relational database, problem handling, first failure data capture (FFDC), error determination, in distributed relational database, first failure data capture (FFDC), FFDC (first failure data capture)" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbafydrda.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../rzala/rzalakickoff.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="rbafyprobhandle" />
|
||
|
<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>Problem handling</title>
|
||
|
</head>
|
||
|
<body id="rbafyprobhandle"><a name="rbafyprobhandle"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Problem handling</h1>
|
||
|
<div><p>The primary strategy for capturing and reporting error information
|
||
|
for the distributed database function is called <dfn class="term">first failure
|
||
|
data capture (FFDC)</dfn>.</p>
|
||
|
<div class="section"><p>The purpose of FFDC support is to provide accurate information
|
||
|
about errors detected in the DDM components of the <span class="keyword">i5/OS™</span> system
|
||
|
from which an APAR (Authorized Program Analysis Report) can be created. By
|
||
|
means of this function, key structures and the DDM data stream are automatically
|
||
|
dumped to a spool file. The first 1024 bytes of the error information are
|
||
|
also logged in the system error log. This automatic dumping of error information
|
||
|
about the first occurrence of an error means that the failure must not need
|
||
|
to be recreated to be reported by the customer. FFDC is active in both the
|
||
|
application requester and application server functions of the <span class="keyword">i5/OS</span> DDM
|
||
|
component. However, for the FFDC data to be logged, the system value QSFWERRLOG
|
||
|
must be set to *LOG. </p>
|
||
|
<div class="note"><span class="notetitle">Note:</span> Not all negative SQLCODEs are dumped; only
|
||
|
those that can be used to produce an APAR are dumped. For more information
|
||
|
about handling problems on distributed relational database operations, see
|
||
|
the <cite>Distributed Database Problem Determination Guide</cite> SC26-4782</div>
|
||
|
</div>
|
||
|
<div class="section"><p>When an SQL error is detected, an SQLCODE with a corresponding
|
||
|
SQLSTATE is returned in the SQLCA. </p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafydrda.htm" title="A distributed relational database consists of a set of SQL objects that are spread across interconnected computer systems.">Distributed relational database function and SQL</a></div>
|
||
|
</div>
|
||
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
<div><a href="../rzala/rzalakickoff.htm">SQL messages and codes</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|