79 lines
4.7 KiB
HTML
79 lines
4.7 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="topic" />
|
||
|
<meta name="DC.Title" content="Library user disk pools" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzalyuserasp.htm" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2002, 2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002, 2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="hdrunolibusrasps" />
|
||
|
<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 user disk pools</title>
|
||
|
</head>
|
||
|
<body id="hdrunolibusrasps"><a name="hdrunolibusrasps"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Library user disk pools</h1>
|
||
|
<div><p id="hdrunolibusrasps__v5r4"><a name="hdrunolibusrasps__v5r4"><!-- --></a>Library user disk pools contain libraries and user-defined file
|
||
|
systems (UDFS). Library user disk pool steps are easier to recover than nonlibrary
|
||
|
user disk pools. </p>
|
||
|
<ul><li>Do not create system or product libraries (libraries that begin with a
|
||
|
Q or #) or folders (folders that begin with a Q) in a user disk pool. Do not
|
||
|
restore any of these libraries or folders to a user disk pool.
|
||
|
Doing so can cause unpredictable results.</li>
|
||
|
<li>Library disk pools may contain both libraries and document library objects.
|
||
|
The document library for a user disk pool is called QDOCnnnn, where <em>nnnn</em> is
|
||
|
the number of the disk pool.</li>
|
||
|
<li>Journals and objects that are being journaled must be in the same disk
|
||
|
pool. Place the journal receivers in a different disk pool. This protects
|
||
|
against the loss of both the objects and the receivers if a disk media failure
|
||
|
occurs. <p>In order to begin journaling, the journal (object type *JRN) and
|
||
|
the object to be journaled must be in the same disk pool. Use the following
|
||
|
commands to start journaling:</p>
|
||
|
<ul><li>Start Journal Physical File (STRJRNPF) command for physical files</li>
|
||
|
<li>Start Journal Access Path (STRJRNAP) command for access paths</li>
|
||
|
<li>Start Journal (STRJRN) command for integrated file system objects</li>
|
||
|
<li>Start Journal Object (STRJRNOBJ) command for other object types</li>
|
||
|
</ul>
|
||
|
<p>Journaling cannot be started again for an object that is saved and
|
||
|
then restored to a different disk pool that does not contain the journal.
|
||
|
The journal and the object must be in the same disk pool for journaling to
|
||
|
be automatically started again for the object.</p>
|
||
|
</li>
|
||
|
<li>No database network can cross disk pool boundaries. You cannot create
|
||
|
a file in one disk pool that depends on a file in a different disk pool. All
|
||
|
based-on physical files for a logical file must be in the same disk pool as
|
||
|
the logical file. The system builds access paths only for database files in
|
||
|
the same disk pool as the based-on physical file (temporary queries are not
|
||
|
limited). Access paths are never shared by files in different disk pools.
|
||
|
Record formats are not shared between different disk pools. Instead, a format
|
||
|
request is ignored and a new record format is created.</li>
|
||
|
<li>You can place an SQL collection in a user disk pool. You specify the destination
|
||
|
disk pool when you create the collection.</li>
|
||
|
<li>If the library user disk pool does not contain any database files, set
|
||
|
the destination access path recovery time for the disk pool to *NONE. This
|
||
|
might be true, for example, if the library user disk pool contains only libraries
|
||
|
for journal receivers. If you set the access path recovery time to *NONE,
|
||
|
this prevents the system from doing unnecessary work for that disk pool. <a href="../rzaki/rzakismappintro.htm">System-managed
|
||
|
access-path protection</a> describes how to set access path recovery times.</li>
|
||
|
</ul>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalyuserasp.htm">Basic disk pools</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|