104 lines
6.5 KiB
HTML
104 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="Scenario: A single server supporting Spanish and an existing EBCDIC database" />
|
||
|
|
<meta name="abstract" content="In this scenario, there is a single server supporting Spanish users and applications and an existing EBCDIC database." />
|
||
|
|
<meta name="description" content="In this scenario, there is a single server supporting Spanish users and applications and an existing EBCDIC database." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsinstallscenarios.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="rbagsixampmultilingsepdb" />
|
||
|
|
<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>Scenario: A single server supporting Spanish and an existing EBCDIC
|
||
|
|
database</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbagsixampmultilingsepdb"><a name="rbagsixampmultilingsepdb"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario: A single server supporting Spanish and an existing EBCDIC
|
||
|
|
database</h1>
|
||
|
|
<div><p>In this scenario, there is a single server supporting Spanish users
|
||
|
|
and applications and an existing EBCDIC database.</p>
|
||
|
|
<p>The primary language of the system is Spanish (NLV
|
||
|
|
2931). Because 2931 is the primary language, the default system settings and i5/OS™ localization
|
||
|
|
preference is set to Spanish.</p>
|
||
|
|
<p>The user has also created a database file where the fields of interest
|
||
|
|
are defined to contain Unicode, because they plan to use this same database
|
||
|
|
file for both 5250 applications and Java™ applications. They also have an existing
|
||
|
|
database in which the fields are defined in EBCDIC.</p>
|
||
|
|
<p>The following example shows the SQL statement used to create the EBCDIC
|
||
|
|
database:</p>
|
||
|
|
<pre>CREATE TABLE SAMPLE (PART_NAME CHAR (10) CCSID 284 NOT NULL WITH DEFAULT,
|
||
|
|
STOCK_NUMBER INT NOT NULL WITH DEFAULT 0)</pre>
|
||
|
|
<p>The following example shows the SQL statement used to create a database
|
||
|
|
containing a Unicode field named PART_NAME and a non-Unicode field named STOCK_NUMBER:</p>
|
||
|
|
<pre>CREATE TABLE SAMPLE (PART_NAME GRAPHIC (10) CCSID 1200 NOT NULL WITH DEFAULT,
|
||
|
|
STOCK_NUMBER INT NOT NULL WITH DEFAULT 0)</pre>
|
||
|
|
<div class="section"><h4 class="sectiontitle">When using the Unicode file</h4><p>If the user wants to
|
||
|
|
display this data with a web service or Unicode enabled application, then
|
||
|
|
Unicode is the natural encoding for web use, and no conversion is needed.
|
||
|
|
To get the correct localization preference for the Java application, the user sets the Java locale
|
||
|
|
to <samp class="codeph">sp_SP</samp> for Spanish in Spain.</p>
|
||
|
|
<p>If the user wants to
|
||
|
|
display this data with a 5250 session, then the Unicode field must be converted
|
||
|
|
to the CCSID of the display device. The user only has to set the user profiles's
|
||
|
|
CCSID value to 284 to tell the system that this user is on a Spanish display.
|
||
|
|
This service is provided automatically by the system if requested with the
|
||
|
|
CCSID keyword and the *CONVERT parameter in DDS.</p>
|
||
|
|
<p>To print the Unicode
|
||
|
|
data, the user specifies the *NOCONVERT parameter of the CCSID keyword, and
|
||
|
|
a TrueType font using the FONTNAME keyword. The unconverted Unicode data can
|
||
|
|
be printed with PSF/400 or with Host Print Transform.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">When using the EBCDIC file</h4><p>If the user wants to
|
||
|
|
display this data with a web service, then the file first must be converted
|
||
|
|
to Unicode. This can be done with the JDBC connector. To get the correct localization
|
||
|
|
preference for the Java application, the user sets the Java locale
|
||
|
|
to <samp class="codeph">sp_SP</samp> for Spanish in Spain.</p>
|
||
|
|
<p>If the user wants to
|
||
|
|
display this data with a 5250 session, EBCDIC is the natural encoding for
|
||
|
|
the 5250 device and no conversion is needed. To print the EBCDIC data, the
|
||
|
|
user sends the data to the printer; because EBCDIC is the default encoding
|
||
|
|
for the printer, no conversion is needed.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Logical file support</h4><p>One of
|
||
|
|
the unique features of i5/OS is the ability to use the system's logical file
|
||
|
|
support to have either the EBCDIC file appear to the application as a Unicode
|
||
|
|
file, or to have a Unicode file appear to the application as an EBCDIC file.
|
||
|
|
This might be of use if you want to move your database to Unicode, but do
|
||
|
|
not want to update your existing applications.</p>
|
||
|
|
<p>If the
|
||
|
|
majority of your application's use of the database involves Unicode, you can
|
||
|
|
have the data stored as Unicode, and create a logical view of the file in
|
||
|
|
EBCDIC. You can then have your EBCDIC programs access this logical file and
|
||
|
|
they do not need to be updated to handle Unicode.</p>
|
||
|
|
<p>If
|
||
|
|
the majority of your application's use of database involves EBCDIC, you can
|
||
|
|
have the data stored as EBCDIC, and create a logical view of the file in Unicode.
|
||
|
|
You can then have your Unicode programs access this logical file and they
|
||
|
|
do not need to be updated to handle EBCDIC. However, because EBCDIC encodes
|
||
|
|
a smaller set of characters than Unicode does, some character loss might occur.</p>
|
||
|
|
<p>The
|
||
|
|
following figure illustrates this scenario.</p>
|
||
|
|
<br /><img src="nls502.gif" alt="Scenario: a single server supporting Spanish and an existing EBCDIC database" /><br /></div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsinstallscenarios.htm" title="Use these scenarios to better understand multilingual support.">Scenarios: Set up i5/OS with a national language version</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|