126 lines
8.5 KiB
HTML
126 lines
8.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="task" />
|
||
|
|
<meta name="DC.Title" content="Use libraries" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.subject" content="library, grouping object, test, production, test library, production library" />
|
||
|
|
<meta name="keywords" content="library, grouping object, test, production, test library, production library" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="objec.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="crlib.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rglib.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="secur.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="defau.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="audit.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="pllib.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="dclib.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="dlnac.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="dsprtv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6libraries.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="opm.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="uslib" />
|
||
|
|
<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>Use libraries</title>
|
||
|
|
</head>
|
||
|
|
<body id="uslib"><a name="uslib"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Use libraries</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="section"> <p>You can use libraries to: </p>
|
||
|
|
<ul><li>Group certain objects for individual users. This helps you manage the
|
||
|
|
objects on your system. For example, you might place all the files that a
|
||
|
|
user JOE can use in a library JOELIB.</li>
|
||
|
|
<li>Group all objects used for an individual application. For example, you
|
||
|
|
might place all your order entry files and programs into an order entry library
|
||
|
|
DISTLIB. You need only add one library to the library list to ensure that
|
||
|
|
all your order entry files and programs are in the list. This is advantageous
|
||
|
|
if you do not want to specify a library name every time you use an order entry
|
||
|
|
file or program.</li>
|
||
|
|
<li>Ensure security. For example, you can specify which users have authority
|
||
|
|
to use the library and what they are allowed to do with the library.</li>
|
||
|
|
<li>Simplify security by having automatic authorization list and public authority
|
||
|
|
assignment for newly created objects based on the CRTAUT parameter value of
|
||
|
|
the library. Auditing attributes for newly created objects can be set based
|
||
|
|
on the Create Object Auditing (CRTOBJAUD) parameter value.</li>
|
||
|
|
<li>Simplify save/restore operations by grouping objects that are saved and
|
||
|
|
restored at the same time into the same library. You can use a <span class="cmdname">Save
|
||
|
|
Library (SAVLIB)</span> command instead of saving objects individually
|
||
|
|
using the <span class="cmdname">Save Object (SAVOBJ)</span> command.</li>
|
||
|
|
<li>Use multiple libraries for testing.</li>
|
||
|
|
<li>Use multiple production libraries. For example, you can use one production
|
||
|
|
library for source files and for the creation of objects, one for the application
|
||
|
|
programs and files, one for objects that are infrequently saved, and one for
|
||
|
|
objects that are frequently saved.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Multiple libraries make it easier to use objects. For example, you
|
||
|
|
can have two files with the same name but in different libraries so that one
|
||
|
|
can be used for testing and the other for normal processing. As long as you
|
||
|
|
do not specify the library name in your program, the file name in the program
|
||
|
|
does not have to be changed for testing or normal processing. You control
|
||
|
|
which library is used by using the library list. (Objects of the same type
|
||
|
|
can have the same names only if they are in different libraries.)</p>
|
||
|
|
<p>The
|
||
|
|
two types of libraries are production and test. A production library is for
|
||
|
|
normal processing. In debug mode, you can protect database files in production
|
||
|
|
libraries from being updated. While in debug mode, any files in test libraries
|
||
|
|
can be updated without any unique specifications.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="crlib.htm">Create a library</a></strong><br />
|
||
|
|
To create a library, use the <span class="cmdname">Create Library (CRTLIB)</span> command.
|
||
|
|
</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rglib.htm">Specify authority for libraries</a></strong><br />
|
||
|
|
Certain authorities can be given to users for libraries.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="secur.htm">Security considerations for objects</a></strong><br />
|
||
|
|
When the system accesses an object that you refer to, it checks to determine if you are authorized to use the object and to use it in the way you are requesting.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="defau.htm">Set default public authority</a></strong><br />
|
||
|
|
When objects are created in a library, the public authority for the object will, by default, be set by using the CRTAUT value of the library.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="audit.htm">Set default auditing attribute</a></strong><br />
|
||
|
|
When objects are created in a library, the auditing attribute of the object will, by default, be set by using the CRTOBJAUD value of the library.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="pllib.htm">Place objects in libraries</a></strong><br />
|
||
|
|
When you create an object, it is placed in a library.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="dclib.htm">Delete and clear libraries</a></strong><br />
|
||
|
|
When you delete a library with the <span class="cmdname">Delete Library (DLTLIB)</span> command,
|
||
|
|
you delete the objects in the library as well as the library itself. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="dlnac.htm">Display library names and contents</a></strong><br />
|
||
|
|
You can use the <span class="cmdname">Display Library (DSPLIB)</span> or <span class="cmdname">Work
|
||
|
|
with Libraries (WRKLIB)</span> command to display or print all the libraries
|
||
|
|
you have authority to and find basic information on each object within the
|
||
|
|
libraries.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="dsprtv.htm">Display and retrieve library descriptions</a></strong><br />
|
||
|
|
You can use the <span class="cmdname">Display Library Description (DSPLIBD)</span> and <span class="cmdname">Retrieve
|
||
|
|
Library Description (RTVLIBD)</span> commands to display and retrieve the
|
||
|
|
description of libraries.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <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 class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbam6libraries.htm" title="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.">Library objects</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="opm.htm" title="You can debug your OPM programs by using testing functions.">Debug OPM programs</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|