ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakb_5.4.0.1/daddcon.htm

104 lines
5.8 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="Additional considerations for describing database files that contain DBCS data" />
<meta name="abstract" content="Be aware of the considerations when describing a database file that contains DBCS fields." />
<meta name="description" content="Be aware of the considerations when describing a database file that contains DBCS fields." />
<meta name="DC.Relation" scheme="URI" content="rzakbmstzdbcs.htm" />
<meta name="DC.Relation" scheme="URI" content="../dds/rbafpmstidlit.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2001, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2001, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="daddcon" />
<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>Additional considerations for describing database files that contain
DBCS data</title>
</head>
<body id="daddcon"><a name="daddcon"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Additional considerations for describing database files that contain
DBCS data</h1>
<div><p>Be aware of the considerations when describing a database file
that contains DBCS fields.</p>
<div class="section"><ul><li>If you describe DBCS fields in the DDS, the system treats the file as
a DBCS file. You do not need to specify IGCDTA(*YES) on the file creation
command to identify the file as DBCS.</li>
<li>The data type of a field in a physical file can be changed as follows
when you refer to that field in a logical file:
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="90%" frame="void" border="0" rules="none"><thead align="left"><tr><th align="left" valign="top" width="29.187817258883246%" id="d0e27">Physical file data type</th>
<th align="left" valign="bottom" width="70.81218274111674%" id="d0e29">Logical file data type</th>
</tr>
</thead>
<tbody><tr><td align="left" valign="top" width="29.187817258883246%" headers="d0e27 ">J</td>
<td align="left" valign="top" width="70.81218274111674%" headers="d0e29 ">J, O, E, H, G</td>
</tr>
<tr><td align="left" valign="top" width="29.187817258883246%" headers="d0e27 ">O</td>
<td align="left" valign="top" width="70.81218274111674%" headers="d0e29 ">O, H</td>
</tr>
<tr><td align="left" valign="top" width="29.187817258883246%" headers="d0e27 ">E</td>
<td align="left" valign="top" width="70.81218274111674%" headers="d0e29 ">O, E, H</td>
</tr>
<tr><td align="left" valign="top" width="29.187817258883246%" headers="d0e27 ">A</td>
<td align="left" valign="top" width="70.81218274111674%" headers="d0e29 ">A, O, E, H</td>
</tr>
<tr><td align="left" valign="top" width="29.187817258883246%" headers="d0e27 ">H</td>
<td align="left" valign="top" width="70.81218274111674%" headers="d0e29 ">J, O, E, A, H</td>
</tr>
<tr><td align="left" valign="top" width="29.187817258883246%" headers="d0e27 ">G</td>
<td align="left" valign="top" width="70.81218274111674%" headers="d0e29 ">G, O, J, E</td>
</tr>
</tbody>
</table>
</div>
<div class="note"><span class="notetitle">Note:</span> When the physical file data type is character (A) or hexadecimal
(H), and the logical file data type is DBCS-only (J) or DBCS-either (E), the
physical file field length (columns 30 through 34) must be an even number
greater than or equal to 4.</div>
</li>
<li>DDS treats DBCS key fields as character fields (the data type specified
in position 35 is O).</li>
<li>DDS uses the EBCDIC collating sequence to sort DBCS data.</li>
<li>Any key field sequencing keywords that can be used with character fields
can be used with DBCS fields, except the following keywords: <p>ALTSEQ<br />
DIGIT<br />
ZONE</p>
</li>
<li>Use bracketed-DBCS data anywhere that comments and character
strings are allowed.</li>
<li>Any bracketed-DBCS field except a field with data type J can be compared
with a character field (data type A).</li>
<li>A DBCS-graphic field can be compared only with another graphic field.</li>
<li>The following validity checking keywords can be specified on DBCS fields:
<p>COMP<br />
RANGE<br />
VALUES</p>
</li>
<li>When specifying the VARLEN keyword in a physical file, the minimum allowed
length for the allocated length is 4 for a bracketed-DBCS field. The minimum
allowed length for the allocated length is 1 for a DBCS-graphic field.</li>
</ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakbmstzdbcs.htm" title="These topics describe the DBCS considerations for the positional entries and keyword entries for physical and logical files, along with general considerations for database files.">DBCS considerations for database files</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../dds/rbafpmstidlit.htm">DBCS character strings</a></div>
</div>
</div>
</body>
</html>