102 lines
7.5 KiB
HTML
102 lines
7.5 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="Library objects" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.subject" content="object, grouping, library, qualified name, description, example, qualified name of object" />
|
||
|
|
<meta name="keywords" content="object, grouping, library, qualified name, description, example, qualified name of object" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6objects.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalyoverview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="uslib.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../ifs/rzaaxkickoff.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="rbam6libraries" />
|
||
|
|
<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>Library objects</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbam6libraries"><a name="rbam6libraries"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Library objects</h1>
|
||
|
|
<div><p>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. </p>
|
||
|
|
<p>You can use libraries to group the objects into any meaningful collection.
|
||
|
|
For example, you can group objects according to security requirements, backup
|
||
|
|
requirements, or processing requirements. The amount of available disk storage
|
||
|
|
limits the number of objects that a library can contain, and the number of
|
||
|
|
libraries on the system.</p>
|
||
|
|
<p>The object grouping performed by libraries is a logical grouping. When
|
||
|
|
a library is created, you can specify into which user auxiliary storage pool
|
||
|
|
(ASP) or independent auxiliary storage pool (independent disk pool) the library
|
||
|
|
should be created. All objects created into the library are created into the
|
||
|
|
same ASP as the library. Objects in a library are not necessarily physically
|
||
|
|
adjacent to each other. The size of a library, or of any other object, is
|
||
|
|
not restricted by the amount of adjacent space available in storage. The
|
||
|
|
system finds the necessary storage for objects as they are stored in the system.</p>
|
||
|
|
<p>Most types of objects are placed in a library when they are created. The
|
||
|
|
AUT parameter on CRTLIB defines the public authority of the library. The CRTAUT
|
||
|
|
parameter specifies the default authority for objects that are created into
|
||
|
|
the library. If the command creating the object specifies <strong>*LIBCRTAUT</strong> for
|
||
|
|
the AUT parameter, the object's public authority is the create authority that
|
||
|
|
was specified for the library. You can move most object types from one library
|
||
|
|
to another, but a single object cannot be in more than one library at the
|
||
|
|
same time. When you move an object to a different library, the object is not
|
||
|
|
moved in storage. You now locate the object through the new library. You can
|
||
|
|
also rename and copy most object types from one library into another.</p>
|
||
|
|
<p>A library name can be used to provide another level of identification to
|
||
|
|
the name of an object. As described earlier, an object is identified by its
|
||
|
|
name and its type. The name of the library further qualifies the object name.
|
||
|
|
The combination of an object name and the library name is called the <em>qualified
|
||
|
|
name</em> of the object. The qualified name tells the system the name of the
|
||
|
|
object and the library it is in.</p>
|
||
|
|
<p>The following diagram shows two libraries and the qualified names of the
|
||
|
|
objects in them:</p>
|
||
|
|
<br /><img src="rbafn548.gif" alt="diagram shows two libraries and the qualified names of the objects in them" /><br /><p>Two objects with the same name and type can exist in different libraries.
|
||
|
|
Two different objects with the same name cannot exist in the same library
|
||
|
|
unless their object types differ. This design allows a program that refers
|
||
|
|
to objects by name to work with different objects (objects with the same name
|
||
|
|
but stored in different libraries) in successive runs of the program without
|
||
|
|
changing the program itself. Also, a workstation user who is creating a new
|
||
|
|
object does not need to be concerned about names used for objects in other
|
||
|
|
libraries. For example, in the following diagram, a new file named MONTHUPD
|
||
|
|
(monthly update) could be added to the library OELIB, but not to the library
|
||
|
|
ACCTLIB. The creation of the file into ACCTLIB would fail because another
|
||
|
|
object named MONTHUPD and of type file already exists in library ACCTLIB.</p>
|
||
|
|
<br /><img src="rbafn549.gif" alt="In the diagram, a new file named MONTHUPD (monthly update) could be added to the library OELIB, but not to the library ACCTLIB. The creation of the file into ACCTLIB would fail because another object named MONTHUPD and of type file already exists in library ACCTLIB" /><br /><p>An object is identified within a library by the object name and type. Many
|
||
|
|
CL commands apply only to a single object type, so the object type does not
|
||
|
|
have to be explicitly identified. For those commands that apply to many object
|
||
|
|
types, the object type must be explicitly identified.</p>
|
||
|
|
<p>Objects that use the integrated file system are located in
|
||
|
|
directories and can be found by using path names or object name patterns instead
|
||
|
|
of searching libraries. You can also use these directories to locate objects.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<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="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="uslib.htm" title="A library is an object used to group related objects and to find objects by name. Thus, a library is a directory to a group of objects.">Use libraries</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../rzaly/rzalyoverview.htm">Independent disk pools</a></div>
|
||
|
|
<div><a href="../ifs/rzaaxkickoff.htm">Integrated file systems</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|