90 lines
6.1 KiB
HTML
90 lines
6.1 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="System/38-compatible query utility (Query/38)" />
|
|
<meta name="abstract" content="The System/38-compatible query utility (Query/38) can be used with DDM to create and use interactive or batch query applications." />
|
|
<meta name="description" content="The System/38-compatible query utility (Query/38) can be used with DDM to create and use interactive or batch query applications." />
|
|
<meta name="DC.subject" content="batch, queries, interactive, processing" />
|
|
<meta name="keywords" content="batch, queries, interactive, processing" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5sys38tools.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5dbquery.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5nqueryx.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5dbquery.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5oqryf.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rbae5qryutil" />
|
|
<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>System/38-compatible
|
|
query utility (Query/38)</title>
|
|
</head>
|
|
<body id="rbae5qryutil"><a name="rbae5qryutil"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1"><span class="keyword">System/38</span>-compatible
|
|
query utility (Query/38)</h1>
|
|
<div><p>The <span class="keyword">System/38™</span>-compatible
|
|
query utility (Query/38) can be used with DDM to create and use interactive
|
|
or batch query applications.</p>
|
|
<div class="section"><p>If the target server is an <span class="keyword">iSeries™ server</span> or
|
|
a <span class="keyword">System/38</span>, most of these functions
|
|
can be performed as though the remote file is a local file. When creating
|
|
or changing a Query/38 application and the remote file is a logical file,
|
|
the following consideration applies: either DDM files referring to each remote
|
|
based-on file must exist on the source server, and the DDM file and library
|
|
names must match those of the remote based-on files; or, alternatively, physical
|
|
files with the same file and library names and the same record formats as
|
|
the remote based-on files must exist on the source server. Because only the
|
|
record formats are needed from the physical files, they need not contain data.
|
|
Using this alternative, if the record formats of the remote based-on files
|
|
are changed, the record formats on the source server must also be changed
|
|
so that the record formats match.</p>
|
|
</div>
|
|
<div class="section"><p>If the target system is not an <span class="keyword">iSeries server</span> or
|
|
a <span class="keyword">System/38</span>, you should refer
|
|
to a local file for the format and fields that describe the data in the remote
|
|
file, and then use the <span class="cmdname">Override Database File (OVRDBF)</span> command
|
|
to override the local file with a DDM file when the Query/38 application is
|
|
run. The
|
|
local file used to create (or re-create) the query must have the same record
|
|
format name as the source description of the non-<span class="keyword">iSeries</span> or
|
|
non-<span class="keyword">System/38</span> target file. The
|
|
default record format name is the name of the source DDM file.</p>
|
|
</div>
|
|
<div class="section"><p>Although Query/38 can create an application that uses a file on
|
|
a non-<span class="keyword">iSeries</span> or non-<span class="keyword">System/38</span> system, the default field descriptions
|
|
created on the source <span class="keyword">iSeries server</span> for
|
|
the non-<span class="keyword">iSeries</span> remote file
|
|
probably would be too general to be useful. (These files appear to be physical
|
|
files with one member, whose member name is the same as the file name. The
|
|
file has one record format and within that format: one field for the entire
|
|
record, if it is a nonkeyed file; two fields for keyed files, one for the
|
|
key and one for the remainder of the record; or more than two fields for keyed
|
|
files with separate key fields.)</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5sys38tools.htm" title="The topic collection describes the System/38-compatible data file utility (DFU/38) and the System/38-compatible query utility (Query/38).">System/38-compatible database tools</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rbae5dbquery.htm" title="The database interactive query function, provided by the i5/OS licensed program, supports DDM files.">i5/OS database query</a></div>
|
|
<div><a href="rbae5nqueryx.htm" title="This example shows how to create a local file and use it to define the data that is to be queried in a non-iSeries or non-System/38 remote file.">Non-iSeries or non-System/38 Query/38 example</a></div>
|
|
<div><a href="rbae5oqryf.htm" title="You can query remote files using the Open Query File (OPNQRYF) command, but only if the remote files are on a target iSeries server or a target System/38.">OPNQRYF (Open Query File) command</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |