ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddp_5.4.0.1/rbal1appprob.htm

64 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="concept" />
<meta name="DC.Title" content="Application problems" />
<meta name="abstract" content="The best time to handle a problem with an application is before it goes into production. However, it is impossible to anticipate all the conditions that will exist for an application when it gets into general use." />
<meta name="description" content="The best time to handle a problem with an application is before it goes into production. However, it is impossible to anticipate all the conditions that will exist for an application when it gets into general use." />
<meta name="DC.subject" content="problem handling, application problems, application program, handling problems, SQLCODE, SQLSTATE, SQL program" />
<meta name="keywords" content="problem handling, application problems, application program, handling problems, SQLCODE, SQLSTATE, SQL program" />
<meta name="DC.Relation" scheme="URI" content="rbal1problem.htm" />
<meta name="DC.Relation" scheme="URI" content="rbal1list.htm" />
<meta name="DC.Relation" scheme="URI" content="rbal1sqlc.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="rbal1appprob" />
<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>Application problems</title>
</head>
<body id="rbal1appprob"><a name="rbal1appprob"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Application problems</h1>
<div><p>The best time to handle a problem with an application is before
it goes into production. However, it is impossible to anticipate all the conditions
that will exist for an application when it gets into general use.</p>
<p>The job log of either the application requester (AR) or the application
server (AS) can tell you that a package failed; the listings of the program
or the package can tell you why it failed. The SQL compilers provide diagnostic
tests that show the SQLCODEs and SQLSTATEs generated by the precompile process
on the diagnostic listing. </p>
<p>For Integrated
Language Environment<sup>®</sup> (ILE) precompiles, you can optionally specify OPTION(*XREF)
and OUTPUT(*PRINT) to print a precompile source and cross-reference listing.
For non-ILE precompiles, you can optionally specify *SOURCE and *XREF on the
OPTIONS parameter of the Create SQL program (CRTSQL<em>xxx</em>) commands to
print a precompile source and cross-reference listings.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbal1list.htm">Listings</a></strong><br />
The listing from the Create SQL program (CRTSQL<em>xxx</em>) command
provides these kinds of information.</li>
<li class="ulchildlink"><strong><a href="rbal1sqlc.htm">SQLCODEs and SQLSTATEs</a></strong><br />
Program interfaces using SQL return error information to the application program when an error occurs. SQLSTATEs and their corresponding SQLCODEs are returned to the application program in either the SQL communication area (SQLCA) or the SQL diagnostic area.</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>