206 lines
13 KiB
HTML
206 lines
13 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="Example: Locales as part of a multilingual environment" />
|
||
|
|
<meta name="abstract" content="i5/OS, through the use of locales, user profiles, and subsystems, can provide a multilingual environment. Users of a system that is set up for multilingual environments work with their national language and all of its cultural conventions (for example, the character used to separate hours, minutes, and seconds)." />
|
||
|
|
<meta name="description" content="i5/OS, through the use of locales, user profiles, and subsystems, can provide a multilingual environment. Users of a system that is set up for multilingual environments work with their national language and all of its cultural conventions (for example, the character used to separate hours, minutes, and seconds)." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagslocaleprogexamp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsnatlangfeatcode.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaks/rzaks1.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="rbagslocalemultilingenvi" />
|
||
|
|
<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>Example: Locales as part of a multilingual environment</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbagslocalemultilingenvi"><a name="rbagslocalemultilingenvi"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: Locales as part of a multilingual environment</h1>
|
||
|
|
<div><p>i5/OS™,
|
||
|
|
through the use of locales, user profiles, and subsystems, can provide a multilingual
|
||
|
|
environment. Users of a system that is set up for multilingual environments
|
||
|
|
work with their national language and all of its cultural conventions (for
|
||
|
|
example, the character used to separate hours, minutes, and seconds).</p>
|
||
|
|
<p>Assume that the system used in this example has its primary language defined
|
||
|
|
as English and the secondary national language versions (NLVs) for French
|
||
|
|
and Spanish have been installed.</p>
|
||
|
|
<p>Follow the steps in this example to:</p>
|
||
|
|
<ul><li>Create the locales for English, French, and Spanish</li>
|
||
|
|
<li>Create user profiles for users named: English, French, and Spanish</li>
|
||
|
|
<li>Create separate subsystems for French and Spanish language users.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="section" xml:lang="en-us" id="rbagslocalemultilingenvi__createlocales"><a name="rbagslocalemultilingenvi__createlocales"><!-- --></a><h4 class="sectiontitle">Step 1. Create locales</h4><ol><li>Type CRTLOCALE and press the Prompt key (F4).</li>
|
||
|
|
<li>Enter these values for the following fields:<ul><li>Locale name: qsys.lib/localelib.lib/en_us.locale</li>
|
||
|
|
<li>Source file path name: qsys.lib/qsyslocale.lib/qlocalesrc.file/en_us.mbr</li>
|
||
|
|
<li>Coded character set ID: 37</li>
|
||
|
|
<li>Generation severity level: 20</li>
|
||
|
|
<li>Text 'description': US English locale</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Press Enter.</li>
|
||
|
|
</ol>
|
||
|
|
<p>Repeat the CRTLOCALE command for the FRENCH and SPANISH locales, using
|
||
|
|
these values for the following fields.</p>
|
||
|
|
<p>For the French locale:</p>
|
||
|
|
<ul><li>Locale name: qsys.lib/localelib.lib/fr_fr.locale</li>
|
||
|
|
<li>Source file path name: qsys.lib/qsyslocale.lib/qlocalesrc.file/fr_fr.mbr</li>
|
||
|
|
<li>Coded character set ID: 297</li>
|
||
|
|
<li>Generation severity level: 20</li>
|
||
|
|
<li>Text 'description': French locale</li>
|
||
|
|
</ul>
|
||
|
|
<p>For the Spanish locale:</p>
|
||
|
|
<ul><li>Locale name: qsys.lib/localelib.lib/es_es.locale</li>
|
||
|
|
<li>Source file path name: qsys.lib/qsyslocale.lib/qlocalesrc.file/es_es.mbr</li>
|
||
|
|
<li>Coded character set ID: 284</li>
|
||
|
|
<li>Generation severity level: 20</li>
|
||
|
|
<li>Text 'description': Spanish locale</li>
|
||
|
|
</ul>
|
||
|
|
<p>You have created three locales (EN_US (English US), FR_FR (French),
|
||
|
|
and ES_ES (Spanish). They are stored in library localelib.lib.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section" xml:lang="en-us" id="rbagslocalemultilingenvi__createuserprofile"><a name="rbagslocalemultilingenvi__createuserprofile"><!-- --></a><h4 class="sectiontitle">Step 2. Create the
|
||
|
|
user profile</h4><p>In this example, three user profiles
|
||
|
|
are created; each one will use one of the locales that was just created. The
|
||
|
|
user profile names are English, French, and Spanish.</p>
|
||
|
|
<ol><li>Type CRTUSRPRF and prompt (F4).</li>
|
||
|
|
<li>Type ENGLISH for the User profile parameter value.</li>
|
||
|
|
<li>Scroll forward until you see the Locale job attributes parameter and the
|
||
|
|
Locale parameter.</li>
|
||
|
|
<li>Type:<ul><li>/qsys.lib/localelib.lib/en_us.locale for the Locale parameter value.</li>
|
||
|
|
<li>Type + for the Locale job attributes parameter value and press Enter.
|
||
|
|
Type:<pre>*CCSID
|
||
|
|
*DATFMT
|
||
|
|
*DATSEP
|
||
|
|
*TIMSEP
|
||
|
|
*SRTSEQ
|
||
|
|
*DECFMT</pre>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> At job start, the system finds the actual job attribute
|
||
|
|
values defined in the locale object. The job attributes found in the locale
|
||
|
|
override the values specified in the user profile fields for the CCSID and
|
||
|
|
SRTSEQ parameters. They also override the date format, date separator, and
|
||
|
|
time separator job attributes specified in any system value.</div>
|
||
|
|
</li>
|
||
|
|
<li>Press Enter. You have now created the user profile for a user named ENGLISH.</li>
|
||
|
|
</ol>
|
||
|
|
<p>Repeat the CRTUSRPRF command for user IDs FRENCH and SPANISH. The
|
||
|
|
next two displays provide the correct Locale parameter and Locale job attribute
|
||
|
|
information for creating the user profiles for FRENCH and SPANISH.</p>
|
||
|
|
<pre>+--------------------------------------------------------------------------------+
|
||
|
|
|Locale job attributes . . . . . > *CCSID *SYSVAL,*NONE, *CCSID... |
|
||
|
|
|> *DATFMT |
|
||
|
|
|> *DATSEP |
|
||
|
|
|> *TIMSEP |
|
||
|
|
|> *SRTSEQ |
|
||
|
|
|Locale . . . . . . . . . . . . . >'/qsys.lib/localelib.lib/fr_fr.locale' |
|
||
|
|
+--------------------------------------------------------------------------------+</pre>
|
||
|
|
<pre>+--------------------------------------------------------------------------------+
|
||
|
|
|Locale job attributes . . . . . > *CCSID *SYSVAL,*NONE, *CCSID... |
|
||
|
|
|> *DATFMT |
|
||
|
|
|> *DATSEP |
|
||
|
|
|> *TIMSEP |
|
||
|
|
|> *SRTSEQ |
|
||
|
|
|Locale . . . . . . . . . . . . . >'/qsys.lib/localelib.lib/es_es.locale' |
|
||
|
|
+--------------------------------------------------------------------------------+</pre>
|
||
|
|
</div>
|
||
|
|
<div class="section" xml:lang="en-us" id="rbagslocalemultilingenvi__creatsubsysnlangvers"><a name="rbagslocalemultilingenvi__creatsubsysnlangvers"><!-- --></a><h4 class="sectiontitle">Step 3. Create
|
||
|
|
subsystems for each national language version</h4><p>Subsystems can be
|
||
|
|
tailored to provide users an environment in which they see their own national
|
||
|
|
language with data presented in the cultural format and conventions they are
|
||
|
|
used to seeing.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Because the primary language of the system is English,
|
||
|
|
it is not necessary to create a subsystem for English.</div>
|
||
|
|
<ol><li>Type CRTSBSD and prompt (F4).</li>
|
||
|
|
<li>Specify values for the following parameters to ensure that the subsystem
|
||
|
|
is enabled for a specific national language (such as French and Spanish in
|
||
|
|
our example).<ul><li>Subsystem description <p>This can be any name you choose.</p>
|
||
|
|
</li>
|
||
|
|
<li>Text 'description' <p>The description can be anything you want it to be.</p>
|
||
|
|
</li>
|
||
|
|
<li>Sign-on display file and Library <p>This often is QDSIGNON. The important
|
||
|
|
information here is to know the name of the library where the national language
|
||
|
|
version (French in this example) is stored.</p>
|
||
|
|
</li>
|
||
|
|
<li>Subsystem library <p>It specifies a library that is entered ahead of other
|
||
|
|
libraries in the library list of jobs started in this subsystem. This parameter
|
||
|
|
allows you to use a secondary language library causing messages and displays
|
||
|
|
to appear in your spoken language.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> The correct values for Sign-on
|
||
|
|
display file library and Subsystem library parameters are determined by adding
|
||
|
|
QSYS to the national language version feature code. For example, the French
|
||
|
|
national language library is named QSYS2928.</div>
|
||
|
|
<p>The following screen
|
||
|
|
shows the correct values to ensure that users of the FRENCH subsystem
|
||
|
|
interact with the computer in the French language.</p>
|
||
|
|
<pre>+--------------------------------------------------------------------------------+
|
||
|
|
|Create Subsystem Description (CRTSBSD) |
|
||
|
|
| |
|
||
|
|
|Type choices, press Enter. |
|
||
|
|
| |
|
||
|
|
|Subsystem description . . . . . SBSD > FRENCH |
|
||
|
|
|Library . . . . . . . . . . . *CURLIB |
|
||
|
|
+--------------------------------------------------------------------------------+</pre>
|
||
|
|
<pre>+--------------------------------------------------------------------------------+
|
||
|
|
|Text 'description' . . . . . . . TEXT > 'Subsystem for French users' |
|
||
|
|
| |
|
||
|
|
| |
|
||
|
|
|Additional Parameters |
|
||
|
|
| |
|
||
|
|
|Sign-on display file . . . . . . SGNDSPF > QDSIGNON |
|
||
|
|
|Library . . . . . . . . . . . > QSYS2928 |
|
||
|
|
|Subsystem library . . . . . . . SYSLIBLE > QSYS2928 |
|
||
|
|
|More... |
|
||
|
|
|F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display |
|
||
|
|
|F24=More keys |
|
||
|
|
| |
|
||
|
|
| |
|
||
|
|
+--------------------------------------------------------------------------------+</pre>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Press Enter.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div class="section" xml:lang="en-us" id="rbagslocalemultilingenvi__moreinfosubsys"><a name="rbagslocalemultilingenvi__moreinfosubsys"><!-- --></a><h4 class="sectiontitle">Step 4. More information
|
||
|
|
about subsystems</h4><p>Creation of a subsystem requires additional work
|
||
|
|
such as:</p>
|
||
|
|
<ul><li>Setting subsystem attributes</li>
|
||
|
|
<li>Adding workstation entires</li>
|
||
|
|
<li>Adding job queue entries</li>
|
||
|
|
<li>Adding communications entires (if your national language users are attached
|
||
|
|
over communications lines)</li>
|
||
|
|
<li>Adding autostart job entires if you want to use this feature</li>
|
||
|
|
<li>Adding prestart job entires if you want to use this feature</li>
|
||
|
|
<li>Creating a class</li>
|
||
|
|
<li>Adding routing entries</li>
|
||
|
|
</ul>
|
||
|
|
<p>How to perform the tasks in the previous list is not described in
|
||
|
|
this example.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagslocaleprogexamp.htm" title="In addition to the examples in this topic, The locale categories information provides programming examples for each of the different locale categories.">Examples: Locale programming</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbagsnatlangfeatcode.htm" title="This table lists the available national language version feature codes.">National language version feature codes</a></div>
|
||
|
|
<div><a href="../rzaks/rzaks1.htm">Work management</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|