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

53 lines
3.8 KiB
HTML
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?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="Positional entry considerations for database files that use DBCS" />
<meta name="abstract" content="These topics describe DBCS considerations for the length, data type, and decimal positional entries on database files. Positional entries that are not mentioned have no special considerations for DBCS." />
<meta name="description" content="These topics describe DBCS considerations for the length, data type, and decimal positional entries on database files. Positional entries that are not mentioned have no special considerations for DBCS." />
<meta name="DC.Relation" scheme="URI" content="rzakbmstzdbcs.htm" />
<meta name="DC.Relation" scheme="URI" content="dbclen.htm" />
<meta name="DC.Relation" scheme="URI" content="dbcdtype.htm" />
<meta name="DC.Relation" scheme="URI" content="dbcdec.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="dbpos" />
<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>Positional entry considerations for database files that use DBCS</title>
</head>
<body id="dbpos"><a name="dbpos"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Positional entry considerations for database files that use DBCS</h1>
<div><p>These topics describe DBCS considerations for the
length, data type, and decimal positional entries on database files. Positional
entries that are not mentioned have no special considerations for DBCS.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="dbclen.htm">Length (positions 30 through 34)</a></strong><br />
The length of a field containing bracketed-DBCS data can range from 4 through 32 766 bytes (4 through 32 740 bytes if the field is variable length). The length of a DBCS-graphic field can range from 1 through 16 383 characters (1 through 16 370 characters if the field is variable length).</li>
<li class="ulchildlink"><strong><a href="dbcdtype.htm">Data type (position 35)</a></strong><br />
You can use any of the four DBCS data types: J (Only), E (Either), O (Open) and G (Graphic).</li>
<li class="ulchildlink"><strong><a href="dbcdec.htm">Decimal (positions 36 and 37)</a></strong><br />
Leave these positions blank when using DBCS data.</li>
</ul>
<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>
</body>
</html>