144 lines
9.9 KiB
HTML
144 lines
9.9 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="Object naming rules" />
|
||
|
|
<meta name="abstract" content="This describes rules for naming i5/OS objects." />
|
||
|
|
<meta name="description" content="This describes rules for naming i5/OS objects." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6objects.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6commnames.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6genericnames.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6names.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6pathnames.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6snames.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6uniquenamerules.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6hownamed.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6nameincom.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6genobj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6nameincom.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6folddocnames.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="rbam6objnamrules" />
|
||
|
|
<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>Object naming rules</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbam6objnamrules"><a name="rbam6objnamrules"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Object naming rules</h1>
|
||
|
|
<div><p>This describes rules for naming i5/OS™ objects.</p>
|
||
|
|
<p> In addition, the following rules are used to name all i5/OS objects
|
||
|
|
used in control language commands. The parameter summary table for each CL
|
||
|
|
command shows whether a simple object name, a qualified name, or a generic
|
||
|
|
name can be specified. </p>
|
||
|
|
<dl><dt class="dlterm">Naming a Single Object</dt>
|
||
|
|
<dd>In the name of a single object, each part (the simple name and the library
|
||
|
|
qualifier name) can have a maximum of 10 characters.</dd>
|
||
|
|
<dt class="dlterm">Naming a User-Created Object</dt>
|
||
|
|
<dd>To distinguish a user-created object from an IBM-supplied object, you
|
||
|
|
should not begin user-created object names with Q because the names of all
|
||
|
|
IBM-supplied objects (except commands) begin with Q. Although you can use
|
||
|
|
as many as 10 characters in CL object names, you may need to use fewer characters
|
||
|
|
to be consistent with the naming rules of the particular high-level language
|
||
|
|
that you are also using. Also, the high-level language might not allow underscores
|
||
|
|
in the naming rules. For example, RPG limits file names to eight characters
|
||
|
|
and does not allow underscores.</dd>
|
||
|
|
<dt class="dlterm">Naming a Generic Object</dt>
|
||
|
|
<dd>In a generic name, a maximum of nine alphanumeric characters can be used,
|
||
|
|
not including the asterisk (*) that must immediately follow the last character. <p>INV
|
||
|
|
and INV* are valid values where a generic name is accepted. When the name
|
||
|
|
INV is specified, only the object INV is referenced. When the generic name
|
||
|
|
INV* is specified, objects that begin with INV are referred to, such as INV,
|
||
|
|
INVOICE, INVENTORY, and INVENPGM1. When the quoted generic name "INV*" is
|
||
|
|
specified, objects that begin with "INV" are referred to, such as "INV%1"
|
||
|
|
and "INV>."</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Object Library Qualifier Limitations</dt>
|
||
|
|
<dd>No library qualifier can be specified with the object name if the object
|
||
|
|
being created is a library, user profile, line description, controller description,
|
||
|
|
device description, mode description, class-of-service description, or configuration
|
||
|
|
list. A library name can never be qualified because a library cannot be placed
|
||
|
|
in a library. The other object types (*USRPRF, *LIND, *CTLD, *DEVD, *MODD,
|
||
|
|
*COSD, and *CFGL) appear to be types that exist only in the QSYS library.
|
||
|
|
When only the name of an object of these object types is accepted, a library
|
||
|
|
qualifier cannot be specified with the object name. On the <span class="cmdname">Display
|
||
|
|
Object Description (DSPOBJD)</span> command, where any object name is accepted,
|
||
|
|
QSYS can be specified.</dd>
|
||
|
|
<dt class="dlterm">Library List Qualifiers</dt>
|
||
|
|
<dd>The predefined value *LIBL (and others, such as *CURLIB) can be used in
|
||
|
|
place of a library name in most commands. *LIBL indicates that the libraries
|
||
|
|
named in the job's library list are used to find the object named in the second
|
||
|
|
part of the qualified name.</dd>
|
||
|
|
<dt class="dlterm">Duplicate Object Names</dt>
|
||
|
|
<dd>Duplicate names are not allowed for objects of the same type in the same
|
||
|
|
library. <p>Two objects with the same name cannot be stored in the same library
|
||
|
|
unless their object types are different. Two objects named OBJA can be stored
|
||
|
|
in the library LIBx only if, for example, one of the objects is a program
|
||
|
|
and the other is a file. The following combinations of names and object types
|
||
|
|
could all exist on the system at the same time.</p>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
<p> <img src="rbam6503.gif" alt=" Name and Object Type Combinations" /> </p>
|
||
|
|
<p>If more than one library contains an object with the same name (and both
|
||
|
|
libraries are in the same library list) and a library qualifier is not specified
|
||
|
|
with the object name, the first object found by that name is used. Therefore,
|
||
|
|
when you have multiple objects with the same name, you should specify the
|
||
|
|
library name with the object name or ensure that the appropriate library occurs
|
||
|
|
first in the library list. For example, if you are testing and debugging and
|
||
|
|
choose not to qualify the names, ensure that your test library precedes your
|
||
|
|
production library in the library list.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Default libraries</h4><p>In a qualified object name, the
|
||
|
|
library name is usually optional. If an optional library qualifier is not
|
||
|
|
specified, the default given in the command's description is used (usually
|
||
|
|
either *CURLIB or *LIBL). If the named object is being created, the current
|
||
|
|
library is the default; when the object is created, it is placed either in
|
||
|
|
the current library or in the QGPL (the general purpose library ) if no current
|
||
|
|
library is defined. For objects that already exist, *LIBL is the default for
|
||
|
|
most commands, and the job's library list is used to find the named object.
|
||
|
|
The system searches all of the libraries currently in the library list until
|
||
|
|
it finds the object name specified.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6commnames.htm">Communication names (*CNAME)</a></strong><br />
|
||
|
|
This describes the rules for creating communication names.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6genericnames.htm">Generic names (*GENERIC)</a></strong><br />
|
||
|
|
A generic name is one that contains at least one initial character that is common to a group of objects, followed by an asterisk.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6names.htm">Names (*NAME)</a></strong><br />
|
||
|
|
This describes the rules for creating basic names and basic names in quoted form.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6pathnames.htm">Path names (*PNAME)</a></strong><br />
|
||
|
|
A path name is a character string that can be used to locate objects in the integrated file system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6snames.htm">Simple Names (*SNAME)</a></strong><br />
|
||
|
|
This describes the difference between simple names and basic names, and the circumstances when simple names should be used.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6uniquenamerules.htm">Additional rules for unique names</a></strong><br />
|
||
|
|
This describes additional rules involving special characters for object naming.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbam6objects.htm" title="An i5/OS object is a named unit that exists (occupies space) in storage, and on which operations are performed by the operating system. i5/OS objects provide the means through which all data processing information is stored and processed by i5/OS.">Objects</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbam6nameincom.htm" title="You can use only specific characters for naming within commands.">Naming within commands</a></div>
|
||
|
|
<div><a href="rbam6genobj.htm" title="Generic object names can be used when referring to multiple objects with similar names.">Generic object names</a></div>
|
||
|
|
<div><a href="rbam6folddocnames.htm" title="Folder and document names should describe the contents of the folder or document.">Folder and document names</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbam6hownamed.htm" title="The command name identifies the function that will be performed by the program that is called when the command is run. Most command names consist of a combination of a verb (or, action) followed by a noun or phrase that identifies the receiver of the action (or object being acted on): (command = verb + object acted on).">Command names</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|