ibm-information-center/dist/eclipse/plugins/i5OS.ic.ifs_5.4.0.1/rzaaxnlsname.htm

67 lines
4.9 KiB
HTML
Raw Permalink 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="reference" />
<meta name="DC.Title" content="Naming and international support" />
<meta name="abstract" content="The support for the root (/) and QOpenSys file systems ensures that the characters in object names remain constant across encoding schemes used for different national languages and devices." />
<meta name="description" content="The support for the root (/) and QOpenSys file systems ensures that the characters in object names remain constant across encoding schemes used for different national languages and devices." />
<meta name="DC.subject" content="integrated file system, programming interfaces, national language support, names, continuity across national languages, national language support, code page, character conversion, extended attributes, continuity across national languages, conversion, object names, encoding schemes" />
<meta name="keywords" content="integrated file system, programming interfaces, national language support, names, continuity across national languages, national language support, code page, character conversion, extended attributes, continuity across national languages, conversion, object names, encoding schemes" />
<meta name="DC.Relation" scheme="URI" content="rzaaxpgmifs.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaaxunicode.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaaxnlsname" />
<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>Naming and international support</title>
</head>
<body id="rzaaxnlsname"><a name="rzaaxnlsname"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Naming and international support</h1>
<div><p>The support for the <span class="q">"root"</span> (/) and QOpenSys file systems ensures
that the characters in object names remain constant across encoding schemes
used for different national languages and devices.</p>
<div class="section"><p>When an object name is passed to the system, each character of
the name is converted to a 16-bit form in which all characters have a standard
coded representation.
When the name is used, it is converted to the proper coded form for the code
page being used.</p>
</div>
<div class="section"><p>If the code page to which the name is being converted does not
contain a character used in a name, the name is rejected as not valid.</p>
</div>
<div class="section"><p>Because characters remain constant across code pages, you should
not do an operation on the assumption a particular character will change to
another particular character when a specific code page is used. For example,
you should not assume the number sign character will change to the pound sterling
character even though they may have the same coded representation in different
code pages.</p>
</div>
<div class="section"><p>Note that the names of the extended attributes of an object are
converted in the same way as the name of the object, so the same considerations
apply.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxpgmifs.htm" title="The addition of the integrated file system to the iSeries server server in V3R1M0 did not affect existing iSeries server applications. The programming languages, utilities, and system support (such as data description specifications) operate in the same way as they did before the addition of the integrated file system.">Programming support</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzaaxunicode.htm" title="When you use the root (/), QOpenSys, and user-defined file systems, you can take advantage of system support that ensures characters in object names remain the same.">Name continuity</a></div>
</div>
</div>
</body>
</html>