178 lines
8.1 KiB
HTML
178 lines
8.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="DDM-related DDS keywords and information" />
|
|
<meta name="abstract" content="The information about DDS keywords that relates specifically to DDM is provided in this topic." />
|
|
<meta name="description" content="The information about DDS keywords that relates specifically to DDM is provided in this topic." />
|
|
<meta name="DC.subject" content="keyword, DDS, DDM-related DDS keyword, keyword, DDM-related DDS, DDS keyword" />
|
|
<meta name="keywords" content="keyword, DDS, DDM-related DDS keyword, keyword, DDM-related DDS, DDS keyword" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ddsinfo.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5crtpf.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="rbae5ddskywd" />
|
|
<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>DDM-related DDS keywords and information</title>
|
|
</head>
|
|
<body id="rbae5ddskywd"><a name="rbae5ddskywd"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">DDM-related DDS keywords and information</h1>
|
|
<div><p>The information about DDS keywords that relates specifically to
|
|
DDM is provided in this topic.</p>
|
|
<div class="section"><ul><li>Considerations for creating local files: <ul><li>The following DDS keywords <em>cannot</em> specify the name of a DDM file:
|
|
REFACCPTH, and FORMAT.</li>
|
|
<li>The DDS keywords REF and REFFLD <em>can</em> specify the names of DDM files
|
|
to refer to remote files; however, the remote files must be on an <span class="keyword">iSeries™ server</span> or a <span class="keyword">System/38™</span>.
|
|
When a DDM file name is specified as the database file name in either keyword,
|
|
it refers to the DDM file on the source server, and the referred to field
|
|
name and record format name refer to a field and record format used in the
|
|
remote file on the target server.</li>
|
|
</ul>
|
|
</li>
|
|
<li>Considerations for creating logical files when the remote server is not
|
|
an <span class="keyword">iSeries server</span>: <ul><li>At least one key field must be specified in the record format for the
|
|
logical file.</li>
|
|
<li>Only one file can be specified on the PFILE keyword.</li>
|
|
<li>SELECT and OMIT functions are not supported.</li>
|
|
<li>Logical join files are not supported.</li>
|
|
<li>Field names of remote physical files have the naming convention of F00001,
|
|
F00002, F00003, and so forth (F<em>nnnnn</em>) for nonkeyed fields and K00001,
|
|
K00002, K00003, and so forth (K<em>nnnnn</em>) for keyed fields. <p>The exception
|
|
to this naming convention is when the target server is a <span class="keyword">System/38</span> and
|
|
the physical file was created locally. In this case, the field
|
|
names are the same as the field names specified when the physical file was
|
|
created.</p>
|
|
</li>
|
|
<li>All the fields defined for the logical file must be specified in the same
|
|
order as defined in the physical file. This can be done by default.</li>
|
|
<li>The SST keyword can be used to access partial fields of the physical file.
|
|
The use of two or more substring fields is required to define the entire physical
|
|
field. In addition, the partial fields must be in the same order as defined
|
|
in the substring field of the physical file.</li>
|
|
<li>The CONCAT keyword can be used to group physical file fields into one
|
|
logical field. The concatenation order of the fields must be in the same order
|
|
as defined in the physical file.</li>
|
|
<li>The fields of the physical file must be specified in the same order as
|
|
defined in the physical file.</li>
|
|
</ul>
|
|
</li>
|
|
<li>Considerations for using the VARLEN DDS keyword when creating files on
|
|
a non-<span class="keyword">iSeries</span> target server:
|
|
<ul><li>Target server must support variable-length record files.</li>
|
|
<li>Only one variable-length field is allowed in the file format and it must
|
|
be the last field.</li>
|
|
<li>The field with the VARLEN keyword must not be a key field.</li>
|
|
</ul>
|
|
</li>
|
|
<li>PFILE and JFILE considerations for creating remote files: <ul><li>The record format name specified for the physical file in the DDM file
|
|
on the JFILE or PFILE keyword must be the same name as the DDM file that represents
|
|
the remote physical file.</li>
|
|
<li>When creating a logical file, the file specified on PFILE or JFILE must
|
|
be a DDM file, and the location for each physical file in the DDM file on
|
|
the JFILE or PFILE keyword must be the same as the location of the DDM file
|
|
for the logical file. In other words, the physical files and logical file
|
|
must be on the same remote server.</li>
|
|
</ul>
|
|
If the remote server is a release 1.0 or 1.2 <span class="keyword">iSeries server</span>,
|
|
attempting to create a file using the FCFO keyword will fail.</li>
|
|
<li>When the server is not an <span class="keyword">iSeries server</span>,
|
|
these keywords are either ignored or not supported for <em>logical</em> files:
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="90%" frame="void" border="1" rules="all"><tbody><tr><td valign="top" width="33.33333333333333%"> <p>ABSVAL <br />
|
|
ACCPTH <br />
|
|
ALIAS <br />
|
|
ALL <br />
|
|
ALTSEQ <br />
|
|
CHECK <br />
|
|
CMP <br />
|
|
COLHDG <br />
|
|
COMP <br />
|
|
DIGIT <br />
|
|
DYNSLT</p>
|
|
</td>
|
|
<td valign="top" width="33.33333333333333%"> <p>EDTCDE <br />
|
|
EDTWRD <br />
|
|
FCFO <br />
|
|
FLTPCN <br />
|
|
FORMAT <br />
|
|
JDFTVAL <br />
|
|
JDUPSEQ <br />
|
|
JFILE <br />
|
|
JFLD <br />
|
|
JOIN <br />
|
|
JREF</p>
|
|
</td>
|
|
<td valign="top" width="33.33333333333333%"> <p>LIFO <br />
|
|
NOALTSEQ <br />
|
|
RANGE <br />
|
|
REFSHIFT <br />
|
|
RENAME <br />
|
|
SIGNED <br />
|
|
TEXT <br />
|
|
TRNTBL <br />
|
|
VALUES <br />
|
|
ZONE</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</li>
|
|
<li>When the server is not an <span class="keyword">iSeries server</span>,
|
|
these keywords are either ignored or not supported for <em>physical</em> files:
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="90%" frame="void" border="0" rules="none"><tbody><tr><td valign="top" width="33.33333333333333%"> <p>ABSVAL <br />
|
|
ALTSEQ <br />
|
|
CHECK <br />
|
|
CMP <br />
|
|
COLHDG <br />
|
|
COMP <br />
|
|
DIGIT</p>
|
|
</td>
|
|
<td valign="top" width="33.33333333333333%"> <p>EDTCDE <br />
|
|
EDTWRD <br />
|
|
FCFO <br />
|
|
FLTPCN <br />
|
|
FORMAT <br />
|
|
LIFO <br />
|
|
NOALTSEQ</p>
|
|
</td>
|
|
<td valign="top" width="33.33333333333333%"> <p>RANGE <br />
|
|
REFSHIFT <br />
|
|
SIGNED <br />
|
|
TEXT <br />
|
|
VALUES <br />
|
|
ZONE</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5ddsinfo.htm" title="Data description specifications (DDS), which is used to externally describe the fields and record formats, can also be used with DDM to describe the file and record formats of a remote file.">Data description specifications considerations for DDM</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rbae5crtpf.htm" title="The Create Physical File (CRTPF) command can be used to create files on the source and target servers through the SYSTEM parameter.">CRTPF (Create Physical File) command</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |