64 lines
4.5 KiB
HTML
64 lines
4.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="Mapping of data" />
|
||
|
|
<meta name="abstract" content="i5/OS uses the EBCDIC encoding scheme. However, not all clients attached to it use an EBCDIC encoding scheme to store, retrieve, and process data. Therefore, some clients use Unicode as an exchange mechanism that is safe across all platforms." />
|
||
|
|
<meta name="description" content="i5/OS uses the EBCDIC encoding scheme. However, not all clients attached to it use an EBCDIC encoding scheme to store, retrieve, and process data. Therefore, some clients use Unicode as an exchange mechanism that is safe across all platforms." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsunicodeucs2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagswithoutucs2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagswithucs2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsucslevel1maptble.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="rbagswhyuseucs2" />
|
||
|
|
<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>Mapping of data</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbagswhyuseucs2"><a name="rbagswhyuseucs2"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Mapping of data</h1>
|
||
|
|
<div><p>i5/OS™ uses
|
||
|
|
the EBCDIC encoding scheme. However, not all clients attached to it use an
|
||
|
|
EBCDIC encoding scheme to store, retrieve, and process data. Therefore, some
|
||
|
|
clients use Unicode as an <em>exchange mechanism</em> that is safe across all
|
||
|
|
platforms. </p>
|
||
|
|
<p>Some clients might use ASCII, PC DATA, or other encoding schemes. They
|
||
|
|
can using Unicode to prevent the loss of data due to incomplete conversion
|
||
|
|
between encoding schemes and code pages.</p>
|
||
|
|
<div class="section"><p>These examples highlight two users on the same system. One user
|
||
|
|
is English and the other Greek. The English user has his display device CCSID
|
||
|
|
set to 37. The Greek user has his display device CCSID set to 875. Both users
|
||
|
|
query, update, and replace data in the DATABASE1. DATABASE1 is tagged with
|
||
|
|
CCSID 37.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagswithoutucs2.htm">Example: Display data without Unicode</a></strong><br />
|
||
|
|
Problems with data integrity develop because users are operating with CCSIDs that have varied character support. That is, not all characters in CCSID 37 are available in CCSID 875 and vice versa.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagswithucs2.htm">Example: Display data with Unicode</a></strong><br />
|
||
|
|
This example, using UCS-2 as the CCSID of DATABASE1, shows how data integrity is maintained both in storing and retrieving data.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsucslevel1maptble.htm">UCS-2 level-1 mapping tables</a></strong><br />
|
||
|
|
You can convert characters encoded in universal coded character set 2 level 1 (UCS-2 level-1) from uppercase to lowercase. The uppercase-to-lowercase mapping table shows the mapping for this conversion.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsunicodeucs2.htm" title="Unicode is a standard that precisely defines a character set as well as a small number of encodings for it. It enables you to handle text in any language efficiently. It allows a single application to work for a global audience.">Work with Unicode</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|