184 lines
12 KiB
HTML
184 lines
12 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="Database restrictions" />
|
||
|
|
<meta name="abstract" content="The following restrictions apply to using the iSeries Access for Web database support in a Web application server environment." />
|
||
|
|
<meta name="description" content="The following restrictions apply to using the iSeries Access for Web database support in a Web application server environment." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzammhdatabase.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2003, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2003, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rdatabase" />
|
||
|
|
<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>Database restrictions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rdatabase"><a name="rdatabase"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Database restrictions</h1>
|
||
|
|
<div><p>The following restrictions apply to using the iSeries™ Access
|
||
|
|
for Web database support in a Web application server environment.</p>
|
||
|
|
<div class="section"><dl><dt class="dlterm">General</dt>
|
||
|
|
<dd>iSeries Access
|
||
|
|
for Web only supports using the IBM<sup>®</sup> Toolbox for Java™ JDBC driver, to access the database
|
||
|
|
server. Although other drivers might work, this is an unsupported and untested
|
||
|
|
environment.<p><img src="./delta.gif" alt="Start of change" />The iSeries Access for Web preferred language
|
||
|
|
setting is not used on database connections. Therefore, all messages received
|
||
|
|
from the database server will be in the language derived from the <samp class="codeph">LANGID</samp> and <samp class="codeph">CNTRYID</samp> of
|
||
|
|
the user profile used to start the WebSphere<sup>®</sup> Application Server.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Tables</dt>
|
||
|
|
<dd>The table list returns relational database tables, aliases, materialized
|
||
|
|
query tables, and views. Non-relational database tables are not returned.<dl><dt class="dlterm">Insert table records restrictions</dt>
|
||
|
|
<dd><ul><li><img src="./delta.gif" alt="Start of change" />Insert does not support binary large object (BLOB), integer
|
||
|
|
with scale, or ROWID column types. Insert does support the character large
|
||
|
|
object (CLOB) column type, however, entering a very large value could potentially
|
||
|
|
consume all of the browser's memory. All other column types, supported by
|
||
|
|
the iSeries server,
|
||
|
|
are supported by Insert.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li>Insert only supports setting the URL portion of a datalink.</li>
|
||
|
|
<li>Insert does not support inserting a null column value, unless the default
|
||
|
|
value for the field is null and the field value is left unchanged.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Update table records restrictions</dt>
|
||
|
|
<dd><ul><li><img src="./delta.gif" alt="Start of change" />Update does not support binary large object (BLOB), integer
|
||
|
|
with scale, or ROWID column types. Update does support the character large
|
||
|
|
object (CLOB) column type, however, entering a very large value could potentially
|
||
|
|
consume all of the browser's memory. All other column types, supported by
|
||
|
|
the iSeries server,
|
||
|
|
are supported by Update.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li>Update only supports setting the URL portion of a datalink.</li>
|
||
|
|
<li>Update does not provide a way to insert null column values. However, if
|
||
|
|
a column has a null value and the field is left blank, the column value will
|
||
|
|
remain null. </li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Run SQL</dt>
|
||
|
|
<dd>You cannot run a saved MS Excel 3 or MS Excel 4 request from a Netscape
|
||
|
|
browser, if you have the NCompass DocActive plug-in installed. You can run
|
||
|
|
these requests dynamically, using the Run SQL button.<p>On Windows<sup>®</sup> 2000
|
||
|
|
using Internet Explorer, if you have Microsoft<sup>®</sup> Excel installed and you
|
||
|
|
try to write your results to MS Excel 3, MS Excel 4 or MS Excel XML, you will
|
||
|
|
be prompted to logon to the iSeries server again. This will cause an additional
|
||
|
|
license to be used. This only happens the first time you try to load an Excel
|
||
|
|
file into the browser. As an alternative, you could save the request without
|
||
|
|
running it, run the saved request, and redirect the results to a file. This
|
||
|
|
is done by right-clicking on the Run link and choosing the Save Target As
|
||
|
|
option. After saving the SQL output file, you could load it using Microsoft Excel
|
||
|
|
or some other application.</p>
|
||
|
|
<p>If you choose PDF as the output type and
|
||
|
|
the SQL statement generates a very large number of columns, the resulting
|
||
|
|
output might be too compressed to read, or might be a blank page. In this
|
||
|
|
case, use a different page size, choose a different output type, or modify
|
||
|
|
the SQL statement to return a subset of the columns.</p>
|
||
|
|
<p>If you are using
|
||
|
|
the Opera browser and your output contains very long column data, your data
|
||
|
|
may be truncated when displayed.</p>
|
||
|
|
<p>If you use Microsoft Internet Explorer, choose
|
||
|
|
PDF as the output type, and get a blank page instead of the SQL output, try
|
||
|
|
one of the following circumventions: </p>
|
||
|
|
<ul><li>Ensure you have the installed the latest version of Microsoft Internet
|
||
|
|
Explorer.</li>
|
||
|
|
<li>Instead of running the request directly from Run SQL, save the request
|
||
|
|
and use the Run action from My Requests.</li>
|
||
|
|
<li>Change your Adobe Acrobat Reader configuration to display the reader in
|
||
|
|
a separate window, instead of within the browser.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Restrictions with the character large object (CLOB) column type</dt>
|
||
|
|
<dd><ul><li>Output types with a maximum cell size, such as Microsoft Excel and Lotus<sup>®</sup> 1-2-3<sup>®</sup> version
|
||
|
|
1, will truncate the data if it exceeds the maximum cell size.</li>
|
||
|
|
<li>Other output types will not truncate the data, however, retrieving very
|
||
|
|
large values could potentially consume all of the browser's memory. </li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">SQL wizard</dt>
|
||
|
|
<dd><ul><li>Only single table selects are supported.</li>
|
||
|
|
<li>Nested conditions are not supported.</li>
|
||
|
|
<li>Building conditions is supported for the column types supported by the iSeries,
|
||
|
|
with the following exceptions: Binary large objects (BLOBs), Character large
|
||
|
|
objects (CLOBs), and Datalinks.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Copy data to table</dt>
|
||
|
|
<dd>When using the iSeries Access for Web Extensible Markup Language
|
||
|
|
(XML) document format to copy data to a table on the iSeries server, the document must be
|
||
|
|
the same XML format as generated by Run SQL. An embedded schema is required
|
||
|
|
only if the document is set to Validate document with its schema.<p><img src="./delta.gif" alt="Start of change" />In
|
||
|
|
order to copy an OpenDocument spreadsheet file, the file must be in package
|
||
|
|
format and must not be compressed or encrypted. <img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />When a
|
||
|
|
saved request is edited or run, the file name is not automatically specified
|
||
|
|
in the <span class="uicontrol">Copy Data to Table</span> form to protect the data
|
||
|
|
on your workstation. The original file name is shown beneath the <span class="uicontrol">File
|
||
|
|
to Copy</span> section. This file name does not include path information
|
||
|
|
when the browser is run from the Linux<sup>®</sup> operating system.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">My requests</dt>
|
||
|
|
<dd>When a shortcut is created the connection information is stored directly
|
||
|
|
with a shortcut. Therefore, when the connection in the original request is
|
||
|
|
changed, the shortcut does not pick up the new connection. </dd>
|
||
|
|
<dt class="dlterm">Import request</dt>
|
||
|
|
<dd>Importing a request containing a reference to a file member will result
|
||
|
|
in the member being removed from the file name. iSeries Access for Web will only provide
|
||
|
|
access to the default member of a file (table).<p>Certain Data Transfer From AS/400<sup>®</sup> statements
|
||
|
|
cannot be converted into statements that can be modified by the SQL Wizard.
|
||
|
|
The SQL Wizard does not support building or editing SQL statements containing <samp class="codeph">GROUP
|
||
|
|
BY</samp>, <samp class="codeph">HAVING</samp> or <samp class="codeph">JOIN BY</samp> clauses.
|
||
|
|
In this case, you must hand-edit the resulting statement on the Run SQL panel.</p>
|
||
|
|
<p>Data
|
||
|
|
Transfer has an option for specifying whether ANSI or ASCII data is written
|
||
|
|
to or read from a PC file. Requests imported into iSeries Access for Web will use the Data
|
||
|
|
Transfer setting, combined with the language and character set specified by
|
||
|
|
the browser to determine the encoding of the client file. This may or may
|
||
|
|
not be correct. You may have to manually change this setting.</p>
|
||
|
|
<p>iSeries Access
|
||
|
|
for Web will not differentiate between source physical and data physical files.
|
||
|
|
An imported request that selects all columns (<samp class="codeph">SELECT *</samp>) from
|
||
|
|
a source physical file will produce output containing all columns contained
|
||
|
|
within the source physical file, including the sequence and date columns.
|
||
|
|
An identical request run with Client Access Express produces output containing
|
||
|
|
only the data column(s).</p>
|
||
|
|
<p>When importing Client Access Data Transfer
|
||
|
|
to AS/400 requests
|
||
|
|
that copy data to a source physical file, the request must be using an FDF
|
||
|
|
file. This situation cannot be detected by the import function and an error
|
||
|
|
will not be issued. However, if an FDF was not being used, the resulting copy
|
||
|
|
data to table request will not work correctly.</p>
|
||
|
|
<p>iSeries Access for Web does not support
|
||
|
|
all the file types currently supported by Client Access Data Transfer. In
|
||
|
|
some cases, a Data Transfer file type may be mapped to a corresponding iSeries Access
|
||
|
|
for Web file type. If a corresponding file format cannot be found the import
|
||
|
|
will fail.</p>
|
||
|
|
<p>Some output options available in Client Access Data Transfer
|
||
|
|
are not available in iSeries Access for Web. These options will be ignored.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />Import query<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />Query files with SQL statements containing program variables or replacement
|
||
|
|
variables are not supported. Query files containing forms or procedures are
|
||
|
|
not supported. <img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzammhdatabase.htm" title="Access database tables, run SQL statements, extract system object information into a database table, import Client Access Data Transfer requests, and import Query for iSeries and DB2 UDB for iSeries Query Manager query files.">Database</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|