134 lines
9.1 KiB
HTML
134 lines
9.1 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="reference" />
|
|
<meta name="DC.Title" content="NetWare file system (QNetWare)" />
|
|
<meta name="abstract" content="The QNetWare file system provides access to data on stand-alone PC servers that are running Novell NetWare 5.1 or 6.0." />
|
|
<meta name="description" content="The QNetWare file system provides access to data on stand-alone PC servers that are running Novell NetWare 5.1 or 6.0." />
|
|
<meta name="DC.subject" content="file system, NetWare file system (QNetWare), characteristics and limitations, NetWare file system (QNetWare), characteristics and limitations, QNetWare file system" />
|
|
<meta name="keywords" content="file system, NetWare file system (QNetWare), characteristics and limitations, NetWare file system (QNetWare), characteristics and limitations, QNetWare file system" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxfsknow.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxqnetauth.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxqnetaudit.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxqnetfile.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxqnetnds.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxqnetlinks.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxqnetifscom.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxqnetapi.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="rzaaxqnetw" />
|
|
<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>NetWare file system (QNetWare)</title>
|
|
</head>
|
|
<body id="rzaaxqnetw"><a name="rzaaxqnetw"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">NetWare file system (QNetWare)</h1>
|
|
<div><p><span>The QNetWare file system provides access
|
|
to data on stand-alone PC servers that are running Novell NetWare 5.1 or 6.0.</span></p>
|
|
<div class="section"><p>In addition, QNetWare also provides the following functionality:</p>
|
|
<ul><li>Provides access to NetWare Directory Services (NDS) objects.</li>
|
|
<li>Supports data stored in stream files.</li>
|
|
<li>Provides dynamic mounting of NetWare file systems
|
|
into the local name space</li>
|
|
</ul>
|
|
</div>
|
|
<div class="section"> <div class="note"><span class="notetitle">Notes:</span> <ol><li>The QNetWare file system is available only when NetWare Enhanced Integration,
|
|
BOSS option 25, is installed on the system. After the next IPL following
|
|
the installation, the <samp class="codeph">/QNetWare</samp> directory and its subdirectories
|
|
appear as part of the integrated file system directory structure.</li>
|
|
<li>The NetWare Enhanced Integration product does not support Novell Storage
|
|
Services (NSS), so access to the data contained on that partition might be
|
|
limited or restricted.</li>
|
|
</ol>
|
|
</div>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Mount NetWare file systems</h4><p>NetWare file systems
|
|
located on Novell NetWare servers can be mounted on the <span class="q">"root"</span> (/), QOpenSys,
|
|
and other file systems to make access easier and perform better than under
|
|
the <samp class="codeph">/QNetWare</samp> directory.</p>
|
|
<p>Mounting NetWare file systems
|
|
can also be used to take advantage of the options on the <span class="cmdname">Add Mounted
|
|
File System (ADDMFS)</span> command, such as mounting a read-write file
|
|
system as read-only. See the <a href="../cl/addmfs.htm"><span class="cmdname">Add
|
|
Mounted File System (ADDMFS)</span> command</a> topic for more information.</p>
|
|
<div class="p">NetWare
|
|
file systems can be mounted using an NDS path or by specifying a NetWare path
|
|
in the form of <samp class="codeph">SERVER/VOLUME:directory/directory</samp>. For example,
|
|
to mount the directory <samp class="codeph">doorway</samp> located in volume <samp class="codeph">Nest</samp> on
|
|
server <samp class="codeph">Dreyfuss</samp>, you would use this syntax: <pre>DREYFUSS/NEST:doorway</pre>
|
|
</div>
|
|
<p>This
|
|
path syntax is very similar to the NetWare MAP command syntax. NDS paths
|
|
can be used to specify a path to a NetWare volume but cannot themselves be
|
|
mounted.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">QNetWare directory structure</h4><p>The <samp class="codeph">/QNetWare</samp> directory
|
|
structure represents multiple distinct file systems. </p>
|
|
<ul><li>The structure represents Novell NetWare servers and volumes out in the
|
|
network in the following form: <pre>/QNetWare/SERVER.SVR/VOLUME</pre>
|
|
<p>The
|
|
extension <samp class="codeph">.SVR</samp> is used to represent a Novell NetWare server.</p>
|
|
</li>
|
|
<li>When a volume under a server is accessed either through the integrated
|
|
file system menus, commands, or APIs, the root directory of the NetWare volume
|
|
is automatically mounted on the VOLUME directory under <samp class="codeph">/QNetWare</samp>.</li>
|
|
<li>QNetWare represents NDS trees on the network in the following form: <div class="p"> <pre>/QNetWare/CORP_TREE.TRE/USA.C/ORG.O/ORG_UNIT.OU/SVR1_VOL.CN</pre>
|
|
</div>
|
|
<p>The extension <samp class="codeph">.TRE</samp> is used to represent NDS trees, <samp class="codeph">.C</samp> represents
|
|
countries, <samp class="codeph">.O</samp> represents organizations, <samp class="codeph">.OU</samp> represents
|
|
organizational units, and <samp class="codeph">.CN</samp> is used to represent common
|
|
names. If a Novell NetWare volume is accessed through the NDS path through
|
|
a volume object or an alias to a volume object, it's root directory is also
|
|
automatically mounted on the NDS object.</p>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Use QNetWare through the integrated file system interface</h4><p>The
|
|
QNetWare file system can be accessed through the integrated file system interface
|
|
using either the <span class="keyword">i5/OS™</span> file
|
|
server or the integrated file system commands, user displays, and APIs.</p>
|
|
<p>You
|
|
should be aware of the following considerations, limitations, and dependencies.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzaaxqnetauth.htm">Authorities and ownership in the QNetWare file system</a></strong><br />
|
|
Files and directories in QNetWare are stored and managed by Novell NetWare servers.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxqnetaudit.htm">Audit in the QNetWare file system</a></strong><br />
|
|
Although Novell NetWare supports the auditing of files and directories,
|
|
the QNetWare file system cannot change the auditing values of these objects.
|
|
Therefore, the <span class="cmdname">Change Auditing Value (CHGAUD)</span> command
|
|
is not supported.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxqnetfile.htm">Files and directories in the QNetWare file system</a></strong><br />
|
|
The QNetWare file system does not preserve the case in which files or directories are entered in a command or API.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxqnetnds.htm">NetWare Directory Services objects in the QNetWare file system</a></strong><br />
|
|
The QNetWare file system supports the display of NetWare Directory Services (NDS) names in uppercase and lowercase.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxqnetlinks.htm">Links in the QNetWare file system</a></strong><br />
|
|
The QNetWare file system supports only one link to an object. Symbolic links cannot be created or stored in QNetWare.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxqnetifscom.htm">Use integrated file system commands and displays in the QNetWare file system</a></strong><br />
|
|
Many integrated file system commands and displays are valid in the QNetWare file system</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxqnetapi.htm">Use integrated file system APIs in the QNetWare file system</a></strong><br />
|
|
Many integrated file system APIs are valid in the QNetWare file system.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxfsknow.htm" title="A file system provides you the support to access specific segments of storage that are organized as logical units. These logical units on your server are files, directories, libraries, and objects.">Work with file systems</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |