126 lines
7.8 KiB
HTML
126 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="Objects" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.subject" content="object, types, naming" />
|
||
|
|
<meta name="keywords" content="object, types, naming" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6clconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6libraries.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6objecttypes.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6simpqual.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6genobj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6objnamrules.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="objec.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="rbam6objects" />
|
||
|
|
<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>Objects</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbam6objects"><a name="rbam6objects"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Objects</h1>
|
||
|
|
<div><p>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. </p>
|
||
|
|
<p>Objects are the basic units on which commands perform operations. For example,
|
||
|
|
programs and files are objects. Through objects you can find, maintain, and
|
||
|
|
process your data on the iSeries™ server. You need only know what object and
|
||
|
|
what function (command) you want to use; you do not need to know the storage
|
||
|
|
address of your data to use it.</p>
|
||
|
|
<p>CL commands perform operations on the i5/OS objects. Several types of i5/OS objects
|
||
|
|
are created and used in the control language. i5/OS objects have the following in common:</p>
|
||
|
|
<ul><li>Objects have a set of descriptive attributes that are defined when the
|
||
|
|
object is created.</li>
|
||
|
|
<li>Objects have to be used by the system to perform a specific function must
|
||
|
|
be specified in the CL command that performs that function.</li>
|
||
|
|
<li>Objects have a set of attributes that describe it and give the specific
|
||
|
|
values assigned for those attributes.</li>
|
||
|
|
<li>Generally, objects are independent of all other objects. However, some
|
||
|
|
objects must be created before other objects can be created; for example,
|
||
|
|
a logical file cannot be created if the physical file it must be based on
|
||
|
|
does not exist.</li>
|
||
|
|
<li>Objects must be created before other operations that use the object are
|
||
|
|
performed. Descriptions of the create commands (those commands that begin
|
||
|
|
with the letters CRT) give more information about the object types that they
|
||
|
|
create.</li>
|
||
|
|
<li>Every i5/OS object
|
||
|
|
that is used by the control language has a name. The object name specified
|
||
|
|
in a CL command identifies which object is used by the operating system to
|
||
|
|
perform the function of the command.</li>
|
||
|
|
<li>Objects have either a simple, qualified, or generic name.</li>
|
||
|
|
</ul>
|
||
|
|
<p>The system supports various unique types of objects. Some types identify
|
||
|
|
objects common to many data processing systems, such as: </p>
|
||
|
|
<ul><li>Files</li>
|
||
|
|
<li>Programs</li>
|
||
|
|
<li>Commands</li>
|
||
|
|
<li>Libraries</li>
|
||
|
|
<li>Queues</li>
|
||
|
|
<li>Modules</li>
|
||
|
|
<li>Service programs</li>
|
||
|
|
</ul>
|
||
|
|
<p>Other object types are less familiar, such as: </p>
|
||
|
|
<ul><li>User profiles</li>
|
||
|
|
<li>Job descriptions</li>
|
||
|
|
<li>Subsystem descriptions</li>
|
||
|
|
<li>Device descriptions</li>
|
||
|
|
</ul>
|
||
|
|
<p>Different object types have different operational characteristics. These
|
||
|
|
differences make each object type unique. For example, because a file is
|
||
|
|
an object that contains data, its operational characteristics differ from
|
||
|
|
those of a program, which contains instructions.</p>
|
||
|
|
<p>Each object has a name. The object name and the object type are used to
|
||
|
|
identify an object. The object name is assigned by the user creating the
|
||
|
|
object. The object type is determined by the command used to create the object.
|
||
|
|
For example, if a program was created and given the name OEUPDT (for <em>order
|
||
|
|
entry update</em>), the program could always be referred to by that name.
|
||
|
|
The system uses the object name (OEUPDT) and object type (program) to locate
|
||
|
|
the object and perform operations on it. Several objects can have the same
|
||
|
|
name, but they must either be different object types or be stored in different
|
||
|
|
libraries.</p>
|
||
|
|
<p>The system maintains integrity by preventing the misuse of certain functions,
|
||
|
|
depending on the object type. For example, the command CALL causes a program
|
||
|
|
object to run. If you specified CALL and named a file, the command would
|
||
|
|
fail unless there happened to be a program with the same name.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6libraries.htm">Library objects</a></strong><br />
|
||
|
|
A library is an object that is used to group related objects, and to find objects by name when they are used. Thus, a library is a directory to a group of objects.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6objecttypes.htm">External object types</a></strong><br />
|
||
|
|
This topic provides information about various external object types and their default libraries.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6simpqual.htm">Simple and qualified object names</a></strong><br />
|
||
|
|
The name of a specific object that is located in a library can be specified as a simple name or as a qualified name.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6genobj.htm">Generic object names</a></strong><br />
|
||
|
|
Generic object names can be used when referring to multiple objects with similar names.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbam6objnamrules.htm">Object naming rules</a></strong><br />
|
||
|
|
This describes rules for naming i5/OS objects.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbam6clconcepts.htm" title="This describes concepts useful when using control language (CL) commands.">CL concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="objec.htm" title="This provides tasks and concepts specific to objects and libraries, including functions performed on objects, creating libraries, and specifying object authority.">Objects and libraries</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|