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

74 lines
6.0 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="Name continuity" />
<meta name="abstract" content="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." />
<meta name="description" content="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." />
<meta name="DC.subject" content="names, continuity across encoding schemes, national language support, code page, character conversion, encoding schemes, unicode, conversion, object names, extended attributes, continuity across national languages" />
<meta name="keywords" content="names, continuity across encoding schemes, national language support, code page, character conversion, encoding schemes, unicode, conversion, object names, extended attributes, continuity across national languages" />
<meta name="DC.Relation" scheme="URI" content="rzaaxbasics.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaaxtype2.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaaxrootpath.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaaxudfspath.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaaxos4path.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaaxnlsname.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="rzaaxunicode" />
<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>Name continuity</title>
</head>
<body id="rzaaxunicode"><a name="rzaaxunicode"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Name continuity</h1>
<div><p>When you use the <span class="q">"root"</span> (/), QOpenSys, and user-defined file
systems, you can take advantage of system support that ensures characters
in object names remain the same.</p>
<p>This also applies when you use these file systems across <span class="keyword">iSeries™ server</span>s
and connected devices that have different character encoding schemes (code
pages). Your server stores the characters in the names in a 16-bit form that
is known as UCS2 Level 1 (that is also called <em>Unicode</em>) for *TYPE1 directories
and UTF-16 for *TYPE2 directories.
UCS2 Level 1 and UTF-16 are subsets of the ISO 10646 standard. When the
name is used, the system converts the stored form of the characters into the
proper character representation in the code page being used. The names of
extended attributes associated with each object are also handled the same
way.</p>
<div class="fignone"><span class="figcap">Figure 1. Keep characters the same across encoding schemes</span><br /><img src="rv3n141.gif" alt="Keeping characters the same across encoding schemes" /><br /></div>
<p>This support makes it easier to interact with a server from devices using
different code pages. For example, PC users can access an iSeries server
file using the same file name, even though their PCs do not have the same
code page as your server. The conversion from one code page to another is
handled automatically by your server. Of course, the device must be using
a code page that contains the characters used in the name.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxbasics.htm" title="This topic introduces the basic concepts of integrated file system, such as directory, link, path name, stream file, name continuity, extended attributes, and scanning support.">Integrated file system concepts</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzaaxtype2.htm" title="The &#34;root&#34; (/), QOpenSys, and user-defined file systems (UDFS) in the integrated file system support the *TYPE2 directory format. The *TYPE2 directory format is an enhancement of the original *TYPE1 directory format.">*TYPE2 directories</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rzaaxrootpath.htm" title="Path names have specific form in the root (/) file system.">Path names in the "root" (/) file system</a></div>
<div><a href="rzaaxudfspath.htm" title="A block special file (*BLKSF) represents a user-defined file system (UDFS) when the entire UDFS and all of the objects within it need to be manipulated.">Path names in an integrated file system user-defined file system</a></div>
<div><a href="rzaaxos4path.htm" title="Path names have specific form in the QFileSvr.400 file system.">Path names in the QFileSvr.400 file system</a></div>
<div><a href="rzaaxnlsname.htm" title="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.">Naming and international support</a></div>
</div>
</div>
</body>
</html>