85 lines
5.1 KiB
HTML
85 lines
5.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="concept" />
|
||
<meta name="DC.Title" content="Positional entry considerations for display files that use Unicode data" />
|
||
<meta name="abstract" content="The topic describes, by position, DDS for describing display files. Positions not mentioned have no special considerations for Unicode." />
|
||
<meta name="description" content="The topic describes, by position, DDS for describing display files. Positions not mentioned have no special considerations for Unicode." />
|
||
<meta name="DC.subject" content="Unicode, positional entries" />
|
||
<meta name="keywords" content="Unicode, positional entries" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakcvalentries.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="dspfil.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="ucs2pos" />
|
||
<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 display files that use Unicode
|
||
data</title>
|
||
</head>
|
||
<body id="ucs2pos"><a name="ucs2pos"><!-- --></a>
|
||
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
<h1 class="topictitle1">Positional entry considerations for display files that use Unicode
|
||
data</h1>
|
||
<div><p>The topic describes, by position, DDS for describing display files.
|
||
Positions not mentioned have no special considerations for Unicode.</p>
|
||
<div class="section"><h4 class="sectiontitle">Length (positions 30 through 34)</h4><p>Specify the length
|
||
of the field in these positions. The length of a field containing Unicode
|
||
data can range from 1 through 16 381 code units.</p>
|
||
<p>When
|
||
determining the program length of a field containing Unicode data, consider
|
||
the following rules:</p>
|
||
<ul><li>Each Unicode code unit is 2 bytes long.</li>
|
||
<li>The program length of the field is specified in number of Unicode code
|
||
units. For example, a field containing 3 Unicode code units has 6 bytes of
|
||
data.</li>
|
||
<li>The field's default display length is equal to the field's program length
|
||
or 2 times the number of Unicode code units.</li>
|
||
<li>After converting between Unicode data and EBCDIC, the resulting data can
|
||
be equal to, longer or shorter than the original length data before the conversion,
|
||
depending upon the CCSID of the device. For example, 1 Unicode code unit is
|
||
composed of 2 bytes of data. That code unit might convert to 1 SBCS character
|
||
composed of 1 byte of data, 1 graphic-DBCS character composed of 2 bytes of
|
||
data, or 1 bracketed DBCS character composed of 4 bytes of data.</li>
|
||
<li>The field's display length can be specified separately from the program
|
||
length by using the alternate-field-length parm on the CCSID keyword.</li>
|
||
</ul>
|
||
</div>
|
||
<div class="section"><h4 class="sectiontitle">Data type (position 35)</h4><p>The only valid data type
|
||
for Unicode data is the G data type.</p>
|
||
<dl><dt class="dlterm">G (Graphic)</dt>
|
||
<dd>Type G in combination with the CCSID keyword to specify this field contains
|
||
Unicode data. <p>Normally, by specifying G, the field contains graphic-DBCS
|
||
data. In combination with the CCSID keyword, the field now contains Unicode
|
||
data. On output, the data is mapped to corresponding characters in the CCSID
|
||
that the device is configured as. On input, the data is mapped to corresponding
|
||
Unicode code units.</p>
|
||
</dd>
|
||
</dl>
|
||
</div>
|
||
<div class="section"><h4 class="sectiontitle">Decimal positions (positions 36 and 37)</h4><p>Leave these
|
||
positions blank when using Unicode data.</p>
|
||
</div>
|
||
</div>
|
||
<div>
|
||
<div class="familylinks">
|
||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dspfil.htm" title="Unicode is a universal encoding scheme for written characters and text that enables the exchange of data internationally. Two transformation formats, UTF_16 and UCS_2, of Unicode are supported with DDS.">Unicode considerations for display files</a></div>
|
||
</div>
|
||
<div class="relref"><strong>Related reference</strong><br />
|
||
<div><a href="rzakcvalentries.htm" title="The table in this topic shows a list of valid entries for display files.">Valid entries for display files</a></div>
|
||
</div>
|
||
</div>
|
||
</body>
|
||
</html> |