71 lines
4.3 KiB
HTML
71 lines
4.3 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="Update applications to use the SQL diagnostics area" />
|
||
|
|
<meta name="abstract" content="You might consider changing your applications to use the SQL diagnostics area instead of the SQL communications area (SQLCA), because the SQL diagnostics area provides some significant advantages over the SQLCA." />
|
||
|
|
<meta name="description" content="You might consider changing your applications to use the SQL diagnostics area instead of the SQL communications area (SQLCA), because the SQL diagnostics area provides some significant advantages over the SQLCA." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajpdiagnostics.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="rzajpupdiag" />
|
||
|
|
<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>Update applications to use the SQL diagnostics area</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzajpupdiag"><a name="rzajpupdiag"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Update applications to use the SQL diagnostics area</h1>
|
||
|
|
<div><p><span>You might consider changing your applications
|
||
|
|
to use the SQL diagnostics area instead of the SQL communications area (SQLCA),
|
||
|
|
because the SQL diagnostics area provides some significant advantages over
|
||
|
|
the SQLCA.</span></p>
|
||
|
|
<div class="section"><p>One of the best reasons is that the SQLERRM field in the SQLCA
|
||
|
|
is only 70 bytes in length. This is often insufficient for returning meaningful
|
||
|
|
error information to the calling application. Additional reasons for considering
|
||
|
|
the SQL diagnostics area are multiple row operations, and long column and
|
||
|
|
object names. Reporting even simple warnings is sometimes difficult within
|
||
|
|
the restrictions of the 136 byte SQLCA. Quite often, the returned tokens are
|
||
|
|
truncated to fit the restrictions of the SQLCA.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Current applications include the SQLCA definition by using the
|
||
|
|
following: </p>
|
||
|
|
<pre>EXEC SQL <strong>INCLUDE SQLCA</strong>; /* Existing SQLCA */</pre>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>With the conversion to using the SQL diagnostics area, the application
|
||
|
|
would first declare a stand-alone SQLSTATE variable: </p>
|
||
|
|
<pre>char SQLSTATE[6]; /* Stand-alone sqlstate */</pre>
|
||
|
|
<p>And
|
||
|
|
possibly a stand-alone SQLCODE variable:</p>
|
||
|
|
<pre> long int SQLCODE; /* Stand-alone sqlcode */</pre>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The completion status of the SQL statement is verified by checking
|
||
|
|
the stand-alone SQLSTATE variable. If upon the completion of the current SQL
|
||
|
|
statement, the application chooses to retrieve diagnostics, the application
|
||
|
|
would run the SQL GET DIAGNOSTICS statement: </p>
|
||
|
|
<pre>char hv1[256];
|
||
|
|
long int hv2;
|
||
|
|
|
||
|
|
EXEC SQL <strong>GET DIAGNOSTICS</strong> :hv1 = COMMAND_FUNCTION,
|
||
|
|
:hv2 = COMMAND_FUNCTION_CODE;</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajpdiagnostics.htm" title="The SQL diagnostics area is used to keep the returned information for an SQL statement that has been run in a program. It contains all the information that is available to you as an application programmer through the SQLCA.">Use the SQL diagnostics area</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|