113 lines
7.5 KiB
HTML
113 lines
7.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="Work with DBCS data" />
|
|
<meta name="abstract" content="A DBCS file is a file that contains double-byte data or is used to process double-byte data. Other files are called alphanumeric files. You can view DBCS files on display, printer, tape, diskette, and ICF devices." />
|
|
<meta name="description" content="A DBCS file is a file that contains double-byte data or is used to process double-byte data. Other files are called alphanumeric files. You can view DBCS files on display, printer, tape, diskette, and ICF devices." />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagshandlingdata.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdbcsappdesignchklst.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdesigndbcsapps.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdbcscodescheme.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdbcsfonttable.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdbcsfontfiles.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdbcssorttables.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdbcsfielddefin.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../dds/kickoff.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaij/rzaijgetstart.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rbagsenadbcs" />
|
|
<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>Work with DBCS data</title>
|
|
</head>
|
|
<body id="rbagsenadbcs"><a name="rbagsenadbcs"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Work with DBCS data</h1>
|
|
<div><p>A DBCS file is a file that contains double-byte data or is used
|
|
to process double-byte data. Other files are called alphanumeric files. You
|
|
can view DBCS files on display, printer, tape, diskette, and ICF devices.</p>
|
|
<p>You use data description specifications (DDS) to describe DBCS-capable
|
|
device files. For information about using DDS, see the DDS concepts topic.</p>
|
|
<p>You should indicate that a file is DBCS in one or more of the following
|
|
situations:</p>
|
|
<ul><li>The file receives input, or displays or prints output, which has double-byte
|
|
characters.</li>
|
|
<li>The file contains double-byte literals.</li>
|
|
<li>The file has double-byte literals in the DDS that are used in the file
|
|
at processing time (such as constant fields and error messages).</li>
|
|
<li>The DDS of the file includes DBCS keywords.</li>
|
|
<li>The file stores double-byte data (database files).</li>
|
|
</ul>
|
|
<div class="section"><h4 class="sectiontitle">DBCS strings in a mixed data stream</h4><p>Typically,
|
|
both single-byte characters and double-byte characters are used in a DBCS
|
|
environment. For example, an accounting firm in Japan uses both English and
|
|
Japanese for the spreadsheet. If both English and Japanese are being encoded
|
|
as mixed SBCS and DBCS, the product must be able to understand a mixed character
|
|
set that contains both single-byte coded characters and double-byte coded
|
|
characters.</p>
|
|
<p>In IBM<sup>®</sup> systems that use EBCDIC, a DBCS string is bracketed
|
|
in a mixed data stream by a shift-out (SO) control character and a shift-in
|
|
(SI) control character.</p>
|
|
<p>The following example shows the coding for a
|
|
mixed string:</p>
|
|
<pre> sss (SO) D1D2D (SI) ssss</pre>
|
|
<p>The
|
|
following example shows the coding for a mixed hexadecimal string:</p>
|
|
<pre> 818283 0E 41424143 0F 818283</pre>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Supported code ranges</h4><p>i5/OS™ supports
|
|
Japanese, Korean, Simplified Chinese, and Traditional Chinese character-set
|
|
code ranges.</p>
|
|
<p>Using the iSeries™ Access family of products, the servers also
|
|
provide support for these non-IBM personal computer DBCS code pages:</p>
|
|
<ul><li>Republic of Korea National Standard graphic character set (KS)</li>
|
|
<li>Taiwan Industry Standard graphic character set (Big5)</li>
|
|
<li>The People's Republic of China National Standard graphic character set
|
|
(GB)</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbagsdbcsappdesignchklst.htm">Checklist: DBCS application design</a></strong><br />
|
|
When you create an application with double-byte coded character set (DBCS) support, follow these guidelines.</li>
|
|
<li class="ulchildlink"><strong><a href="rbagsdesigndbcsapps.htm">Develop applications that process DBCS data</a></strong><br />
|
|
Design your application programs for processing double-byte data in the same way you design application programs for processing alphanumeric data.</li>
|
|
<li class="ulchildlink"><strong><a href="rbagsdbcscodescheme.htm">DBCS code schemes</a></strong><br />
|
|
IBM supports
|
|
two DBCS code schemes: one for the host systems and the other for personal
|
|
computers.</li>
|
|
<li class="ulchildlink"><strong><a href="rbagsdbcsfonttable.htm">DBCS font tables</a></strong><br />
|
|
DBCS font tables contain the images of the double-byte extended characters used on the system. The system uses these images to display and print extended characters when they are not resident on the device.</li>
|
|
<li class="ulchildlink"><strong><a href="rbagsdbcsfontfiles.htm">DBCS font files</a></strong><br />
|
|
The system provides DBCS font files.</li>
|
|
<li class="ulchildlink"><strong><a href="rbagsdbcssorttables.htm">DBCS sort tables</a></strong><br />
|
|
DBCS sort tables contain the sort information and collating sequences of all the double-byte characters used on the system. The sort utility on the system uses these tables to sort double-byte characters.</li>
|
|
<li class="ulchildlink"><strong><a href="rbagsdbcsfielddefin.htm">DBCS field definition</a></strong><br />
|
|
Consider the characteristics of DBCS data when you define a DBCS field.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagshandlingdata.htm" title="There are ways in which the operating system enables you to handle data in a globalized environment. These topics describe Unicode and Unicode data, the Chinese standard GB18030, how to use CCSIDs to integrate multiple language environments consistently, and how to use bidirectional data, DBCS data, and locales.">Handle data in globalized applications</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="../dds/kickoff.htm">DDS concepts</a></div>
|
|
<div><a href="../rzaij/rzaijgetstart.htm">iSeries Access</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |