94 lines
7.2 KiB
HTML
94 lines
7.2 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="Path name" />
|
||
|
<meta name="abstract" content="A path name (also called a pathname on some systems) tells the server how to locate an object." />
|
||
|
<meta name="description" content="A path name (also called a pathname on some systems) tells the server how to locate an object." />
|
||
|
<meta name="DC.subject" content="path name, what is it?, absolute path name, example, path names, relative path name, relative path name" />
|
||
|
<meta name="keywords" content="path name, what is it?, absolute path name, example, path names, relative path name, relative path name" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxbasics.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxrootpath.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxopenpath.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxiasppath.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxntpath.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxos4path.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxoptpath.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxapipath.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxcmdpath.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxlibpath.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxqdlspath.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudfspath.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="rzaaxpath" />
|
||
|
<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>Path name</title>
|
||
|
</head>
|
||
|
<body id="rzaaxpath"><a name="rzaaxpath"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Path name</h1>
|
||
|
<div><p>A <dfn class="term">path name</dfn> (also called a <span>pathname</span> on some systems) tells the server how
|
||
|
to locate an object. </p>
|
||
|
<p>The path name is expressed as a sequence of directory names followed by
|
||
|
the name of the object. Individual directories and the object name are separated
|
||
|
by a slash (/) character; for example: </p>
|
||
|
<pre> directory1/directory2/file</pre>
|
||
|
<p>For your convenience, the backslash (\) can be used instead of the slash
|
||
|
in integrated file system commands.</p>
|
||
|
<p>There are two ways of indicating a path name: </p>
|
||
|
<ul><li>An <dfn class="term">absolute path name</dfn> begins at the
|
||
|
highest level, or <span class="q">"root"</span> directory (which is identified by the / character).
|
||
|
For example, consider the following path from the / directory to the file
|
||
|
named Smith. <div class="fignone"><span class="figcap">Figure 1. The components of a path name</span><br /><img src="rv3n067.gif" alt="The components of a path name" /><br /></div>
|
||
|
<p>The absolute path name to the Smith file is as follows: </p>
|
||
|
<pre> /Dept2/Photo/Smith</pre>
|
||
|
<p>The
|
||
|
absolute path name is also known as the <dfn class="term">full
|
||
|
path name</dfn>.</p>
|
||
|
</li>
|
||
|
<li>If the path name does not begin with the / character, the system assumes
|
||
|
that the path begins at your current directory. This type of path name is
|
||
|
called a <span>relative path name</span>. For example,
|
||
|
if your current directory is Dept2 and it has a subdirectory named Photo
|
||
|
containing the file Smith, the relative path name to the file is: <pre> Photo/Smith</pre>
|
||
|
<p>Notice
|
||
|
that the path name does not include the name of the current directory. The
|
||
|
first item in the name is the directory or object at the <em>next level below</em> the
|
||
|
current directory.</p>
|
||
|
</li>
|
||
|
</ul>
|
||
|
</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="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="rzaaxopenpath.htm" title="Path names have specific form in the QOpenSys file system.">Path names in the QOpenSys file system</a></div>
|
||
|
<div><a href="rzaaxiasppath.htm" title="Each component of the path name must contain the object name followed by the object type of the object.">Path names in the independent ASP QSYS.LIB file system</a></div>
|
||
|
<div><a href="rzaaxntpath.htm" title="The path consists of the file system name, the server name, the share name, the directory and subdirectory names, and the object name.">Path names in the QNTC 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="rzaaxoptpath.htm" title="The path name must begin with a slash (/). The path is made up of the file system name, the volume name, the directory and subdirectory names, and the file name.">Path names in the QOPT file system</a></div>
|
||
|
<div><a href="rzaaxapipath.htm" title="When using an integrated file system or ILE C/400 API to operate on an object, you identify the object by supplying its directory path. Here is a summary of rules to keep in mind when specifying path names in the APIs.">Path name rules for APIs</a></div>
|
||
|
<div><a href="rzaaxcmdpath.htm" title="When using an integrated file system command or display to operate on an object, you identify the object by supplying its path name.">Path name rules for CL commands and displays</a></div>
|
||
|
<div><a href="rzaaxlibpath.htm" title="Each component of the path name must contain the object name followed by the object type of the object.">Path names in the QSYS.LIB file system</a></div>
|
||
|
<div><a href="rzaaxqdlspath.htm" title="Each component of the path name can consist of just a name.">Path names in the QDLS 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>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|