ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzake_5.4.0.1/icfpos.htm

64 lines
3.8 KiB
HTML
Raw 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="concept" />
<meta name="DC.Title" content="Positional entry considerations for ICF files that use DBCS" />
<meta name="abstract" content="Learn about double-byte character set (DBCS) considerations for describing the length and data type positions for ICF files." />
<meta name="description" content="Learn about double-byte character set (DBCS) considerations for describing the length and data type positions for ICF files." />
<meta name="DC.subject" content="DBCS, positional entry considerations, positional entries, DBCS considerations" />
<meta name="keywords" content="DBCS, positional entry considerations, positional entries, DBCS considerations" />
<meta name="DC.Relation" scheme="URI" content="rzakemstzdbcs.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="icfpos" />
<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 ICF files that use DBCS</title>
</head>
<body id="icfpos"><a name="icfpos"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Positional entry considerations for ICF files that use DBCS</h1>
<div><p><span>Learn about double-byte character set
(DBCS) considerations for describing the length and data type positions for
ICF files.</span></p>
<p>Those positions not mentioned have no special considerations for DBCS.</p>
<div class="section"><h4 class="sectiontitle">Length (positions 30 through 34)</h4><p>The
length of a field containing bracketed-DBCS data can range from 4 through
32 767 bytes.</p>
<p>Keep the following considerations in mind when
determining the length of a DBCS field:</p>
<ul><li>Each DBCS character is 2 bytes long.</li>
<li>Include both shift-control characters in the length of the field. Together,
these characters are 2 bytes long. <div class="p">For example, a field that contains up
to 3 DBCS characters, 1 shift-in character, and 1 shift-out character, has
8 bytes of data: <pre>(3 characters x 2 bytes) + (shift-out + shift-in) = 8</pre>
</div>
</li>
</ul>
</div>
<div class="section"><h4 class="sectiontitle">Data type (position 35)</h4><p>The
data type O (DBCS capable) makes a field DBCS.</p>
<p>Both bracketed-DBCS and
alphanumeric data can be used in a DBCS-capable field. Use shift-control characters
to distinguish DBCS data from alphanumeric data.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakemstzdbcs.htm" title="Read about the bracketed-DBCS (double-byte character set) considerations for positional entries for ICF files, along with general considerations.">DBCS considerations for ICF files</a></div>
</div>
</div>
</body>
</html>