ibm-information-center/dist/eclipse/plugins/i5OS.ic.nls_5.4.0.1/rbagsapppartnames.htm

106 lines
5.8 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="Application part names" />
<meta name="abstract" content="When you want to enable your application for different languages and countries, consider the environments of the target systems in your naming conventions." />
<meta name="description" content="When you want to enable your application for different languages and countries, consider the environments of the target systems in your naming conventions." />
<meta name="DC.Relation" scheme="URI" content="rbagsarngandarchdsgngd.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsinvariantcharset.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsdatabasedefs.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="rbagsapppartnames" />
<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>Application part names</title>
</head>
<body id="rbagsapppartnames"><a name="rbagsapppartnames"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Application part names</h1>
<div><p>When you want to enable your application for different languages
and countries, consider the environments of the target systems in your naming
conventions.</p>
<p>Use characters that are available, can be displayed, and can be printed
in all the target environments. Use only characters of the invariant character
set whenever you specify names for:</p>
<ul><li>Libraries</li>
<li>Database files</li>
<li>Device files (display or printer)</li>
<li>Help panels</li>
<li>Message files</li>
<li>User commands</li>
<li>Programs</li>
<li>Record formats</li>
<li>Fields</li>
</ul>
<p>All other characters either vary their meaning or might not be available
on the keyboard.</p>
<p>To create an internationalized application, you need to divide your application
objects into related parts that are textual data and nontextual data. Your
naming conventions should be able to distinguish between these parts. You
should also be able to distinguish between the textual data of different languages.
You can do this by separating the objects into different libraries.</p>
<div class="section"><h4 class="sectiontitle">Scenario: Library naming convention</h4><p>Your library
naming convention can look like this:</p>
<pre>AAATTTLL</pre>
<p>where:
<span class="uicontrol">AAA</span> is the application identification; <span class="uicontrol">TTT</span> is
the type of objects; and <span class="uicontrol">LLL</span> is the language code.</p>
<p>This
naming convention allows you to have all libraries that belong to an application
grouped together because you have a unique identifier (AAA) at the beginning.</p>
<p>The
second part (TTT) allows you to distinguish between different types of objects:</p>
<dl><dt class="dlterm">Textual data</dt>
<dd> <ul><li>Display files</li>
<li>Printer files</li>
<li>Message files</li>
<li>Help panels</li>
<li>User command</li>
<li>Cultural values</li>
<li>Database files with NLS-sensitive information and specifications</li>
<li>NLS-dependent program modules</li>
</ul>
</dd>
<dt class="dlterm">Nontextual data</dt>
<dd>Programs</dd>
<dt class="dlterm">Data</dt>
<dd>Database files</dd>
</dl>
<p>The third part (LLL) allows you to specify the national
language version for all the textual data parts. This allows you to use the
same names for objects of the different national language versions within
the different libraries. Your program is able to use different objects by
just rearranging the library list accordingly when the job is run.</p>
<p>The
initial library list can be taken from the job description. You can build
a new library list by specifying the library list in the INLLIBL parameter
of the Create Job Description (CRTJOBD) command for a new job description,
or of the Change Job Description (CHGJOBD) command for an existing
job description. The following figure shows an example of this.</p>
<br /><img src="rbags505.gif" alt="Application in two different language versions" /><br /></div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsarngandarchdsgngd.htm" title="When you design an international application, consider the ways that you can organize and structure your application so that it can be used in an international environment.">Application arrangement and architecture</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rbagsinvariantcharset.htm">Invariant character set</a></div>
<div><a href="rbagsdatabasedefs.htm" title="You define a file to specify certain facts, and the specifications are then used on database files.">Database definitions</a></div>
</div>
</div>
</body>
</html>