102 lines
6.5 KiB
HTML
102 lines
6.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="Can I use a library list for resolving unqualified table and view names?" />
|
||
|
|
<meta name="abstract" content="The iSeries server supports a limited capability to use the operating system naming option when accessing DB2 Universal Database for iSeries data from a non-iSeries DRDA client program such as those that use the DB2 Universal Database for Linux, UNIX and Windows product." />
|
||
|
|
<meta name="description" content="The iSeries server supports a limited capability to use the operating system naming option when accessing DB2 Universal Database for iSeries data from a non-iSeries DRDA client program such as those that use the DB2 Universal Database for Linux, UNIX and Windows product." />
|
||
|
|
<meta name="DC.subject" content="Generic bind options, Bind options" />
|
||
|
|
<meta name="keywords" content="Generic bind options, Bind options" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1xplat.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="rbal1faquselibrarylist" />
|
||
|
|
<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>Can I use a library list for resolving unqualified table and view names?</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1faquselibrarylist"><a name="rbal1faquselibrarylist"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Can I use a library list for resolving unqualified table and view names?</h1>
|
||
|
|
<div><p>The iSeries™ server
|
||
|
|
supports a limited capability to use the operating system naming option when
|
||
|
|
accessing <span class="keyword">DB2 Universal Database™ for iSeries</span> data from
|
||
|
|
a non-iSeries DRDA<sup>®</sup> client
|
||
|
|
program such as those that use the <span>DB2 Universal Database for Linux<sup>®</sup>, UNIX<sup>®</sup> and Windows<sup>®</sup></span> product.</p>
|
||
|
|
<div class="section"><p>Previously, only the SQL naming option has been available when
|
||
|
|
connecting from unlike DRDA clients. System naming changes several characteristics
|
||
|
|
of DB2<sup>®</sup> UDB
|
||
|
|
for iSeries.
|
||
|
|
For example:</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"> <ol><li>The library list is searched for resolving unqualified table and view
|
||
|
|
names.</li>
|
||
|
|
<li>When running a CREATE SQL statement, an unqualified object will be created
|
||
|
|
in the current library.</li>
|
||
|
|
<li>A slash (/) instead of a period (.) is used to separate qualified objects'
|
||
|
|
names from the library or collection in which they reside.</li>
|
||
|
|
<li>Certain authorization characteristics are changed.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>For details, read about server naming in the SQL reference. For
|
||
|
|
more information about the implications regarding authorization, see <a href="rbal1plan.htm#rbal1plan">Planning and design</a>.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p id="rbal1faquselibrarylist__rbal1genbind"><a name="rbal1faquselibrarylist__rbal1genbind"><!-- --></a><span>DB2 Universal Database for Linux, UNIX and Windows</span> supports
|
||
|
|
the specification of generic bind options on two of its program preparation
|
||
|
|
commands, the precompile (PREP) command and the (BIND) command. <span class="keyword">i5/OS™</span> naming
|
||
|
|
can be specified on either of them as in the following examples drawn from
|
||
|
|
a Windows batch
|
||
|
|
file: </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>For <span>DB2 Universal Database for Linux, UNIX and Windows</span>,
|
||
|
|
Version 8 and later: </p>
|
||
|
|
<pre>DB2 PREP %1.SQC BINDFILE OS400NAMING SYSTEM ...
|
||
|
|
DB2 BIND %1.BND OS400NAMING SYSTEM ...</pre>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>For <span>DB2 Universal Database for Linux, UNIX and Windows</span>,
|
||
|
|
version earlier than Version 8: </p>
|
||
|
|
<pre>DB2 PREP %1.SQC BINDFILE GENERIC 'OS400NAMING SYSTEM' ...
|
||
|
|
DB2 BIND %1.BND GENERIC 'OS400NAMING SYSTEM' ...</pre>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Note that on the Windows development platform, single
|
||
|
|
quotation marks are used around the generic option name/value pair. On an AIX<sup>®</sup> or UNIX platform,
|
||
|
|
quotation marks should be used.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><div class="note"><span class="notetitle">Note:</span> For OS/400<sup>®</sup> V4R5 and V5R1, the name of the option is AS400NAMING,
|
||
|
|
not OS400NAMING.</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The only valid value for the OS400NAMING option besides SYSTEM
|
||
|
|
is SQL, which is the default value, and the only possible option from a non-<span class="keyword">iSeries</span> client prior to the introduction
|
||
|
|
of this feature.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>If you use the OS400NAMING option on the (BIND) command but not
|
||
|
|
on the (PREP) command, then you might need to code a parameter on the (PREP)
|
||
|
|
command that indicates a bind file should be created in spite of SQL errors
|
||
|
|
detected by the server platform. In the case of <span>DB2
|
||
|
|
Universal Database™ for Linux, UNIX and Windows</span>, use the SQLERROR CONTINUE
|
||
|
|
parameter for this purpose. The capability is described as "limited" because
|
||
|
|
in certain situations, the client-side software might parse an SQL statement
|
||
|
|
intended for execution on the remote server. If a slash instead of a period
|
||
|
|
is used to separate a schema ID from a table ID, as is required for server
|
||
|
|
naming, the statement might be rejected as having improper syntax. </p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1xplat.htm" title="This topic collection concentrates on describing iSeries support for distributed relational databases in a network of iSeries servers (a like environment).">User FAQs</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|