ibm-information-center/dist/eclipse/plugins/i5OS.ic.rbam6_5.4.0.1/rbam6folddocnames.htm

134 lines
7.8 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="Folder and document names" />
<meta name="abstract" content="Folder and document names should describe the contents of the folder or document." />
<meta name="description" content="Folder and document names should describe the contents of the folder or document." />
<meta name="DC.Relation" scheme="URI" content="rbam6nameincom.htm" />
<meta name="DC.Relation" scheme="URI" content="../books/sc415121.pdf" />
<meta name="DC.Relation" scheme="URI" content="../cl/crtdevdsp.htm" />
<meta name="DC.Relation" scheme="URI" content="rbam6objnamrules.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="rbam6folddocnames" />
<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>Folder and document names</title>
</head>
<body id="rbam6folddocnames"><a name="rbam6folddocnames"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Folder and document names</h1>
<div><p>Folder and document names should describe the contents of the folder
or document.</p>
<p> Folder names must be unique and should be easy to type, as well as descriptive
to a user. To find a particular folder on the system and change a document
stored in it, you must either supply the folder name or select it from a list
of names.</p>
<p>Document names must be unique in the folder and should be easy to type,
as well as descriptive. You should give careful consideration to the names
you use to help you find the document later.</p>
<p>The name you use for a folder or a document must follow these rules:</p>
<ul><li>The name must be unique within a folder.</li>
<li>A document or folder name can be 1 to 12 characters long, including an
optional extension. If no extension is included, a document or folder name
can have a maximum of eight characters. If an extension is included, the extension
must start with a period and can have up to three additional characters. An
extension in the document name allows you to identify the document by using
specific information that can help you do a selective listing of documents
on your system. <p> <img src="rbam6504.gif" alt="Art3-2" /> </p>
</li>
<li>A document or folder name can include any single-byte EBCDIC character
<em>except for the following</em> special characters that the system uses for
other purposes:
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="27.1356783919598%" id="d0e44">Character</th>
<th valign="top" width="72.8643216080402%" id="d0e46">Special uses</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="27.1356783919598%" headers="d0e44 ">Asterisk (*)</td>
<td valign="top" width="72.8643216080402%" headers="d0e46 ">Multiplication operator, indicates generic names, and indicates i5/OS™
reserved values</td>
</tr>
<tr><td valign="top" width="27.1356783919598%" headers="d0e44 ">Slash (/)</td>
<td valign="top" width="72.8643216080402%" headers="d0e46 ">Division operator, delimiter within system values, and separates parts
of qualified object names</td>
</tr>
<tr><td valign="top" width="27.1356783919598%" headers="d0e44 ">Question Mark (?)</td>
<td valign="top" width="72.8643216080402%" headers="d0e46 ">Initiates requests for system help</td>
</tr>
</tbody>
</table>
</div>
</li>
<li>When a folder is stored in another folder, both folder names are used,
separated by a slash (/). That combination of names is called a <strong>folder
path</strong>. For example, if a folder named FOLDR2 is stored in FOLDR1, the path
for FOLDR2 is FOLDR1/FOLDR2. FOLDR1 is the <strong>first-level folder</strong>. FOLDR2
is the <strong>next-level folder</strong>. The name of a single folder can be 1 to
12 characters long, including an optional extension. A folder path can contain
a maximum of 63 characters. <p>Folder names should not begin with Q because
the system-supplied folder names begin with Q. The following are examples
of permitted folder names and folder paths:</p>
<pre>@LETTERS
FOLDER.PAY
PAYROLL/FOLDER.PAY
#TAX1/FOLD8.TAX/$1988/PAYROLL/FOLDER.PAY</pre>
</li>
</ul>
<div class="note"><span class="notetitle">Note:</span> <ol><li>In CL commands, folder path names must be enclosed in apostrophes to prevent
the system from processing them as qualified (library/object) names. If an
apostrophe is to be part of the name, it must be specified as two consecutive
apostrophes. </li>
<li>A number of CL commands act on either documents or folders, and some act
on both. The abbreviation DLO (document library object) is used when referring
to either a document or folder. </li>
<li>In CL commands, folder and document names must be enclosed in apostrophes
if they contain characters that are CL delimiters. </li>
<li>The system does not recognize graphic characters; it recognizes only code
points and uses the following assumptions: <ul><li>All folder and document names are encoded using single-byte EBCDIC code
pages. Since code points hex 41 through FE represent graphic characters in
those code pages, they are the only code points that can be used in folder
and document names.</li>
<li>Code points hex 5C, 61, and 6F represent the asterisk (*), slash (/),
and question mark (?) respectively, and cannot be used in folder and document
names.</li>
<li>The code points for lowercase letters in English (hex 81 through 89, 91
through 99, and A2 through A9) are converted to the code points for uppercase
letters (C1 through C9, D1 through D9, and E2 through E9, respectively).</li>
</ul>
</li>
</ol>
</div>
<p>In addition to the folder and document names previously described, folders
and documents are internally classified in the system by their system object
names. These are 10-character names derived from date/time stamps, and, while
they are generally not known to the user, they may be specified on some CL
commands by specifying *SYSOBJNAM for the folder or document name and by specifying
the system object name in a separate parameter.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbam6nameincom.htm" title="You can use only specific characters for naming within commands.">Naming within commands</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rbam6objnamrules.htm" title="This describes rules for naming i5/OS objects.">Object naming rules</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../books/sc415121.pdf" target="_blank">Local device configuration</a></div>
<div><a href="../cl/crtdevdsp.htm">Create Device Desc (Display) (CRTDEVDSP) command</a></div>
</div>
</div>
</body>
</html>