97 lines
6.5 KiB
HTML
97 lines
6.5 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="General considerations for using DBCS text with DDS files" />
|
||
|
|
<meta name="abstract" content="These topics describe the general considerations for positional entries, keyword entries, double-byte character set (DBCS) text literals, and DDS computer printouts that contain DBCS characters." />
|
||
|
|
<meta name="description" content="These topics describe the general considerations for positional entries, keyword entries, double-byte character set (DBCS) text literals, and DDS computer printouts that contain DBCS characters." />
|
||
|
|
<meta name="DC.subject" content="DBCS, considerations, double-byte character set" />
|
||
|
|
<meta name="keywords" content="DBCS, considerations, double-byte character set" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="kickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="genpos.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="genkwd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafpmstidlit.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="gencompo.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakb/rzakbmstzdbcs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakc/rzakcmstzdbcs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakd/rzakdmstzdbcs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzake/rzakemstzdbcs.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="gendbcs" />
|
||
|
|
<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>General considerations for using DBCS text with DDS files</title>
|
||
|
|
</head>
|
||
|
|
<body id="gendbcs"><a name="gendbcs"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">General considerations for using DBCS text with DDS files</h1>
|
||
|
|
<div><p><span>These topics describe the general considerations
|
||
|
|
for positional entries, keyword entries, double-byte character set (DBCS)
|
||
|
|
text literals, and DDS computer printouts that contain DBCS characters.</span></p>
|
||
|
|
<p>DBCS text can be encoded as either Unicode or EBCDIC. If you are working
|
||
|
|
on a new application or enabling an existing application for DBCS text or
|
||
|
|
working on an application involving Java™, ODBC, JDBC, or other web methods,
|
||
|
|
then <span class="keyword">i5/OS™</span> Unicode
|
||
|
|
support provides the easiest way to support not only DBCS text but also other
|
||
|
|
text types. If you are working on an existing application already supporting
|
||
|
|
DBCS text stored as EBCDIC, then <span class="keyword">i5/OS</span> EBCDIC support for DBCS text is useful.</p>
|
||
|
|
<p>DDS uses the following terms to describe the different types of DBCS data:</p>
|
||
|
|
<dl><dt class="dlterm">DBCS data</dt>
|
||
|
|
<dd>A general term to describe any form of EBCDIC-encoded
|
||
|
|
DBCS data.</dd>
|
||
|
|
<dt class="dlterm">DBCS field</dt>
|
||
|
|
<dd>A general term to describe any field that can contain
|
||
|
|
EBCDIC-encoded DBCS data.</dd>
|
||
|
|
<dt class="dlterm">Bracketed DBCS data</dt>
|
||
|
|
<dd> EBCDIC-encoded DBCS data that begins with a shift-out
|
||
|
|
character and ends with a shift-in character.</dd>
|
||
|
|
<dt class="dlterm">DBCS graphic data</dt>
|
||
|
|
<dd> EBCDIC-encoded DBCS data that contains only DBCS
|
||
|
|
data and does not contain shift-out and shift-in characters.</dd>
|
||
|
|
<dt class="dlterm">Unicode data</dt>
|
||
|
|
<dd>A general term to describe any form of Unicode-encoded
|
||
|
|
DBCS data.</dd>
|
||
|
|
<dt class="dlterm">Unicode field</dt>
|
||
|
|
<dd>When the graphic data type is used with CCSID 1200 specified, then Unicode
|
||
|
|
(UTF-16) is stored in the field instead of EBCDIC. When character data type
|
||
|
|
is used with CCSID 1208 specified, then Unicode (UTF-8) is stored in the field
|
||
|
|
instead of EBCDIC.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="genpos.htm">Positional entries for files that use DBCS data</a></strong><br />
|
||
|
|
Positional entries are adapted so that you can define data fields that contain DBCS data. The entries are adapted for the length and data type positional entries.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="genkwd.htm">Keyword entries for files that use DBCS (positions 45 through 80)</a></strong><br />
|
||
|
|
When you work with DBCS data, you can specify DBCS-specific attributes with certain DDS keywords.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafpmstidlit.htm">DBCS character strings</a></strong><br />
|
||
|
|
You can use bracketed-DBCS character strings in DDS files for text-related keywords, such as TEXT and COLHDG, and both bracketed and DBCS-graphic character strings as parameters on the COMP, DFT, RANGE, and VALUES keywords.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="gencompo.htm">DDS computer printouts with DBCS output</a></strong><br />
|
||
|
|
DDS computer printouts are printed as DBCS output in these instances.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="kickoff.htm" title="This topic provides an overview of data description specifications (DDS) on iSeries servers.">DDS concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../rzakb/rzakbmstzdbcs.htm" target="_blank">DBCS considerations for database files</a></div>
|
||
|
|
<div><a href="../rzakc/rzakcmstzdbcs.htm" target="_blank">DBCS considerations for display files</a></div>
|
||
|
|
<div><a href="../rzakd/rzakdmstzdbcs.htm" target="_blank">DBCS considerations for printer files</a></div>
|
||
|
|
<div><a href="../rzake/rzakemstzdbcs.htm" target="_blank">DBCS considerations for ICF files</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|